CobaltWolf / Bluedog-Design-Bureau

Stockalike parts pack for Kerbal Space Program
https://forum.kerbalspaceprogram.com/index.php?/topic/122020-131mostly-functional-141-bluedog-design-bureau-stockalike-saturn-apollo-and-more-v142-%D0%B0%D1%82%D0%BB%D0%B0%D1%81-1feb2018/
120 stars 143 forks source link

possible part merges #1493

Open Rodg88 opened 1 month ago

Rodg88 commented 1 month ago

engines:

~GEM 40 SRBs - trying to toggle the gimbal module isn't working well, the PAW doesn't update correctly like the H-1. no idea why~

* check hypergol patch ^ update methalox patch

probe parts:

Looks like antenna switching doesn't really work well - even if the module looks like it's disabled, it still will transmit science. Updating the antenna power as well can work around this. Non-animated antennas also can't be switched, seems like the antenna deploy animation is partially why the viking antenna switch works. So any non animated ones (all of the rest) would need dummy animations? Antenna info mods also don't handle the modules changing, like Antenna Helper or CommNet Antennas Info. probably not worth it. ~mariner 2 solar/antenna - needs mu merging mariner 2 tracking solar/antenna - needs mu merging mariner 5 solar/antenna - needs mu merging mariner 8/9 solar/antenna - needs only the antenna .mu viking orbiter solar panels - needs only the antenna .mu - would need extrudedSurface2 to be moved under a new transform which the deploy animation moves instead. Just moving it under hinge2 should work? Deploying the panel while it's disabled currently re-enables it.~

other:

JacobB094 commented 1 month ago

I wouldn't merge the TR-201. It's more or less completely unrelated to AJ-10 series, being a modified LMDE. If anything, merge it into that.

Rodg88 commented 1 month ago

It's another Delta upper stage engine however, and the models gimbal setup is the same, which makes merging much simpler. It's probably either the AJ10 or keeping it separate, the LMDE is quite different in-game in terms of performance, model/size, gimbals, and tech tree placement.

CobaltWolf commented 1 month ago

Don't go too crazy with it. The last thing we want is to make it harder to find things. Try to stick to parts that are basically identical except for a nozzle or antenna, stuff like that.

JacobB094 commented 1 month ago

It might be better to keep it separate, then. Although, it would also not be amiss to reinforce the connection to LMDE, it should be together with the late model LMDE in the tech tree. IRL, Delta-P came about specifically because they had a bunch of thrust chambers about the right size and performance for a Delta, and they wanted to fly them off. TR-201 was literally the LMDE modified for fixed thrust, and with a different nozzle extension to improve efficiency in that application.

zorg2044 commented 1 month ago

Should probably merge the Atlas A, D and F skirts too... The D skirt was separate because of the animation module and i dunno I felt since A and D were separate why not make F separate too. Wasn't really thinking straight :P

Anyway would be nice if the animation module can be disabled successfully on D.

JacobB094 commented 1 month ago

There seems to be something wrong with the AJ-260s in real names mode. I'm getting this error: `[EXC 14:39:30.923] Exception: Could not find matching module B9PartSwitch.ModuleMatcher.FindModule (Part part) (at :0) B9PartSwitch.ModuleModifierInfo+d__10.MoveNext () (at :0) B9PartSwitch.PartSubtype.Setup (B9PartSwitch.ModuleB9PartSwitch parent, System.Boolean displayWarnings) (at :0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:LogException(Exception) B9PartSwitch.PartSubtype:Setup(ModuleB9PartSwitch, Boolean) B9PartSwitch.ModuleB9PartSwitch:InitializeSubtypes(Boolean) B9PartSwitch.ModuleB9PartSwitch:GetInfo() PartLoader:CompilePartInfo(AvailablePart, Part)

d__56:PartLoader+d__56.MoveNext_Patch0(d__56) KSPCommunityFixes.Performance.d__62:MoveNext() KSPCommunityFixes.Performance.d__58:MoveNext() UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr) ` The gimbal on the inline variant's main nozzle doesn't seem to work.
JacobB094 commented 1 month ago

Are we planning on merging GEM-60 and GEM-60XL? It seems like that could be done as a length switch.

Rodg88 commented 1 month ago

Those are probably doable yeah. Could possibly merge 46 into the 40 too, but would require new mu files to make an inline 46

JacobB094 commented 1 month ago

Well, that wouldn't exactly be a bad thing, though if you really wanted to avoid that, you could make them into one sequence instead - going something like -40, -40 inline, -46. That said, I do like the idea of an inline GEM-46. Maybe it could have a small tapering section on top, so it comes out to the same diameter as -40, despite being a little fatter.

JacobB094 commented 1 week ago

Is that possible to switch a fairing base along with the sidewalls? I'm asking because the Agena fairing has a lot of variants, each of which is a distinct part. Most other LVs already have a single fairing base that takes care of most of the options.

If not, we should at least unify the display names (both real and Kerbal), so they all show up in the same place in the part list. Something like Agena Standard Fairing, Agena JPL Fairing, Agena Poppy Fairing and so on.

JacobB094 commented 2 days ago

Why was the Vanguard Able tank not integrated with the Thor-Able ones? It's basically identical to the 60 version, only differing visually.

Rodg88 commented 2 days ago

Mainly due to able and vanguard assets being in different part folders