CobaltWolf

Yup. It will include two new experiments and the new storage options.

It really is a neat idea! The wanted to stretch the S-1C but the lowest part of the rocket that was structurally sound enough to attach the top mounting hardware was the interstage between the S-1c and the S-II. The SRBs already wouldn't reach, so they just stuck the fuel from the tank stretch on top of the boosters to lengthen them!

According to Astronautix, the second from the right with the 260 inch solids was supposed to have fuel tanks ON TOP OF THE SRBs, to extend them so that they could mount to the interstage. The fuel would drain from them first and they'd jettison when the SRBs burned out.

More parts, you say?

So I just saw the Europa probe NASA wants to do. It looks pretty cool but I can't decide what about it is special.

They're WIP, you can find them in the latest dev release. Also, I'm streaming for a few hours.

It wasn't that much of a performance hit, either. I was still getting ~40-50 FPS on my 560ti. Well, I guess that is a hit (though I feel as if I never reach 60 in 1.1 anyways) but the game is still very playable. And for KSP, it's not like you need a super high refresh rate.

Thanks Beale! I don't know if I even want the normal maps anymore, I don't think I could handle how beautiful that would be. (joking pls finish them they're amazing) EVE/SVE, Planetshine, RealPlume, SmokeScreen, scatterer, Ambient Light Adjustment, and the Blue Harvest ENB + GEMFX + SweetFX pack. The problem is that the ENB stuff which is prolly 50% of the whole 'pretty' factor only works on 32bit... dunno if that will change now or not, with 1.1 out. JJ Abrams called, he wants his lens flares back...

I recognize that pod...

Oh. Oh baby... No, seriously, @Beale check out your Gemini...

@Rory Yammomoto download the source code for the github repo and you'll get the dev version for 1.1. EDIT: @Rory Yammomoto I had just woken up and forgot your specific issue. Yes, the Atlas shroud wasn't working with the last release. The newest dev build has fixed it. TRAILS is getting included in the next release of the mod. The Leo CSM, including the Vinci command pod, will be included. The Karrot is being removed from the mod as it is basically the exact same part with the same dimensions, just not as good looking.

I'm not sure how to link it, but a quick tour through the various Mars landers on wikipedia would likely yield addtional parts such as science experiments. Don't forget about Hyugens as well as the Venera landers re: experiments and other parts. I will also keep a look out for 'proposed' missions. But overall, seems like a very good list to start with. Good variety.

Awesome, I added a link to OP. Hey everyone, I didn't have work today so I'm going to start streaming now. Got a lot of stuff to test and finish up so let's do it.

Thank you @DMagic! Me and @DiscoSlelge will find this most helpful.

Well, there is a 'SHARED' folder. But apart from that, you can delete every folder without it affecting other ones.

Hurray! (It turns out 1.5m is a very useful size for stockalike recreations. It's almost a necessary size if you want real rockets. Gemini and Thor/Delta etc...)

I agree. Anyone who cares enough to want a 1.1 update is already invested in the mod and willing to put up with it. Lol. Good point. Would I be able to delegate this somehow? You can already delete all the non-LV folders, and if you only want certain LVs, you can delete the folders for the other ones.

Holy smokes why did you quote the entire OP

If only more mods supported 1.5m, it would be a standard size...

*shrug* A lot of people don't like having too many parts. I've known for a long time that more people would enjoy the parts if they could pick and choose what to install. I had no idea you could do that. CKAN could index off the Spacedock listings which would be separate no matter what. I don't know if I'd need a core file. I would prefer just to not get that granular with the different packs, but I know a lot of people don't like the 1.5m size and the Redstone parts for instance are tied to Thor.

Ok. Continuing from the discussion over at the OMSK thread , what would be the best way to break up BDB into packages? It's not an easy question. Obviously Atlas is one package. But what gets included with it? Should I include Centaur? Should I include Agena? Agena has parts related to Gemini - do I include it in both? These are the kind of issues that has made me hesitate to split things up. The compatibility files are already modular and shouldn't be too hard to split up. Should things still install to the Bluedog_DB folder, ie not changing the folder structure? If not, that is ~200 part cfgs to change. So that is one big issue - how to split it up. The next is the logistics of it all, which also am not sure of. How do I distribute it? Would I need a separate GitHub repo for each one ( @raidernick and @Jso come to mind for answers) and what would I do with the current Spacedock and CKAN listings?

@Beale would you be interested in a Small Sammy SRB and some other parts for the Taerobee? @VenomousRequiem wants to practice making some sounding rocket parts and I think they'd go better here.

@above commenters who replied to me I completely understand the sentiment of BDB being too heavy (I often have to spend a bit too long finding things in the VAB) and as much as I'd like to ignore it, the mod really is overdue for being split up. The problem is, while it is modular to an extent, there are some... unfortunate decisions that were made. For example, the Vanguard, Thor, and Redstone rockets share texture sheets for their tanks. So any pack that includes one would have to include all of those. Apart from that, I cannot think of too much else that would present an issue. The next question becomes, how do I split it up (ie what to include in each pack), and how do I transition to a new distribution method? However, that discussion should continue over at the BDB thread. @tjsnh I know SnowWhite posts in the Russian section of the forum sometimes. Perhaps @Niemand303 has a way of contacting them? I know @VenomousRequiem has him on Steam and can likely get a hold of him. I'd rather OMSK stay an option rather than have it completely die out. In any case, since you *do* have those files, make sure to back them up before something stupid happens and they are lost forever!

Are you sure? I don't want to jump and assume the issue isn't somehow on our end.