[1.0.X - Experimental] [On Hold] FusTek Station Parts (WIPs on GitHub)

[Wolf Baginski]

I'm not sure where you should post it.

The IACBM has been in use for a long time, and I don't see any recent signs of changes. That's something that makes a memory leak unlikely. It's got a particular look. but it isn't vital that you use it. Since a lot of in-line docking ports, such as are used in spaceplanes, use the Clamp-O-Tron stock docking port, there is an argument for sticking with the stock docking port at 1.25m size.

There are other 1.25m docking ports. Unless somebody makes an in-line which just has the attachment node, and has the actual docking port as a separate part, if you want to use a spaceplane you have to stick with the Clamp-O-Tron.

I have been pointed at an answer to this, and it does seem to work.

http://forum.kerbalspaceprogram.com/threads/79128-1-0-AdaptiveDockingNode-1-7-Make-Your-Awesome-Docking-Port-Models-Universal%21?highlight=adaptive+docking

That is a plug-in and a basic module manager file. There is also a link to a thread on a multi-size docking port model.

This will use Module Manager to add the plug-in to the Fustek IACBM ports and allow them to dock with Clamp-O-Tron ports of the same diameter. I tested it, and it works.

@PART
[*]:HAS[!MODULE[ModuleAdaptiveDockingNode],@MODULE[ModuleDockingNode]:HAS[#nodeType[IACBM_125]]]:FOR[AdaptiveDockingNode]
{
    MODULE
    {
        name = ModuleAdaptiveDockingNode
        ValidSizes = IACBM_125,size1
    }
}


@PART
[*]:HAS[!MODULE[ModuleAdaptiveDockingNode],@MODULE[ModuleDockingNode]:HAS[#nodeType[IACBM_25]]]:FOR[AdaptiveDockingNode]
{
    MODULE
    {
        name = ModuleAdaptiveDockingNode
        ValidSizes = IACBM_25,size2
    }
}

If you want to use the mod it's recommended that you apply it generally, as if one port uses ModuleAdaptiveDockingNode and the other doesn't, even if they are the same size, behaviour is unpredictable.

My recommendation to stick with the stock Clamp-O-Tron ports is still simplest.

[sharpspoonful]

Why do you think it's a memory leak?

If there were a memory leak, it would cause KSP to crash quite quickly. Within 15-30 minutes even.

[sumghai]

Development of this add-on is on hold until further notice.

In the meantime, feel free to play around with my current dev build on GitHub. I'll reopen this thread at a later date.