MechJeb2

MechJeb2

4M Downloads

Mechjeb, the Toolbar addon and ActiveTextureManagement create large fps loss

JonathanRappner opened this issue ยท 3 comments

commented

I've sat here for 6 hours to pinpoint this problem I have.
I've found a silly clash of three addons that lower my fps by about 20.
It's when you have ActiveTextureManagement, MechJeb and the 000_Toolbar addon installed at the same time.
Take out one of them and my fps goes back to normal.

To experiment, I made a clean install of the game. Then I installed (clean) versions of ATM, MJ and the Toolbar and I was able to recreate the fps loss. If I remove one of those addons and run the game with the other two, the game runs just fine again.
I even tried using older versions of all three addons but no cigar.

I think the problem is that MJ creates a whole lot of icons for the Toolbar based on all your custom windows. It seems to do this way too often. For example if you change the name of one of your custom windows. MJ will create Toolbar icons every time you press a key to enter the new name of your custom window. Leaving you with a lot of nonsense icons with names like "Orbit I", "Orbit In", "Orbit Inf" & "Orbit Info" etc.
I think that every time it does, Active Texture Management goes in and does something that creates cpu spikes because of some "new" button texture being added.

This problem didn't exist back in the day when MJ didn't have any native Toolbar support and we had to use the Optional MechJeb Modules addon. In that addon you had to specifically tell MJ which custom windows that would get corresponding Toolbar buttons.

And before you ask:

  • I'm using the latest version of all of the addons I talked about.
  • I've experimented with this in a completely clean version of KSP. With completely stock/default addon settings.
  • ALL settings files are completely stock and I am able to recreate the fps loss that I get in my main game.
  • I've experimented with both the stable 2.2.1 version and devbuild 2.2.1 #238 of MJ but no difference.
commented

Can you try build 239 and report ? It should fix it.

commented

Yep that fixed it.
Nice job!

commented

Good catch. I'll see what I can do about that.