Rastan9
-
Posts
9 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Bug Reports
Posts posted by Rastan9
-
-
In Module Manager 3.0.0 and above using @EXPERIMENT_DEFINITION[*] doesn't work anymore and I guess should never have worked to begin with. Removing the [*] appears to make everything functional again though more thorough testing is probably needed.
\SurfaceExperimentPackage\Resources\SEP_NH_ScienceDefs.cfg and \SurfaceExperimentPackage\Resources\SEP_OPM_ScienceDefs.cfg were the cfgs that I found that needed modification.
-
In Module Manager 3.0.0 and above using @EXPERIMENT_DEFINITION[*] doesn't work anymore and I guess should never have worked to begin with. Removing the [*] appears to make everything functional again though more thorough testing is probably needed.
\OPM\OPM_ScienceDefs.cfg was the cfg that I found that needed modification.
-
In Module Manager 3.0.0 and above using @EXPERIMENT_DEFINITION[*] doesn't work anymore and I guess should never have worked to begin with. Removing the [*] appears to make everything functional again though more thorough testing is probably needed.
\DMagicOrbitalScience\Resources\DMagicCommunityTechTree.cfg and \DMagicOrbitalScience\Resources\NewScienceDefs.cfg were the cfgs that I found that needed modification.
-
We found the fix, just need to remove [*] after @EXPERIMENT_DEFINITION in the cfg and it will work like normal. Apparently @EXPERIMENT_DEFINITION[*] should never have worked to begin with.
-
2 hours ago, blowfish said:
Hmm, this was not an intentional change, I'll look into it.
I mean, it kind of makes sense as the thing in the brackets is supposed to stand in for a name value, but still.
Hopefully my finding this ends up being useful. Thanks for looking into it.
I've taken a look through the _MMCfgOutput for both 2.8.1 and 3.0.0 and isolated the files that were found to be different via Beyond Compare. Some of it seems like the @EXPERIMENT_DEFINITION[*] issue from Full-Science-reward, some of it looks like not loading patches that require certain mods to be installed that I don't have installed, sometimes there won't actually be a change but a line will be in a different spot, it also looks like there is something related to Surface Experiments Pack adding experiments to Outer Planets Mod. Another weirdness is that the differences found don't seem to account for everything. I've attached a link to both my output_logs and _MMCfgOutput for both 2.8.1 and 3.0.0. I've only included the _MMCfgOutput files that were shown to be different.
https://www.dropbox.com/s/i9ccfrbx738b295/_MMCfgOutput.zip
https://www.dropbox.com/s/xsyap8f2umbf4xe/output_logs fully modded.zip
Any help figuring this out is appreciated.
-
1 hour ago, sarbian said:
Load to the main menu, open MM menu (Modifier + F11). You ll get a _MMCfgOutput dirs in KSP with the cfg exporteds. Rename the dir, do the same with an other MM version. Now compare the dir contents with a good diff tool like Beyond Compare (or WinMerge, but I am not a fan).
Thanks, with this I'll get started on trying to unravel the remaining missing patches. As an aside, is there a way to not need all of my posts to be approved by a moderator? Thanks again sarbian and Aelfhe1m.
-
31 minutes ago, Aelfhe1m said:
It's the [*] that seems to be causing this to fail in 3.0.0. If you remove that then it applies the expected 12 patches to an otherwise stock KSP.
Quick testing suggests that only nodes with a name key are selected by @NODE[*] while nodes that use another primary key (like id in EXPERIMENT_DEFINITION or ResourceName in GLOBAL_RESOURCE) will not be matched and no error will be written to the log either.
Thanks, that change to the cfg fixed it in both an otherwise stock ksp and a heavily modded install.
In my heavily modded install I still have 36 unaccounted for patches after moving from 2.8.1 to 3.0.0. Is there a straight forward way to figure out which *.cfg files need to be modified? Do I need to remove the [*] from any node that uses a primary key? Could the other missing patches be related to something else? I found the problem with the science reward purely by chance earlier. Sorry for being so lost when it comes to this stuff. Here are my logs for my modded install for both 2.8.1 and 3.0.0 https://www.dropbox.com/s/xsyap8f2umbf4xe/output_logs fully modded.zip
Thanks
-
I'm having a problem with a simple cfg not working with 3.0.0 that was fine with 2.8.1
@EXPERIMENT_DEFINITION[*] { %baseValue = #$scienceCap$ }In 2.8.1 it applies 12 patches and recovered science always gives 100% of the reward.
In 3.0.0 it applies 0 patches and of course does nothing in game.
output logs from both 2.8.1 and 3.0.0 are at https://www.dropbox.com/s/ye7wh8p9c71ov7b/output_logs.zip
Hopefully this is the right place to ask for assistance, thanks.
[1.8.x-1.12.x] Module Manager 4.2.3 (July 03th 2023) - Fireworks season
in KSP1 Mod Releases
Posted
So, it looks like all of my problems were from people using @EXPERIMENT_DEFINITION[*] when they shouldn't have. Removing the [*] every time it showed up next to @EXPERIMENT_DEFINITION seems to have fixed everything up as far as I can tell with basic testing. Thanks to Aelfhe1m, sarbian, and blowfish for taking time to help me figure it out. I've let the mod authors' for the impacted mods know.