slumpie Posted October 10, 2014 Share Posted October 10, 2014 (edited) StockScalingBugFix v2.0.1 IMPORTANT: [*=1]There was an error with the first version of this fix. I'm terribly sorry for this. [*=1]Version 2.0 and higher fixes all issues, please download that one. [*=1]I also added the original files to the legacy 1.1 download (2.0 is recommended), you can use them as backup if you want (no longer needed, since version 2.0 uses ModuleManager). I'm sorry for the inconvenience. Features Fixes scaling problems with some stock parts that occur after using the "revert to launch" function or loading a quicksave. Does not affect modded parts, if you want help with those parts: check post 14 (click me) Installation Follow the instructions in the included ReadMe text file. Download Version 2.0 or higher is strongly recommended. [Link to defunct download site removed by moderator] Again: If you want help for parts from mods: check post 14 (click me) This fix is really only for stock parts. IMPORTANT: This is for KSP 0.25 only! Don't use it for older versions! Tired of having this after reverting to launch or loading quicksaves? You want the crafts to stay the same? *Original* Then StockScalingBugFix is the solution for you! ----------------- License: MIT License since version 2.0 http://opensource.org/licenses/MIT Pre 2.0: All assets were made by SQUAD, the developers of Kerbal Space Program, and retain their original licenses, I do not own them. Redistribution and modifiying is allowed as long as these actions are within the limitations of the original license set by SQUAD. Do I even need a license for this? --- Nothing for you people who expected a super genious universal scaling plugin that adds tons of functions and automatic module scaling fixes. Edited April 9, 2022 by Snark Link to defunct download site removed by moderator Link to comment Share on other sites More sharing options...
White Owl Posted October 10, 2014 Share Posted October 10, 2014 Where's the link? Link to comment Share on other sites More sharing options...
slumpie Posted October 10, 2014 Author Share Posted October 10, 2014 It's there now.I completely forgot about that... Link to comment Share on other sites More sharing options...
Eskandare Posted October 11, 2014 Share Posted October 11, 2014 You know this could have been done with a module manager config. Link to comment Share on other sites More sharing options...
slumpie Posted October 11, 2014 Author Share Posted October 11, 2014 (edited) You know this could have been done with a module manager config.EDIT: You were right. Edited October 11, 2014 by slumpie Link to comment Share on other sites More sharing options...
NathanKell Posted October 11, 2014 Share Posted October 11, 2014 Yes it would, because then it wouldn't change stock files (just fix bugs). You would then always have the option of uninstalling (rather than redownloading KSP!), it would be safe if KSP is upgraded and the issue not fixed, and it's just *always* a better idea not to *overwrite files* if you can avoid it. Link to comment Share on other sites More sharing options...
slumpie Posted October 11, 2014 Author Share Posted October 11, 2014 (edited) EDIT: Ok, I'll make a MM config. You were right too.I messed up, ok.---------------I'm sorry for everybody who downloaded version 1.0 and is suffering from broken node placement. EDIT: Version 2.0 is up and fixes everything, it also made the switch to ModuleManager and now you no longer have to replace config files. Edited October 11, 2014 by slumpie Link to comment Share on other sites More sharing options...
White Owl Posted October 11, 2014 Share Posted October 11, 2014 Doesn't everybody use JSGME anyway? Or maybe some other mod manager flavor of the month? No call for high drama.It's a good fix. This issue was bugging me. Link to comment Share on other sites More sharing options...
slumpie Posted October 11, 2014 Author Share Posted October 11, 2014 StockScalingBugFix Version 2.0 The big ModuleManager update! Now with MM config instead of the problematic stock config file replacement. Fixes all mishaps from the previous versions. Works with original configs and also the ones from the previous versions (no longer recommended). Oh and I cleaned up the thread a little Link to comment Share on other sites More sharing options...
iTiamo Posted October 11, 2014 Share Posted October 11, 2014 Thanks, this bug was really annoying on large rockets. Link to comment Share on other sites More sharing options...
slumpie Posted October 11, 2014 Author Share Posted October 11, 2014 Thanks, this bug was really annoying on large rockets.But can I ask you why you use Mk1 parts on your large rockets? Link to comment Share on other sites More sharing options...
NathanKell Posted October 11, 2014 Share Posted October 11, 2014 Cool!10char Link to comment Share on other sites More sharing options...
iTiamo Posted October 12, 2014 Share Posted October 12, 2014 But can I ask you why you use Mk1 parts on your large rockets?This didn't happen only with Mk1 parts for me. It happened with ProceduralParts and some engines, and tweakscaled RCS ports/solar panels. It seems completely fixed! Link to comment Share on other sites More sharing options...
slumpie Posted October 12, 2014 Author Share Posted October 12, 2014 (edited) I know it doesn't just happen with stock mk1 parts, but this fix should really only adress those and not parts from mods. That's actually the reason why it's called StockScalingBugFix.The cause of this bug is that whenever a MODEL node is used in combination with rF = *anything else than 1*, it results in this. Only on parts that are the first part on a vessel to be more precise.The scaling issues other mods are facing, namely shrunken parts, is caused by another change in how the game handles rescaleFactor in combination with the MODEL node.So if you want to do it properly:- For all parts without rescaleFactor, but with any number for scale inside MODEL:Multiply scale inside MODEL by 1.5625 (1.25^2) and set rescaleFactor 1 and multiply scale outside MODEL by 1.25. - For parts without scale inside MODEL and no rescaleFactor:Set scale inside MODEL to 1.5625 (1.25^2) on each axis and set rescaleFactor 1 and multiply scale by 1.25. - For parts with or without scale inside MODEL and rescaleFactor ≠1:s(Mo) = old scale inside MODEL; s(Mn) = new scale inside MODEL; rF(o) = old rescaleFactor; rF(n) = s(o) = old scale outside MODEL; s(n) = new scale outside MODEL [*=2]set rescaleFactor =1 [*=2]if rF(n) =1 -> s(Mn) = s(Mo)*rf(o)^2 [*=2] if rF(n) =1 -> s(n) = s(o)*rF(o) Of course, this only if you want to do it properly, you can also go the lazy way and simply multiply scale inside MODEL by rescaleFactor. The problem is you'll encounter exactly the same bug my fix is actually trying to fix on the stock parts.Although to be fair, you'll only really see it on parts that you use as first part on your crafts. Edited October 12, 2014 by slumpie Link to comment Share on other sites More sharing options...
Tw1 Posted October 21, 2014 Share Posted October 21, 2014 It is annoying this bug, when you have a lot of mod parts. I wish they would fix this. Link to comment Share on other sites More sharing options...
doggonemess Posted June 3, 2016 Share Posted June 3, 2016 Greetings, I don't mean to bring up a dead thread, but I am actually seeing this problem now, with version 1.1.2. Does this mod still exist anywhere? The download link isn't working. Link to comment Share on other sites More sharing options...
Snark Posted June 3, 2016 Share Posted June 3, 2016 On 6/3/2016 at 3:06 PM, doggonemess said: I don't mean to bring up a dead thread, but I am actually seeing this problem now, with version 1.1.2. Does this mod still exist anywhere? The download link isn't working. It's an ancient thread, and the last KSP version listed is 0.25, which is many versions ago. I'd be astounded if it still works, and the fact that there aren't any posts makes it likely that it's completely dead. The download link doesn't work because it's for a hosting site which went permanently off the air several months ago. It's been well over a month since the author even visited the forums, so asking about status is unlikely to get a response any time soon (and I expect the response would simply be "it's dead". Locking the thread to prevent further confusion. To the author: @slumpie, if you would like this thread unlocked, please let us know (easiest way is to just report this post). Link to comment Share on other sites More sharing options...
Recommended Posts