-
Posts
2,132 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Bug Reports
Everything posted by Zorg
-
Just to add to this, we cant provide support for RO installs since it fundamentally reconfigures our parts and BDB RO configs are written and maintained by the RO team. (even then its not the core team but volunteers who have submitted patches to them). Its not feasible for us to provide support as we are not familiar with the details of RO configs and how our parts are meant to work there.
-
Lol don’t understand the reference to airstream, is it just the grey colour? Anyway what this is is the MB-60 (also known as MARC-60 and MB-XX). An expander bleed cycle upper stage engine by Mitsubishi in collaboration with Rocketdyne which at the time was a division of Boeing. it was considered as a Delta IV upgrade along with the RL60. Both engines are sometimes confused for each other and they had very similar stats. Both targeted 60k lbf of thrust (hence the 60 I their name). the fuel turbopump for both was by Ishikawajima Harima Heavy industries and probably was very similar. But RL60 was closed expander and had a little more Isp. The RL60 was a primarily American led project by P&W with IHI fuel pump, CADB from russia doing the lox pump (v different times) and Volvo doing the nozzle extension. In broad terms what you are getting is RL10B2 Isp with over double the thrust. 2x MB60 was briefly considered for the EUS for SLS as well. The MB-XX designation was used later in the project as a broader term because there was a down rated version called MB-35 but the power head looks very different so I’m probably not doing that one
-
BDB does add over 1000 parts so theres not too much to be done about that if your computer can't handle it sorry . Unfortunately KSP loads all parts into memory at game startup. You can go to the BDB parts folder and remove folders for rockets you're less interested in. This might help a bit. Its safe to delete an entire folder inside Bluedog_DB/Parts but you shouldnt try to delete individual models and cfgs.
-
As mentioned by others BDB is balanced against stock (meaning overpowered for stock scale cos stock parts are overpowered too). 2.5 to 2.7 is where its typically best balanced compared to IRL. Since JNSQ came out we have done all our balance testing and validation in that planet pack. More recently we have also been testing in KSRSS in 2.5x rescale and there is a native 2.7x scale KSRSS Reborn version on their gitlab too now which we will likely also begin to use. Side note: due to KSP fuel tank mass fractions there is no one rescale that works perfectly for all sizes of rockets. Saturn V might prefer 3.2x and might be slightly OP even in 2.7x
-
Didn't realise that was missing. Wetlabs should support all the default tank types, guess they havent been updated. Some mods will also get into the so called Z wars. AFTER zRealPlume, AFTER zzRealPlume etc etc. Stuff like this works if its declared using a FOR pass in module manager. using a FOR makes it "exist" in module manager. eg if there is a patch with FOR Bulldog_DB1 somewhere, MM essentially thinks a "mod" named Bulldog_DB1 exists and then you can write other patches that run AFTER or BEFORE Bluedog_DB1 and so on.
-
It's ugly and perhaps more to the point it would be a weird set of parts that are huge, requiring large textures but completely unmodular and cant really lego with other parts. On the other hand the Saturn V derived MLV parts in the mod are high modular and can be configured in all sorts of ways to make up even heavier (or smaller) launch vehicles. We feel thats the Saturn V upgrade path that works for us.