v2.0 introduced a toggleable service module umbilical port model that can be optionally retrofitted to the stock Mk1-2 Command Pod (#3). At the time, it used FSanimateGeneric from the Firespitter plugin, which was configured such that the umbilical port can only be toggled while in the VAB/SPH editor scene (and not the flight or EVA scene).
In v2.3, Firespitter was dropped as a dependency in favor of the stock KSP ModuleAnimateGeneric (#27), which at the time did not distinguish between different scenes, resulting in the umbilical port now being toggleable while in-flight.
KSP 1.0.5 features a new update to ModuleAnimateGeneric, which now supports additional fields with the following defaults:
actionAvailable = true
eventAvailableEditor = true
eventAvailableFlight = true
eventAvailableEVA = true
evaDistance = 5
By setting eventAvailableFlight and eventAvailableEVA to false, it may be possible to bring back the "VAB/SPH editor-only" behaviour from Firespitter, while still using the stock animation module.
v2.0 introduced a toggleable service module umbilical port model that can be optionally retrofitted to the stock Mk1-2 Command Pod (#3). At the time, it used FSanimateGeneric from the Firespitter plugin, which was configured such that the umbilical port can only be toggled while in the VAB/SPH editor scene (and not the flight or EVA scene).
In v2.3, Firespitter was dropped as a dependency in favor of the stock KSP ModuleAnimateGeneric (#27), which at the time did not distinguish between different scenes, resulting in the umbilical port now being toggleable while in-flight.
KSP 1.0.5 features a new update to ModuleAnimateGeneric, which now supports additional fields with the following defaults:
By setting eventAvailableFlight and eventAvailableEVA to false, it may be possible to bring back the "VAB/SPH editor-only" behaviour from Firespitter, while still using the stock animation module.