Macel

[quote name='komodo']I hadn't noticed it performance wise (Don't shoot me) but just as a matter of course, habit from running on OS X to have a tail -f log running on second screen, to see when its going to crash. I haven't seen this one before though, and its on linux x64 besides. It has to be an addon, but i've not had a chance to run down which one. I'm not at home at the moment, but i'll try to upload a list next time i'm able. (Plus the log, for that matter). Perhaps we can determine between us what common mod might be amiss.[/QUOTE] It was doing this with no mods installed at all. I reported the bug to squad. Workaround is to run ksp.exe with the -nolog option

... And I was able to resolve the issue by disabling logging. Turns out the exception itself isn't slowing the simulation down, it's the act of logging it to the file hundreds of times a second.. See if your performance improves by running your KSP.exe with the -nolog option.

Well, I uninstalled all mods from my game and I am still getting spammed with this in my logs when I switch to a ship in orbit in my career 266631 [EXC 22:47:57.844] NullReferenceException: Object reference not set to an instance of an object 266632 Vessel.<GetUnloadedVesselMass>m__477 (.ProtoPartResourceSnapshot x) 266633 System.Linq.Enumerable+<Sum>c__AnonStorey3A`1[ProtoPartResourceSnapshot].<>m__74 (Single a, .ProtoPartResourceSnapshot b) 266634 System.Linq.Enumerable.Sum[ProtoPartResourceSnapshot,Single] (IEnumerable`1 source, System.Func`3 selector) 266635 System.Linq.Enumerable.Sum[ProtoPartResourceSnapshot] (IEnumerable`1 source, System.Func`2 selector) 266636 Vessel.GetUnloadedVesselMass () 266637 Vessel.GetTotalMass () 266638 Vessel.CalculatePhysicsStats () 266639 Vessel.FixedUpdate () [COLOR="silver"][SIZE=1]- - - Updated - - -[/SIZE][/COLOR] Messing around with it some more.. My career mode game has a ton of space junk floating around because I tend to be messy and don't deorbit things... I tested setting the max persistent debris down to 25 and loaded up the same piece of floating debris I was previously getting spammed in the log file with.. The game performed noticeably better.. I was still getting hit in the log file with that null ref exception but not nearly as often. I think the null ref gets spammed exponentially more often with more craft in orbit and causes serious slowdown for games with large numbers of ships/debris/etc... I can't say for 100% certain if its specific to my career mode but its looking like its a bug with the core game, not mod-related at this point...

I am getting this exact message spammed in my ksp.log ... It's some mod but I'm not sure which one... Trying to find that out...

To expand on my prior post... After further testing, it appears to have started when I uninstalled CH Control Manager to troubleshoot another issue. This caused my throttle to be renamed from "Control Manager Device 00" or similar to CH PRO THROTTLE USB when mapping it. I deleted the settings and ran a vanilla installation of KSP 1.04 ... I proceeded to map one control at a time and noted that binding axes on my T.16000M worked fine. As soon as I tried to bind the throttle axis on CH PRO THROTTLE USB, the issue would reoccur and I would have to delete the settings file (or, I suspect, clear out the binding in the file). I was able to get around the issue by installing VJoy and UJR so that the throttle axis would bind to a different device name. In any case, I confirmed this issue is not at all mod related and perhaps this thread should be moved to the unmodded support forum... Or perhaps a new issue for this should be created there.

I've had this issue too, and I can confirm that after removing all mods I could reproduce the problem. I started experiencing the issue when I tried to plug in a set of CH pedals to complement my CH throttle and Thrustmaster T.16000M stick

Hey, sorry to bother.. I just had my first mistake with not equipping enough supplies using USI life support and noticed that, despite having the -crew lost- message, I still had control of the ship. Is this a known issue or caused by conflict with another mod that anyone knows about?

Murdabenne - Is there a way we can force install mods via CKAN even if marked incompatible when this situation arises? I know I could just manually copy the mod folder in but I like managing everything thru CKAN. The other issue I've run into though is that KSP reports the mod as incompatible when I load it. Does this prevent the mod from loading? Or is it just a warning?