Weird issue with SXT parts using FSBuoyancy
Closed this issue · 13 comments
1)This is the part unmodified (defaultScale was set to 1.25 because of an error in the TS patch in SXT, but shouldn't matter) - the max floatBuoyancy is 50:
2)This is the part scaled up to 2.0x - note the mysterious new value for floatBuoyancy, which does not persist when launching the craft. Upon launching, right clicking on the part reveals floatBuoyancy maxed out at 102.4 or so, but adjusting floatBuoyancy changes the range back to 0-50.
3)Then, this is the part scaled back down to 1.0x - the floatBuoyancy is now more than it was at 1.25x, for some reason:
It works for me!
I need more information:
- KSP version used (are you using Making History�?)
- SXT version used
- I'm assuming the latest orthodox TwekScale version.
For the recored, my test was made using:
- KSP 1.4.5 + MH
- "My" fork of SXT (just because I'm testing it before a proper release - unlikely I had "fixed" something by accident….)
- This Version of TweakScale (Experimental, for logs)
I just tested it with KSP 1.5.1 + MH. Exactly the same add-ons (I just copied from one KSP into another).
Same results: works for me.
I realized that I didn't properly reproduces all the steps. Will redo the tests
Another issue: This is not a round part. The 1.260 scale shouldn't be applied.
This appears to be like the parachutes, check what was done on the chutes and replicate it here.
This can be related (or not) to issue TweakScale/TweakScale#11 , [see this comment](url
TweakScale/TweakScale#11 (comment)).
Possible problems with MH parts too. Investigate
Playing around with rescaling other Structual Tubes looks like the scale factors are just off for all of them. For example, if I scale down a short T-37 3.75m tube to 1.875m it visually looks to be the same size as the T-18 tube, but weighs .544t vs .075t for the short size T-18 tube. Likewise scaling up a T-18 to 3.75m weights .3t vs .6t for a stock size T-37.
It appears to be a bug. "Promoting" this to a proper status.
TweakScale 2.4.0.7 will "solve" this issue by dropping support for parts using FSBuoyancy. Sorry.
Proper support will be implemented in the new code tree.
Since this commit kinda of "solve" the problem, I'm closing this.
This issue was transfered to TweakScaleCompanion_FS as it's a Firespitter related problem
I'm reopening this issue as it will be correctly tackled down on TweakScaleCompantion_FS
This issue was closed in release 0.0.1.0. #HURRAY