AmanitaVerna

IFS's Kerbalism patch ("Kerbalsim.cfg") has typos in the resource names in 13 processes' output fields, and in one process's input field, which causes errors to show up in the log when both IFS and Kerbalism are present. I assume it also prevents them from working properly, but I never found out because I fixed it locally with a custom MM patch before I started actually playing my current game. Process Field Correct value LqDeuterium Boiloff input [email protected] Kerosene Heating output [email protected] LqdKrypton Heating output [email protected] LqdNeon Heating output [email protected] NTO Heating output [email protected] LqdMethane Heating output [email protected] LqdNitrogen Heating output [email protected] LqdNitrogen15 Heating output [email protected] LqdOxygen Heating output [email protected] LqdOxygen18 Heating output [email protected] LqdTritium Heating output [email protected] LqdWater Heating output [email protected] LqdHeavyWater Heating output [email protected] LqdXenon Heating output [email protected]

I experienced the exact same thing. When I tried to remove a thruster (using kerbalism) with eva construction in flight with KJR - Continued installed, it would either snap back to where it was mounted and the ship would spin, or if it touched another component, the ship would explode. When I switched to KJR - Next, the ship stayed still and I was able to remove and replace the failed thruster successfully.

Combining RR + B9PartSwitch + ClassicStock + Far Future results in KSP doing this: This appears to be the result of ClassicStock detecting Far Future and removing the Explodium resource and switching its stuff to use NuclearSaltWater (from Far Future) instead, followed by RR attempting to create an Explodium fuel tank type (via RationalResources/Classic/zTankTypes.cfg) because it sees that both B9 and ClassicStock are installed. P.S. It looks like there are other places in RR that try to do things with Explodium without checking if Far Future is installed. P.P.S. (After removing Far Future) Deep Sky Core is also trying and failing to create some tank types using resources that don't exist, starting with RR_CryoA, via DeepSky/00DeepSky/00DeepSkyCRP/ds0_B9PS.cfg, but in this case it's because RR only creates them when [B9PartSwitch,CommunityResourcePack,!ClassicStock] and Deep Sky Core appears to only be looking for B9PartSwitch and RR for those? I guess it's assuming that only one of ClassicStock or CRP will be installed and is trying to use CRP resources while RR is trying to set up ClassicStock ones? I've never done KSP modding and it's getting very late so I'm not certain how accurate my understanding of what the RR and Deep Sky Core cfg files are trying to do is.