Jump to content

Docking port trouble


Recommended Posts

I wasn't sure if I should put this here or in the bug report place.

Basically, I am building a modular surface base on Laythe, seen here in its current state:

D8dAUNv.png

here is the testing prototype at KSC:

OIS4HQL.png

The whole thing is assembled by those two rovers. Due to an error on my part, I only have one rover on Laythe at the moment, but that's beside the point.

Here is the issue:

0o3doyc.png

For some reason, the docking port on top of the rover in the picture no longer works. No magnetism, no docking, no nothing. I noticed this when I went to pick up the second one of those tunnel segments that you can see in the first picture. At first I thought that it was a problem with the tunnel segment, as I had already assembled three pieces with that rover. With no docking, I had to haul the thing on top of the rover, without them being joined, which made for a nerve-wracking 2.5 km drive and a very tedious docking. Problem is, I have the same issue with the habitation module in the last picture, and i don't think I can pull off the same stunt this time.

As you can gather, this is a serious and weird issue. This really makes no sense, the thing worked before, has no visible damage, and everything has been tested to hell and back! And now all my Laythe efforts are in jeopardy. Worst case scenario I have to send out a shipment of new assembly rovers, but that would take ages, and I would prefer to avoid it, especially if there is some sort of invisible alien being on Laythe that feed off docking port magnetism but which is also really picky about only getting it from my rovers.

Does anyone have any idea whats going on with this thing? Any help would be appreciated.

Edited by SofusRud
Link to comment
Share on other sites

It's not an uncommon issue, sometimes the state of the docking port becomes incorrect. If a save/load cycle doesn't fix it, you need to save/edit/load - basically identify the errant docking port in the save file (persistent.sfs) - here is the state of a docking port that is currently unattached ...


PART
{
name = dockingPort2
uid = ( 9 digit number specific to individual part )
mid = ( 9 digit number specific to individual vessel )
parent = 2
position = 0,1.56843280792236,0
rotation = 0,0,0,1
mirror = 1,1,1
istg = 0
dstg = 0
sqor = -1
sidx = -1
attm = 0
srfN = None, -1
attN = None, -1
attN = bottom, 2
mass = 0.05
temp = -189.1217
expt = 0.5
state = 0
connected = True
attached = True
flag = Squad/Flags/default
rTrf = dockingPort2
EVENTS
{
}
ACTIONS
{
}
MODULE
{
name = ModuleDockingNode
isEnabled = True
state = Ready
dockUId = 0
dockNodeIdx = 0
EVENTS
{
Undock
{
active = False
guiActive = True
guiIcon = Undock
guiName = Undock
category = Undock
guiActiveUnfocused = True
unfocusedRange = 2
externalToEVAOnly = True
}
UndockSameVessel
{
active = False
guiActive = True
guiIcon = Undock
guiName = Undock
category = Undock
guiActiveUnfocused = True
unfocusedRange = 2
externalToEVAOnly = True
}
Decouple
{
active = False
guiActive = True
guiIcon = Decouple Node
guiName = Decouple Node
category = Decouple Node
guiActiveUnfocused = True
unfocusedRange = 2
externalToEVAOnly = True
}
SetAsTarget
{
active = True
guiActive = False
guiIcon = Set as Target
guiName = Set as Target
category = Set as Target
guiActiveUnfocused = True
unfocusedRange = 200
externalToEVAOnly = False
}
UnsetTarget
{
active = False
guiActive = False
guiIcon = Unset Target
guiName = Unset Target
category = Unset Target
guiActiveUnfocused = True
unfocusedRange = 200
externalToEVAOnly = False
}
EnableXFeed
{
active = False
guiActive = True
guiIcon = Enable Crossfeed
guiName = Enable Crossfeed
category = Enable Crossfeed
guiActiveUnfocused = False
unfocusedRange = 2
externalToEVAOnly = True
}
DisableXFeed
{
active = False
guiActive = True
guiIcon = Disable Crossfeed
guiName = Disable Crossfeed
category = Disable Crossfeed
guiActiveUnfocused = False
unfocusedRange = 2
externalToEVAOnly = True
}
MakeReferenceTransform
{
active = True
guiActive = True
guiIcon = Control from Here
guiName = Control from Here
category = Control from Here
guiActiveUnfocused = False
unfocusedRange = 2
externalToEVAOnly = True
}
}
ACTIONS
{
UndockAction
{
actionGroup = None
}
DecoupleAction
{
actionGroup = None
}
}
}
}

The key part is the lines 'state = Ready' but you may find other status lines show the incorrect state also. Take a backup copy of the file, edit the parts showing up wrongways, restart and test. Good luck, those kerbals are all counting on you.

Link to comment
Share on other sites

This bug usually arises from docking ports placed on physicsless parts (like the octagonal strut and the cubic octagonal strut), or docking ports placed on parts placed on physicsless parts. Just avoid the physicsless parts altogether.

Link to comment
Share on other sites

  • 1 month later...
This bug usually arises from docking ports placed on physicsless parts (like the octagonal strut and the cubic octagonal strut), or docking ports placed on parts placed on physicsless parts. Just avoid the physicsless parts altogether.

Is there a list somewhere of parts that don't work well with docking ports? I'm trying to work this out as well. I've had a lot of difficulty getting them to work with struts, and now I'm trying the fuselage.

Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...