Did it not used to be possible to undock via either of two docking ports?

[THX1138]

I thought it used to be possible to undock from the context menu of either docking port but it seems now to be possible from only one of them. Did something change and if so, does anyone know why? I would prefer to be able to undock via the menu of either port.

[Kermanzooming]

I have also noticed this... When two ports are docked, only one of them offers the option for undocking.

[Aragosnat]

I think only one undocking as been an option since before 1.0. Not 100% sure on that. But, yeah the last few updates it has been like this. Would be great if we could choose which one to use for undocking.

[MaxwellsDemon]

I've noticed "Undock" on one and "Force Undock" on the other, but that might be a mod I have.

[LordFerret]

7 minutes ago, MaxwellsDemon said:

I've noticed "Undock" on one and "Force Undock" on the other, but that might be a mod I have.

Stock Bug Fix Modules

 

Yes, used to be able to undock from either. I'm thinking maybe the whole thing revolves around which vessel is first designated docking target. Observe this when station building.

[Archgeek]

I think it used to be "undock" and "decouple node".  Undock would leave focus on the craft the port belonged to, while decouple node would give it to the other craft.  I didn't actually know it'd changed.

[Alshain]

1 hour ago, Archgeek said:

I think it used to be "undock" and "decouple node".  Undock would leave focus on the craft the port belonged to, while decouple node would give it to the other craft.  I didn't actually know it'd changed.

This is correct.

[cubinator]

19 hours ago, Archgeek said:

I think it used to be "undock" and "decouple node".  Undock would leave focus on the craft the port belonged to, while decouple node would give it to the other craft.  I didn't actually know it'd changed.

Well, my Rubik's cube seems to assign one of those two to each docked node at random, even in 1.0.5. The only noticeable difference is that "decouple node" can be done to either port, but "undock" can only be done to one of the two. There's probably some stuff that happens to the focus, but I've never systematically checked what it is.

Edited August 4, 2016 by cubinator

[pandaman]

I think the 'decouple node' option appears when the ports were docked in the VAB as part of the construction and 'undock' when they were actually docked in flight.

But yes, it does only seem to give the option on one of the pair now.

[Johnny Wishbone]

I always used the "decouple node" option whenever I had a docking port attached to another, non-docking port part. For example, lets say I put a docking port on the nose of a crew capsule, and then attached a LES tower to the docking port in the VAB. In order to jettison the LES during flight, I'd have to use the "decouple node" option on the docking port to release the LES tower (sort of like a separator) since it wasn't actually "docked" to the docking port.

[Sharpy]

Yes, the docking port can act as a decoupler, and then the decouple node is available. It can decouple anything that was attached to it in VAB, including another docking port. And in that case you can decouple any of the two, the effect is the same - but you can only do it once.

Once "decoupled" (or never actually coupled), the ports can dock together and then only one can be "undocked".

This is how my "docking lift" works:

the stack actually exploits heat shields having three nodes, and goes:

Heatshield 1 - Node 1 free (to attach the whole subassembly to the craft), node 2: docking port, node 3 winch.

Heatshield 2 - Node 1 free (to attach payload), node 2: docking port, node 3 KAS port.

The winch and the KAS port are connected. The docking ports aren't connected, just aligned in such a way that they will dock together the moment the craft spawns on the launchpad. There's never anything to decouple, undock from moment one.

 

Edited August 6, 2016 by Sharpy
actual image of the subassembly

[magnemoe]

On 4.8.2016 at 9:00 PM, Johnny Wishbone said:

I always used the "decouple node" option whenever I had a docking port attached to another, non-docking port part. For example, lets say I put a docking port on the nose of a crew capsule, and then attached a LES tower to the docking port in the VAB. In order to jettison the LES during flight, I'd have to use the "decouple node" option on the docking port to release the LES tower (sort of like a separator) since it wasn't actually "docked" to the docking port.

Yes, this is very smart for drop tanks or secondary payloads, just a bit heavier than an decopler and gives you an docking port for later use. 

[Curveball Anders]

12 hours ago, magnemoe said:

Yes, this is very smart for drop tanks or secondary payloads, just a bit heavier than an decopler and gives you an docking port for later use. 

I use this for addon modules for stations or sometime refuellers.

Robo-core and lifter with payload attached via a reversed docking-port.

Robo-core docks the payload to station, dumps possible excess resources, detaches and goes for a fiery death while the newly attached module still provides a free docking port.

Without wasting money on a docking port on the robo-lifter that will not be used.

 

[magnemoe]

17 minutes ago, Curveball Anders said:

I use this for addon modules for stations or sometime refuellers.

Robo-core and lifter with payload attached via a reversed docking-port.

Robo-core docks the payload to station, dumps possible excess resources, detaches and goes for a fiery death while the newly attached module still provides a free docking port.

Without wasting money on a docking port on the robo-lifter that will not be used.

 

Yes, if you want to dock an module you don't need an port on the delivery craft who is just deorbited. However as I use KAS I mostly atatch during EVA if possible.

 

[Curveball Anders]

Just now, magnemoe said:

Yes, if you want to dock an module you don't need an port on the delivery craft who is just deorbited. However as I use KAS I mostly atatch during EVA if possible.

 

I don't use KAS, but I do make sure that I've got EVA Struts endpoint on those module, so I can integrate 'em with the station if needed.

It's a bit of a brain teaser for me to have the payload above the command module, and to regard the command/lifter as the expendable part.

[Sharpy]

One more thing I often slap on the docking ports: nosecones (often doubling as fuel tanks and sometimes air intakes).

By the time the craft is above the atmosphere, the nosecone or intake is unneeded, and the fuel tank is depleted. And the location is usually optimal for docking ports.

 

[Tex]

As this seems to be a gameplay question, I've moved it to Gameplay Questions. Better late than never.