Debug version of KSP (module manager error)

[stk2008]

Hi all I am trying to run a heavy modded KSP with Debug enabled following this guide

https://gist.github.com/gotmachine/d973adcb9ae413386291170fa346d043

Now it all works I can profile the game with Unity but as soon as I add Module manager I get this error on starting the game

So I am at a loss because the mods I use need module manager.

any one got any ideas please

 

Thanks

[Stone Blue]

What mods? i see reference to TweakScaler, there...
If you use TweakScale, or any others by Lisias, I suggest contacting them directly, or posting on one of their threads for the mod in question. They maintain their own experimental, unofficial version of ModuleManager for their mods. I would direct you to their release thread for their version of ModuleManager, for support, but alas, I guess they didnt bother to make one.

Edited December 13, 2022 by Stone Blue

[Lisias]

On 12/13/2022 at 10:44 AM, stk2008 said:

Hi all I am trying to run a heavy modded KSP with Debug enabled following this guide

https://gist.github.com/gotmachine/d973adcb9ae413386291170fa346d043

Now it all works I can profile the game with Unity but as soon as I add Module manager I get this error on starting the game

So I am at a loss because the mods I use need module manager.

It looks like a KSP's Assembly Loader/Resolver issue, and TweakScale (and the Companions) are sensible to this problem. Send me the full KSP.log using dropbox or something and I will check who's triggering the problem.

 

On 12/13/2022 at 1:20 PM, Stone Blue said:

They maintain their own experimental, unofficial version of ModuleManager for their mods. I would direct you to their release thread for their version of ModuleManager, for support, but alas, I guess they didnt bother to make one.

I didn't opened a thread here exactly because that thing is an unofficial and experimental version of MM - people installing and using it is expected to know that opening issues/discussions on github is the only acceptable way to get support for the thing -  make it perfectly clear on the README and project's page that people using that thing should not expect getting support on Forum, even when the problem is related to any other add'on.

Forum's Module Manager is still active, by the way - and unless someone has some very specific needs (as I did), there's no reason to use my fork as it aims to behave exactly like Forum's MM (including functional bugs - if some patching works on my fork that doesn't on Canon, please report as it is a bug!  ).

That said, I don't see how my fork would help on this situation, neither how it would induce the problem if used - but, granted, maybe a need new glasses. I will try to follow that Debugging tutorial here using both MM and see if I find any differences.