Dave Kerbin

Innes 1 (Part 4) I was originally planning on trying to burn back to Kerbin directly from Laythe orbit to take advantage of the added velocity. However I'm not sure it would work and from my low orbit I was concerned I could hit the atmosphere so I made a simple burn to exit Laythe's orbit and make the return to Kerbin from around Jool. With so much weight shed the ship can now turn easily on RCS, speaking of which I transfered the remaining RCS from the 6 tanks hidden in the center (visible in part 1 in the rear shots) to the probe's own tank to refill it. Out in Jool orbit I found that I couldn't burn directly to Kerbin either, as my orbit was going to reencounter Laythe around the time I needed to burn. I played around with some minor adjustment to my orbit and got a path that would boost me past Laythe using its gravity to pass Vall and get another assist from Tylo to steady my orbit up there. It will take a 1638 m/s burn to reach home but I know I'll have enough since the outer transit stage is still left and the inner stage has around that much by itself. With 500 m/s burned from the outer stage it is finally shed and the return stage is used to complete the burn. This also reveals the pair of NUK NUK reactors that have been providing the power for this trip. On the way home a minor correction is made to bring my PE within a few hundred km of Kerbin. After entering Kerbin's SOI and passing the Mun one last burn is setup, an intentionally inefficient burn to lower the PE to 26 km that will also slow the ship down by almost 400 m/s. I simply consider this a good use of the remaining fuel that will hopefully ensure a safe reentry. With the batteries held at a full charge the entire trip the return stage is discarded to burn up. After the effects of reentry are over (velocity was over 4 km/s but the shield still had ablative material left over when it was done) the heatshield is detached and the parachute armed for automatic deployment. The probe comes in for a smooth landing and the science is recovered, completing the mission. This completes this playthrough of BTSM.

Innes 1 (Part 3) To ascend I need to wait until the transit section has orbited back around. There is a small issue of it being in a retrograde orbit so I need to launch in the opposite direction. All of the landing equipment is dropped as soon as the probe takes off. I had considered several engine configurations for the probe but using the large tank I found only two real options, the Poodle or the 8 radial rockomax engines. Both had similar delta-v values so I took the lighter and shorter version that used the little radial engines. I still have plenty of electrical power but ascending I start to get really worried about fuel. It's draining really fast. I'm basing my ascent profile on how I launch from Kerbin but referencing the atmosphere scale instead of the altitude reading since the atmosphere on Laythe is lower. As I reach the start of the gravity turn the fuel tank is almost half empty which is not good. I thought I had a good idea for the delta-v requirements - 2800 m/s min and 3200 m/s for safety. While the atmosphere makes it hard to determine my average ISP during the ascent I was expecting about 3000 m/s (worst case burning at the surface the ship would have over 2750 m/s unless Laythe ISP is even lower then Kerbin). Maybe it was my ascent profile (it didn't look good at the circulization point where I had to spend 782 m/s) and maybe it was because I was going into a retrograde orbit where I was losing out on the free velocity from the moon's rotation but I barely made it into orbit. I entered a 55 x 71km orbit and when I looked I had 0.67 L of fuel left in the tank. There are only two things going for me. The first is that for the moment I have plenty of power which means I have some time (about 5 hours in the current configuration). And second I made it into orbit with very little RCS used, I relied on the excessive amount of thrust vectoring I had at my disposal for everything but lining up the circulization burn. You see the original flight plan was to enter orbit and rendezvous with the transit section. That section would be dead in space since it doesn't have a probe core which means that any little bump will send it into an uncontrolled spin. To dock when in RCS range the little top part of the probe would detach and move in. It's light weight would make docking easy and it carries it's own 40 minute power supply in addition to all the RCS gear, science instruments and probe core. With the probe almost out of fuel the plan changes. I'll need to seperate much earlier so I can use the RCS thrusters as my primary engine. With just the docking segment I'll have almost 300 m/s of delta-v to work with which I'll need in order to cover the inclination difference. KSP .23.5 introduced a feature with manuever nodes that lets you place them one or more orbits into the future. I used that to peek ahead and find that if I waited 2 orbits I would have an opportunity to setup a close encounter of about 8 km right at the point where the 2 orbits crossed each other (descending node). It's a cheap maneuver at just 4.6 m/s so it's ideal for my purposes. Prior to executing it I charged up the batteries on the docking segment so that I could seperate - at this point I was assuming that I'd need RCS to complete some of the burn. Fortunately I got really lucky. The fuel was enough to complete the course change with 0.08 L now remaining in the tank, about 0.5 m/s based on the previous performance. At this point the liquid engine is useless but by completing the entire burn with it I still have the battery (in hind sight I should have really planned to complete the entire burn with the full probe attached even if it would have wasted RCS, as battery power was the more essential resource at that specific point). Approaching the closest encounter point I charged the docking batteries again, this time locking down both of them so that only the probes battery was being drained. This way I could keep that battery charged right up until the moment of seperation. The docking section seperates leaving the ascent body behind and executing a 129 m/s burn with RCS thrusters to zero out the relative velocity (roughly matching orbit and inclination) and bringing me down to 30 L of monopropellent. From here I start a series of burns to try and quickly bring the docking section to the transit section. I don't want to burn too hard as any speed I add (change of orbit) will have to be undone to dock. Instead each small burn puts me about 2-3 minutes away from my next close encounter where I roughly half the distance each time. 15 minutes after seperating I am within 150m of the transit section. I'm approaching from behind (in relation to its docking port) so I'm going to need to pass it and turn around to dock - the transit stage is inert so it can't turn to face the probe. I have 14.68 L of monopropellent left having burned half my supply to rapidly reach this distance and match orbits. At this point final docking is easy since the probe is so light, ensuring that the magnetic docking port can easily pull it in and dock without disturbing the transit stage. As soon as it docks the probe recieves power and begins recharging its batteries. With plenty of fuel, mono propellent and an unlimited power supply now attached the probe should be able to make it home after the close call during ascent, which again ironically was the stage I had planned and checked the most before launch.

It sounds like the intercept rather then the docking is where you are having the issue and that isn't something related to size. You may need to scale back and brush up on your approach and docking before you try it with a large station. If the ships are shooting by each other then you are going way too fast which again sounds like you haven't learned basic docking before trying it on a more advanced scale. The approach is just 3 simple steps repeated until you get as close enough to dock using RCS thrusters 1. Within about 5km point toward the target indicator on the navball. Burn to add a small amount of speed - the closer you are the less speed you want to pile on. At more advanced levels you'll learn that you really want to manipulate your velocity so that your prograde indicator overlaps the target indicator. 2. Coast toward your target. The map screen will show you the closest you're going to get with your current direction and velocity. Wait until you are there. 3. Cancel out your relative velocity by checking that the navball says 'Target' and then burning in the direction marked retrograde until velocity is at or near 0 m/s. If you are close enough to dock with RCS do it, otherwise go back to step 1.

Innes 1 (Part 2) Now in low orbit around Laythe I need a place to land. There is a continent on the right but it passed into the night side as I entered orbit. The current day side is almost entirely ocean with no land mass near the equator. Fortunately as I approached Laythe I noted that it had a quick rotational period so I should have to wait too long. Five and half hours later the planet has turned, first revealing a single island at the equator before also revealing the large continent I observed earlier. However with daylight to help study it from orbit the continent seems extremely mountainous near the equator and is not much thicker there compared to the island either. With the landing site picked the probe detaches on the dark side of the planet. It has a 6 hour battery supply to make the landing and return. For the descent I have about 600 m/s though thrust is low. The descent engine, fuel tank and some monopropellent (to avoid wasting any of the ascent supply on the way down) are mounted outside the heatshield where they will be destroyed. I have learned that this doesn't affect the functioning of the heatshield so there is no seperator for them. On the dark side I lower my PE to just above the atmosphere on the light side and plot a manuever to hopefully land me somewhere on land. The burn needs to start very early so my target isn't even on the horizon as I burn for almost 2 minutes. About 70% of the way into the burn I pause while the projected path is still off the coast of the island. I'm not entirely sure about drag and I don't want to undershoot. As soon as it is clear I won't undershoot the island I burn to close up the path to the coast so that I can't overshoot. It takes a while to reach any significant atmosphere. Reentry effects don't start until about 23km when the monopropellent tanks on the descent stage explode and they don't last very long. Both the engine and fuel tank don't heat up enough to suffer damage so once it has slowed down enough they are ejected with the heatshield. The landing legs are deployed to get them out of the way of the parachutes just before they are deployed. During the soft portion of the descent the one spare Goo container is used to sample the atmosphere. I'm coming down in the center of the island toward a relatively smooth desert. After soft touchdown the main Goo container is used and a Double-C reading taken. The next phase will be ascent back to the transit stage in orbit.

Innes 1 (Part 1) There is a new version of BTSM so I really wanted to get this wrapped up. I felt I had a design for the landing/rendezvous but only had a set of estimated delta-v numbers for the rest. I don't have fuel lines so my normal method of making an efficient ship for this kind of journey was out. Instead I just tossed together something very fast - it's very ugly and overweight (launch efficiency is 11%) but surprisingly the system that nearly lost the mission was the module I had spent the most time on. I had also been considering layouts that would add more science instruments but ultimately dropped them. The goal is to get a sample and return. You can see the launcher is big - this kind of ship won't fly after I update to the latest version based on the launchpad restrictions I've read so far. It was also built even faster then the transit stage without checks or revision which is only possible in .23.5. As the fuel is almost empty on the first stage it starts to bend wildly, things stabilize after that. There is a lot of mass to be pushed with 6 poodle engines so I spent the remaining fuel in the 2nd booster stage to raise my orbit to 250 km. This way I'll avoid entering the atmosphere during the burn. After I finished the circularization I ditched the booster with a little remaining fuel so that I could fire the main transit engines for a brief second and calibrate the manuever node's burn time indicator. At this stage changing orientation is a slow process, I've burnt about 80L of monopropellent. It's a 1924 m/s burn to make the Jool intercept that will take 12 minutes to complete and consume seven and half orange tanks worth of fuel. I've shed almost half the ships weight. 66 days into the trip a pair of course corrections are made. The first one tightens up the approach to Jool, burning 74 m/s to bring the PE from far beyond Bop and Pol to below Tylo's orbit. This burn is immediately followed by a smaller (4.1 m/s) but much more precise burn to setup an encounter with Laythe. This is all thanks to PreciseNode which lets me plan and execute this burn from over 200 days out. Enter Jool's SOI a final course correction is plotted (16 m/s) to fine tune how I'll enter orbit around Laythe. Jool is still a small dot but it's gravity extends far enough to be felt almost 2 weeks before arrival at Laythe. Another 4 orange tanks worth of fuel are burned to capture around Laythe into a 69 km orbit. It's not quite equatorial (later figures suggest I'm inclined around 2.5 degrees) but it's close enough to support a landing and return. I'm ahead in fuel for the transit section and should be good for the return trip as long as I can actually make the landing and return.

I'd really have to test out the engines, I rarely if ever use the jets so my ability to estimate the correct amount of fuel, thrust and intake (and avoid intake spam) wouldn't be easy. I think I only have the basic engine and intake part wise. I have thought of doing some kind of plane since that would make it much easier to make a precise landing, but like I said I have very little experience with them, I don't think I have the small control surface part, and I'm completely in the dark as to what kind of heatshield I might need to allow it to enter the atmosphere for a landing without breaking up.

Still working on things when I have spare time. I found the main design restrictions where thrust for lift off from Laythe, low center of gravity for a safe landing and finally fitting it all inside the heatshield. One option which could still be viable is simply using a large 16X fuel tank (720L) in a single stage lifter. It would need to use the Poodle engine to provide enough thrust (I also looked at radial rockomax engines but the ISP was too low). Another option is using an adapter so I can link together multiple engines - but that doesn't seem to work well for center of mass. Finally one option I've brought all the way to the prototype stage is using the tiny booster rocket. Two provide enough thrust for lift off from Laythe and 6 (3 stages) combined with a small liquid tank and engine for final orbit. The design certainly looks nice but I think it might simply be heavier then just throwing on a big fuel tank.

If you have BTSM installed then there are two things: First you almost certainly don't have enough solar panels to power a small city (unless you have access to the 16,000 science tier 9 ones). Solar panels and batteries in BTSM are vastly scaled back. If you have more then one probe core you are draining a lot of power by BTSM standards (you can right click to turn off probe cores as long as you have one other command part to turn them back on again) Second have you updated to the latest version? The mod has been updated in the last month or so to work around some limitations with how stock handles power generation/consumption when you are timewarping. Right click on your solar panels and see if they have internal batteries.

I'm still in the early concept stage for a Goo return mission to Laythe. I've unlocked the technology I think I'll need. I've unlocked all the normal engines now including LV-909s, LV-45s and Mainsails (LV-N and ion are still locked) and all the fuel tanks including the large diameter ones. I've unlocked the decoupling and docking parts in all sizes. I've unlocked radial decouplers and the very large heatshield. Finally I've unlocked the most important part, the NUK-NUK reactor. There are some parts which I don't have unlocked however: in addition to the ion engines I don't have fuel lines, advanced batteries or inflatable heatshield. I also don't have the final set of probe cores, the retractable solar panels or cubic struts for mounting things in odd places. Since my best probe core consumes 2 em/min I'll need to carry 2 reactors with me to Laythe orbit and back to Kerbin. No fuel lines means that staging will need to be simple. Design a lander/return craft that can reach Laythe orbit is also challenging due to the parts - the extra large heatshield is still not as big as the inflatable heatshield and that greatly limits how wide a ship I can land. I may need to try an orbital drop test to see if small diameter parts can be radially mounted to other small parts and still be considered inside the shield. Visually it looks like they are a bit over the edge but I've found the heatshield mechanics might not be based on that. That width also poses problems for engines, I need a certain amount of thrust to take off in Laythe's near Kerbin gravity.

Hall 1 While I could gain some more science around Kerbin I want to get out and explore. My final destination is an (unmanned) landing and sample return from Laythe so Eve is a good stop where I might get some experience in precision landing. From the tech tree I'm unlocking several parts but banking the rest of my science. I'm getting the basic solar panels, the first item to cost 360 science. I'm unlocking Precision Engineering (which also gives me the radial RCS tank) in order to reach both Miniaturization (interplanetary antenna) and Unmanned Tech (2em probe with built in SAS). And finally High Altitude Flight is unlocked to get the Sensor Nose Cone. I'm not interested in developing a seperate launch platform for this mission. The blueprints for Gamow 1 are brought up and everything above the heatshield is removed (pod, RCS tank, parachute) and then the landing legs and old batteries are taken off as well. Assuming I keep the same launch weight this platform should provide all the delta-v needed to reach and brake at Eve. Including the heatshield and any other addons I make I have a healthy budget of 20 tons. The probe is mostly batteries. With Eve's thick atmosphere I won't need many parachutes (my previous Eve lander had many parachutes because it was a design intended to land on Duna too). The old 'lander' portion is now a second orbital stage. I examined several solar panel arrangements but I was never happy with the look, it's hard to arrange the big panels in a way that looks aerodynamically credible, it would be nice if they came in a package that could be unpacked a single time and didn't have sun tracking. With a lot of spare weight I ended up just coating the ship with solar cells. I'm still under the weight budget by several tons and it means I have little to worry about when it comes to correct alignment. After waiting for a window launch is pretty standard. I did make a mistake, I had intended to collect sensor nose cone readings for Kerbin and that lost me 80 science. Fortunately the expected science return for this mission is big enough that I should be able to unlock everything I want even without that experiment. With PreciseNode it's almost too easy to setup a course to Eve. I dropped the node in by hand, typed in 2 numbers and I had a transfer already setup. I made a tiny change to the time in order to lower the PE and then I was ready for the burn. Out in deep space temperature readings can be taken and beamed back to Kerbin. Solar alignment isn't really an issue as long as I don't point the nose or the tail at the sun. As I approach Eve I setup a course correction to set my PE to low orbit, make sure it will be a prograde orbit and to put it roughly around the equator. This is helped a lot by the conics model that I seemed to have stumbled into which lets me easily see my approach. It will take 1600 m/s to capture at Eve without aerobraking. The 1st orbital stage runs out of fuel after the first 1000 m/s so the 2nd stage is started up to complete the rest. Orbital readings of Eve are taken and then the batteries are given a chance to recharge (solar power provided some assist to the transmission). In addition to the science my goal here was to try a precise landing. I spotted a prominent dimple above a darker area and decided I would try to land there. However I ran into a few problems. One was that I was already very close to it in my orbit and so I really started burn far too late. I also didn't really have enough fuel to completely stop over the target, I misjudged my orbital velocity (going much faster over Eve compared to the Mun or Minmus) and really should have been aiming for a longer approach. Realizing this I stopped my burn before my descent path came too close to one of Eve's smaller seas. You can see the dimple to the left of the sea and my descent which is going to be to the right of it. I realized I didn't have the fuel or the TWR to avoid falling into the water if I kept burning. I did get a bit distracted as I entered the upper atmosphere. I was trying to keep my solar panels as long as possible while I started taking some readings so I only realized I was taking too long when the 2nd transit stage starting smoking. I immediately cut the link to the transit stage as it was consumed by the atmosphere. I relied on the navball to stay on track as the probe was frequently obscured by the explosions and it wasn't until the transit stage had been completely consumed that I could verify if the probe had come through all right. Fortunately there is no shrapnel in KSP. After things cool down work can resume and lower atmosphere readings are also taken. The probe has some tiny legs that extend just below the bottom of the heatshield. They are all set to be rigid so that they don't retract inward when touching down. In theory Eve's atmosphere provides enough drag that a soft landing is possible on the heatshield, at least at lower altitudes but I wasn't taking any chances. I also transfered power from the large bottom battery into the upper batteries. In the event that the heatshield and large battery where damage by impact there is enough power in the remaining batteries to perform surface operations. Safely on the surface after a 5 m/s touchdown the Double-C and other instruments can report their findings. I now have 4335 science to spend toward my next and final mission in this playthrough, going to Laythe.

I've located the transit boosters discarded by Gamow 2. They are currently in a high orbit around Kerbin though the kerbals at the observatory claim they are on an escape trajectory - from the orbit it looks like they could be nudged out into deep space by Minmus in a couple of weeks. At least at the moment they don't pose any danger, even if they where pushed into a lower orbit they would more likely impact Kerbin then enter a path that would endanger ships holding in LKO.

Gamow 2 (Part 2) Now in orbit (it's a bit inclined and it's retrograde since that's how we came in, but there is no docking so it's not a problem) we can take some readings, though I actually have to wait until the ship passes below 30km into "low orbit". The AP is just above that so I'll want to adjust that on the other side. During the pass around the dark side I collect crew reports on a number of places, in particular the Great Flats, Lesser Flats and thanks to the inclination the Flats are also found right beside the Lesser Flats. Getting good shots is another matter. A long while back I switched to XVID encoding to improve the capture quality of darker scenes over MJPEG. However it was really dark and apparently dark green doesn't compress very well. Even before I adjusted the contrast the images where filled with obvious compression artifacts. I did a 3 m/s burn on the far side to lower my orbit so I could take low orbit readings from any point. Coming around I found the Highlands (Midlands, Lowlands and Slopes where all located quickly since they are everywhere) and began preparations to land in the one obvious flats area I couldn't scan because I was too high up (and also burning to capture at the time). The decision to land was based on the fact that I had only used ~60 m/s from the lander's supply which meant I should still be within my safety margin. While I want to land in the flats area (Greater Flats as now detected by instruments and recorded) I am aiming to do it close to that out cropping. I might be able to grab a second biome. It's a soft touchdown at 1.3 m/s, landing on the Minmus flats isn't especially difficult though I did try to save fuel by waiting until I could see ground scatter before really removing a lot of my vertical velocity. It's a longer climb down to the surface. Samples are taken and the ships instruments are also run. Satisifed that everything is in order Barrigh can return to the lander. Reviewing consumables it seems I'm good for power (at least a days worth) and fuel wise I have 1089 m/s. That's close to my safety margin, if I go over on the return burn I could really use that fuel to get home safely. I look around to get an idea of how far away those slopes are (the darker portion near the bottom, the little object is the lander). If I had jets for my space suits it might be just within range for an EVA to run over there and take a sample. Walking it's too far to risk. I could fly the lander over there but I can't reasonably land on the slope so it would be a matter of landing close and hoping I could reach the part that registers as 'slope' biome by foot. Ultimately I decide it's not worth the risk - I haven't used this return path before so I'm very iffy on the fuel use. This mission was planned for a single landing (I've already exceeded my science objectives by cover 2 more biomes from low orbit then scheduled) so I'll stick with that even if it loses 150 science. The science I have in the lander is already past the amount estimated as the requirement to do the next mission. So we launch back into orbit. Back in orbit (this time a normal equatorial one thanks to a lander close to the equator and a easterly launch) the return burn is calculated. To get one that appears right I need to apply a lot of prograde thrust, 500 m/s, combined with radial and normal adjustments to place me on a return to Kerbin. The final result is a 527 m/s burn that will return me to Kerbin in 18.5 hours on a retro-grade approach (I'll fine tune the PE enroute). This will leave me with a healthy supply of fuel - in hind sight I could have flown to another biome but I had no way of knowing for sure I'd have that fuel so I stuck with the safety margin. In future I'll have a better idea of the fuel requirements for this kind of run. The return burn will take me close to the surface, 7 km over a large ridge. However the burn time is low, estimate is 46 seconds, so I'm not worried about a collision. Because the center fuel tank has less fuel I need to factor that into the burn time though it's not very hard - a 1/7th loss of thrust midway through a 46 second burn will throw off the burn time by an amount almost too small to correct for. I start the burn 3 seconds early (T-26s) to account for it. The burn is successful and the lander safely passes well above the ridge and back toward Kerbin. The return brings the ship on a retrograde encounter with Kerbin's atmosphere. I've tweaked the arrival to 27km and as the PE is neared the ship rapidly picks up speed since without the atmosphere to slow it down it is on an escape trajectory once it slingshots around the planet. The return pod seperates and uses RCS to push away and then move a little laterally. However orbital mechanics can be fickle when approached too casually and the pod, now on a faster orbital path, nearly hits the lander as it quickly moves past it. At more then 3 km/s the reentry speed has me a little concerned for the safety of the crew. The heatshield reaches a temperature of 1308 C before cooling down. After the worst of the reentry is over everything else fell into place. With good daylight the pod splashes down and is recovered, returning Barrigh and his science.

Gamow 2 (part 1) Gamow has been modified for the run to Minmus I described. The principle changes are upgrading the battery technology and moving some of the battery capacity to the lander segment. The reason for this is the inverse for why it was on the transit portion in the first place. For the Mun I fully intended the transit stage to remain with the ship right up to descent. Fuel was budgeted to ensure this (resulting in most of Gamow 1's descent being powered by the transit engines) and the batteries placed on that segment where designed to cover all the power needed (including budgeted safety margins) up until descent. Gamow 2 needs to work in the opposite manner. First I need every drop of power I can get, so throwing away any power with the transit stage is unacceptable. Second is that I'm not 100% sure about the delta-v requirements - I've been forced to consider the outcome of several scenarios where I am short on fuel and how to deal with them. The first scenario is if I get into Kerbin orbit and find out the injection burn maneuver exceeds the delta-v in the transit stage. In that event I can simply abort the mission without doing the burn, returning safely to Kerbin. The second and third scenario are closely linked. After safely passing the first hurdle I should be on my way to a Minmus intercept with the transist stage attached. Executing the capture burn I might run out of fuel in the transit stage, forcing me to use the lander engines to capture (and avoid flying off into deep space or on a long orbit that exceeds the life support limit). This is the main reason the transit batteries are engineered to run out before actually reaching Minmus. If I'm forced to use the lander to capture I'll still have the power I need to return safely to Kerbin - I would simply skip the landing which should be enough to cancel out whatever delta-v was lost in the capture. The last scenario would be if I landed but didn't have enough fuel to return all the way to Kerbin (or couldn't return fast enough since getting there fast involves burning much more fuel). I want to avoid that scenario entirely by knowing the go/no go point. The lander alone slightly exceeds the delta-v requirements (including safety margins) to land, ascend and return. So if I can enter Minmus orbit with the transit stage still attached I am definitely a go. If I capture but have wasted more then a token amount of the landers fuel then I'm a no go and need to abort. In terms of construction I did underestimate the height of the upgraded batteries a bit. I had estimated that 4 batteries would be about the height of a T200 tank but with was more like 3. To keep the shape I wanted I moved one center battery from below the capsule on the lander stage to the top of the capture near the parachute. Otherwise the changes where stretching the ladder and adding some science instruments. I did perform a pad test to verify that I could move the camera around enough to select the center battery of the transit stage - this was combined with some calculations of how the batteries would drain since I wasn't using the deactivated battery method I used in the first flight. Instead I checked to ensure that enough power would have drained from the landers outer batteries that I could transfer the remainder from the transit stage up there when the time was right. Because I need to stretch the life support consumables I can't carry 3 kerbals. With the mission risks involved I decide to carry just one, Barrigh. It should even out the number of missions everyone has done (1 solo, 1 group) and he's really the only one to trust to take a ship out alone so I put him in the pilot's chair with the other seats empty. The launch goes fairly well - I did have some minor issues with RCS attitude control that wasted a little fuel since I wasn't burn a bit up when I should have been burning purely sideways for orbital speed. It's a 1050 m/s burn to Minmus. I'm not adjusting my inclination (6 degrees) as I hardly ever do that and it would cost about 250 m/s which I don't have budgeted. Making the burn some other routes present themselves. With the basic burn done I do make a 30 m/s normal burn to bring my PE down to 30km. 10 hours into the flight and with Minmus still several hours away I go about moving all the electrical charge into the lander batteries. I start by shifting some power around in the lander to leave a single nearly empty battery. This way I only need to perform the camera gymnastics needed to reach the center transit battery once - I transfer all remaining charge from that center battery to the one I emptied out. The other 6 cells are then then drained into sequence, their charge distributed between the 3+1 batteries above them on the lander. Arriving at Minmus some high orbit data is taken; in addition to the crew report I have a 2Hot to take readings with. I didn't bring along Goo containers since I didn't have the weight budget for them. However I do have an issue, the capture burn will cost just over 800 m/s, more then I had budgeted for. Now at this point I had extra fuel by burning under budget for the injection but I had some small unknowns from the launch. Without calculating my exact fuel cost the burn time and fuel left in the tank made it look close. It was good that this was one of the scenarios I had planned for so I was still confident I could bring Barrigh home safely even if the mission couldn't complete its objectives. I started the burn with a very close eye on my fuel supply. My estimate based on the burn time seemed to be panning out, fuel and delta-v markers where draining at about the same rate. Ultimately it wasn't enough though - the transit stage was exhausted with 58 m/s left to burn. Since this was planned with the battery strategy it was safe to stage and use the lander engines to complete the burn. The lander safely made orbit with 95.6% of it's fuel reserves. The transit stage (well really 7 seperate engine assemblies) where now on an escape trajectory from Minmus. Since I was close to the end of the burn I have a feeling they where put into Kerbin orbit albeit a high one. Kerbin astronomers will need to track them down. This does end my streak of leaving no junk around Kerbin.

I've actually already done the calculations I've just been too busy to boot up KSP. Based on some screenshots from Poddster of his journey to Minmus it seems I can make a modified version of the rocket by unlocking the middle tier batteries (the first set of stackable batteries). His route involves performing an Kerbin escape velocity burn that intersects Minmus and then braking before you are flung out into deep space. That part adds about 400 m/s to my budget (yes he did it for less but I've never flown that path before and I'm using some other screenshots to determine a min/max requirement to reach and capture at Minmus using that approach). For that I need a 13 hour budget of power, plus a budget for orbit, landing and asscent/orbit (1-2 hours). Getting back Poddster is using a big burn (budget 600 m/s) that uses a radial push to encounter Kerbin's atmosphere on a direct line from the return instead of a more gentle pass around the back of Kerbin. Time budget of about 18-22 hours. The transit stage would be stripped of the older batteries and replaced with a single 360 battery to top off each engine assembly (7 in total) just below the decoupler. The lander would require more extensive modifications. After stripping the old batteries the center fuel tank would be halfed - the center T400 tank would be replaced with a T200 tank and 4 '360' batteries. All 7 engine stacks would then receive 3 more batteries (7 total in the center now) and the outer 6 stacks would recieve one of the tiny 360 Core batteries. These modifications would ensure that the launch weight remains within a margin of error for the boosters and transit stage. The lander itself is heavier and carries less fuel, losing 20% of its delta-v, but the requirements are less. Of course I would rerun all of those calculations before actually flying the mission, but it would have enough fuel to make at least one landing (a second hop should be possible if it was short, but the fuel requirements for the return dictate that it would be safer to do a single landing only).

Gamow 1 (Part 3) As soon as everything is stowed away the lander takes off. We don't need to wait for a docking window since the ship will return directly to Kerbin. It's not like there is anything in orbit anyway since the transit stage, split into 7 pieces, crashed into the Mun prior to the lander's touchdown and thus kept my universe debris free. But since the transit stage did so much of the work the lander has plenty of fuel and monopropellent and is only limited by a budget of 13 hours of power to reach home. Orbit circularization is made into a fast 9.5km orbit to speed up how quickly we can reach a orbit breaking maneuver node (we need to orbit around to the opposite side of the Mun for this burn). With PreciseNode allowing me to discreetly set the maneuver node time and magnitude I wanted to try something I haven't done before, doing a Mun return with a single burn instead of two. Normally I'd perform two burns, the first one would be to exit Mun orbit and enter a Kerbin orbit with a relatively low PE (ideally one of several hundred km but before PreciseNode it might be in the 1-2 million km range). The second burn would be carried out after leaving the Mun's SOI to immediately lower the PE to the precise altitude I want for reentry. However in this case I plotted for a direct return with a single burn. I'm going to see if I can get home without any additional burns or RCS adjustments. This goes well. I slow down time warp until I hit 1x as the ship is passing out of the Mun's SOI. This is to keep my reentry PE on track since passing between areas of influnce at high warp can through off orbits. This is because at high warp you are performing calculations for a longer time steps - if my velocity is x and position is y and acceleration due to gravity is z, where will I be in 10 minutes. If you are just about to cross into another SOI (where acceleration due to gravity will suddenly change) then some of that 10 minutes will have been calculated with the wrong value. As it is my PE stays within 78m of it's original value. Approaching Kerbin's atmosphere with plenty of power and life support (and 680 m/s of delta-v in the tanks) the pods battery is filled up again from external batteries in preparation for seperation. The lander is oriented around to face tail first and at 60km the pod seperates and uses RCS to push away, first upward and then laterally to put the return pod on a different return vector to the lander stage. RCS and SAS are then used to keep the pod oriented (it should orient properly due to weight but using RCS prevents it from swaying which could expose parts to deadly reentry forces). The pod safely splashes down at 12:49:56 off the coast of the westward continent, the crew and their cargo is quickly recovered. With the lander stage burned up the only thing left is the flag I left on the Mun. I'll be going to Minmus next, should I go manned or unmanned?

Gamow 1 (Part 2) In Kerbin orbit an injection burn is planned to reach the Mun. If you look closely you'll see that the burn happens to occur almost directly over the KSC, making it one complete orbit before leaving for the Mun. With 7 powerful engines the burn will only take 53 seconds despite the fuel being carried. Coasting out to the Mun is uneventful and upon arriving in high Mun space a crew report can be taken. As the ship enters low space and prepares to make a capture burn some more science is done. Passing over the Midlands, Highlands and Highland Craters the 3 kerbals record Crew Reports and take gravity readings. There are 2 GravMax instruments mounted to the big transit stage. Each one is keyed to a different action group that also triggers a crew report. This way two different biomes can be captured in quick succession before having to go through the process of transfering data from the instrument into the command pod to make it ready for another reading. The capture burn provides about 600em from the engine's alternator, it's not very useful since I am running well within my safety margin and the batteries being charged will be discarded soon. Capture occurs just slightly north of the twin craters, the orbit missing them so I couldn't take readings. The ship begins an orbit of the Mun, collecting information on all the biomes along the equator. In all 9 biomes are scanned as the ship circles around the dark side. and emerges back into the dawn. Back on the light side a landing position is picked just short of the twin craters. I'm aiming for a flat area with no visible craters. Before a deorbit burn can begin the battery systems are reviewed. An action group brings all the batteries on the lander stage online and then power is pulled from some of the transit batteries to top up the capsules own power supply. With all preparation complete the transit stage is used to brake from orbit. It was planned that the transit stage would provide at least 200-300 m/s for the descent (though the lander was designed with just enough dV to make the descent, ascent and return on its own) in order to ensure that its batteries would be attached up until that point (if any of the landers fuel was required for the Mun capture it would mean discarding the transit batteries at that point). With fuel saved up to this point the transit stage is able to completely brake from orbit with 50L of fuel left, so the lander only need to concern itself with a soft landing. The Mk1-2 lacks landing radar (well there is an indicator in the cockpit I think) but I used to landing by sight anyway. Touchdown is at 5:58:20 at 3.1 m/s, 2 hours ahead of the first safety margin. Barrigh is the first down the ladder and is quickly joined by Kenby and Aldrick. While I have budgeted the electrical cost of a 10 minute EVA by the three kerbals I do want to keep their time on the surface short to conserve supplies. Barrigh plants the flag while Kenby gathers rocks. After surfaces activites are down everyone gets back into the ship and things are stowed away to prepare for the last leg of the mission.

KER isn't the only way to design efficient rockets, it can be done by hand too. In fact I'd argue it may be easier to do with an Excel spreadsheet since you can directly manipulate the numbers and even use reverse functions to immediately find the optimum values instead of just going by trial and error in the VAB to see what numbers KER displays for each combination of parts. My rockets for BTSM aren't exactly small, but that's because I find that BTSM has other goals to reach for like safety margins and even just getting there. In stock where the risks are low I can be much more aggressive. For example my .23 career in the signature, or for combining looks and light weight my Duna ship.

It depends on the injection burn. Assuming a 'normal' injection burn (between about 850 and 900 m/s) the time can vary from about 4.5 hours up to something like 10 or 12 hours for a poorly planned burn. You can get there faster (or slower!) by burning more fuel.

Well it weighs just a tad short of 600 tons on the launchpad. I would actually be interested in knowing how heavy other BTSM player's manned Mun spaceships are. The only other reference I really have is my own previous ship (almost the same weight) and a work in progress by Ninjatsu that I can estimate is around 1000 tons. You can find the weight of your entire ship by starting it up on the launchpad but instead of launching press M to go to the map and then over on the right click on the button labeled (i). It will expand and show information about your ship, including the total mass and the number of parts. If you are playing BTSM and have sent kerbals to the Mun please post a screenshot showing off your ship and its launchpad mass.

I had a question about Gamow 1 over in the BTSM mod thread but I thought it would be better to answer it here rather then derail that discussion. The ship is built using a combination of the symmetry feature and the cloning feature. You should already how to use symmetry, it's the little button the lower left you can click to get 2x, 3x, 4x, 6x or 8x symmetry when placing a part. Cloning is a feature that a lot of people know about but can be easily overlooked if you haven't read the list of keyboard shortcuts. You clone something by holding down the alt key and clicking on it. You'll now be holding a copy of that part along with all the parts attached to it as if you had just removed it from the parent (but the original is still there!). Below I've created a basic copy of the top of the landing stage of the ship - a Mk1-2 capsule, a heatshield and a decoupler. Below that is a fuel tank and an engine. By alt clicking on the fuel tank I get a copy of the tank and engine. Using 6x symmetry I can place the tank radially, creating 6 symmetrical tanks and engines around the center one. There is one final 'feature' that I use for this kind of assembly, though it's really more a work around to a minor bug/glitch. Sometimes when you are placing things with symmetry, especially when they are close together like I'll be doing here, you'll find that it rejects some or all of the placements (some or all of the parts show up in red instead of green and you can't place the group). This happens if you have accidently clipped parts together but can also seem to happen for no reason even on parts with no possible clipping issue. The solution is to move the camera a bit and try again. For some really close placements it can get tricky to find just the right angle you need to get it to register but it can be done. Next we'll create the injection stage. We'll start by building the center tank assembly first using a decoupler, 2 of those long fuel tanks and an engine. Just like before we'll clone it but instead of cloning it from the tank we'll alt+click on that decoupler, cloning the entire assembly including the decoupler. With symmetry mode on we'll then attach the decoupler to the bottom of one of the 6 exposed lander engines - symmetry mode will automatically duplicate it to create 6. Struts can be added at this point to ancher the 6 long tanks so they don't sway around, but I'm not going to cover that part. At each stage assume a single set of struts is used to ancher any long sections together. It doesn't take many, the final rocket has about 1 strut per engine (including the 6 struts used to ancher the command pod at the top). The injection stage had 7 engines, but the 2nd booster stage is going to need more to lift all that weight. It's going to need 19 engines. That means in addition to the 7 'inner' engines we'll need an outer layer of 12 more. First we construct the inner engines (which are composed of a decoupler, T200 tank, T400 tank, T800 tank and LV-T30 engine) the same way we did with the injection stage. Next we clone the engine assembly but without including the decoupler. Much like when we constructed the lander portion we attach it radially. You'll notice that you only have two symmetry options when touching the tank - 1x or 6x. The VAB won't let you use any of the others because you are attaching to/extending an existing symmetrical group (there are some tricks for assembly with multiple layers of differing symmetry but that's for another day). You can experiment with the exact angle to attach them in combination with the next step. You'll want to be just off the straight on attachment angle in order to make the next set of tanks you add appear seamless. Now we can start creating some fake 12x symmetry. Clone the tank again and attach it to your outer most tank, but instead of extending them out again you'll do the opposite, try to place them as close in as possible without clipping (if it turns red you are clipping and can't place). Look closely and you'll see the small T200 tank I'm attaching the assembly to, it's highlighted one on the left. In this arrangement the tank is technically attached to the one to its left, but the gap between it and the tank to the right is small enough that they appear equally space for all but the closest inspection. If the gap is big then go back to the previous step and adjust the attachment angle. You can now add some nose cones. You'll notice that they only attach to 6 tanks at a time, this is because you're really still using 6x symmetry, but wrapping it around to fake 12x. For the bottom of the rocket, the first stage booster, we'll need 37 engines in total. The first 19 are placed the way we placed the first 7 engines of the previous stage. We start with the very center and build a single assembly consisting of a decoupler, T400, T800 and LV-T45 engine. Now clone that at the decoupler and attach it to the bottom of the other engines with symmetry on. Each placement will automatically be copied to 5 other engines so you'll need to place it 3 times to get all 18. At this stage you will probably start encountering those placement issues so rotate the camera a bit if it doesn't recognize all 6 as valid. To form the outer most layer we'll need 18 engines. That means for each of the existing 12 outside engines we'll need to attach 1.5 more. Clone an assembly, minus the decoupler, and place it sticking straight out from one of the existing ones. You've extended 6 of the 12 existing engines, leaving 6 with nothing attached radially. Pan the camera around to focus on one of those assemblies with nothing attached. You're going to clone and attach 2 assemblies to this engine, one angled toward the left neighbor and one to the right. If you do it correctly it the distance between all the tanks should appear equal, creating fake 18x symmetry. One thing that will take a little practice at all stages is getting the height lined up (in the example I've been assembling for these screenshots I've been moving quickly so there is a small amount of vertical misalignment). Once assembled you can add nose cones and you're almost done. Remember that this isn't true 18x symmetry, it's 6x symmetry with three pieces. So when it comes to attaching the fins we don't have to worry about any manual attachment, we can just attach them to a single grouping of 6. The little boosters are added last and again you will need to pay a little attention to make sure you vertically line them up. And now you have a completed ship* *Batteries, landing gear, RCS and parachutes extra.

In stock you can, if you hit it in the right place, click the PE marker to 'sticky' it. However if you are modifying a maneuver node and even briefly break the encounter or lower PE to 0 you'll lose the sticky. I tried for a long time to do it pure stock but after some frustration at Eeloo I finally installed PreciseNode. Among other things it lets you adjust the maneuver using the keyboard so you can keep the mouse where you want it. It can also optionally show the ejection angle (there is an O button for options that lets you hide/show various features). Finally it has a conic mode feature to let you change how projections are shown. I don't know what I changed it to but I like it more then what it was before (I now have it showing interception paths in the same frame of reference as the body they are intercepting, so for example a Mun encounter isn't a line that bends bit as it encounters the Mun and then goes back, it sharply twists around to show the half orbit, then breaks off to continue elseswhere)

Gamow 1 (Part 1) This is my early Mun shot. I've unlocked the Mk1-2 Capsule to get there, the space suits to explore the surface and the heat shield to return. What I haven't unlocked are the advanced batteries to run the life support system or any of the large diameter fuel tanks or engines. Engine wise I've only unlocked one more, the LV-T30 to replace the LV-T15 and I'm still relying on the experimental LV-420 which is heavier, less efficient and lacks the thrust vectoring of the LV-909. My crew for this mission consists of the 2 kerbals who have already flown into space, Aldrick and Kenby and the last kerbal from the public voting Barrigh Kerman who is the only one who isn't dumb as a post. I need a kerbal like him running the mission since we aren't just throwing them up for a single orbit around the planet. As I showed before I was already planning this as a direct ascent mission: this is where the lander returns directly to Kerbin instead of docking with a mothership. Even though I had the lander can (since I needed space suits) the direct ascent profile was still important because of the complexity of having both a lander and the mercury style recovery capsule. Once I decided on getting the heatshield instead of batteries I could have changed the profile to a munar rendezvous but I wanted to do it direct ascent simply because I had already done it the other way. The main mission objectives where simple: Launch from Kerbin, burn to the Mun and capture into low orbit there, perform an orbital survey, land and do an EVA, launch back into orbit and return to Kerbin. The data I recorded from Fleming 1 proved invaluable in planning this mission. I determined that the smallest reasonable time to reach orbit and begin landing was 6 hours (remember that reasonable means itaking into account less then perfect orbital alignment and burns) and that padding it out to 8 hours would ensure safety. This estimate wasn't that much smaller then my old play through's mission plan. The second estimate was a bit more daring. It told me from Mun descent to final splashdown on Kerbin could be reasonably done in 8 hours, though with an imperfect return 11 or 12 should be budgeted for safety. That gave me a total of 20 hours, again not very different from my first play through, but I intended to use the Fleming profile of carrying some batteries in an injection/capture stage which would be discarded at the beginning of the Mun descent. The final rocket weighs in at 598 tons, only 10 tons more then my original Uniform 2 mission. And if you compare the designs I think you'll agree that Gamow 1 is much, much more streamlined and realistic in appearance. It also doesn't have a lander sitting on top which makes escape easier in a launch failure (if I had the escape lower unlocked I might have thought to use it, since it would easily integrate into this design). Lift off is smooth but a little slower then usual, I cut it close with the thrust calculations which is why there are those little solid boosters to get it over the top. Those big XL control surfaces combined with the pod SAS keep the first stage flying straight. At 10.5km the first stage booster is exhausted and discarded. The ship is going about 30 m/s slower then my usual launches as the second stage booster takes over and begins a gravity turn using RCS for control. The SAS system is turned off at this point as it would only waste monopropellent - I'm not so much steering with RCS but using a bit of it to tip the rocket and then let it turn by itself, using RCS to slow down the turn a bit as needed. This seemed to be the scariest portion of the launch judging by the crews reaction. The second stage runs out at 50km, leaving about 600 m/s for the orbital engines to pickup to reach orbital speed (~2.3km/s). Fortunately they are T30s and where designed to handle this portion of the ascent. A 172 m/s circularization burn is used to complete the setup of a 72km orbit. This orbital section is carrying the only active batteries besides the one in the command pod (which I kept on for safety). All the batteries on the next stage are currently on stand by. Due to symmetry I ended up with more batteries then I needed on this stage, 9.6 hours worth instead of 8, but it wasn't too much of an overage so I kept it instead of splitting things up.

Manned Mun landing technology I have a limited budget of 731 science to unlock new items for a manned Mun landing. Here is where I'm starting from. First I think there are two techs I can't do a landing without. One is Advanced Landing, without this I don't have space suits so my kerbals can't even get out of the ship and look around. The larger landing legs are useful too. The second is Advanced Exploration. I don't think it's practical to try and reach the Mun without the life support of the Mk1-2 capsule. In hindsight it would technically be possible with just Advanced Landing but I'd need to stack at least 4 Mk2 Lander Cans together and that would look stupid. In order to reach Advanced Exploration I need to unlock Electrics first (I can see Advanced Exploration without it, but it's grayed out and Electrics is the only nearby node that might assist in unlocking it). I've spent 450 science leaving me with 281, enough for one more 90 point science item and one more 180 point item. There are multiple choices here, each one fills in a part of the mission but by taking it I would be leaving out the others. At the very top of the tech tree I could pursue the large diameter fuel tanks and the Keel Haul (prototype Skipper). Next down I could unlock better engines with thrust vectoring. Going further down I have already unlocked the 90pt portion (so I'd still spend 90 on either orange tanks+adapters or T30 engines and small fuel tanks). In the aerodynamics area I could spend 180 to unlock the large heatshield and radial parachutes - I can't realistically land the big Apollo capsule without a heatshield. Or I could spend 180 to get the upgraded batteries. I don't really have a lot of trouble with the first part of the choice - a heatshield or batteries are much better then the engines or fuel tanks. I can still spend 90 to unlock the T30, which gives me better thrust over the T15. That leaves heatshield or batteries. Initially I was actually leaning toward the batteries, since electricity was my limiting factor in my Mun and Minmus flights. I considered the idea of a direct ascent, single kerbal mission. It would carry a Mk1 escape pod on top for reentry. I loaded up my old save and mocked up what the direct descent lander would look like (I did accidently use a ladder I wouldn't have access to). However while I stayed with direct ascent I decided it was better to go with the heatshield after running some numbers. First was that the mass of the landers was very close - the heatshield weighed less then the Mk1, but the primitive batteries added slightly more weight in return, however in order to use the Mk1 I would need to brake before reentry to lower my speed. That resulted in an extra 7 tons of fuel in the lander. Mockup of direct ascent lander using Mk1 pod for heatshielded return So I went with spending science to unlock Super Sonic Flight for the heatshield and Heavy Rocketry for the T30 engine and T200 fuel tank. I also hired on my third kerbal based on the poll results, Barrigh Kerman.

There are two types of physics in KSP. The full simulation and 'on rails'. Whenever you are going at 4x timewarp or below you are in full simulation mode; Your ship and everything within ~2.2km is being fully simulated. Each part can exert forces on the other parts, parts can rotate, parts experience drag, engines and thrusters can fire, etc. When you timewarp to 5x or above you switch to on rails mode. On rails is a much faster type of simulation where it treats your ship as a single solid mass and simply calculates it's orbit. This is the reason you can't timewarp to 5x while your ship is in the atmosphere - it would stop simulating important things like drag. Anything outside of the 2.2km bubble is always 'on rails' regardless of timewarp. This way you can have dozens of ships in orbit without the game slowing down. When it comes to planets objects that are on rails follow much simplier rules - drag is not simulated and anything that passes below a certain altitude (set by planet) is assumed to have crashed and is deleted. This is generally considered a good trade off, since any object you leave unattended is usually either in a stable orbit or is on a collision course (discarded boosters or other things).

I consider the red button a bit of a cheat, it just magically removes stuff. I didn't bother this time around but on previous careers I've edited the setting that disables that button (unfortunately if you do that it also alters how recovery works - you need to actually visit the object to use the recovery button at the top of the screen, and visiting objects after they've landed can sometimes result in kraken attacks). (From my first career playthrough where I was experimenting with experiment return methods)