Dynamic part payload (not just fuel) switching in VAB/SPH -- does this exist yet?

[cakepie]

I'm looking for functionality to enable the player to change the internal payload of a part while in the VAB/SPH. I am aware that this functionality already exists for different fuel loads, e.g. Firespitter's FSfuelSwitch -- but I'd like to be able to also include other PartModule options besides RESOURCE, such as ModuleGenerator or even mod modules, like KASModuleContainer.

The use case is my WIP airstairs part here, relevant discussion starts top of page 3. tl;dr: I'd like the player to be able to select between, say, the default "empty" part, some battery capacity, an APU (ModuleGenerator), or cargo capacity (KASModuleContainer) while in the editor. Different payload configurations should of course alter part cost and mass.

If this kind of functionality already exists in some mod somewhere, please point me to it; if someone is already working on something like this or plans to do so, I would be willing to help where I can and/or be your guinea pig.

If not, I might consider taking a stab at this sometimeâ„¢. (Not in the near future, though, got other things in the pipeline atm.)

Edited September 17, 2014 by cake>pie
spelling

[NathanKell]

Not as far as I know.

Also, it's a bit of a pain, because dynamic modules don't exist OnLoad and therefore won't load persistent data.

[cakepie]

Yeah figures -- if it weren't so troublesome someone would probably have already done it.

Just to check my understanding, the persistence issue would entail requiring such a plugin to define a (not dynamic) module as a wrapper to take care of serializing and unserializing the dynamic modules, that should do the trick, yes?

[NathanKell]

Yep. OnSave it would create a node for each dynamic module and call each dynamic module's OnSave on those nodes; OnLoad it would recreate the modules (if they don't exist) and call their onloads on the nodes.

[johnqevil]

Yep. OnSave it would create a node for each dynamic module and call each dynamic module's OnSave on those nodes; OnLoad it would recreate the modules (if they don't exist) and call their onloads on the nodes.

What about having a new module that references these, and having an enable/disable option? Then all of the possible modules would be loaded but not active, depending on selection.

I have no idea though, just a thought.