JonnyOThan

You're welcome! However....I'll have to say that I did not do extensive testing with lots of other mods (other than fuel switching. What a pain). But the heuristic system should mean that anything that is set up similarly to stock parts should just work. If you come across things that are broken, please let me know (see the support section at the top) and I'll get em fixed.

Yes please! I think the best way to do this would be to add the reviva and b9ps modules alongside where it adds the INTERNAL node. And ideally that would be in a pretty early pass. We could populate it with all the mods that we know about. The subtypes should have a name that makes it clear the config is coming from PCR, so that the other mods can delete it or tweak it and provide their own.

Yes, it works fine. What issues are you referring to?

TweakScaleRescaled 3.2.0 is now available: https://spacedock.info/mod/3514/TweakScale Rescaled This is hopefully the version that will go live on the mod releases page, barring any showstopper bugs. You can even install it with CKAN: https://github.com/JonnyOThan/TweakScale/wiki/Experimental-CKAN-Support Changes From Previous Release Disable tweakscale when KSPWheelBase or ModuleEngineConfigs (used in RO) are on the part Fix fatal errors when duplicate scale keys are provided Fix a bug with scale children after re-rooting Fix a fatal bug when scaletype is null

Hey, somehow I was completely unaware of this database! I haven't looked very deep into it at all, but what would you think about adding it to CKAN (with a dependency on Patch Manager of course)?

I'm sure there are exceptions, but @Gotmachine has indicated to me that simple MM patches or config changes for QOL issues are out of scope for KSPCF. Thanks for bringing this to my attention though, and I'll second Poodmund's suggestion that it should be added to that database (which I was unaware of!). And perhaps there should be a stronger link between KSPCF and the community patch database.

Yeah the hands are referenced by name in the cfg files so it should be fixable with a MM patch.

Thanks. It looks like you copied my version over an existing TweakScale install. You need to delete the old folders first.

Thanks for the report, but your log file is restricted access.

@cyberKerb if you can, it would be great to get all this info into an issue on github. It's far less likely to be lost or forgotten there.

TweakScaleRescaled 3.1.4 is now available https://spacedock.info/mod/3514/TweakScale Rescaled Changes from previous release Consider KSPIE centrifuge modules to be crewed parts Removed inventory and EVA related patches - these are now in KSPCF 1.34 and later More completely fixed the issue where crew capacity could be reset on scaled-down parts Fixed Jr dockingport scaling Fixed some bugs with attachnodes being in the wrong place when pulling parts out of inventory in EVA construction Scale CoM, CoP, CoL offsets Fix some bugs related to IVA scaling Scaled up wheels no longer break easily Struts and fuel lines behave correctly when changing scale on parts they are attached to

[snip] I opened a GitHub issue here for tracking: https://github.com/KSPModdingLibs/KSPCommunityFixes/issues/191

That's a decent theory - I'm not going to spend any time investigating it though, because BetterEditorUndoRedo is honestly very high cost:benefit - it's a pretty massive patch for a relatively small QOL increase. It's not a big deal to disable the patch when other mods are installed that it doesn't work correctly with. I was originally going to ship KSPCF 1.34 with BetterEditorUndoRedo disabled by default, but gotmachine said that it was production-ready. FYI I did test the same case with only KSP-Recall installed and not TweakScale/L, and the bug did not occur. I don't think so, because the bug doesn't occur when TweakScale/L isn't installed. It also doesn't occur with TweakScaleRescaled. To be clear: I'm not trying to place blame anywhere. Mods sometimes have bad interactions and things that work in isolation don't work in combination. That's all this is. Update: KSPCF 1.34.1 is now available, disabling BetterEditorUndoRedo when TweakScale/L is installed: https://github.com/KSPModdingLibs/KSPCommunityFixes/releases/tag/1.34.1

OK, I've confirmed that this is some kind of bad interaction with the BetterEditorUndoRedo patch and TweakScale/L. Heads up to @Lisias in case people report this over there. In the short term I'll disable that patch in KSPCF when TweakScale/L is installed. (and as always note you can disable any patch in KSPCF in the settings.cfg)

Try without tweakscale. To be clear: I have no idea what the issue here might be. The ModulePartVariantsNodePersistence patch should be a no-op in the editor and loading scenes. The InventoryPartMass and EVAConstructionMass patches shouldn't be dealing with attachment nodes. BetterEditorUndoRedo would then be my prime suspect but I didn't write that one so I'm not sure how it might be interacting. I'll note that you have a 000_KSPAPIExtensions directory in gamedata, which seems like it probably shouldn't be there: https://github.com/net-lisias-ksp/KSPe/blob/mestre/INSTALL.md

Can you please post your logs? I've seen this reported a few times, but it doesn't happen when I try to reproduce it . The log files might help isolate where the problem is.

hey @linuxgurugamer I've seen a few reports of degraded performance because of log spam. Seems like a new issue introduced in the last version. Also your readme on github is pointing to the old thread, not this one. And you don't have issues enabled on github so I have to report it here.

ack disregard; LGG needs to update the forum link in his readme...

There are buttons in the part action window to toggle those two features, and they also indicate the hotkey for toggling them (K for scaling children, M for match node size). All 4 of the options in the part action window should be persistent - whatever you set them to, they should stay set like that until you change them again. If that's not the case for you, please let me know and post your log file. Also note that both Scale Children and Match Node size can be temporarily toggled (off to on or vice versa) by holding Left Ctrl. All of the keybindings can be changed in TweakScale\Plugins\PluginData\Scale\config.xml. Names of keys can be found here: https://docs.unity3d.com/ScriptReference/KeyCode.html Most likely the automatic systems I have in place aren't calculating the correct diameters for those parts (it uses a lot of heuristics, but if the parts aren't set up according to common standards then they're often wrong). If you let me know what parts are broken I can take a look and maybe fix them.

You have a number of mods installed that are only marked as compatible with KSP 1.7 - that's quite dangerous. If you used CKAN, would you mind exporting a .ckan file so I can replicate your setup easily?

Which part? Post logs? These kinds of problems don't happen on simple installs, so in order to fix any bugs we need to know exactly what you have installed and what you did. The ksp.log file is best way to provide that info.

Well I'm not sure what's going on here. I couldn't reproduce this with a simple install of Restock+ and KSPCF. You might want to verify your game files, or start removing mods to try to find a trigger.

Thanks, tracked it down to an issue in RPM: https://github.com/JonnyOThan/RasterPropMonitor/issues/127

I'm not really sure what you're saying here. Does disabling that patch make the issue go away? Are you sure you didn't change anything else? The mismatched module index patch was not touched in this last release (though there still could be some interaction). I'm pretty sure this is related to your bug, and it occurs before any of the module index mismatch errors: [ERR 22:23:21.696] Module ModuleDynamicNodes threw during OnStart: System.NullReferenceException: Object reference not set to an instance of an object at ModuleDynamicNodes.InitializeNodeSets () [0x0002f] in <4b449f2841f84227adfaad3149c8fdba>:0 at ModuleDynamicNodes.OnStart (PartModule+StartState state) [0x00000] in <4b449f2841f84227adfaad3149c8fdba>:0 at Part.ModulesOnStart () [0x00120] in <4b449f2841f84227adfaad3149c8fdba>:0 And ModuleDynamicNodes was also not touched in this release.. Could you post the modulemanger.configcache as well?

Thanks for the report. Please always include your KSP.log file when reporting bugs or asking for support.