Rodger

Maybe try saving the craft with a new name after swapping? And make sure there's no other depreciated parts remaining - it's not just the engines.

Modding comes down to motivation. If RTB (or anyone) isn't feeling it (for whatever reason), thats just how it is. RTBs reasons for demotivation certainly make sense to me. And maybe if the situation changes that will be enough to remotivate, but I'm not sure telling him he's not thinking straight will help much.

I just launched it manually in 2.6666x (jnsq scale, 1,600km kerbin radius) too, and had 322m/s left in the 2nd stage even having overshot the 100x100 orbit. Are you using some other mod that changes fuel types or something? Also make sure KSPCF is up to date if you're using that.

My first guess for weird issues like this is the old version of TweakScale. If you have it, try replacing it and all of it's associated mods like Recall/Companion with TweakScale Rescaled instead. Otherwise if you post your ksp.log I can have a quick look, but if you have old TS, that'd be my first suggestion anyway

Not experiencing that myself, either on the Mun or in 0g.

Do you have any other mods trying to apply TU to the atlas parts? Anything else applying TU to them will break resurfaced application. If you use Tweakscale Rescaled, you don't really need custom compat cfgs. The older version of Tweakscale is unsupported and not recommended.

It's just due to one of the multiple IVA mods preventing the part from being updated with the B9 subtype's data on launch. The forced-hydrogen patch is the only real workaround, the switchable fuel cells patch just is incompatible with one or more of the IVA mods. Unless they get updated with a fix. I don't even know which ones.

Found the issue, waterfall patch just wasn't updated properly. If you want to fix it yourself now just download the raw file from here (download button is top right) and replace the same file in your local installation.

Noted thanks, something to keep an eye out for when troubleshooting. But I will say BDBNIC is likely just not compatible with BDB 1.14, esp that atlas config. With Resurfaced installed you don't need that reflection config anyway, and all it's extra (old) models, as the new Atlas parts will already have shiny PBR textures. Any Titan configs BDBNIC ships are probably going to be pretty messed up by recent changes too. There may be some parts that have extra paintjobs that still work for now, but it'd take some careful updates for BDBNIC to work with 1.14, and I don't think BDBNIC is maintained actively anymore. May be worth recommending the user just uninstalls BDBNIC. Installing Resurfaced and Shabby 0.4 will enable shiny Atlases too if that's the reason they wanted BDBNIC in the first place.

If you've previously installed FAR and uninstalled it, there may still be a FAR config left over triggering FAR patches. Double check your gamedata for any FAR related .cfg files and remove them.

Do you have RSE?

Ah this seems like it might be a description bug, I think it's probably meant to say the ZE-3-LYC "Zeus" motor, since the real name version of the description mentions the BE-3 solid motor.

Well, there's not very many 1.875m atlas parts anymore, as they're consolidated into just a few tank parts with variants. Should just be the core/extension/conical tanks. I'd recommend VABO and CCK (with the optional CCK patch installed) to be able to find them much easier: If you are still missing parts, I'll need more details/logs.

@jacks @marxman28 If you’re using the CCK optional patch for the custom categories, make sure it’s also updated from the 1.14 download. Various optional patches also had updates

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

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

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. 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.

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!

Shouldn't be any major changes in the last couple of weeks, it sounds like either download or install issues. Try downloading it again, the zip should be about 985MB. Alternately using GitHub Desktop to download it can make it much easier to keep up-to-date without redownloading a GB each time, and it can prevent download errors as it will validate each file after you've downloaded it. I posted about how to download dev branch using GH Desktop here Also updating from 1.13 to dev should be *relatively* safe, nothing should be destroyed on loading as any depreciations are "soft" ones. I've even tested loading a 1.5 year old long-term career save of mine, just updating BDB to dev, and no craft got destroyed. However some parts may have the active variants change on you mid-flight if they had new variant options added to them, and ideally you'll want to update craft files to remove or update any depreciated parts

That sounds like a mod is automatically swapping/updating any instance of the default mk1 cockpit IVA - X-15 is just set to use the default one lol. Glad it works though!

Does TURD apply any shaders to BDB or Tantares parts? If not, you can probably have both without issue. Resurfaced is only used when specifically configured per part by mod authors, and as long as TU shaders aren't also applied to the same parts it should be fine.

They can both be installed at once, as long as parts using resurfaced aren't also getting TU shaders applied to them too.

This mod shouldn't effect it at all. It's possibly due to installing Deferred and not updating CD.

PackedMetal is one of the shaders Beale made for Resurfaced, where each channel of the metal texture can contain a different metal map, and then the material can specify which channel of the texture to use for the metal map. So if you use all 3 channels of the metal map for different materials, you save having two extra metal maps, and the 3 channel metal texture is the same size as a single metal map texture (due to bc1 dds compression). I don't know if there's any difference to memory use in-game.

The metal map will generally be half the file size of either the main or bump textures, so in general only 25% more texture memory per texture sheet (not per part), and that's without using some of the other optimizations available such as the PackedMetal shader (multiple textures covered by one metal map file) or downscaling, which BDB does make use of in many cases. If by performance you mean in-game fps, I haven't noticed any difference personally