Once you have the DOCKEDVESSEL section assembled, paste it into the module for the docking port from which it is missing. Also carry over the vessel type (not sure how to find that one out) and the vessel name. Once you found that rootUId, put that in the rootUId in the DOCKEDVESSEL section you're creating. I know you can find all this stuff with a lot of cross referencing and searching the save file. you constructed a lifting vehicle, decoupled the payload, docked the payload to the station, and removed the lifting vehicle), because then the vessel has a name like " Debris" or " Probe" etc. This could be difficult if the part you decoupled to put it on the station wasn't the root part you made in the VAB (i.e. I just happened to remember what the root part (the first part you put down in the VAB) of the connected vessel was, and it was the only one on my station. Maybe someone can reply with a way to do this by analyzing the parent/root structure of the save file. ![]() This involves a little bit of remembering what the component vessel names are and finding the rootUId of those vessels.įind the root ID of the vessel on which the docking port that has the bugged "Undock" botton is. You have to create it, which is the hard part. Note in the above the second docking port doesn't have a "DOCKEDVESSEL" section within the module. Find this part by using the dockUId from the port above: VesselName = Thatsnomun RCS Spindle <-name of docked vessel (not a unique vessel in the save file, part of the mother vessel that is the conglomeration of docked vessels where you'll find these docking ports)ĭocking port that the bugged docking port is attached to (in its bugged state). The parts of it you need are as follows, the bits that will have to be changed are bolded, the bits that you need to pay attention to are italicized: Then ctrl+F "enablexfeed" and find the one that says "active = True" that's the bugged docking port. Make sure crossfeed is enbled on every other port (in the whole save file is best, use find and replace to your advantage). The best way to find the particular docking port that you want is to disable crossfeed before going into the save file on the bugged port that says "Undock" but does nothing. In the save file docking ports have a module that describes their docking behavior. The reason this doesn't respond is because the docking port you right click knows its docked, but the docking port it's docked to does not. ![]() The bug I'm talking about is when you right click on a docking port and click "Undock" but nothing happens. Maybe the mods can format it properly once I post it? Hope this helps out! It's also a selfish move because I want to see Scott Manley continue his trip to Moho! Excuse me for my lack of proper annotations/formatting, this is probably the first time I've ever really posted in a forum. Since Scott Manley recently encountered this bug in his most recent reusable space program, I thought I'd be a constructive member of the community and post my solution. So I don't know why it happens but I found out how to fix the undock bug from someone's suggestion in another thread (I forget where I saw it).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |