dymanoid

This is already fixed. The fix will be available with the next release.

I have lots of exceptions in the KSP.log file: NullReferenceException: Object reference not set to an instance of an object KERBALISM.Habitat.UpdateCrew (HostedFromToAction`2 dat) EventData`1[GameEvents+HostedFromToAction`2[ProtoCrewMember,Part]].Fire (HostedFromToAction`2 data) UnityEngine.Debug:LogException(Exception) EventData`1:Fire(HostedFromToAction`2) CrewTransfer:MoveCrewTo(Part) CrewTransfer:OnPartSelect(Part) PartSelector:LateUpdate() Seems that this occurs when transferring kerbals from one part of a vessel to another. I also see a message "transfer aborted" in the game, but kerbals are transferred anyway. There are same NREs but triggered from another place: NullReferenceException: Object reference not set to an instance of an object KERBALISM.Habitat.UpdateCrew (HostedFromToAction`2 dat) EventData`1[GameEvents+HostedFromToAction`2[ProtoCrewMember,Part]].Fire (HostedFromToAction`2 data) UnityEngine.Debug:LogException(Exception) EventData`1:Fire(HostedFromToAction`2) FlightEVA:onGoForEVA() FlightEVA:spawnEVA(ProtoCrewMember, Part, Transform, Boolean) FlightEVA:SpawnEVA(Kerbal) KSP.UI.Screens.Flight.KerbalPortrait:ClickEVA() UnityEngine.EventSystems.EventSystem:Update() And: NullReferenceException: Object reference not set to an instance of an object KERBALISM.Habitat.UpdateCrew (HostedFromToAction`2 dat) EventData`1[GameEvents+HostedFromToAction`2[ProtoCrewMember,Part]].Fire (HostedFromToAction`2 data) UnityEngine.Debug:LogException(Exception) EventData`1:Fire(HostedFromToAction`2) KerbalEVA:proceedAndBoard(Part) KerbalEVA:BoardPart(Part) KerbalEVA:<SetupFSM>m__32() KerbalFSM:RunEvent(KFSMEvent) KerbalFSM:updateFSM(KFSMUpdateMode) KerbalFSM:UpdateFSM() KerbalEVA:Update() The last one caused my kerbal to "not completely enter" a vessel, so the game then went mad: no staging UI anymore, no MechJeb UI, ComNet status panel showing multiple symbols with "No text" tool-tips etc. I had to restart the game. Could you please check whether there's an issue in Kerbalism?

A question about the rescue missions - those where we need to rescue kerbals from debris in orbits. On rendezvous, I first get a bunch of Kerbalism's messages "no oxygen, no food, no water" etc. I suppose it's because the found debris is initially "empty". Then, I get a bunch of messages "oxygen OK, food OK, water OK" etc. Seems like Kerbalism fills up the debris with resources needed. But there's a very strange thing (bug?) happening with monoprop & kerbal's jetpack. When the kerbal being rescued exits the debris, Kerbalism warns "do not let go the ladder". When I check the kerbal stats, monoprop is full (5.0). The monoprop in the debris is also full. But the jetpack doesn't work! So it is almost impossible to rescue the kerbal without the debris. Is this intentional? Or is it maybe a bug caused by some mod incompatibility? I use the latest game v1.5 and the latest Kerbalism (via CKAN), and also a couple of other mods (like Chatterer and MechJeb). I see no errors in KSP.log.

Yes, already in progress. Deleting all the mods and running with Kerbalism only helped. So there's something not compatible with Kerbalism, or Kerbalism is not compatible with something. That's really strange - no related errors in the log file.

Just tried it out. Still the same... Maybe there's a conflict with some other mod? A have a couple of them: Does anyone observe the same weird behavior? My Kerbalism windows don't show up, and trying to open any window breaks the mouse wheel zooming.

Just downloaded and tried the build #100. I have the same issues some other users posted above even with this build: the Kerbalism windows don't show up (e.g. Data or Configure Pod, the list of vessels etc.), and zooming with the mouse wheel stops working after trying to open a Kerbalism window. Any thoughts? Do you need my log file?