Docking changed in latest version?

[kurja]

Hi all,

I've successfully docked in earlier version but can't do it after updating to .21.1; I've set the other craft's docking port as target and the ports are touching, but there's no "magnet effect" and they're not getting attached. Is there something new to docking in this version? What could be going wrong? Both ports are of the same type (jr. ports) and they're facing the "text side out" so they should just work, right?

Edited August 18, 2013 by kurja

[Johnno]

Is there something new to docking in this version?

Nope

What could be going wrong?

Could be your mod.

Or could be a bug with one of the docking ports, in your pesistance file. In which case:

Posted by kujuman

HOW TO FIX THE DOCKING PORT

1. Go into the persistent.sfs file

2. Search for a line which says "state = Acquire"

3. Change to "state = Ready"

4. Load up the game and dock with the port nearby.

[kurja]

My only mods are Kerbal Engineer redux and the one you see on the screenshot (Docking Port Alignment Indicator) which I added after getting this problem, so that I could be more certain that I'm 100% aligned for docking.

I'll try the fix you posted.

[Dortmunder]

Those docking ports look a little weird to me. Are they stock ones?

I pretty much always use the medium sized and large ones, maybe they're the small ones and that's why they look weird to me

[kurja]

Yes, they're stock Jr. type docking ports, like I said I don't have any mod parts (apart from Kerbal Engineer which uses a part).

Editing the persistence file did the trick, now they're docked!!!!

[kurja]

Any idea what causes this, is it something I did? Looks like a bug anyway, if a port's state can get changed to acquired when it's not in fact docked to anything?

[Johnno]

Any idea what causes this, is it something I did? Looks like a bug anyway, if a port's state can get changed to acquired when it's not in fact docked to anything?

No idea what the cause is, threads pop up with the issue and the fix you got is passed around. I've yet to see any way to reproduce the bug, so I don't think it was anything you did.