Strange docking port problem

[Scarecrow]

This particular problem has only manifested itself in the last few days and I am not sure what is causing it, other than my game file may be corrupted somewhere.

Basically I have an Apollo style craft where the Mun lander is initially attached to the engine of the Command module.  The docking port on the lander is bound to an action group key for ease of separation.  Once the craft has finished the Munar injection burn, the action group key is used to separate the Munar lander from the CM, the CM is turned through 180 degrees and then re-attaches to the lander, docking port to docking port.  So far so good.  However, once an orbit at Mun has been established is where the problems begin.  Having transferred crew to the lander, I can't get it to undock from the CM.  The action group key no longer works as it always used to up to this point.  Right clicking on either docking port, lander or CM, and selecting Undock, only makes the option disappear without actually doing anything.

I haven't added any new mods, and there hasn't been a new version for a little while, so I am struggling to understand why this problem should suddenly appear.  Be interested to hear any theories.

 

ETA:  The above is occurring in v1.1.3  I've just copied and tried the same craft in 1.1.2 which is running with the same mods and it works fine, so it doesn't appear to be a problem with the craft or the mods I'm running.

Edited July 30, 2016 by Scarecrow

[Snark]

Moving to Technical Support.

[Scarecrow]

I've tried again with a completely mod free install, and am getting the same problem.  I have also noticed that the Sepratrons I have fitted to the stage that includes the lander also disappear from the staging list when the Cm docks back to the lander.

[Frozen_Heart]

Yeah I've had this several times now. Mods or no mods still happens.

[Glaran K'erman]

@Scarecrow I feel your pain. I had this happen very recently to a station and used @Claw's stock bug fixes found here. Installed it will add the option to 'Force undock' in the click menu of the port if it detects that it failed to do anything. Not sure if they have nailed down the cause but it was mentioned that it's caused by certain staging events. I wonder if the sepratron thing is a clue?

[Scarecrow]

@Glaran K'erman thanks for that.  Not only has @Claw's bug fix sorted out the docking port problem, but the sepratrons are also back in the staging list once the two vehicles are re-docked.

 

[JohnWittle]

(Reposting here since this post shows up in Google searches for the problem)

 

So it turns out that people are aware of this bug and have a much better idea of what's going on and how to fix it; those people just don't come into this forum. But if you read the "Common Issues" thread, it turns out this bug has nothing to do with any mods.

The problem is with the ShieldedPart function, which gets called on parts that are A) inside a fairing or B) inside an engine shroud. If a crewed capsule starts inside a fairing, then EVAd kerbals will bug out. If a docking ring starts inside a fairing, it will bug out. If an engine starts inside a shroud, it will bug out (I assume your separatrons were inside the Lander's fairing?).

The Stock Bug Fixes mod fixes the issue for stock fairings and engine shrouds, but not modded fairings.

The devs are aware of the bug and intend to fix it in an upcoming patch. Until then, install the Stock Bug Fixes mod and use only stock fairings and stock engines (except for unshrouded egines), and, if I have understood things correctly (always a chancy proposition), it will work.

 

Source: 

 

Edited August 4, 2016 by JohnWittle

[DDE]

Back-up solution is through a save file editor like

 

[Gryffyn]

I have had this problem with docking ports as well. I started using the shielded docking port on my crafts and when it comes time to undock instead of clicking undock I click the option to close the shield. This causes the docking port to force undock and problem solved. Just figured I would throw this out there. I will def go check out the stock mod fix thingy or whatever it is called (Im too lazy to scroll up but dont mind typing all this extra stuff out. lol).