SpeedDaemon

I've found that using a standardized recoverable SSTO boost stage makes it much easier to be consistent with the landing. In my case I primarily use it for putting ~20T station modules in orbit, so it always begins its de-orbit from a 130km circular equatorial orbit, which also makes things easier. (I know that it takes exactly 100m/s burn at 160 deg E to hit KSC) It's expensive (70k funds for the booster), but at 98% recovery, it's still difficult to be cheaper, even for fairly small stuff. If you can standardize your boosters, and flight test a few standard pre-return orbits, you can be pretty consistent and not have to drag stuff across the surface.

There's no way to get a satellite constellation to stay put using in-game methods that I know of. Maybe a mod I haven't found yet... Here's a post of mine from last year on how I handle this:

Here's how I usually handle stations (around Kerbin, anyway): 1. I use a reusable SSTO rocket that can put about 20T in a 200km orbit (my stations are usually at around 130km), and return via parachute (because it's quick and easy, and I'm lazy). 2. I start with a core module that's basically all 2.5m docking ports and reaction wheels. 3. Send up modules for habitation, power generation, and fuel storage to get things started. 4. Anything else is added on an as-needed basis. 5. I like to pre-place KAS strut endpoints in the VAB in case i need them later for stability. They can be removed later to reduce part count if you don't use them. I use one of the aforementioned "orbital fork trucks" to move modules around in orbit (basically probe core and fuel, main engine, and two long spars that fit around the 2.5m modules with RCS at the ends). All station modules are designed to fit within the limits of the launcher and orbital tug. I usually keep a small utility craft docked to it with KIS containers full of small solar panels, antennas, science gear, etc. that can get to the Mun and Minmus and back for fixing design errors and rescuing Kerbals.

If you don't already have it, get the RCS Build Aid mod. It will show you full, empty, and average CoM at the same time, which is great for balancing space planes. Now that fuel drains evenly, I've had a pretty easy time of making craft where the CoM doesn't move at all as the tanks empty just by re-arranging the fuselage segments (using "short" versions gives you more flexibility and makes this easier - when you're done, you can replace any adjacent ones with long segments)

Nice! Just finished this. Also, it's been a year, and am I really the only one that noticed the Starship Troopers reference here?

The big reason: If you have limited funds, getting fuel to LKO from Minmus is cheaper than from the surface of Kerbin. Everything involved is reusable, and the fuel is free! Having a lot of cheap fuel in LKO means you can either launch larger craft empty, or use their fuel for ascent, which drastically reduces the size/cost of your launches. I also like to have a few high-TWR reusable stages at the station that can be docked to inter-planetary craft to kick them out of Kerbin SOI, then return to refuel.

Good Start! I would actually suggest making Reactors and Heat Management part 2, since that's a prerequisite for a lot of the other stuff. Might also want to note which version of KSPI-E these are for.

How are you CoT and CoM aligned? How does that alignment change as you burn through your fuel? Also, are you actually launching that with it starting rotated 45 degrees off of a cardinal direction? Rotating it so that "up" for the shuttle is 90deg might help some.

The other thing about Moho is that it moves so fast in its orbit that splitting a burn can put you far enough off of your target transfer window that you spend more dV correcting later. Usually for Moho xfers, I spend the extra effort to get as high a TWR as I can for that first burn, so I can get it over with as fast as possible.

Well, there is, sort of... The way I've handled this in the past is to build my satellites as if there was some kind of station-keeping facility (usually just including RCS thrusters, and 2 or so units of monopropellant per year of planned lifetime). Once they're launched into the proper orbits, edit the save file to make all of the satellites in the constellation have exactly the same orbital parameters, with no digits after the decimals, and the proper phase separation. They will stay perfectly lined up as long as they stay on rails (you never fly them, or get close enough to load them into physics). I don't really consider this to be cheating, given there's no other way to do it that I know of, and I'm spending the extra mass/funds to outfit them for station keeping. Same technique might work for placing craft at L4/L5. Once their station-keeping fuel is "used up", you can send a "refueling" mission, or replace them, or whatever.

I have a reusable SSTO lifter like this based around an orange tank/Mainsail, with 8 Whiplashes radially mounted to it on the 1.25m 200u tanks. It can get ~18T to LKO. During ascent, you have to toggle the mainsail on/off strategically to get the TRJs to where they produce enough thrust, and the margins are pretty slim, dV-wise. Pros: - Simpler ascent profile than a spaceplane-type SSTO - Lands on its tail via parachutes, so that's easier than landing a spaceplane on the runway - Can fit things under fairings that won't fit in spaceplane cargo bays Cons: - Hard to pinpoint the landing, so never get the full 100% refund, which matters, because: - It's expensive (~70k for the re-usable part) - The different kinds of fuel flow (jets vs. rockets) are difficult to manage without TAC fuel balancer (the jets will steal LF from the whole craft unless you actively do something to stop them)

I would highly recommend checking Slashy and Val's profiles for some of the SSTO/spaceplane-related threads they've posted in, and reading those. Those two are almost entirely responsible for my spaceplane ability going from "500 engines and no space for you!" to getting a 190T beast of a Mk3 spaceplane into orbit, and back to the runway (after Valentina dealt with some fuel-balance !fun! during reentry) using only five Rapiers.

For boost stages, design the rocket so that they're staged off before your PE is out of the atmosphere. Design the next stage (for LKO-only missions) so that you use it for your de-orbit burn as well. For Mun/Minmus missions, burn so that you'll hit them, then stage off the transfer stage, and adjust again so you have a PE. Or keep the xfer stage long enough to get into a sub-orbital trajectory before you dump them, then either land or circularize again. Some amount of debris is going to be inevitable unless you spend a lot of effort. It could just be left up there until you have the tech to go get it.

In the new aero model, you're almost required to have fins at the bottom of the rocket for stability. Your previous designs probably don't have them. Also, make sure you cover anything aerodynamically "dirty" at the top of the rocket with fairings, and keep weight as far towards the nose as possible. You can't go straight up to 8k and tilt way over anymore, either. Start your gravity turn at about 50-70m/s by tilting over 2-3 degrees, and then follow the prograde marker. Pointing your rocket outside of the prograde circle too low in the atmosphere (below about 35km) will often result in RUB-ing. (rapid unplanned backwardness) Slowing down a bit lower in the atmosphere can help, too.

If you're going to dump rep, you might as well get some funds or science out of it by doing it via the admin building strategies.

Remember that when you use maneuver nodes, the longer the burn, the less accurate the node's trajectory prediction will be. This is fine for most planets, but Moho is the exception. It orbits quickly, so unless your burn is short, you'll be far enough off the node's prediction that you'll miss your encounter, and have to spend a lot of dV to adjust (and it can be a lot!). The inclination of Moho's orbit just makes this worse. So, Moho is one where I'll usually spend the extra funds/effort to get a beefier transfer stage for the Kerbin->Moho burn. (I like to just refuel the core boost stage, since it usually already has good TWR)

For a relatively large lander like that, you might be better off getting the lander to LKO with one launch, then getting a more efficient transfer stage into LKO with a second launch (and maybe more fuel with a third). If you have to dock to the transfer stage anyway, it also means you can use it to get back home, which means you don't need to haul that engine and fuel (and long-term life support equipment, since you're doing that) down to the surface of Duna and back up.

Wait, then what's this: Granted, not a hybrid rocket engine...

If docking is the major issue, have you tried KIS/KAS? You can connect with either a rigid pipe, or a flexible winch/hose, which might work around the problem. You can add the attachment points with KIS tools to the existing base with an EVA engineer.

Is MET all that counts for "new craft" regarding contracts? If so, then based on this thread, it would seem that if you can get the root part of your station to be some small, insignificant part (not critical to contract completion) separated by docking ports from the rest of the station, you can reset the MET for most of the rest of the station by un-docking it from the root part, at which point it should get it's own MET reset to zero. So the procedure would then be: 1. Dock updated hardware to station 2. Un-dock from root (contract completes) 3. Re-dock to root Not sure how the root part of a station moves around as you dock/un-dock, though.

Assuming you're in an equatorial orbit of the Mun/Minmus: Imagine you're looking "down" from the north pole (so your equatorial orbit is going counter-clockwise), with Kerbin at 12 o'clock. From the Mun, you generally want to burn prograde when you get to about 2 o'clock in your orbit. I usually don't bother with maneuver nodes from the Mun, since its orbit isn't inclined. Just burn prograde until my Kerbin PE is where I want it. From Minmus, you can wait until you get to 1 o'clock or so. Here, (or from an inclined orbit of the Mun, or if my dV budget is really tight) I usually will drop a maneuver node, because if you want to land at/near KSC, you'll probably want to fiddle the normal/anti-normal controls a bit to make your eventual Kerbin orbit have as little inclination as possible. If you use a maneuver node, slide it along your orbit so that the exit vector is as parallel to the Mun/Minmus's orbit around Kerbin as possible. When you do this, you can easily see the effect it has on the required dV by watching your Kerbin PE change.

I prefer about 130km for my Kerbin stations. - It allows 100x time warp to cut down on rendezvous time (cut-off is 120km) - Low enough to reach with spaceplanes - High enough that you can put your PE below it without hitting atmosphere to make rendezvous easier

Are you using the KSP store download version, or the Steam version? Running as admin will mess up anything that looks in the user profile directory for files. I've not used the Steam version, but if so, it might not be allowing the loading of mods from a protected folder (Steam's default program files location). Can you uninstall, and try installing it to a custom folder or something, and see if that works without running it as administrator? Or try the .zip download version, and put it somewhere your user has full rights to. EDIT: reinstall KSP to a new location, not Steam

The KSP process memory usage isn't affected by the number of parts on the current craft so much as having mod parts loaded when the game starts. Just having a lot of extra parts installed will cause problems, whether they're on a craft or not.

If you're still a ways out from the Jool system, it should be pretty easy to adjust your arrival time to get it to work. If you're already in-system, it might be a bit harder, depending on how far out you are, but you should still be able to fiddle with a node to see if you can get the timing to work out for a reasonable amount of dV. EDIT: (usually, I have trouble *avoiding* encounters that I don't want...)