Kerbal Space Program

This only occurs when the docking ports are on the same vessel. For instance, I have no problem docking and undocking two different vessels with action keys. I can even mount a subassembly on a craft at design time and it will undock fine by action key in-game.

The "Same Vessel Interaction" property of "Yes/No" is also curious in that it seems to do absolutely nothing. ...or at least nothing noticeable as it relates to this specific bug. Would be helpful to know what the intention of that property setting is?

I know this has been confirmed, but I wanted to report that, even if I separately build the part and then merge it to the primary vessel or save it as a sub-assembly and add it, I'm not consistently able to use the action keys to undock it. I have a hinge with a docking port jr. to secure the hinged component. The only way I can make an action key undock is to make the docking port jr. the root part of the hinged component, add it to the main vessel from the docking port jr connection that I want to action key, and then let the other end of it connect on load-up (through a standard docking port). Then I can action key separate the docking port juniors the first time by using "decouple node" (makes sense, since the subassembly's root part is the docking port jr). After that, however, it will not consistently let go with action keys--I've tried including both decouple node and undock for both ports.

Very disappointing this still has not been addressed in 1.9.1.

Why are we not allowed to undock own-vessel ports via action group key assignment???

Any feedback or movement on this one at all?

No point in creating custom loading bays/ramps if this will never work.

Seems to be a lot more interaction with the bugtracker by squad over the last few versions.

Lets see what they do with 1.10