Navball node marker runs away...

[eddiew]

OS: Win 7 64-bit

KSP: 0.90 32-bit

Mods: more than a few... none of them seem relevant to the problem though.

Ok, this one is really odd and really specific and I'm getting desperate Sometimes - but not always - around Duna, if I set a node, aim at the marker on my navball, and timewarp x5 or more, the marker will side away.

This doesn't happen in other scenarios, which is a warning sign, but it's also hiding a bigger problem; when executing the node, getting down towards the last few m/s, the marker will run away and end up radially outwards from the planet. No amount of thrust in this direction will change it to being completed. Following it blindly for a 'circularisation' will instead crash you into the far side of the planet as you chase the bugged node until your PE is below zero.

If the node is for a rendezvous, it behaves very oddly. This kind of marker will also try to run away at the end, but if you bail out when you have an intercept of, say, 2km separation, then timewarp forward; you won't have an intercept by the time the ships get there. Putting the navball in target mode when 'anywhere close' can sometimes show a relative velocity towards the target, or of zero, even while the distance shown is rapidly increasing!

This most commonly happens to me during Kerbal Construction Time simulations, but I have had it in a totally different playthrough, using totally different ships that I'd HyperEdited out to Duna.

I can guarantee that the problem is not:

- Asymmetrical or clipped ships causing phantom forces. I have tried multiple ships, some of them super-simple and HyperEdited out to Duna orbit, all of them have the problem. Sometimes.

- Rookie stupidity. Honestly, I can manoeuvre and rendezvous just fine around Kerbin/Mun/Minmus. Duna on the other hand is in some kind of time-distortion and things aren't where they should be.

I'm completely at a loss as to how to solve this one. I'm at the point of ripping all my mods out and putting them back half at a time, but I've already lost half my weekend to it and not found the culprit

Anyone maybe heard of / had a similar problem and knows the cause / fix? ^^;

[eddiew]

Following up my own post, this turned out to be probably an issue with Kerbal Construction Time.

I've raised the matter with Magico13 and any further follow up on the matter can be found here: http://forum.kerbalspaceprogram.com/threads/69310-Kerbal-Construction-Time-Dev-Thread?p=1665185&viewfull=1#post1665185