Krydax

So the rescale mod includes "rescaleAntennas.cfg", which includes the following: @PART:FOR[SigDim2]:FINAL { @MODULE:HAS[#name[ModuleDataTransmitter]] { @antennaPower *= #$@SigmaDimensions/Rescale$ } } I add the ":FINAL" to it, because it was ONLY applying to the probe cores, and none of the antennas. However, that did not seem to fix the problem. Antennas still are not multiplied by 3.2x range. Any ideas? I have commnet antennas consumptor, exntension, info, as well as scansat, and NFE exploration (to name the mods that affect antenna stuff)

Well I guess that depends on if the new tweakscale works better/more safely or not! Haha. Either way, the weird behavior I was running into is probably worth looking into as I'm sure other players will run into it too eventually.

Thanks for your work! There's also a NEW tweakscale fork in the works now. What a time to be alive! So many modders still keeping this amazing game alive! Can't wait until KSP2 actually has enough stability & features that it can be better in every way than KSP1!

I guess I'll be the guinea pig

How would I, for experiments sake, add AttachedOnEditor back to the Procedural Parts?

Yeah it's frustrating when compatibility isn't being supported from both sides

Haha. Classic programming issue. Trying to understand 2-years-ago-you is like trying to decipher ancient greek texts. In any case, thank you for your work looking into a fix! If it does indeed fix it, just let me know how to add it back in. And who knows. Maybe it breaks something else, but it's not as annoying? Cause currently this issue is annoying enough that it's gonna cause me to not use PP tanks at all which is kinda defeating the whole point.

I am very intrigued on trying out this tech tree. I'm curious if it's still a good experience if I don't use BDB? I do have all of Nertea's mods, as well as things like spaceY, restock+, dmagic orbital science, infernal robotics. Also does this mod prune its own empty nodes (if it has them?) EDIT: Oh, i just realized this mod has BDB as a dependency. Nevermind! I'm not sure if I can handle BDB since I'm not really into the whole historical-missions/parts thing anyway.

Yay! I love when I find new and interesting bugs. Makes me feel special.... I did what you said. Open game, make the craft i explained above, launch, revert to vab, glitch is happened, quit KSP, and here you go! https://filebin.net/saih0x8b958ahsq3 <- KSP log https://filebin.net/8c4vekh75my7l6er <- Janky craft in question. Launch & revert to VAB as many times as you want to increasify the jank! =D

Okay More testing complete. By changing the engine on the bottom to uncheck "KSP-Recall::Attached on Edit", the engine properly "follows" the tank up into the service bay. So they both move together. (this is still bad though, cause the tank moves up into the service bay in the first place, because the service bay is tweaked to be smaller and the procedural part somehow double compensates when it loads in or something) That being the case, now I'm convinced that the issue is that the procedural tank does NOT have the "attached on edit" module. Is that meant to be the case? Or is it supposed to be lacking the attached on edit module?

I also saw that in KSP-Recall.cfg, Line 17, ProceduralPartsAttachmentNodes = false That stuck me as odd, but changing it to true didn't fix anything either. So idk. I think I'm in too deep at this point and have no idea what I'm messing with.

Here's an interesting fact: You mentioned the 999-KSP Recall 101_ProceduralPartsAttachmentNodesFix.cfg Guess what, I deleted it out of my gamedata folder (just to see what happened), and the bug still persists the same way. So was that cfg even doing anything? It seems like it isn't doing what its intended to do.

I don't think that's the same issue. In this case, a procedural part is not the root. I started with a probe core. To add more info, I just reproduced it easily: 1. Probe core (okto in this case) 2. Service bay 1.25m, tweakscale it to .625 3. add procedural fuel tank 4. add terrior, tweakscale it down. 5. launch craft 6. revert and BOOM. Things moved and now stuff is janked. I just tried with a flt400 instead of a procedural fuel tank, and the issue did NOT occur. So that does narrow it down to being procedural part related.

You are amazing. I will try this! Here's my ksp.log too if you're interested. I'll report back with results! Ah. Just checked. I already have that file/patch. So I don't *think* that's the issue then?

Yes, I have b9 part switch. As well as firespitter. I also have smart parts, but the auto-stuff is disabled on them, so that *shouldn't* be messing with anything. I can try removing it and see if bug continues.