Editor bug with fairings

[Vindelle_Sunveam]

Hello, I do not know if this is a known bug, but I've been able to reproduce it consistently.

I use a octagonal probe core, put a 1.25m fairing on top of it, upside down, and right click.

Then, I stack a girder segment underneath the probe core (the girder that's unlocked from the beginning of the game) and strap a mystery goo experiment on the side of it.

After that, I place a 1.25m fairing at the base of the contraption, and make the fairing go to the other fairing base (like an interstage).

From this point, I just have to grab the girger segment, put it back right where it was, and I cannot move any part in the VAB anymore. I cannot add any from the side menu either, but I can still right click on the objects and animate them, edit and delete fairings.

Quitting and reentering the VAB does not solve the problem.

In the debug console, there is this message that appears right after the statement of what have been done.

[Exception]: InvalidOperationException: Operation is not valid due to the current state of the object

It can appear just after the generation of a fairings drag cube, or just after the update of the part count.

Edited May 27, 2015 by Vindelle_Sunveam

[misterbk]

Getting the exact same bug myself, and the exact same InvalidOperationException in KSP.log.

[LOG 22:00:57.511] ---DockingAsDecoupler  : 2
 [LOG 22:01:05.794] fuelTank2-2 added to ship - part count: 104
 [EXC 22:01:05.799] InvalidOperationException: Operation is not valid due to the current state of the object
         System.Linq.Enumerable.Last[FairingXSection] (IEnumerable`1 source)
         ModuleProceduralFairing+.MoveNext ()
         UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
         ModuleProceduralFairing:scheduleReconnect()
         ModuleProceduralFairing:<SetupEditorFSM>m__19B()
         KerbalFSM:RunEvent(KFSMEvent)
         ModuleProceduralFairing:onInterstageReattach()
         Part:onAttach(Part, Boolean)
         EditorLogic:attachPart(Part, )
         EditorLogic:<SetupFSM>m__CD()
         KerbalFSM:RunEvent(KFSMEvent)
         KerbalFSM:updateFSM(KFSMUpdateMode)
         KerbalFSM:UpdateFSM()
         EditorLogic:Update()

This has been happening a lot. I'm having to restart KSP 10 or 20 times to successfully finish any rocket that involves fairings.

[sal_vager]

You don't need fairings both ends, just one is enough, it can be closed around some other part such as a decoupler instead.

[Vindelle_Sunveam]

Thanks for the answer, flagging as solved until further issues (let's hope not)

[Gristle]

Seeing similar error with same VAB symptoms. Using on fairing and up to LEM. After clicking close cannot select parts either on ship or in toolbox. Has nothing to do with 2 fairings.

fairingSize1 added to ship - part count: 53

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

InvalidOperationException: Operation is not valid due to the current state of the object
  at System.Linq.Enumerable.Last[FairingXSection] (IEnumerable`1 source) [0x00000] in <filename unknown>:0 

  at ModuleProceduralFairing+.MoveNext () [0x00000] in <filename unknown>:0 
UnityEngine.MonoBehaviour:StartCoroutine_Auto(IEnumerator)
UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
ModuleProceduralFairing:scheduleReconnect()
ModuleProceduralFairing:<SetupEditorFSM>m__19B()
KerbalFSM:RunEvent(KFSMEvent)
ModuleProceduralFairing:onSelfReattach()
Part:onAttach(Part, Boolean)
EditorLogic:attachPart(Part, )
EditorLogic:<SetupFSM>m__CD()
KerbalFSM:RunEvent(KFSMEvent)
KerbalFSM:updateFSM(KFSMUpdateMode)
KerbalFSM:UpdateFSM()
EditorLogic:Update()

(Filename:  Line: -1)

[Theriss]

I just today got the nest version (I was still on 0.90) and of course immediately tried using the fairings, and immediately got the same bug. I attached and closed a fairing in the VAB, then I couldn't edit any parts. I could still flip through the part lists or right click existing parts, but I couldn't move or place new. Has anyone found a way to fix this? 

[sal_vager]

Hi Theriss, when this happens open the debug window with alt+F2 and check for errors, also, upload the output_log.txt from the KSP_Data folder somewhere and post the link to it so we can see what's going on.

[Theriss]

Sorry I didn't include that, but my computer isn't hooked up to the Internet right now, so I can't upload a file quite so easily... I'll copy what I can by hand, but I apologize it's not ideal. 

When I hit alt+f12, the debug says "[Exception] InvalidOperationException: Operation is not valid due to the current state of the object"

In the output log, I found where it says the same thing, followed by:

at System.Linq.Enumerable.Last[FairingXSection] (IEnumerable`1 source) [0x00000] in <filename unknown>:0

at ModuleProceduralFairing+|□.Movement () [0x00000] in <filename unknown>:0

The "|□" in the second line are symbols I can't recreate on my phone. First one is a double ended arrow, pointing up and down. 

It bears noting that this happens after grabbing and placing the fairing a couple times. Sometimes after only a couple times, sometimes after several. 

Looking again, the section of my output log is exactly the same as in Gristle's post above, except for slightly different values after "SetupFSM"

Again, I'm so sorry that I can't conveniently upload the files for you to look at. I hope this was able to give you enough information anyway. 

[sal_vager]

Okay, there is an input lock when building a fairing, and the steps above can cause it to engage but not be cleared.

Just open the debug window with alt and F12, click on the input lock stack and click the button to clear it.

You'll be able to pick up parts again after that.