Not thrusting during part of an escape orbit.

[Rune]

So, this is a weird one. A really weird one, so I am looking for pointers. See, some of you might have seen this pic I posted yesterday of me, moving a big potato with lots of patience:

And it all went well, until about when I crossed Mun's orbit: the [censored] won't keep thrusting! I mean, I get the engine effects, I get the consumable drain, I get the torque, all indicators including KER show thrust... (yeah, I know, technically non-stock, but please tell me how that mod can mess with the orbital physics). And yet, the freaking maneuver node shows no change in velocity happening. It seems as if the acceleration was too low to register, or something. So I started experimenting, and ended up redoing the whole capture burn again from periapsis... same thing happened, suddenly I couldn't move the maneuver any further and the dV readout "froze". Interestingly enough, at high levels of phsyical timewarp, the thing seems to accelerate, but the whole thing becomes so wonky it's difficult to say whether it is the usual wonky orbits of oscillating vehicles due to CoM changes, or actual sustained thrust, before you start spinning.

The only thing I can think of, is that this is somehow related to the coordinate system, where I have crossed some boundary where my coordinate changes between timesteps is just the right amount for my acceleration to be ignored as an error or rounded out or something. Because you see, as soon as I let it escape into solar orbit, I again can see progress in the maneuver burns. And when I was thrusting close to periapsis, the same thing. The dev console shows no weird stuff happening (or no weirder than usual). I'm at my wit's end, and I might just lose 10+ hours of gameplay spent in building and flying this mission. So I need your help smart guys! You can take a stab at replicating by loading this savefile, you don't really need any mods since this ship has no modded parts, just a bunch of vessels will puff out of existence when you load. It's a quicksave, and excuse my colorful language when naming bug-hunting saves:

http://www./download/485pcw7zfkvkmz1/....sfs

It's set up so you just have to load it from the quicksave menu, and start thrusting and see if that maneuver node goes down. Acceleration should be visible in a short time, I was making 0.015m/s² without issues even with the nuke throttled down to keep up with the refinery output, and that is 0.1 m/s in less than ten seconds, so you will know quickly if things go as wrong as they go for me, every time. Even if you just tell me that maneuver node goes down for you, it would still be a great help, means there is something wrong on my end and I can stop throwing swear words at the game and direct them at myself instead. Thanks for your time in any case!

Rune. Honestly, I am this close to calling "bugs" and installing hyperedit for the first time in three years. It's that frustrating.

[Majorjim!]

Hi Rune. Have you tried editing the nukes stats? Upping the thrust in increments. It may tell you if it's that rounded out issue you mentioned. If so then its just a current game limitation that can be overcome or circumvented.

It's an easy file edit and even easier to undo. Can't hurt.

Edited September 25, 2015 by Majorjim

[Vanamonde]

Please provide the usual stuff.

Also, moved to modded support.

[Rune]

Please provide the usual stuff.

Also, moved to modded support.

What "usual stuff"? There is a savegame there to replicate it, set up focused on the affected ship and everything. There is no log, since there is no crash. If you need the clarification, it is KSP 1.04 running in a windows machine, as the thread name implies.

Also, I have replicated it in a stock install just now, so are you going to move it back? I told you it wasn't mod-related.

Rune. Then again, I can copy-paste the thread, again, in its correct forum, if you prefer that.

- - - Updated - - -

are you going to move it back?

I'll take the resounding silence as a no. Notice I did give you more time than you did me, and 100% more notice, before re-posting. We'll see what happens.

Edited September 25, 2015 by Rune