When you change the size of the thermal power generator it first works fine. If you connect it to the magnetized target fusion reactor then the weight goes back to 6 tons even if you shrunk it all of the way. After you disconnect it from the reactor it stays the same weight. If you then scale it back to its original size it now weighs more then it did originally. This uses the interstellar extended mod.

It's time to give this a closure. Moving the deadline to 2.4.7.6

Hi, @c1derly . I will need a full KSP.log in order to check what's happening.

What you are describing looks like some bad interaction with a 3rd party add'on - such a evident bug would had been reported before, I think.

Did you reprpoduced the problem on a clean install (i.e., only KSP-Recall, TweakScale and Interstellar Extended)?

I will try a clean install a little later today when I get a chance.

@c1derly ,

I can confirm it happens in stock. Which logs do you need exactly? Do I need to enable anything for more detailed logs?

The KSP.log itself is enough. It will tell me anything I need to know to be sure I'm reproducing your installment correctly, as well will be a reference to be compared to what I get here.

The standard logging settings are enough.

Sorry about the delay on vacation atm and didn't have time. I can confirm it happens in stock. Which logs do you need exactly? Do I need to enable anything for more detailed logs?

Here is the log. I have to change my original description with the stock version anyway. It doesn't go above the weight it was originally when you scale it up after you disconnect it from the fusion reactor. It does decrease in weight if you shrink it first but when you connect a fusion reactor it jumps up in weight a lot and stays that weight after you disconnect it from the fusion reactor. Also if you add the thermal generator to the fusion reactor and then shrink it the weight doesn't change.
KSP.log
.

@c1derly Sorry the delay, Real Life™ is bitting a bit too much.

Just got time to check your log today, and I already found something weird…

[EXC 21:58:19.357] MissingMethodException: bool ModuleManagerWatchDog.SanityLib.IsEnforceable(int,int)
        UnityEngine.DebugLogHandler:LogException(Exception, Object)
        ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object)
        UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object)
[EXC 21:58:19.358] MissingMethodException: bool ModuleManagerWatchDog.SanityLib.IsEnforceable(int,int)
        UnityEngine.DebugLogHandler:LogException(Exception, Object)
        ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object)
        UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object)

This suggests that you don't have the 666_ModuleManagerWatchDog.dll installed on your GameData, please check!

I also found MiniAVC on your rig. Please uninstall all MiniAVC.dll (or install ZeroMiniAVC). MiniAVC have a pretty nasty history of causing random problems - I don't know if this is still the case, but frankly… Install KSP-AVC for the feature and get rid of this MiniAVC.dll , it just doesn't worth the trouble.

I'm checking your report now, I will be back to you Soon™

(marking as unrelated because this is not related to TweakScale - it is the victim, not the perpetrator)

I made some tests with the PB-NUK and with the Fuel Cells, and the Converters behave as expected. No mass changes, no nothing.

So this is not related to TweakScale or KSP, is something specific to KSPIE - or perhaps a misbehaviour related to the same thing that is screwing up Module Manager Watch Dog? I double checked your KSP and the 666_ModuleManagerWatchDog.dll is on the right place, so the exception I quoted above is related to a bad DLL (unlikely) or to something silently borking the Assembly Loader - that have this nasty side effect.

Please remove all MiniAVC.dlls from your system and check if it improves something. It's a blind guess, but I had solved lots of problems in the past by removing all the MiniAVC.dlls from the system and perhaps we are lucky this time.

Otherwise, I will need to execute a fishing expedition in order to figure out who is the culprit!