![]() Please choose one fork and remove the other(s). So, if you got this message, you installed MM /L Experimental and also the Canonical MM, and this is hairy to say the least. However, this had the side effect of preventing this tool to easily detect when more than one copy of Module Manager is present - what is a problem if you choose to experiment with the /L Experimental fork. "There're conflicting Module Manager versions on your instalment!"įrom KSP 1.12.0 and forward, multiple assemblies with the same name are not a problem anymore, as KSP will elect the Assembly with the biggest FILEVERSION and ignore the others. This was diagnosed on TweakScale's thread. There's no other solution available but to manually DELETE all redundant copies of Module Manager, leaving only one on the GameData. This caused some problems to TweakScale at least once. Unfortunately, from KSP 1.8.0 and above a fatal bug is affecting Module Manager when more then one MM dll is installed on your system, what renders Module Manager choosing to use the oldest version to be used. "There're more than one Module Manager on this KSP instalment!" Oukey, you need to install Module Manager! :) See the "How-To" below. "There's no Module Manager on this KSP instalment!" Well, somehow you managed to have installed more than one copy of this tool itself!Ĭheck GameData/ for DLLs with the name "ModuleManagerWatchDog" on it and delete all of them - but the newest one. There're more than one MM Watch Dog on this KSP instalment! Please add "KSP:ModuleManagerWatchDog" as the subject of the email, or my email filter will not detect your email and I may miss it. If you need help about how to fix your system, drop me a message on Forum or send me a email using the address support at lisias dot net. This is a troubleshooting list to help you on fixing your instalment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |