stuck docking ports

[Laie]

First off: Claw, that guide is priceless, thanks! (http://forum.kerbalspaceprogram.com/threads/78863-FIX-Dock-Undocking-Bug-in-0-23-5)

However... after fixing it, I immediately ran into the same problem with the next port I wanted to undock. It's my Jool-5 mission, and using multi-node docking, I've got like 50 ports. On closer inspection, almost all of my docking ports lack a top attachment (and it's not as if they'd all be pointing into space). The prospect of fixing the whole mess doesn't look too inviting. Then again, assembling the mission and sending it on its way took like two days -- doing that all over again also lacks appeal. The more so because I completed some other mission in the time since.

Question1: once I fixed it, will it stay fixed? Or will I have to go through this again and again?

Question2: what is the root cause of the problem? Is there anything that I could have done to avoid it altogether?

[Sirrobert]

I don't know anything about the bug, but if you don't want to go through manually editing each port, maybe there is an alternative.

First, rebuild the craft (this time without the bug) in the VAB. Launch, and than quicksave (while it's still on the launchpad).

Now editting the save file, swap the orbitall characteristics of the 2 crafts (bugged and fixed version). Than quickload this.

This will (if you did it right) swap the 2 crafts. So now you have the fixed rocket in space, and you can recover the broken one

[Taki117]

First off: Claw, that guide is priceless, thanks! (http://forum.kerbalspaceprogram.com/threads/78863-FIX-Dock-Undocking-Bug-in-0-23-5)

Question1: once I fixed it, will it stay fixed? Or will I have to go through this again and again?

Question2: what is the root cause of the problem? Is there anything that I could have done to avoid it altogether?

Once fixed it will stay fixed, no more editing required. The root cause, near as I can tell, is that KSP doesn't recognize the two ships as being docked, there really is no way to avoid it, though in my multitude of hours played I have only had this bug once.

[Laie]

Quick&dirty hack: I edited ports on that vessel to undock/decouple on abort. Disassembly by backspace, reassembly by saveload -- that fixed all ports but two. The latter had to be dealt with in the old-fashioned way.

Hint: "control from" a port makes those ports easy to identify. Much easier than the crossfeed thing, IMO.

		VESSEL
		{
			pid = 9c935094b4a74b96bfc41736667cb0e1
			name = Jool-5                   ship name, search for that first
                        ...                                    (about 20 lines)
			ref = 2057798780             this is the UID of the controlling part (in this case, the stuck port)

[Claw]

Question1: once I fixed it, will it stay fixed? Or will I have to go through this again and again?

Question2: what is the root cause of the problem? Is there anything that I could have done to avoid it altogether?

As far as I can tell, once it's fixed it will stay that way.

I can't tell what actually causes the problem. I'm sure there is some sequence of events that causes it, but it seems completely random. I rarely encounter it (maybe like once), but others seem to be stricken with it a lot.

Also, thanks for the "control from here" tip. That certainly sounds MUCH easier than the x-feed option.

Cheers,

~Claw