Jump to content

[1.12.5] Bluedog Design Bureau - Stockalike Saturn, Apollo, and more! (v1.14.0 "металл" 30/Sep/2024)


CobaltWolf

Recommended Posts

6 hours ago, Mr. Kerbin said:

 

Wait- like Orbiter Vehicle 1 and 10? Like how the space shuttles are OV-100?

That’s actually a typo in the changelog there. It OV1-1 and OV1-10. The series that flew on Atlas was known as OV1 within the broader OV program. OV2 and OV3 series flew on Titan test flights and Scout respectively while OV4 flew on the MOL test flight. The boiler plate MOL mockup in fact was technically OV4-3. 

Link to comment
Share on other sites

SpaceDock update is up now! (that was quicker than expected lol)

As a reminder for people installing 1.14 manually from the SD or GH release, you need to do a clean install when updating from 1.13. As in, delete the previous installation before installing 1.14. If you use CKAN you shouldn't need to worry about this.

Also for manual installs, please double check where you install the optional extra patches. The "BD_Extras (No Warranty)" folder itself doesn't go into GameData, the "Bluedog_DB_Extras" does, with each optional patch folder living inside that. I'd recommend against just installing all the optional patches at once, and just pick the ones you actually want. Some of them are difficulty settings (eg UpperStageThrustBuff, DecayingRTGs), add complication to parts you may not want (eg S1CMountDecouple, TitanLRBNode), old patches that no longer do anything (MethaloxRL10 was depreciated and merged into MethaloxEngines, or the CryoTanks patch which should be stock behavior now), or patches which need some updates still or have compatibility issues (eg BDB_nuclearEngines_systemHeat needs updates, and Fuel Cell has some issues with some IVA mods)

If you are starting a new save file for 1.14 (recommended):

You can safely delete the Bluedog_DB/OldParts folder, which will stop the game loading 158 depreciated parts, which are inaccessible anyway. Though if you wanted to use old craft files, this will prevent them from loading. This will delete in-flight craft if you load a save from BDB 1.13.

If you are continuing a save from 1.13:

Don't remove the Bluedog_DB/OldParts folder, and also check for custom patches that may be auto-deleting parts with "TechHidden = True". These will destroy in-flight craft.

Parts that have been depreciated this update will have "**DEPRECIATED**" added to their in-game name, but should generally still function. If you come across any such parts on in-flight craft and want to update them, you can do so by updating the craft in the VAB replacing any depreciated parts with the new versions, launching the new craft and cheating it to the same location as the old craft, then removing/cheating home and recovering the old craft. You may not want to do this if you have kerbals or science data on board you want to recover legitimately.

Some of the most common depreciated parts (besides the entire Atlas family, and a lot of Titan parts), include most of the RCS blocks (merged into new combo parts with different variants), the 4 older standalone science parts (the Radek-716 Geiger Counter, SWD-CCCP Ion Trap, COS-B3N3T Mass Spec, and P1NG-0WW Micrometeoroid Detector), engines witch previously had separate parts for their variants (including AJ10s, RL10, J-2, H-1C/D, XLR81, RL20, MB60, A7), Delta P/K tanks, some Redstone/Thor extension tanks, and the Saturn SLA adapters. You can check the Bluedog_DB/OldParts folder to see all the depreciated parts, this list isn't exhaustive.

Some parts which have had variants added to them may also change after updating, such as engines that previously had no subtypes but now do. For eg J2 engines may change to being J2A2 variants, as that's the highest priority subtype now, and there wasn't a subtype on the old part at all for the game to keep track of.

New Recommended Mods:

I'd also like to highly recommend getting Nertea's new mod VAB Organizer, which adds size tags to all parts, and subcategories to the part tray in the VAB. BDB 1.14 comes with compatibility patches for it, and it makes looking for the parts you want so much easier!

And as has previously been mentioned, installing Resurfaced (along with the latest Shabby) will enable PBR shaders on Atlas, Atlas V, standalone engines/NTRs, and a good majority of probe parts. PBR makes metal actually look metallic, and allows for a wide range of smoothness to be represented much more accurately. The probe family solar panels look particularly good if I do say so myself! There's some preview images and videos or BDB parts in the Resurfaced forum thread too! (Resurfaced is different from the Deferred mod's auto-converted PBR shaders in that the mod authors have full control over the look of the part. Deferred and Resurfaced can safely be installed together, and if you already use Deferred it's even more strongly suggested to install Resurfaced - the custom PBR shaders will take priority over any auto-converted ones)

Also, RealChute is now recommended - BDB now includes compatibility patches for all it's chutes, and installing it allows the X-15 Ventral fin to work correctly. (the control surface is disabled without RC installed due to base KSP restrictions with the stock parachute module)

As usual, please feel free to tag me if you find any issues, and enjoy!

Edited by Rodger
Link to comment
Share on other sites

15 hours ago, Rodger said:

SpaceDock update is up now! (that was quicker than expected lol)

As a reminder for people installing 1.14 manually from the SD or GH release, you need to do a clean install when updating from 1.13. As in, delete the previous installation before installing 1.14.

Well, crap. I went through some of the CFGs from 1.13 to add IVAs from Tantares and WBI, mainly for the European laboratory and the Skylab airlock plus a few others that escape me. I kept the 1.13 folders for Skylab but updated the others to 1.14—am I screwed?

 

EDIT:

Uh...help? Is it because I have 1.13 and 1.14 mixed?

 my8xcokp9d4.png

Edited by marxman28
Link to comment
Share on other sites

I am having a really difficult time trying to install the update through CKAN. It states it is not compatible with my game version, yet it is listed as compatible with the version I am using. Refreshing does nothing, nor does downgrading to 1.12 and upgrading (now I cant even update it back to 1.13 because of it conflicting with Magpie Mods despite this not being an issue beforehand).

Edited by Hank Kerman
Added information
Link to comment
Share on other sites

20 hours ago, bigyihsuan said:

IT'S HERE! 1.14 IS HERE!

Maybe it's time to finally get Skyhawk updated and the ETS parts moved to their proper places.

I continued the Skyhawk tree on my repo -> https://github.com/Gupyzer0/Spacelines-Tree It's only the tree, not the fuels and other things Skyhawk Science System adds (you can use Pappysteins  extras) but it's BDB 1.14 ready :D Also working on a kerbalism config, look into my User in Github :)

Link to comment
Share on other sites

5 hours ago, marxman28 said:

Well, crap. I went through some of the CFGs from 1.13 to add IVAs from Tantares and WBI, mainly for the European laboratory and the Skylab airlock plus a few others that escape me. I kept the 1.13 folders for Skylab but updated the others to 1.14—am I screwed?

 

EDIT:

Uh...help? Is it because I have 1.13 and 1.14 mixed?

 my8xcokp9d4.png

Yes, that error is due to not installing the update fully.

If you’re applying base changes to parts, you should be using module manager patches (in a separate folder) to apply the changes instead of editing the base parts. This way you don’t need to keep reapplying them for updates, and dont risk errors from unexpected things in the part cfg.

50 minutes ago, Hank Kerman said:

I am having a really difficult time trying to install the update through CKAN. It states it is not compatible with my game version, yet it is listed as compatible with the version I am using. Refreshing does nothing, nor does downgrading to 1.12 and upgrading (now I cant even update it back to 1.13 because of it conflicting with Magpie Mods despite this not being an issue beforehand).

Magpie mods is now listed an incompatible due to the new native PBR stuff. If you absolutely must have that mod, you can probably install manually from spacedock instead of ckan

Link to comment
Share on other sites

12 hours ago, Gupyzer0 said:

I continued the Skyhawk tree on my repo -> https://github.com/Gupyzer0/Spacelines-Tree It's only the tree, not the fuels and other things Skyhawk Science System adds (you can use Pappysteins  extras) but it's BDB 1.14 ready :D Also working on a kerbalism config, look into my User in Github :)

I'm actually working on a MR for BDB 1.14 specifically, here: https://github.com/CessnaSkyhawk/SkyhawkScienceSystem/pull/84 (early days, started it an hour or so ago)

 I'm planning on splitting up the BDB file into multiple files based on rocket families; it's simply too large in its current state.

Edited by bigyihsuan
Link to comment
Share on other sites

25 minutes ago, Rodger said:

Yes, that error is due to not installing the update fully.

If you’re applying base changes to parts, you should be using module manager patches (in a separate folder) to apply the changes instead of editing the base parts. This way you don’t need to keep reapplying them for updates, and dont risk errors from unexpected things in the part cfg.

So I can't just drag the contents of the 1.14 parts folder in? I need to get everything?

And how do I use Module Manager for my IVA patches?

Link to comment
Share on other sites

1 hour ago, Rodger said:

Magpie mods is now listed an incompatible due to the new native PBR stuff. If you absolutely must have that mod, you can probably install manually from spacedock instead of ckan

Did that and CKAN allowed me to update to 1.14. Thanks for the help!

Link to comment
Share on other sites

30 minutes ago, marxman28 said:

So I can't just drag the contents of the 1.14 parts folder in? I need to get everything?

And how do I use Module Manager for my IVA patches?

Yeah it’s not just the parts folder, and some files have moved or been removed, so just copying over the top would result in duplicate files too, thats why a clean install is needed. Maybe move the edited version elsewhere if you want to reference what changes you’ve made before instead of deleting it.

For MM patches, there should be a lot of examples around. Like here or the MM wiki. This is some of the stock BDB IVA setup patches for eg too: GameData/Bluedog_DB/Spaces/Skylab/SkylabIVA.cfg

Link to comment
Share on other sites

13 hours ago, GoldForest said:

356zn0.png

pPkdnNF.png

LqFCOly.png

ea6fl7S.png

T9BqrA9.png

 

you have a lot of nerve trying to alter the orbit of Kerbin that way :D

Impacting soon.   Asteroids that should have missed Kerbin. 

 

:P :P :P

Thanks for making the cake! :D   Happy Birthday BDB!

Link to comment
Share on other sites

8 minutes ago, slyfox023 said:

alright so I have another question, it's been on my mind for a bit lol, on the shelter/lab module for the landers, there's a "crane hook" that can be used, but what are they used for exactly?

I guess they'd be for hoisting anything from the ground up to the platform and vice versa. Trying to climb or hand up anything, especially something large and heavy like a rock sample box, would be difficult in a EVA suit.

Link to comment
Share on other sites

@CobaltWolf I noticed that the regular LM and LM Taxi are labeled as "unmanned" in the VAB, while the LM Shelter, Early LM Shelter, LM Lab, and LM She/Lab require at least one pilot for control. Should those requirements be swapped? (LM and LM Taxi require at least one pilot, while the others can be unmanned)

Link to comment
Share on other sites

5 hours ago, Ultim32 said:

@CobaltWolf I noticed that the regular LM and LM Taxi are labeled as "unmanned" in the VAB, while the LM Shelter, Early LM Shelter, LM Lab, and LM She/Lab require at least one pilot for control. Should those requirements be swapped? (LM and LM Taxi require at least one pilot, while the others can be unmanned)

If anything none of them should be unmanned, autonomous control should come from using the “truck” descent tanks.

Link to comment
Share on other sites

2 hours ago, jacks said:

not every atlas part is in the atlas category for some reason. idk if its a issue on my end or not

We'll need a little more info. 

What parts are not coming up under Atlas?

Have you updated to 1.14?

Are you using VABO?

Link to comment
Share on other sites

3 hours ago, GoldForest said:

We'll need a little more info. 

What parts are not coming up under Atlas?

Have you updated to 1.14?

Are you using VABO?

I'm also having a similar issue in 1.14—no 1.875m Atlas parts except for the stage-and-a-half skirt. I have the larger 2.5m parts, though. I'm not using VABO.

Also on a somewhat related note, the Atlas V Centaur adapter that goes inside the larger fairing spawns rotated 180 degrees, i.e. with the Centaur bump facing towards the flag side of the VAB. For reference, the Centaur bumps on the other Centaur pieces face away from the flag side.

Edited by marxman28
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...