Lisias

I don't know how much in a rush you are, but I'm studying a (non too much intrusive) way to transparently support CC on TweakScale (hint: more or less as I did on TweakScale Companion for Firespitter). The bad news is that this can take some weeks - I'm finishing a pretty important delivery on work (almost ready to be honest, but we are in bug-hunt mode, and this is also time consuming - besides not too much demanding) and have some late work on TweakScale and Companions, but this will be tackled down for sure. Make a backup of everything before rebuilding things - with luck and a bit of (yet more) time, we can salvage it.

Has not support (yet) is a better way of saying it.

I think CC is not handling the Scaling events, and relying on the previous values only - but I need to check that code to be sure. Every time TweakScale detects it needs to change something (and it happens, it issue an Event to any interested on that part alerting that it had changed something, so anyone that also change things can reapply itself on the "new part". This one is on TweakScale. It will be tackled down. https://github.com/net-lisias-ksp/TweakScale/issues/127

Not surprising at all, we can't have more than one fuel switch on the same part, and CC is essentially a fuel switch with steroids. However, with all that SAS bashing fest I got in the last months, I ended up with a pretty decent knowledge about how patching works, and how to "undo" some patching. I'm toying with this concept because I like MFT a lot, but can't have it when B9PS is installed (and some really nice add'ons use this), and I'm working on a TweakScale Companion for MFT that will allow coexistance by removing B9PS from the parts I want MFT instead - but the concept can be easily extended to anything else. The worst part is about a configuration mechanism - everything I came with ended up cumbersome to use. If you have any ideas, I'm hearing. Obs: MM can't help here - it understands config nodes, not modules. The solution I tinkering is semantically one step above what MM knows about. B9PS does a lot more than fuel switching, it's not only removing the whole B9PS section - it's a complex transformation rule. Great!

Midnight Oil is back to the action!

Hi, I just realised that recently Configurable Containers had implemented (or fixed) TweakScale support, and remembered you. Do you want to give it a try? Cheers!

Announce! TweakScale Companion "Living Style" 0.0.1.0 Beta is on the wild! TweakScale Companion Living Style adds (up to date) TweakScale /L support for the following Add'Ons: PorkJet's HabPack Forum EoL, currently distributed on Tokamak Industries (see below) HabTech (1) Forum SpaceDock GitHub (Community maintenance) HabTech 2 Forum SpaceDock GitHub Tokamak Industries Original Forum GitHub Current Maintainer Forum SpaceDock GitHub And more to come! -- -- -- Moar Releases! TweakScale Companion "Rockets" 0.0.1.0 Beta is on the wild! TweakScale Companion Rockets adds (up to date) TweakScale /L support for the following Add'Ons: Real Engines Pack Forum SpaceDock And more to come! @Ciko, I think this will interest you! (as asked here). Please note that it's an initial release, still in beta, and some bugs and adjustments are expected! -- -- -- Moar moar Releases! TweakScale Companion OPT 0.0.1.0 Alpha is on the wild! TweakScale Companion OPT adds (up to date) TweakScale /L support for, surprisingly , OPT!: Continued Legacy "Classic" All the patches were remade from scratch, using the latest "best practices" from TweakScale. It will work on Current TweakScale 2.4.3.21, but please read the Known Issues. This thing is terribly Alpha yet, and it may compromise savegames using old OPT TweakScale patches, please use S.A.V.E. @Xithyl515, you will like this one! (you had asked for it here!). Downloads on the OP.

In how many dimensions you are talking about? Source.

There're no planes on Universe - only curves with infinite radius.

Announce. I found a pretty embarrassing mishap on TweakScale, and issued a new final release for TweakScale 2.4.3.x series with that fixed. Downloads on the OP. TL;DR:

The problem was not landing, the computers of that era could handle this. It was landing where you intent to. They would need to move all the launch complex to a position where the ship could land on a huge dry lake after the reentry, so the lack of precision could be tolerable.

Essentially what solved this case. I don't remember now the exact versions, but I suggested installing the needed releases from 13 days ago (I hate how Github masks dates nowadays), that I verified be compatible. Cheers!

Well, the stunt works around here: replace the generator with solar panels, call the "ecological card" on the advertisings and sell the generator later as a "backup option". That battle is not over yet, the wound never closed. What will happen is that I will need to close inspect (a.k.a. reverse engineer it - but tell no one!) some modules in order to really understand how they works (as nowadays, I only know what they do). Well, one problem at time. It would be a shame not to use such power! Embrace your darkness, there's a whole Kerbal System under your rule!!!

Things are clearer to me now. You want "on the fly" customisations of the distribution packages, selectively preventing parts (or dependencies) of the package to be applied. I can see your point, but I also see the package maintainer's point of view: they probably aren't going to give support for instalments customised this way. What's probably not a problem for you. Oddly enough, in the end what would really solve your problem is a personal fork of the thing. I think you will still need to maintain your black-list on a release to release basis to a point you may prefer to do it manually again and save the burden of fixing the blacklist after having to debug the instalment when something had changed.

Or use KSP-AVC . it warns you about new versions, and on a click you are directed to where to download it. And yet, you ended up going back to manualy doing things because you don't want what they are installing automatically on your KSP. If you want things your way, you probably need to do it yourself. If you prefer that someone else do it for you, he will do it his way, unless you convince him otherwise. How to do it? Don't install it! Perhaps the problem you have is diferent you describes? You want to prevent that something be patched on some parts, but still be available to others? The approach I took was to undo the unwanted patches, but it can be cumbersome because you usually needs to patch back the original values - what usually demands to have a copy of the ModuleManager.ConfigCache before you installed the thing you want to second guess. Since I do control my KSP using mercurial, it's easy to me. What you want, I think, is a fork of the thing customized to your needs. Even Gentoo and its very custimizable portage ends up forcing you to accept some things - unless you write your own package. Well, this is the path I ended up taking. I needed some tools to help me on that, and it's indeed a bit cumbersome sometimes. But I couldn't find any other way.

You can try not installing it... I kinda "solved" this problem shoving some patches on my __LOCAL stunt with :FINAL on them. It helped me to solved some problems on the field, as Fuel Switches being shoved on parts that already had Fuel Switches. It's a bit worksome to craft that stunts, but once it is made right, they are pretty convenient.

Next time it happens, take a screenshot and publish here with KSP.log and ModuleManager.ConfigCache. I may be some bad interaction between some other add'on. It's more common than we would like, and some are pretty hard to identify.

I need to refrain myself from posting here before taking my coffee. Some parts are getting TS disabled on your craft, not all. I will fix the original post too. -- POST EDIT -- I found a new workaround that doesn't involves editing the OPT_SAGE.cfg to something non-conformal: on launch, and before hitting the STAGE the first time for the launch, click on the "Toggle Mode" button of the SAGE at least one time (two, to get it reset to the initial configuration). I'm convinced this is something on B9PS.

Nope, there's nothing to be fixed. KAX works fine from KSP 1.3.1 to 1.7.3, where I said it's meant to work. I could agree it are in need to be updated to 1.10, however, if you would be kind enough to explain what's broken? It looks fine to me:

I know. I was trying to zero in on the problem - i was kinda tired too, and probably didn't expressed myself the best way. (More than one ModuleEngineFX is used for MultiModeEngine support. It's legit, indeed) But somehow opt_sage is behaving as TweaskScale when rogue patched. Now we will work on detecting why this is happing. The Rapier engine also uses this same stunt, and at least me didn't noticed this behaviour on it (I will check on a few hours) [ a few hors later: NOPE. Rapier works as intended.] What does not means that opt_sage is at faulty neither. Rapier engine also uses the same stunt, the second module does not have enabled = false, and yet it works fine, no duplicated buttons on PAW. We have a toe stomping fest here. Something is overruling MultiModeEngine and re-enabling the second engine [or forgetting to disable it] - as a matter of curiosity, there's something disabling TweakScale on [some parts from] that craft on @pmborg instalment, so perhaps this problem is related. It's your lucky day, there's a TweakScale Companion for OPT on the works on this exact moment. Give a look on the TweakScale Companion Program Thread now and then, I'm publishing what's being released there. Spoiler:

I find you lack of ecological caring... disturbing. I think it needs more heat dissipators thou. Curiously, if I turn off the gigantors, the Electricy Charge is not sustainable anymore after returning them on, and I need to turn the generators on too.

Sometimes I find my English skills.... Insufficient.

Yep, it handle resources its own way, but it also handles TweakScale events, so things just works - as long no other fuel switch is installed, when IFS waives the switching but still tries to scale the part when TS asks it. It's the reason TS yells when it finds more than one Fuel Switch on a part, as it can't know who is switching and who is scaling, with the net result of something borking on the Rescale and TS taking the blame. Users of KSPI didn't needed the KSP-Recall exactly due this - it was not affected by the resource overwritting. On TS, this triggers the TweakScaleRogueDuplicated stunt, and until recently was due rogue patching - patches that blindly adds an additional TweakScale module on a part instead of modifiyng the existent one. But this can be verified by inspecting the MM ConfigCache, and on this case the MM ConfigCache was ok, no double TweakScale on it..... Hummm... I'm an idiot. I didn't checked if anything else was double patched. I will check that file again and see if I find anything else duplicated on opt.sage . -- -- -- POST EDIT -- -- -- Yep. The opt_sage engine is double patched. There're TWO ModuleEnginesFX modules working on this part, I found both on the MM ConfigCache, so this is a double patching for sure. At least on TweakScale, only the first copy is active - knowing it, TweakScale declares the second a RogueDuplicate and get rid of it. But since you don't do it, the second module lingers around with incomplete data and when something tries to probe it, you have the NullReferenceException mentioned . [edit: Multiple ModuleEnginesFX are used by MultiModeEngine module. It's legit, it not the same as TweakScale] This is the two copies of the module I found on the ConfigCache: MODULE { name = ModuleEnginesFX engineID = WJOpen thrustVectorTransformName = thrustTransform exhaustDamage = True ignitionThreshold = 0.03 minThrust = 0 maxThrust = 250 heatProduction = 160 useEngineResponseTime = True engineAccelerationSpeed = 0.7 engineDecelerationSpeed = 0.35 useVelocityCurve = False flameoutEffectName = flameout powerEffectName = running_open engageEffectName = engage disengageEffectName = disengage spoolEffectName = running_turbine engineSpoolIdle = 0.05 engineSpoolTime = 1.0 EngineType = LiquidFuel exhaustDamageMultiplier = 200 exhaustDamageMaxRange = 10 atmChangeFlow = True useVelCurve = False useAtmCurve = True PROPELLANT { name = ElectricCharge ratio = 3.1 DrawGauge = True } PROPELLANT { name = IntakeAtm ratio = 1 DrawGauge = True } atmosphereCurve { key = 0 300 key = 1 240 -22.22222 -12.72055 key = 10 190 -1.065011 0 } atmCurve { key = 0 1.5 0 0 key = 0.01 2 0 0 key = 0.1 2 0 -2.810402 key = 0.4 1.079561 -0.4394221 -0.4630589 key = 1 1 8.414095E-07 -0.2883541 key = 9 0 -0.1323353 0 } PROPELLANT { name = LiquidFuel ratio = 0 DrawGauge = False } } ---- copy two ---- MODULE { name = ModuleEnginesFX engineID = WJClosed thrustVectorTransformName = thrustTransform exhaustDamage = True ignitionThreshold = 0.01 minThrust = 0 maxThrust = 375 heatProduction = 190 useVelocityCurve = False flameoutEffectName = flameout powerEffectName = running_closed engageEffectName = engage disengageEffectName = disengage engineSpoolIdle = 0.05 engineSpoolTime = 1.0 EngineType = Electric exhaustDamageMultiplier = 200 exhaustDamageMaxRange = 20 PROPELLANT { name = ElectricCharge ratio = 101.927 DrawGauge = True } PROPELLANT { name = IntakeAtm ratio = 1 DrawGauge = True } atmosphereCurve { key = 0.001 3000 key = 1 30 key = 1.05 0.001 0 0 } } Ignore that PROPELLANT[LiquidFuel] at the end of the first copy of the module, it looks like my hack. I asked a fresh copy from @pmborg to confirm thou. This is the complete list of patches being applied to opt_sage: [LOG 10:51:11.317] Applying update Jettison/ModuleManager_Jettison/@PART[*]:HAS[@RESOURCE,!RESOURCE[Ore],!RESOURCE[Ablator],!RESOURCE[SolidFuel],!RESOURCE[ElectricCharge],!RESOURCE[MonoPropellant]] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:12.474] Applying update OPT_Legacy/MM_Patches/OPT_SAGE_VIsp/@PART[opt_sage]:NEEDS[B9PartSwitch] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:12.564] Applying update OPT_Legacy/MM_Patches/OPT_TweakScale2/@PART[opt_sage|opt_egg|opt_vtol_egg]:NEEDS[TweakScale] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:12.565] Applying update OPT_Legacy/MM_Patches/OPT_TweakScale2/@PART[opt_sage|opt_egg|opt_vtol_egg]:NEEDS[TweakScale] to OPT_Legacy/Parts/Engines/VTOL/EnginesEggDog.cfg/PART[opt_vtol_egg] [LOG 10:51:12.722] Applying update OPT_Legacy/MM_Patches/Category/Category/@PART:HAS[#manufacturer[OPT?Prop*Division]] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:12.852] Applying update OPT_Legacy/Parts/DepthMasks/Patches/@PART[opt_sage|J61] to OPT_Legacy/Parts/Engines/J61/OPT_J61.cfg/PART[J61] [LOG 10:51:12.853] Applying update OPT_Legacy/Parts/DepthMasks/Patches/@PART[opt_sage|J61] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:13.778] Applying update OPT_Reconfig/OPT_CTT/@PART[opt_surge|opt_sage|j81turbojet|opt_vtol_wrap?2|opt_vtol_jumpa2] to OPT_Legacy/Parts/Engines/J81/j81turbo.cfg/PART[j81turbojet] [LOG 10:51:13.778] Applying update OPT_Reconfig/OPT_CTT/@PART[opt_surge|opt_sage|j81turbojet|opt_vtol_wrap?2|opt_vtol_jumpa2] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:13.778] Applying update OPT_Reconfig/OPT_CTT/@PART[opt_surge|opt_sage|j81turbojet|opt_vtol_wrap?2|opt_vtol_jumpa2] to OPT_Legacy/Parts/Engines/SURGE/OPT_SURGE.cfg/PART[opt_surge] [LOG 10:51:13.778] Applying update OPT_Reconfig/OPT_CTT/@PART[opt_surge|opt_sage|j81turbojet|opt_vtol_wrap?2|opt_vtol_jumpa2] to OPT_Legacy/Parts/Engines/VTOL/EnginesAT-WJ.cfg/PART[opt_vtol_jumpa2] [LOG 10:51:13.778] Applying update OPT_Reconfig/OPT_CTT/@PART[opt_surge|opt_sage|j81turbojet|opt_vtol_wrap?2|opt_vtol_jumpa2] to OPT_Legacy/Parts/Engines/VTOL/EnginesWrapperWJ.cfg/PART[opt_vtol_wrapj2] [LOG 10:51:13.778] Applying update OPT_Reconfig/OPT_CTT/@PART[opt_surge|opt_sage|j81turbojet|opt_vtol_wrap?2|opt_vtol_jumpa2] to OPT_Legacy/Parts/Engines/VTOL/EnginesWrapperWJ.cfg/PART[opt_vtol_wrapl2] [LOG 10:51:13.778] Applying update OPT_Reconfig/OPT_CTT/@PART[opt_surge|opt_sage|j81turbojet|opt_vtol_wrap?2|opt_vtol_jumpa2] to OPT_Legacy/Parts/Engines/VTOL/EnginesWrapperWJ.cfg/PART[opt_vtol_wrapk2] [LOG 10:51:14.178] Applying update OPT_Reconfig/OPT_LiftSurface/@PART:HAS[@MODULE[ModuleLiftingSurface]:HAS[#dragAtMinAoA[>0.1]],#manufacturer[OPT*Division]]:NEEDS[!FerramAerospaceResearch] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:14.221] Applying update OPT_Reconfig/OPT_LiftSurface/@PART:HAS[#title[OPT?*],#manufacturer[OPT*Division]]:NEEDS[!FerramAerospaceResearch] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:14.621] Applying update OPT_Reconfig/CRP/OPT_B9PS_Cryo/@PART:HAS[#manufacturer[OPT*Division],@MODULE[ModuleB9PartSwitch]]:NEEDS[B9PartSwitch,CryoEngines|KerbalAtomics,!Pathfinder,!ModularFuelTanks,!RealFuels] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:14.683] Applying update OPT_Reconfig/CRP/OPT_IntakeAtm/@PART:HAS[@RESOURCE[IntakeAir],!RESOURCE[IntakeAtm]]:NEEDS[CommunityResourcePack] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:14.831] Applying update OPT_Reconfig/CRP/OPT_RCS_toggles/@PART:HAS[#manufacturer[OPT*Division],@MODULE[ModuleB9PartSwitch]]:NEEDS[B9PartSwitch,!Pathfinder,!ModularFuelTanks,!RealFuels] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:26.816] Applying update __LOCAL/hack/@PART[opt_sage] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:33.013] Applying update OPT_Reconfig/CRP/OPT_IntakeAtm/@PART[opt_sage|opt_vtol_wrap?2|opt_vtol_jump?2]:NEEDS[CommunityResourcePack]:AFTER[OPT_Legacy] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:33.013] Applying update OPT_Reconfig/CRP/OPT_IntakeAtm/@PART[opt_sage|opt_vtol_wrap?2|opt_vtol_jump?2]:NEEDS[CommunityResourcePack]:AFTER[OPT_Legacy] to OPT_Legacy/Parts/Engines/VTOL/EnginesAT-WJ.cfg/PART[opt_vtol_jumpa2] [LOG 10:51:33.014] Applying update OPT_Reconfig/CRP/OPT_IntakeAtm/@PART[opt_sage|opt_vtol_wrap?2|opt_vtol_jump?2]:NEEDS[CommunityResourcePack]:AFTER[OPT_Legacy] to OPT_Legacy/Parts/Engines/VTOL/EnginesWrapperWJ.cfg/PART[opt_vtol_wrapj2] [LOG 10:51:33.015] Applying update OPT_Reconfig/CRP/OPT_IntakeAtm/@PART[opt_sage|opt_vtol_wrap?2|opt_vtol_jump?2]:NEEDS[CommunityResourcePack]:AFTER[OPT_Legacy] to OPT_Legacy/Parts/Engines/VTOL/EnginesWrapperWJ.cfg/PART[opt_vtol_wrapl2] [LOG 10:51:33.015] Applying update OPT_Reconfig/CRP/OPT_IntakeAtm/@PART[opt_sage|opt_vtol_wrap?2|opt_vtol_jump?2]:NEEDS[CommunityResourcePack]:AFTER[OPT_Legacy] to OPT_Legacy/Parts/Engines/VTOL/EnginesWrapperWJ.cfg/PART[opt_vtol_wrapk2] [LOG 10:51:33.053] Applying update OPT_Reconfig/OPT_00Clean/@PART:HAS[#manufacturer[OPT*Division]]:FOR[OPT_Reconfig] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:33.093] Applying update OPT_Reconfig/OPT_B9PS_TAC/@PART:HAS[#manufacturer[OPT*Division],@MODULE[ModuleB9PartSwitch]]:FOR[OPT_Reconfig]:NEEDS[TacLifeSupport,!ModularFuelTanks,!RealFuels] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:36.260] Applying update WarpPlugin/Patches/AtmosphericIntake/@PART[*]:HAS[!MODULE[AtmosphericIntake],@MODULE[ModuleResourceIntake]:HAS[#resourceName[IntakeAir]]]:FOR[WarpPlugin] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:36.364] Applying update WarpPlugin/Patches/AtmosphericIntake/@PART[*]:HAS[@MODULE[ModuleResourceIntake]:HAS[#resourceName[IntakeAir],#area]]:FOR[WarpPlugin] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:36.435] Applying update WarpPlugin/Patches/AtmosphericIntake/@PART[*]:HAS[@MODULE[ModuleResourceIntake]:HAS[#resourceName[IntakeAir],#intakeTransformName]]:FOR[WarpPlugin] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:36.529] Applying update WarpPlugin/Patches/AtmosphericIntake/@PART[*]:HAS[@MODULE[ModuleResourceIntake]:HAS[#resourceName[IntakeAir],#intakeSpeed]]:FOR[WarpPlugin] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:39.870] Applying update B9PartSwitch/PartInfo/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]]:FOR[zzzzzz-B9PartSwitch] to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:40.167] Applying update InterstellarFuelSwitch/PatchManager/ActiveMMPatches/IntegratedDecoupler/@PART[*]:FINAL to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:42.297] Applying update PartInfo/PartInfo/@PART[*]:Final to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] [LOG 10:51:43.173] Applying update WarpPlugin/Patches/OreTanksFix/@PART[*]:FINAL to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] This is the exact patching log I have on my rig except by one extra patch: [LOG 10:51:42.297] Applying update PartInfo/PartInfo/@PART[*]:Final to OPT_Legacy/Parts/Engines/SAGE/OPT_SAGE.cfg/PART[opt_sage] That it's part info that I didn't installed. But this is harmless for sure. Now the interesting part: my ConfigCache is also double patched for opt_sage, but my rig don't suffer of the NREs reported by @pmborg. Or this is something related to something else I didn't installed, or by some twist of fate the MacOS port of KSP is immune to this (the MacOS version is more resilient on some borderline situations related to multithreading).[nah, I managed to reproduce it. I was clicking on the right "wrong" button, instead of the wrong "right" button"] So, this is not about finding who is borking anymore - given the "rogue duplicated" situation, I take for granted that sooner or later someone will try to fetch some data from the rogue and bork. The task is to search and destroy the rogue patch that it's shoving the duplicate, and this patch is on one of the patches I listed above.[It was not a rogue patch. It's a legit use of double Modules, the problem is somewhere else].

The heat exchange is not scaling properly, there's something missing somewhere and I didn't managed to have the time to find it. The problem is that this exponent is not doing what it's expected to do - or perhaps, I'm misunderstood what it's expected to do and so I'm failing to tinker with it. There's no wrongdoing on a personal gaming. KSP is not a competitive game, there's no cheating, there's no wrong way of playing it. There's TechTree support on TweakScale for people wanting to give it a try, by the way - I just can't do it on Vanilla TweakScale because it will ruin any previously running savegame. I agree that TweakScale can spoil terribly an career game, but on the other hand, it can make it more interesting too: As trying to go Virgin Galactic with WW2 technology. It's up to the users to decide how they will use the tools I made available for them. Not to mention a myriad of interesting things waiting for being unlocked on KSP:

Nope, TweakScale is working fine with SAGE and B9 on my test rig, I would had detect any problem at first glance - I'm reproducing the @pmborg instalent gradativelly to detect exactly what's going wrong. Sounds more like an (bad) interaction between B9 and some other fuel switch, as it already happened in the past. I will get into it in the exact instant I install the conflicting Add'On