JadeOfMaar
commented
4 years ago The new use case is where B9PartSwitch, with its feature/module switching capabilities is applied to a given module to affect what is consumed or produced by it (precisely, B9PS can add and remove keys and whole sub nodes of a target node and refresh the target module). Particularly the modules I mess with are ModuleEnginesFX{}, ModuleRCSFX{}, ModuleResourceConverter{}. I haven't tested other modules but I might do ModuleResourceHarvester{} at some point.
When B9 is used to change just the INPUT_RESOURCE{}, OUTPUT_RESOURCE{}, PROPELLANT{} in these modules, it's not going to be looking for whatever values (per module?) Tweakscale uses to remember how much the affected part was resized, so the module's rates are never scaled.
Example: the stock fuel cells and Restock+ MonoProp APU are changed from:
- Just LFO to [ LFO, LH2O(hydrolox) , LCH4O (Methalox) ]
- Just MonoProp to [ MonoProp, LqdAmmonia ]
(Available now in Rational Resources + Rational Resources Parts mod):
Example: the OPT SAGE engine's secondary engine mode is hooked and given 4 subtypes so you can change its Isp and thrust in Closed Cycle like a VASIMR.
- Open/Air-breathing mode scales just fine when Tweakscaled. There's no B9 hook on it.
- Closed Cycle never scales.
(Available now in OPT Legacy):
Lisias
As mentioned here.
For OPT Reconfig.