-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Editor's ReRoot is screwed from KSP >= 1.8.0 #66
Comments
Hanlor's razor: "Never attribute to malice that which is adequately explained by stupidity." - but, boy, sometimes it's hard not to do such. |
This is a craft made on the naked 1.8.1 test bed using only new parts from the Palette mimicking the steps on the OP (no clones, no dupes): And this is a craft made using the steps from the OP: The files have different sizes, what is a hint that something is pretty different between them - besides being essentially the same parts tied together in the same way:
|
This is the very same test done with TweakScale (and KSP-Recall). Apparently, other than the problems already mentioned above, no new misbehaviours were detected - the TweakScale (and Recall) The only difference is that the FTL-400 tanks from step 4 and forward were scaled up. |
Reproducing the test using only ScrapYard and OhScrap did not triggered any new misbehaviours (i.e., no Log Spam on Flight!). I'm concluding that whatever is screwing up ScrapYard, it's happening on a later KSP Version (i.e., yet a new bug on KSP). test-syd-bad.craft.zip Again - all the tests made until this moment were done on KSP 1.8.1. |
Oukey, we are handling TWO problems when ScrapYard is involved. On a nearly naked KSP 1.12.5 (only KSPe and my MM fork, and a specially debug compiling for ScrapYard and OhScrap), the problem described on the OP was easily reproduced: But now things get hairy: the problem described on this post and also on zer0Kerbal/ScrapYard#81 WAS NOT!! But I had reproduced the ScrapYard's FlowGraph LogSpam before on this very same KSP rig - but using the user's savegame. This savegame was created from scratch - what suggests that something on the user's machine is screwing their savegames. The ReRoot feature is broken, no question about. But it's also only a trigger for the ScrapYard's LogSpam, there's something else royally screwing up things too on a collective bug |
It was finally revealed that the ReRoot problem has not relation to the ScrapYard's LogSpam. See #67 . |
We have hard evidence that ReRoot is affecting also Stack Nodes: #70 Rebalance (or not???) size1p5 to use Attachment Nodes with Size 1 instead of 2 I initially misdiagnosed the issue as being something related to the Attachment Node sizes, but apparently this is not a factor. The problem should be really the ReRoot feature, that it's completely screwed up. COMPLETELY. Since KSP 1.8.0. Something similar is also affecting KSP2 at flight time, when docking and undocking. I suspect this may be affecting KSP¹ too - after all, last year after closing shop on KSP¹, Squad was hired to help on development of KSP2. |
That's sweet (I'm being sarcastic).
From KSP 1.8.0, a new old bug on Editor was detected when using the ReRoot feature. To reproduce the problem, fire up a KSP >= 1.8.0 (any one) completely "naked" (i.e., only DLCs installed, no 3rd parties) and then:
Open VAB (SPH also works, but VAB is easier for this test).
Place a FTL-400 Fuel Tank as root part:
Add 4 TT-38K Radial Decouplers in 4 radial symmetry:
Add another FTL-400 Fuel Tank on top of the root part:
Alt+Click (Clone) the newest Tank and place it over the original:
Alt+Click (Clone) the top Tank and place it over the original:
Click on the first Tank after the root and leave it on the side:
Select the ReRoot feature and ReRoot the 3 tanks stack to the center one:
Attach the stack into the Decoupler.
Voilà:
This M.O. was reproduced on KSP 1.8.1 and 1.12.5, it was assumed anything between is also affected.
This was not reproduced on anything below 1.8.0 (i.e., 1.7.3. to 1.4.1 works fine, didn't bothered to check 1.3.x and 1.2.x). The following ScreenShot is the result of the same procedure on KSP 1.7.3:
Notes
I have reasons to believe that the ReRoot feature is screwing things beyound the Attachment Points, as at least one 3rd party
PartModule
I'm debugging is presenting misbehaviours after its part is ReRooted.The text was updated successfully, but these errors were encountered: