![]() ModuleManager thinks color-changing is available via Firespitter or InterstellarFuelSwitch, but neither is installed.įix: This is a little trickier to pinpoint. Delete it, and install the latest version of it.ĥ. Firespitter and/or InterstellarFuelSwitch are installed, but not functioning.įix: The most likely cause is that the version of FS or IFS doesn't work with your version of KSP (for instance, you upgraded to KSP 1.1, and the mod is meant for 1.0.5 or earlier), or your copy is only partially installed. The MM config files include rules for what to do when color-changing isn't available, so please don't delete those.Ĥ. This mod is installed incorrectly, or you've deleted the color-change ModuleManager configs.įix: Reinstall the mod correctly, and in its entirety. ModuleManager recreates it on the next KSP start.ģ. Delete the file called "ModuleManager.ConfigCache" in GameData. Everything is installed correctly, but ModuleManager's cache hasn't noticed the changes yet.įix: This is a great one to try first. Now that I've seen probably most of them, I can give you a good list:ġ. Usually it boils down to one of a few different things. Problem: Fuel tanks or SRBs flash different colors, with glitchy "z-fighting": Lithobrake Exploration Technologies (lander parts, large chutes/legs/ladders/etc).ColorFuel Lines (color-selctable fuel lines).Fuel Tanks Plus (collection of large stock-like tanks with Color Coded Canister style).Color Coded Canisters (replacement models/textures for stock fuel tanks: prettier, cleaner, and diameter color-coding for the tank end-caps).SpaceY Heavy Lifters Parts Pack (stock-balanced large rocket parts, 5m parts, large SRBs).Modular Rocket Systems (stock-alike parts pack, NASA-like alternatives, and filling the gaps).Part of the NecroBones suite of mods, that work nicely together: ModuleManager (for mild customization of the tech tree).NOTE: Requires ModuleManager and SpaceY Heavy Lifters as dependencies! going from 1.7.0 to 1.7.1 is even less likely to break things than going from 1.6 to 1.7, for example.SpaceY Expanded is an optional expansion to the SpaceY Heavy Lifters, adding 7.5m parts and other accessories that go beyond the original intent of the original main pack. Which is pretty common, because mod authors have busy lives and often don't get around to updating compatibility information.Īlso, minor KSP version releases almost never break things these days, since those are minimal bugfix-type updates, usually. It just means that the author hasn't marked it as such. For example, if a mod says "1.7.0" on it, then that doesn't necessarily mean that it doesn't work on 1.7.1. It does not say anything about whether the mod works with other versions of KSP- that's an unknown. It means that the mod author has personally verified that that specific version of the mod happens to work on that specific version of KSP. When SpaceDock says that a mod is for a particular version, that means "This mod works on this version of KSP". (My own mods, for example, have generally worked just fine as-is for the last several KSP versions.) ![]() The overwhelming majority of mods work just fine after KSP updates these days, it's fairly rare for a KSP update to break any given mods. ![]() Just to elaborate on what pointed out above:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |