CobaltWolf

Yeah I still need to figure the parachute thing out...

I'm tossing in another vote for New Horizons. The first time I saw Sonnah (Blue gas giant that Kerbin orbits around) rising over the horizon... phew, I could never go back.

Here's a dev release. Most of the new stuff has been brought up to release status (names, tech tree placement, descriptions, balance) and the Agena fuel tanks are included. EDIT: Oh and there's that new probe core I showed a few pages back.

Did you set the animation in Unity? You need to click n the model asset, set the animation type to 'Legacy' in the middle tab, and then make sure to name the animation the same as what is in your cfg, in the third tab.

Looks fantastic. But I thought you got rid of the blue Gemini in favor of a gray one?

I still need to fix a lot of things with the Mercury stuff. I know the parachute still deploys sideways (does it?). I didn't know about the rest of it, I'll look into it.

Mars Pathfinder? With Sojourner? I have a small list of rover parts I want to make once 1.1 brings an update to the way wheels are implemented. As far as Sojourner goes, I think you can pretty much make that using stock parts. I don't know about Pathfinder. In general, when I go to make probe parts, I haven't been making the whole thing. I've just been making bits and pieces I see that I think are useful or look cool.

Yes. It's a matter of TWR. I use Kerbal Engineer, and keep an eye on the TWR readout. Once it reaches around 2.5-3, I jettison the boosters. EDIT: Here's a dev update. Contains updated names/descriptions for many of the parts, as well as the Agena A and D engines. Does not have any of the other Agena parts. This is mostly so Venom can start making RP configs, and A1Ch1 can start making RO configs.

Here's a sneak peek at the new system we're working on, using KAS/KIS. Players will have to assemble a full experiment package using an engineer kerbal. First, you place the central station, part that makes everything run. There is a pad on the central station for mounting the power supply of your choice, either an RTG or solar panels. There is a pole and solar cells provided for players that haven't yet unlocked an RTG. Then, experiments are placed and connected back to the central station via power cables. There will be two types of multi connectors that you can use to split the cables or redirect them (see screenshot). The experiments are then activated via a Scientist kerbal, and their results transmitted back via the central station. Running an experiment takes power, and bigger setups will want to connect batteries to the system to make sure you have enough headroom. RemoteTech/AntennaRange/the upcoming stock relays will likely need to have their results forwarded home via a larger dish/antenna mounted on your lander. So, to reiterate, what you'll need: Engineer kerbal scientist kerbal Power connectors (two for each connection you'll make, due to KAS limitations) Central station Power supply Experiment(s) (optional) Power stations - give you additional power ports and battery storage.

I'll push the engines through Unity and get a dev release out next chance I have to work.

Don't apologize! It was certainly a worthy critique, especially because I am particularly stingy with my textures. The Brun tanks/fairing aren't exactly low res, it's more that I didn't want to include any stripes on them. I haven't touched them but I can look at them after the upcoming release. While there certainly is a bit more leeway with 64bit, memory/size is still something I'm leery of. Perhaps some day soon I'll be able to drop the habit. Also, I have a general question for the peanut gallery. I put a lot of time into BDB, but it looks like it may not be enough. Between that and SEP (see sig) I don't think I'll be able to get everything done for this update before Christmas. I'll need another day or two of work to finish Agena, and another day or so after that to clean up the rest of the things laying around in order to push out a release. My question is: Should I try and package a new release before Christmas (basically move a bunch of things planned for this release, that I haven't had time to start on) so y'all have a new one to play over vacation, or should I just keep doing what I'm doing and release once the 'todo' list is done. This list is only things that still have to be done for the update. It isn't inclusive, and is missing things such as giving all the parts names and descriptions, and balancing them, both of which are required for nearly all the WIP parts. It currently contains: The starred items are items that tentatively would be cut from this update and pushed to the next, which would probably release near the end of January or even February, what with all the stuff that's going in it already. Also, I need suggestions for names for the Agena parts, including Series name (IE Muo, SSR, Brun) Agena A casual name (IE Reliant, Terrier) Agena D casual name Secondary thruster casual name Probe core casual name Additionally, I need casual names for: Pioneer/Venera Probe core Lunar Orbiter engine casual name (its in the latest dev release) Cheers!

I forgot to reply to this. Do you have any particular parts that have that issue? Many of the launcher parts were 'low res' because I didn't have time (read: forgot to get around to it before release) to add detail to the textures. The next release has tweaks or complete reduxes done on most if not all of the launcher textures. I'd also like to point out that 64bit does not give mod authors a free pass with their mod size. Because KSP will still not have a proper asset loader, the textures still have to be loaded in on startup. So keeping the overall size of the mod down will help keep load times down. At the end of the day, I am going for the resolution around that of stock parts. Most of the parts in the mod are about where I want them, the new Atlas V being a big exception that I will redo after I finish this update. I will definitely look into increased texture size in the future (for example, on the new Agena I am using a 1024 texture map for something I previously would have used two 512 textures before)

It's not even my cat. I don't like cats. I got conned... Anyways, it looks like I'll only have another hour or two to work today. The good news is 1) the worst part is behind us I think, because 2) This is what I have so far. Their textures aren't quite done, but I think I'm going to move to other pieces right now. It looks like what's left is: -Secondary engine module (modeled, needs UVmap and texture) -Tanks, 3 (4?) sizes. -Probe core I also graduated up to working with 1024 texture maps so there is plenty of room left for, for example, an antenna, or the ATV docking module. Let me know if there are any other Agena things you'd like to see. The engines wound up being a bit long, so they'll have some LFO in addition to monopropellant. In terms of balancing, I was thinking of making them fairly expensive, seeing as Agena is a pretty capable upper stage, with it's own RCS, probe core, etc.

xD EDIT3: Bringing this as close to the top as I can. As Curt stated higher up in the thread, the Agena does indeed scale to .9375m. What would people prefer: .9375m Agena, or 1.25m Agena? I personally would prefer 1.25m, if only for gameplay - BDB doesn't have a 1.25m upper stage yet. But it could also expand the .9375m parts... I'm modeling it at 1.25m, and it can easily be scaled down later. EDIT: Forgot to make the actual post I came here for... inhales deeply Ahhhhh a blank canvas. Now I know how Bob Ross feels. What shall we create today? EDIT: If this little nerd ever lets me get to work... EDIT4: Agena D model is coming along well I think. EDIT: Wheee~~~

In the top toolbar, there is a black box with an i in it. Click that, give it the album code (the part of the link after the /a/) and it will insert an album.

Yes.

I'm just gonna leave these here...

Did somebody say retroreflector? Again, to reiterate, this is not for BDB. It's something I've been working on for a while with someone else. We are hoping to get a release out in time for vacation. Keep an eye out, it will be added to my signature.

Thank you so much @A1Ch1 and @curtquarquesso you've certainly given me a lot to think about! I'll be cooped up inside all day tomorrow watching my friend's cat so it seems like I have my work cut out for me. DING DING DING DING But what could it mean?!?

The inflatable hab is from CONTARES

*cough*knewit*cough* What options do you have? Perhaps increase the diameter of the colliders slightly, without increasing the size of the mesh. That may improve stability.

Pretty much the whole thing to the right of station 384. The issue is that Agena went through many different revisions. The style most KSP players are familiar with is the ATV, or Agena Target Vehicle. But I'm trying to make the Agena Upper stage, which is fairly distinct from the ATV. Or rather, the ATV looks a bit different from a normal Agena upper stage. I'd like to take a moment to add that the ATV is not a priority for BDB, and parts such as the antenna and docking interface won't be provided. At least no in the first release. For some reason the Agena has been something I can't wrap my head around since the very beginning of the mod. I have tried several times to design it with no success. I think a lot of time this weekend will be spent with just a pen and paper, drawing it over an over again. Well I'd hope so! EDIT: Ooooh, what could it be? Hint: It's not for BDB! Super mega bonus for anyone that can recognize it.

I edited my post upwards in the thread. Not a full tutorial yet. I'll get around to it. One day haha.

That doodle is adorable. I vote you make a Doodle pack that is in that art style. What roles do the three engines serve? Remember the various things to balance engines around: Thrust is the obvious one, but you also have ISP and weight. There is room in the stock balance for, example, a less efficient but lighter 1.25m orbital engine. When dealing with small amounts of fuel, lowering the weight of the overall system can count for more than the ISP of the engine. That's why the Spark is often better than the Terrier. Overall the parts look good. Make sure to take a look over in the Texturing and UV Mapping megathread for advice on texturing. Your models look good, but the textures could use work. The biggest things I see is there isn't enough variation. KSP parts have lots of scuff marks, scratches in the paint where bare metal is exposed. When I texture, I have several layers I work with to combat this. One, I have a 'Light Edges' layer where I lay in scratches and scuff marks along the edges that would be exposed to wear. Edges in KSP are, as a rule of thumb, always lighter than the surrounding parts. They are only darker when two big panels come together and you want to show there is a small gap. I usually work with this layer inside a layer folder of the same name. There is an 'outer glow' effect on the folder, with the noise set at 1 or 2. Having the effect apply to the folder, and not the layer, means I can create multiple 'Light Edges' layers for when I don't want to worry about messing one or the other up. Two, I have an 'Edge Smudges' layer. Around the inside perimeter of every panel, just past the light edges, I run a 3% opacity, soft black brush once or twice around, very quickly/sloppily. This helps further add variation, because you have the panel's most extreme light and dark next to each other. This layer often has to have extra blurring applied, and if I get too zealous, lower the opacity. This layer works best when it's hardly noticeable. It should be something felt, not seen. Three, I have a 'Smudges' layer. This is pretty much what it sounds like. Take a big, soft, 3% opacity brush and run it across the canvas somewhat randomly a couple times. One or two of the passes can be tinted brown for faint fuel stains or rust. Because you have to be mindful of your UV layout with this, it can be helpful to use selection boxes to work on one section of the texture at a time. This layer is purely to add light / dark variation to your texture. Never leave something a solid color. Break it up with some smudges. Sorry for the wall of text. I started off simple then wound up writing the whole megathread post I've been meaning to make. Oops.

Darnit @curtquarquesso xD Now look what you've done! Am I expected to make Angara now? No, I annoyed you because you're good at 1) scaling and 2) your google-fu is better than mine. I am having trouble figuring out how to break up Agena. I'd like to enable the maximum number of configurations with the smallest number of parts. The problem isn't so much the tanks but the engine section - the best way to break it down. My initial thought was to have the secondary mono engines be radially attached to the last section of the fuel tank (the part that necks down), but that's not a fuel tank. It's basically the body around the engine. So if I make the whole thing (including the adapter section to the main tank) the engine, then that at least solves the issue of the fairing, since then I can make a full length one to cover the whole engine section. But then what do I do for the secondary engines?