NathanKell

The versioning is listed in the readme, but I edited the post above to show it there too.

V1.23.0 New performance / KSP bugfix patch : RestoreMaxPhysicsDT (contributed by @JonnyOThan). KSP 1.8.0-1.12.3. Fix typo in Strategy's SendStateMessage where bold was not disabled after title (as part of StrategyDuration fix, since that is the only place it would be used in stock KSP). Fix bug in ConfigNodePerf where it did not properly early-out of parsing if the cfg file had an extraneous } (stock parser aborts in that case). Added Chinese localization (contributed by @tinygrox).

Assuming one of you kind folks verifies it works for you too (it worked for me in dev mode), I'll release tomorrow (well, today).

Here is a test of the forthcoming release. Please verify it fixes your problems @[email protected]@610yesnolovely https://www.dropbox.com/s/xllxh2ymchwrl0x/KSPCommunityFixes_1.23.0.zip?dl=1

Ok I've tracked the problem down. The Reflection.cfg file in BDBNIC has a ton of extra } in the middle of the file and somehow KSPCF1.22+ responds differently to those errors than stock does. Fixing. Thanks for narrowing this down!

@[email protected] work narrowing that down, but maaaan that's bonkers. AFAICT from the spacedock download of BDBNIC all it does is patch some part variants (and add some new assets), it doesn't touch any part with a RealChute module (let alone the part that's erroring in the log).

Hmm. Those files are identical. I think there might be something else going on here, because I'm not sure what you might have had installed that would set PersistentIConfigNode to true in the 1.21 cache, so I'm wondering if the cache wasn't regenerated when swapping versions? Did ModuleManager *say* it was re-applying the patches?

@[email protected] seeing anything obvious, so...gonna make a request that'll take a bit of work. Please: (a) in your working game (i.e. with old, or no, KSPCF installed), load all the way to the main menu and then quit, and copy out your ModuleManager.ConfigCache. (b) Install latest KSPCF and do so again (until it hangs) and copy out *that* ModuleManager.ConfigCache. (c) upload both files. I will need to manually compare the resultant nodes in both files in the hopes that will give a clue. Clearly RC is failing to parse the PARACHUTE node in the mercuryRCS part, but I don't see how.

@RaketeJust tried what you mentioned and KSPCF happily created the file. Only thing I can think of is your KSP somehow doesn't have write permissions in that folder. (Also you have an outdated version of Kerbal Konstructs.) Create a new file in that folder and call it DisableManeuverTool.cfg and put this in it: DisableManeuverTool { enableManeuverTool = False } (make sure it's actually a cfg file, not .cfg.txt by the way).

The value is stored in that cfg file. I don't need MM cache because that cfg file is under PluginData and thus not managed by ModuleManager. KSP.log is right next to your KSP executable. If the value in the cfg is true, that means KSPCF is saving it to disk as enabled, which means either it's being reset or it's never being saved correctly in the first place. Please try the following: 1. Launch KSP, load a save, toggle the setting, apply, accept, and immediately quit KSP. Then give me the log and the cfg file I mentioned (and check its properties, make sure it's not read-only). 2. Make a clean install of KSP and add only KSPCF to it (use CKAN to install it so it gets all dependencies). Then repeat step 1. Oh that's very interesting, just saw your edit. I'll double-check that it properly creates it.

Actually what would be most helpful is your ModuleManager.ConfigCache file. Then I can compare the ConfigNodes generated by KSPCF and by stock KSP's loader. (And btw KSP.log is superior to player.log, player.log has a lot of excess junk and lacks some data KSP.log has)

Can't repro. Just tried locally and it worked fine. Check your KSPCommunityFixes folder in GameData -- look in PluginData and open the DisalbeManeuverTool.cfg file--does it show the correct state in that? (Does the file even exist for you??)

What version of BDB do you have? The game is choking compiling the parachute and RCS part for the BDB Mercury.

@seyMonstershas a good tutorial RP-1 series that's worth a look! As to installing, it's very simply, just follow the steps here: https://github.com/KSP-RO/RP-0/wiki/RO-&-RP-1-Express-Installation-for-1.12.3 If you run into further trouble I highly recommend asking on the RO/RP-1 discord, folks can walk you through step by step.

Ah, I misread a previous quote. Then I'm not sure where the confusion is? RP-1 disables stock delta V. Because stock delta V is worse than useless when RP-1 is installed. So if you have RP-1 installed, you don't get stock delta V. If you uninstall RP-1, you should get it back. What's the actual question?