Flight Camera Null Reference Exception

[Sirius K]

[EXC 14:10:13.949] NullReferenceException
    UnityEngine.Transform.get_position () (at <5aeafee3fea24f37abd1315553f2cfa6>:0)
    FlightCamera.UpdateCameraTransform () (at <c1858a3f77504bd1aaa946fdccf84670>:0)
    FlightCamera.LateUpdate () (at <c1858a3f77504bd1aaa946fdccf84670>:0)
    UnityEngine.DebugLogHandler:LogException(Exception, Object)
    ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object)

This is what I frequently encounter now, a flight camera error. First, I was just going to change some flags on a part via save file editing. Then when I load up the save THIS BLOODY loveING THING KEEPS SHOWING UP. And then KSP crashes. Then I use bon vonyage to plot a rover to go to the highlands near the KSC. But Bon Voyage always things up at destination so i reload the save, a quick save that i have load before that I didn't touch or edit anything. AND THIS SAME loveER COMES BACK AGAIN. FIX THIS BUG PLEASE.

There's no mode affecting camera in my mod list, just visual mods, readout mods, dock rotate, better time warp and bon voyage

Edited October 27, 2020 by Vanamonde
Mind the language, please.

[Snark]

17 hours ago, Sirius K said:

There's no mode affecting camera in my mod list, just visual mods, readout mods, dock rotate, better time warp and bon voyage

It can be hard to know what a mod does or doesn't touch, if you're the author. For example, I would not be at all surprised if a visual mod affects the camera in some way at the code level, even if it's not obvious to the player.

Since this is affecting you, but appears not to be affecting all the players in stock games, there's a reasonable chance that some mod might be causing your problem.

So, that would be the first thing you'd need to diagnose, before anyone could help you.  Is it a mod causing this, and if so, which one?

 

Have you tried running a stock game without the mods and see if you can still reproduce the problem? If you can't (i.e. if it only happens with your mods installed), then the next thing you'd need to do is to narrow it down to which one might be the problem.

[Sirius K]

7 hours ago, Snark said:

It can be hard to know what a mod does or doesn't touch, if you're the author. For example, I would not be at all surprised if a visual mod affects the camera in some way at the code level, even if it's not obvious to the player.

Since this is affecting you, but appears not to be affecting all the players in stock games, there's a reasonable chance that some mod might be causing your problem.

So, that would be the first thing you'd need to diagnose, before anyone could help you.  Is it a mod causing this, and if so, which one?

 

Have you tried running a stock game without the mods and see if you can still reproduce the problem? If you can't (i.e. if it only happens with your mods installed), then the next thing you'd need to do is to narrow it down to which one might be the problem.

The first time I encounter something similar to this error is when i started merging saves, during Upsilon time. I copied the vessel but not the Kerbals and it resulted in something similar to what I encounter. And before Upsilon I played stock for most of the time, and still haven't encounter this error when I have more mods added. It only starts to appear when I save file editing. The only thing I can link to is save file editing, and maybe TUFX (since it was the most recent mod I have) or Editor Extension (that mod also causes null reference when I delete symmetry). 

 I've only edit save files for Savefile merging, Kerbal name changing, part flag changing, Part adding (if i forgot an essential part), part deleting, Reattaching parts (docking port bug of unable to decouple node), editing part location and editing part location.

[Snark]

4 hours ago, Sirius K said:

 I've only edit save files for Savefile merging, Kerbal name changing, part flag changing, Part adding (if i forgot an essential part), part deleting, Reattaching parts (docking port bug of unable to decouple node), editing part location and editing part location.

If you've been manually editing save files, then almost certainly what's happened is that you horked something and corrupted the save.

With a corrupted save file, all bets are off what the program will do. That's not a bug; it isn't the program's fault that broken input causes it to break, any more than it would be your car's fault for having mechanical problems if you put apple juice into the gas tank. It's not designed for that.

If you revert to a "clean" version of your save from before you edited it, does that resolve the problem?

[Sirius K]

4 hours ago, Snark said:

If you've been manually editing save files, then almost certainly what's happened is that you horked something and corrupted the save.

With a corrupted save file, all bets are off what the program will do. That's not a bug; it isn't the program's fault that broken input causes it to break, any more than it would be your car's fault for having mechanical problems if you put apple juice into the gas tank. It's not designed for that.

If you revert to a "clean" version of your save from before you edited it, does that resolve the problem?

But during one of my Save, I only change the parts flag. And restarting KSP then reloading the same save that has the error before, will work nicely. 

Also, what about the Bon Voyage time where I didn't file edit at all?

[Snark]

6 hours ago, Sirius K said:

But during one of my Save, I only change the parts flag. And restarting KSP then reloading the same save that has the error before, will work nicely. 

Also, what about the Bon Voyage time where I didn't file edit at all?

Still having a bit of trouble following exactly what you've done in which order, but basically the diagnostic sequence goes like this:

1. Getting an error upon loading a save that you manually edited?
   • If so, assume that it's your edit that's causing the problem.  Revert to a clean copy of the save that you didn't edit.
   • If you get the error even when it's a "clean" save that you haven't edited, continue below.
2. Getting an error when you're running any mods?
   • If so, assume that it's likely the source of the error.  Try running without the mod and see if you can still reproduce the problem.
   • If it reproduces only when you're running the mod... then that's likely the culprit.  Go ask your question in the release thread for that mod.
   • If it reproduces even when you're not running any mods... then continue below.
3. If you're getting the error on a clean, pure stock game-- where you're using a clean save you've never edited, and no mods are running-- then you have a legitimate tech-support issue and this tech support sub-forum is the right place to be asking.

Which of the above cases are you running into?  More to the point:  Have you, or have you not, gotten this error when you're running completely unmodded on a clean save that you haven't edited?