You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I really want to use Kethane, but it seems to be bust for me.
I have built Kethane probes for the Mun, Minmus, and Kerbal, and they all work (don't work) the same way. There is no overlay grid, no beeping or booping noises as the scanner scans, no indication that anything is wrong. I didn't get any sort of module warning. However, there are failures in the log file that specifically mention Kethan.
I downloaded Kethan a second time, and loaded it to the GameData folder. Same result.
I WAS able to use the Kethane tutorial just fine. The grid appeared (or not, as I directed with the Kethane tool bar). It scanned, and beeped / booped for scans and Kethane. However outside of the tutorial it doesn't seem to work at all.
I'm assuming that there is a module conflict, but I have so many modules I really don't know which it would be. Perhaps my data will be of use? I'm trying to find a module conflict now.
CPU Intel Core i7-3770 3.4GHz Quad-Core
Motherboard ASRock Z75 Pro3 ATX LGA1155
Memory G.Skill Ares Series 16GB (4 x 4GB) DDR3-1600
Storage Samsung 840 Pro Series 128GB 2.5" SSD
Video Card MSI GeForce GTX 760 2GB TWIN FROZR
Operating System Microsoft Windows 7 Home Premium SP1 (OEM) (64-bit)
It looks like the vessel is being set to null somehow. There are a ton of exceptions in your log from various mods, including SCANsat suffering from the same null-vessel issue as Kethane. You should investigate your log and tackle the mods throwing the earliest exceptions. (TarsierSpaceTech is one, for example.)
My programming experience is limited to ANSI C in embedded systems and to Verilog. I'm not used to reading error logs, and am trying to get the hang of it.
So I really want to use Kethane, but it seems to be bust for me.
I have built Kethane probes for the Mun, Minmus, and Kerbal, and they all work (don't work) the same way. There is no overlay grid, no beeping or booping noises as the scanner scans, no indication that anything is wrong. I didn't get any sort of module warning. However, there are failures in the log file that specifically mention Kethan.
I downloaded Kethan a second time, and loaded it to the GameData folder. Same result.
I WAS able to use the Kethane tutorial just fine. The grid appeared (or not, as I directed with the Kethane tool bar). It scanned, and beeped / booped for scans and Kethane. However outside of the tutorial it doesn't seem to work at all.
I'm assuming that there is a module conflict, but I have so many modules I really don't know which it would be. Perhaps my data will be of use? I'm trying to find a module conflict now.
Here's a link to the log file:
https://drive.google.com/file/d/0B8mKTsimtARwNlBiQnZ5ajByazA/view?usp=sharing
Here's a link to images as it is being used:
http://imgur.com/a/TYUoe
My system hardware / software:
CPU Intel Core i7-3770 3.4GHz Quad-Core
Motherboard ASRock Z75 Pro3 ATX LGA1155
Memory G.Skill Ares Series 16GB (4 x 4GB) DDR3-1600
Storage Samsung 840 Pro Series 128GB 2.5" SSD
Video Card MSI GeForce GTX 760 2GB TWIN FROZR
Operating System Microsoft Windows 7 Home Premium SP1 (OEM) (64-bit)
The mods I'm using are:
000_Toolbar
ActiveTextureManagement
AviationLights
B9_Aerospace
B9_Aerospace_DEPRECATED
BoulderCo
Chatterer
ConnectedLivingSpace
CrossFeedEnabler
DMagic Orbital Science
EditorExtensions
EnhancedNavBall
EnvironmentalVisualEnhancements
ExsurgentEngineering
Firespitter
HabitatPack
JSI
KAS
Keramzit
KerbalJointReinforcement
Kerbaltek
Kethane
KineTechAnimation
Klockheed_Martian
KSPLua
KWRocketry
MagicSmokeIndustries
MechJeb2
MP_Nazari
NASAmission
NavyFish
NEAR
PartCatalog
ProceduralFairings
ResGen
ResourceConverter
Robau
SCANsat
SelectRoot
SmokeScreen
Squad
StationScience
TarsierSpaceTech
ThrottleControlledAvionics
ThunderAerospace
TweakScale
US_Core
US_KAS
Virgin Kalactic
112 B9GearFix.cfg
42,496 ModuleManager.2.4.4.dll
3,181 toolbar-settings.dat
The text was updated successfully, but these errors were encountered: