Gordon Dry

either FOR or AFTER

@Shizen For scaling stuff to fit to planet packs I use a template like this: scalefactor = 1 @scalefactor:NEEDS[SigDim] = #$@SigmaDimensions/Rescale$ @scalefactor:NEEDS[!SigDim,RealSolarSystem] = 10.10625 @scalefactor:NEEDS[!SigDim,JNSQ] = 2.7 @scalefactor:NEEDS[!SigDim,GPP_Rescale_10x] = 10 @scalefactor:NEEDS[!SigDim,JNSQ_Rescale_10x] = 10 scalesqrt = #$scalefactor$ @scalesqrt != 0.5 and then from within a patch node I refer to #$/scalesqrt$ to for example multiply with it. In some cases I even use #$/scalefactor$ if I need the bigger number. In a later patch I remove those temporary variables to unclutter the MM cache.

GameData\QuickMods\QuickSearch\QuickSearch.version { "NAME": "QuickSearch", "URL": "http://ksp.spacetux.net/avc/QuickSearch", "CHANGE_LOG_URL": "https://raw.githubusercontent.com/linuxgurugamer/QuickMods/master/QuickSearch/README.md", "DOWNLOAD": "http://spacedock.info/mod/101/QuickSearch", "GITHUB": { "USERNAME": "linuxgurugamer", "REPOSITORY": "QuickMods" }, "VERSION": { "MAJOR": 3, "MINOR": 3, "PATCH": 0, "BUILD": 9 }, "KSP_VERSION_MIN": { "MAJOR": 1, "MINOR": 8, "PATCH": 0 } } http://ksp.spacetux.net/avc/QuickSearch: { "NAME": "QuickSearch", "URL": "http://ksp.spacetux.net/avc/QuickSearch", "CHANGE_LOG_URL": "https://raw.githubusercontent.com/linuxgurugamer/QuickMods/master/QuickSearch/README.md", "DOWNLOAD": "http://spacedock.info/mod/101/QuickSearch", "GITHUB": { "USERNAME": "linuxgurugamer", "REPOSITORY": "QuickMods" }, "VERSION": { "MAJOR": 3, "MINOR": 3, "PATCH": 0, "BUILD": 11 }, "KSP_VERSION": { "MAJOR": 1, "MINOR": 12, "PATCH": 2 }, "KSP_VERSION_MIN": { "MAJOR": 1, "MINOR": 12, "PATCH": 0 } } 3.3.0.9 vs. 3.3.1.1 vs. 3.3.1 (as previous post says). Confuzizous!

This is a personal zFinal patch that limits the minThrust to 25% and could be edited accordingly. It only looks for entries without minThrust or with a minThrust = 0, so any already existing custom value is not affected: @Kwebib DO NOT USE THAT PATCH This patch is not working in this way as it needs code (which would be Realism Overhaul). Just with this patch an engine never can throttle down. Sorry for the confusion.

https://github.com/net-lisias-ksp/ModuleManager/wiki/Patch-Ordering

Those patch manager patches do FINAL and just overwrite any previous mod specific settings.

I got the same issue as @Tivec suddenly. And unfortunately there are no forks from anybody fiddling with it.

I got a similar reaction wheel nerf in my personal zFinal folder: @PART[*]:HAS[@MODULE[ModuleReactionWheel]]:NEEDS[!RWSaturatable,!MandatoryRCS,!SETIrebalanceReactionWheels,!UnmannedTech]:FINAL { @MODULE[ModuleReactionWheel] { @PitchTorque *= 0.05 @YawTorque *= 0.05 @RollTorque *= 0.05 @RESOURCE[ElectricCharge] { @rate *= 0.5 } } } @PART[*]:HAS[@MODULE[ModuleReactionWheel],@MODULE[ModuleCommand]]:NEEDS[!RWSaturatable,!MandatoryRCS,!SETIrebalanceReactionWheels,!UnmannedTech]:FINAL { @MODULE[ModuleReactionWheel] { @PitchTorque *= 0.2 @YawTorque *= 0.2 @RollTorque *= 0.2 @RESOURCE[ElectricCharge] { @rate *= 0.5 } } } @PART[*]:HAS[@MODULE[ModuleReactionWheel]:HAS[@UPGRADES]]:NEEDS[!RWSaturatable,!MandatoryRCS,!SETIrebalanceReactionWheels,!UnmannedTech]:FINAL { @MODULE[ModuleReactionWheel] { @UPGRADES { @UPGRADE,*:HAS[#PitchTorque] { @PitchTorque *= 0.05 } @UPGRADE,*:HAS[#YawTorque] { @YawTorque *= 0.05 } @UPGRADE,*:HAS[#RollTorque] { @RollTorque *= 0.05 } } } } @PART[*]:HAS[@MODULE[ModuleReactionWheel]:HAS[@UPGRADES],@MODULE[ModuleCommand]]:NEEDS[!RWSaturatable,!MandatoryRCS,!SETIrebalanceReactionWheels,!UnmannedTech]:FINAL { @MODULE[ModuleReactionWheel] { @UPGRADES { @UPGRADE,*:HAS[#PitchTorque] { @PitchTorque *= 0.2 } @UPGRADE,*:HAS[#YawTorque] { @YawTorque *= 0.2 } @UPGRADE,*:HAS[#RollTorque] { @RollTorque *= 0.2 } } } } @PART[*]:HAS[@MODULE[ModuleReactionWheel],#mass[>1]]:NEEDS[!RWSaturatable,!MandatoryRCS,!SETIrebalanceReactionWheels,!UnmannedTech]:FINAL { @MODULE[ModuleReactionWheel] { @PitchTorque *= #$/mass$ @YawTorque *= #$/mass$ @RollTorque *= #$/mass$ @RESOURCE[ElectricCharge] { @rate *= #$/mass$ } } } @PART[*]:HAS[@MODULE[ModuleReactionWheel]:HAS[@UPGRADES],#mass[>1]]:NEEDS[!RWSaturatable,!MandatoryRCS,!SETIrebalanceReactionWheels,!UnmannedTech]:FINAL { @MODULE[ModuleReactionWheel] { @UPGRADES { @UPGRADE,*:HAS[#PitchTorque] { @PitchTorque *= #$/mass$ } @UPGRADE,*:HAS[#YawTorque] { @YawTorque *= #$/mass$ } @UPGRADE,*:HAS[#RollTorque] { @RollTorque *= #$/mass$ } } } } You even could make it subject of a tier upgrade in one or two more tiers for a slightly less EC/s in the first and a slightly more torque in the 2nd upgrade.

I remember there was something about MM not applying patches inside the GameData\KerbalismConfig\Settings.cfg so it has to be calculated manually and entered into the Settings.cfg. Just after the line DataRateDampingExponentRT = 6 // same as above, but for RemoteTech like this unfortunately does not work: scalefactor = 1 @scalefactor:NEEDS[SigDim] = #$@SigmaDimensions/Rescale$ @scalefactor:NEEDS[!SigDim,RealSolarSystem] = 10.10625 @scalefactor:NEEDS[!SigDim,JNSQ] = 2.7 @scalefactor:NEEDS[!SigDim,GPP_Rescale_10x] = 10 @scalefactor:NEEDS[!SigDim,JNSQ_Rescale_10x] = 10 scalesqrt = #$scalefactor$ @scalesqrt != 0.5 @DataRateDampingExponent /= scalesqrt @DataRateDampingExponentRT /= scalesqrt -scalesqrt = delete -scalefactor = delete RSS would be 1.887 JNSQ/GPP 10x would be 1.897 JNSQ default would be 3.652 But this is a rule of thumb, just take the sqrt of the scale, divide 6 by that factor.

A tankMass of 0 is allowed? And I suggest a different boiloff config for LqdMethane compared to LqdHydrogen, there are configs circulating with proper values.

Well, they're the 1%. Nobody sane likes them.

Or both, paired with MM cache and what not. Use 7z and go for it.

btw, as a JNSQ_10x + GPP_10x + GPP_secondary user I do NOT have this issue.

Both is correct. On Windows there is C:\Users\<username>\AppData\LocalLow\Squad\Kerbal Space Program\Player.log and also KSP folder\KSP.log

@mmamh2008 doing a little research you would find something, but your first find would lead to the need of more research, so I condensed it: https://www.dropbox.com/s/al9dnsf59xkuybg/MechJebForAll (with variants).zip?dl=1 There are 3 variants in - as you need to learn more about how KSP and mods / MM-patches work, see for yourself, I do NOT explain.

Within the last 6 weeks: 4 issues by me https://github.com/jrbudda/KerbalEngineer/issues there are some newer (cosmetical) commits at https://github.com/lampeh/KerbalEngineer/tree/UImod but neither a PR nor a compiled version of it.

I dared to quickly adapt the patches for "RN_US_Rockets (only Aerobee)" that I already did for SkyhawkScienceSystem to KTT: https://github.com/hemeac/kiwiTechTree/pull/110/files I hope that it's good enough this way.

Darn, the icon is gone mid-flight, there is one NRE in the log: [EXC 16:18:03.555] NullReferenceException: Object reference not set to an instance of an object AntennaHelper.AHShipList.ComputeRealSignal (Vessel v) (at <410b4d9350104f37b1e9f94804bc30cc>:0) AntennaHelper.AHShipListListenerTR+<ParseVesselsConnection>c__Iterator1.MoveNext () (at <410b4d9350104f37b1e9f94804bc30cc>:0) UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) (at <12e76cd50cc64cf19e759e981cb725af>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) Log: https://www.dropbox.com/s/nchx3zxybl5pojt/KSP logs 2021-12-20-01.7z?dl=1

Necroing. I still don't get it why those interstage nodes cannot decouple themselves? An Apollo-like setup is nearly impossible, as trying to rotate and dock is impossible with either the truss structure in the way or a floating separator inbetween the docking ports. And having a face-down decoupler sticking at the engine of the CSM is a no-go. Why are there all these bad design decisions? To make the players brainz melt?

GameData\Pebkac\Parts\LaunchEscape\pebkac_mk1_LES.cfg got just MODULE { name = ModulePebkacLesController2 } and both GameData\Pebkac\Parts\LaunchEscape\pebkac_mk2_LES.cfg GameData\Pebkac\Parts\LaunchEscape\pebkac_mk2_LES_noBPC.cfg got MODULE { name = ModulePebkacLesController2 hasPitchControl = True stagingEnabled = True } I wonder it at least stagingEnabled = True should be in the first as well?

I just also recognized this, and also it happens that when the (fuel switchable) RCS part is enabled (stageable RCS), then picked up in VAB and attached again at another position, it's disabled. Edit: yep, the source of the patching is GameData\RationalResourcesRCSFamily\

There is one thing that really makes me wonder. At one point the resource container parts from Tac-LS were adopted by Kerbalism, in those folders GameData\KerbalismConfig\Parts\TacLifeSupport\TacLifeSupportContainers\ GameData\KerbalismConfig\Parts\TacLifeSupport\TacLifeSupportHexCans\ but there are not balanced to Kerbalism measures... So somebody decided to put them in, but did not alter the resource amounts to make them fit?

@Michel Bartolone Hmm. Well, coincidence, as I had a nullref issue after docking, a lot of log spamming with HullcamVDS, I had to go to SPC and back to the vessel to get the issue away. And I had that again and again for years, so...

Huh? You got more mods than I got subfolders in GameData? How come?

Could please anybody check those? https://github.com/judicator/KerbalismSystemHeat/pull/7