Kerbal Space Program

Update: I am absolutely sure there are no engines turned on, I did a little test decoupling everything (that's what I still can do though, I can't steer nevertheless), making sure I had electric charge, and somehow I magicly had an acceleration of about 10ms^2, completely ruining my orbit.
It has now become completely impossible to play KSP in a normal way, so for the love of god, help me fix this.

I tried to reproduce it as you describe but no success. My ships are behaving regardless whether there is a maneuver or not, physical warp or on-rails warp.

Are you sure your MechJeb is up to date?

Does it happen to you on new save after you have restarted the game?

You may be better off taking this to the forums first and posting craft files, logs, pictures, etc. Also, try creating a second, completely mod free version and see if you can recreate.

I am seeing what appears to be this bug on stock KSP 23.5.464 on OSX Mavericks. This is also a game ruining bug for me. I don't have a simple set of steps to duplicate, as it is also intermittent for me, however; it has occurred on about 4 of my first 7 missions in career mode. It has happened for me when I am doing my orbital insertion burn at apoapsis and has also occurred during my trans-minimus injection burn. I set a node for burn, burn until I run out of fuel, quickly jump back and forth between the map mode and std view. Then, while in map mode I try to Time-Warp (period), it says "Cannot ... while throttled up", switch to std mode, press X to go to zero throttle, jump back to map mode, press Time-Warp (period) it says "Cannot ... while under acceleration".

• I cannot adjust my attitude with reaction wheels
• Instruments seem to show a constant .25 - .5 G acceleration (if I'm reading it right)
• Orbit is changing , slowly, and seems to be in the direction that the capsule was pointing when it entered this state.
• Acceleration is constant, and does not change direction even while the capsule progresses through the orbital path.

During the first round of career mode I built what "looks" like an asparagus staged rocket. Central stack is, LV-30, 5 * FT-200, Capsule, Parachute, surrounded by 4 stacks of LV-30, 5 * FT-200, parachute. Staging is all 5 engines in stage 1, all 5 parachutes in stage 0. No action groups, the LV-30, 5 * FT-200 in the outer stacks were constructed from a saved subassembly with quad symmetry and snap on.

If I were a newbie starting out, I would have had no idea this was a bug, and been frustrated enough to stop playing the game. It has driven me to create an account just so I could let you know.

I hit the bug again... additional info if it helps ... While running out of fuel on the trans-minimus burn, I hit the bug again .. I dropped the stage and was able to activate the engine on the next stage. (lv30, FT-400, capsule, parachute)

• Still no control
• Orbital velocity is frozen, surface velocity is increasing at a steady .2 m/s/s (still in Kerbin SOI)
• I can throttle up and down, and consume fuel, but orbital velocity is still fixed, and surface velocity steadily increasing
• Going to the space center then back to "fly" the current mission seems to have freed me from the bad-state. Engines are effective, and I have regained control
• Interesting note, trying to go to the space center previously (earlier missions) prompted me about losing everything to the last save prior to the acceleration.

Ted wrote:

Thanks for the info, KSP-JG, that's very helpful.
Hmm, does this issue occur when coming out of warp at all? Or is it seemingly random in the events that take place before it?

I experienced this problem and was as wits end trying to figure it out. I mean, I'd been playing for months and all of a sudden this starts happening? To every ship, every time I warp towards a maneuver node?

To make a long story short, I noticed that there were 128 mechjeb ship config files in C:\Program Files\Steam\steamapps\common\Kerbal Space Program\GameData\MechJeb2\Plugins\PluginData\MechJeb2. 128 being a suspicious number, I deleted them all.

Poof. Problem gone.