Docking port error spam

[smjjames]

I have absolutely no clue where this error is coming from (besides docking ports) or what mod, but for some reason, this ship, after undocking from the MKS orbital dock (MKS version of EPL orbital dock) and going out of range of the station, started spamming these two errors.

NullReferenceException: Object reference not set to an instance of an object
  at ModuleDockingNode.<SetupFSM>m__126 () [0x00000] in <filename unknown>:0 

  at KerbalFSM.FixedUpdateFSM () [0x00000] in <filename unknown>:0 

  at ModuleDockingNode.FixedUpdate () [0x00000] in <filename unknown>:0 

(Filename:  Line: -1)

NullReferenceException: Object reference not set to an instance of an object
  at ModuleDockingNode.<SetupFSM>m__134 (.KFSMState st) [0x00000] in <filename unknown>:0 

  at KerbalFSM.updateFSM (KFSMUpdateMode mode) [0x00000] in <filename unknown>:0 

  at KerbalFSM.UpdateFSM () [0x00000] in <filename unknown>:0 

  at ModuleDockingNode.Update () [0x00000] in <filename unknown>:0 

(Filename:  Line: -1)

This is an earlier instance of it happening, but it's the same ship, except in this instance, the error spam didn't start until I had gone back to KSC, went to tracking station, time warped a bit to get it out of physics loading range, and then when I went back to the ship, it started spamming the error.

Output log: http://sta.sh/01p24xx7yuq8

Not shown on there is diazos action groups extended mod.

Can someone help me save this ship?, I want to practice interplanetary colonization before 1.0 comes out.

Edited April 23, 2015 by smjjames

[smjjames]

Attempt 1: change the root part from the taurus HCV pod to the probe disk pod closer to the middle. No success.....

Edit: I realize that there is a slim chance of this getting fixed before 1.0, but any modders out there that can figure out what's going on?

Attempt2: Replaced some of the clampotron sr ports with decouplers, found that one of them seemed to have glitched a node, replaced that in case it was what's doing it, and nope..... Also crash due to unrelated OOM when I went back to KSC.

Attempt3: Removed the remaining clampotron sr ports, spawned it with EPL, went to KSC and back, nope.....

Attempt4: Removed ALL remaining docking ports, and.... no error spam. However, there was one thing that I did do differently, and that's closing the rigging arms of the orbital dock, so I'll check that. Edit: Actually, I just realized that I had left one on for attempt4, so, yeah, hopefully just closing that orbital dock fixes it.

I put it back where it was before, closed the orbital dock, built it, and that error still happens.

I'll just smash this bleeping ship into bleeping kerbin, though I still have a few more ideas maybe.

Edit: I'm going to go and build it at my Minmus base instead, tomorrow morning, I'm tired of the OOM crashes........................................................................

Edited April 23, 2015 by smjjames

[smjjames]

smjjames: that looks like a stock bug: quicksave while two docking ports are in "aquire" mode (magnets engaged) and load, you will get the error. The fix is to find the docking port in the sfs and change Aquire to Ready.

So, yeah, stock bug apparently and it's fixed now.

[BARCLONE]

So, yeah, stock bug apparently and it's fixed now.

Uhh, nope. The problem still exists in 1.0.2...

Logfile Linky

Don't know if this is a stock issue, or a MKS issue. The ship in question is a lander using a couple of MKS base modules and four MKS docking ports.

[smjjames]

By 'fixed now' I meant that it's 'fixed now in my game'.

Did you try the solution that I posted above?