rendezvous bug?

[TheTranceMan]

being adept at orbital rendezvous and docking, i typically approach my target "hot" and execute what would be described as a hard burn to match velocity at close range.

when playing a rescue contract, every single time my craft approaches the stranded kerbalnaut, the SAS, RCS, and throttle all go dead; they either turn themselves off or the throttle is killed. this completely screws my rendezvous and i'm finding this behavior beyond frustrating. is this a bug, or is this just the way KSP works from now on?

Edited July 24, 2014 by TheTranceMan

[sal_vager]

It's a bug, it's not meant to happen.

I've informed the devs, all we can do now is cross our fingers.

[Russoft]

I'm pretty sure it's a bug. It's new to .24. It just happened to me this morning. As I usually make rendezvous at moderate speeds it didn't mess up my approach too badly but I believe I was 200 meters out from the stranded kerbal when it happened.

[Alshain]

It's a known issue which presumable will be fixed in the next patch (since it's kinda bad). It happens whenever you get close to any other craft at all (the Kerbal is a craft) and it copys the throttle, brakes, and SAS settings from the other craft to the active one.

[TheTranceMan]

thx guys

It's a known issue which presumable will be fixed in the next patch (since it's kinda bad). It happens whenever you get close to any other craft at all (the Kerbal is a craft) and it copys the throttle, brakes, and SAS settings from the other craft to the active one.

that makes sense; earlier i docked with a station in orbit (it had both SAS and RCS active) and i did not encounter any anomaly.

[Skorpychan]

It's a known issue which presumable will be fixed in the next patch (since it's kinda bad).

Or, more likely, when they figure out what's wrong and how to fix it, they'll release an update.

Because, this being beta, even the bugfixes need bugfixes. At least it's not as bad as Dwarf Fortress and the random unforseen crap THAT throws up.

[Russoft]

The issue just got patched with .24.1. I was testing the fix when my power went out, so I can't say first-hand that everything is fixed.