ReScale Bug

[!(Jojo)BugHunter]

Game Version​

2026.9.7.5402

Operating System​

[Windows 11]

What Happened​

Objects that have been rescaled do not save their properties correctly.

Reproduction Steps​

1. add 2 tank one above the other
2. rescale all to max size
3. save
4. reload
5. Only the root part has the correct properties , weight, volume, thrust, etc.
6. The problem affects all types of parts tanks , engines , structures ect...

Reproduction Rate​

[always]

Additional Info​

 

[Herbal Space Program]

I am definitely seeing this as well, although I'm not sure if it really applies to everything. Rescaled tanks and engines however definitely retain some of their properties on vessel save/reload, but forget others. Some behaviors that seem to happen 100% of the time include:

1) If make a stack of upscaled tanks and then save/reload it, detaching one of them will cause the attachment node on its parent to migrate inward to the place where it presumably would have been if it had not been rescaled. Anything you subsequently attach to that node will end up clipped into the parent tank, in the case of engines or engine plates so deeply that you can't select it anymore.

2) Up-scaled engines retain their upscaled size on save/reload, but then show in the staging display as still having their original, unrescaled thrust levels. If you launch before having done a save/reload on the vessel, the values show still correctly on the pad, but if you save/reload the game from that point, just like in the VAB they come back at their original default values.

3) When you reload a vessel with rescaled engines and then try to fix the problem by rescaling them again, the engines jump away from their attachment nodes so you have to translate them upwards to put them back in the right place. The re-rescaled engines will again keep their properties when you launch from the VAB, but again lose them if you save/reload your launch situation.

 

[Herbal Space Program]

...Another data point I can add to this bug report is that upscaling lander legs and then saving/reloading them breaks them so their attachment strength is like chewing gum-level. I first noticed it landing on Mars, where even a <2m/s touchdown would just snap all 6 supposedly beefed-up legs off of a basic lander that was ~17 tons fully fueled. Funny thing is my engine bell was able to take the g load just fine and I came down on it stably, so it didn't even mess up my mission, but I think it's pretty obvious that is not the behavior you want from that part!

Anyway, when I went back to the VAB and tried to put that same lander on the launchpad it was stable just sitting there, but retracting the legs made them all pop off, as did launching it with retracted legs and then trying to extend them to make it stand up. Importantly, if I did all that, including the rescaling, without ever saving/reloading the lander in the VAB before launch, I saw none of these problems, so the issue seems very specific to the save/reload process.


...After doing a more stringent test in response to another report of the same issue, I must withdraw my conclusions above. Lander legs are just straight-up borked. This bug appears to be unrelated.