nelso

Congrats, 3000m/s at 3:48 is definitely a sign this is record breaking early on, and 24:32 is by far the best. I would give you a recommendation for that. Think it could do even better though, perhaps by 30 seconds by not doing the loop at the end. I also did another run with a craft that can carry 32 passengers, in under 30 minutes. Trying to optimize takeoffs and landings, and getting decent at quick landings. This craft has all the requirements of OP but it's a little hard to board passengers from the ladder.

In my experience the descent is really critical and can shave 1-2 minutes from the time. It's also possible a reverse powered descent is optimal, which would mean the backward-moving COM isn't so bad. It is a more complex maneuver and closer to what spacex wants to do with the starship. I've also considered using an inflatable heat shield as a nose cone.. superior heat resistance (3500k) but don't know about the aerodynamics. Also if inflated it can't be deflated. Very nice and congrats. I was trying an automatic takeoff for my most recent huge craft, but I couldn't get the right attack angle in the 10000-15000m range to maximize airbreathing fuel usage, while also getting above that range when I reached an optimal speed.

Those are some good ideas. I did not know that about MK2 parts. I did manage to roughly tie your time (about 26:29) with a vertical ascent and landing craft and cruise maxing out at 3250.5m/s (at ~18:48) (with comfortable heating, just didn't have the fuel and thrust to go faster). It lands on the tail, not quite on the runway but close. I had shock cone intakes closer to the central axis of the craft which I believe greatly reduces the heat. For the nuclear engines, I used shock cones and 2 ncs adapters cause of their heat tolerance. There is another optimization which is to use ion engines to get just a little more thrust. The nuclear engines provide enough electric charge to run some of them, but I didn't use this.

Very nice and congrats! I guess you fly upside down because the drag from the tail fin helps rotate down, and optimized drag to maximize the use of the nerv. Craft looks great too and it looks like you really tweaked it. Guess I will have to try some new approaches to get faster than that, but it will certainly be tough.

Thanks, this was fairly challenging and took quite some time (many failed approaches in ship design), although after a while I got a sense of how fast I needed to be going early in the run: 2650m/s at 3 minutes was my goal, with about 20 minutes of nuclear fuel remaining. My goal was less about going faster during the cruise - every 50m/s faster is only about 30 seconds off the final time, but consumes a lot more fuel. Also note this was 43 tons so in the higher mass category. It was easier to balance numbers of engines, intakes, fuel/engine weight balance, and aerodynamics, and had a higher mass to drag ratio, so a quicker descent and presumably better aerodynamics in cruise. I think it's possible to shave off another 2 minutes using a powerful rocket for ascent, that's probably the 80+ ton category. You said you were having trouble with kRPC. I found kOS language awkward, but no reliability problems, just had to restart the script when loading a save. Here is my script, it's a "PD" control of orbital energy (factoring in speed and altitude) and another PD control for altitude. This already has the particular issues worked out like disabling SAS while using it, and giving back control to the player when exiting (by pressing any key). It's configured to retrograde, but changing the 270 to 90 will allow prograde. PRINT 1234. SET gui TO GUI(200). gui:SHOW(). LOCAL label IS gui:ADDLABEL("Low Orbit Autopilot"). SET label:STYLE:ALIGN TO "CENTER". SET label:STYLE:HSTRETCH TO True. gui:ADDLABEL("Altitude"). LOCAL field1 IS gui:ADDTEXTFIELD("33000"). gui:ADDLABEL("Orbital Speed"). LOCAL gui_speed IS gui:ADDTEXTFIELD("2360"). UNTIL SHIP:ALTITUDE > 4000000 { //PRINT SHIP:VELOCITY:ORBIT:MAG. SAS OFF. SET targheight TO field1:TEXT:TONUMBER(33000). SET targspeed TO gui_speed:TEXT:TONUMBER(2360). SET targthrottle TO (targspeed^2-SHIP:VELOCITY:ORBIT:MAG^2+(targheight-SHIP:ALTITUDE)*20)*.0005. LOCK THROTTLE TO targthrottle. SET pitch to MAX(-14,MIN(14,(targheight-SHIP:ALTITUDE-ship:VERTICALSPEED*80)*.01)). LOCK STEERING TO HEADING(270, pitch). //PRINT ship:VERTICALSPEED*50. PRINT throttle+" "+ pitch. //LOCK STEERING TO HEADING(90, 0). //PRINT SHIP:ALTITUDE. // pid:update() is given the input time and input and returns the output. gforce is the input. if terminal:input:haschar { break. } WAIT 0.1. } SAS ON. UNLOCK STEERING. UNLOCK THROTTLE. SET SHIP:CONTROL:PILOTMAINTHROTTLE TO 0.

My best yet: 28:45. 43 tons starting mass. I went retrograde, used 2 nuclear engines and 4 rapier engines which I used for orbital insertion and brief boosts at takeoff, and I found rapiers to be the best for this purpose. Instead of a nose cone at the front I used a fairing which has higher heat resistance for this critical part. Mainly it was a combination of a good ascent and descent, and going retrograde which lessens lift needed to keep below 35k, allowing significantly higher speeds for the same thrust. I only recorded a video, which does have an edit for an autosave towards the end. Thanks, this was very helpful.

I gave it a test in reverse and got significant savings on fuel, approximately 40% less at cruising for the same surface speed (@ around 2560 m/s surface, circular orbit ~33km). I was able to test this precisely with my kos script. It does take stronger engines to get into orbit, since you need to go faster to start feeling weightless, but the fuel consumption is so much less for the cruise, it enables options like using higher power rocket engines for the ascent. Question for more experienced players - do wings create any drag if they are headed straight in the prograde direction (any helpful threads would be appreciated)? Below would've been my best run (crash landed at 32:00, and this included doing a 180 turn after takeoff), except I blew up the nose cone on descent. It used an aerospike instead of nuclear because of better thrust, lower weight, and decent enough ISP. During cruising I was thrusting about 8 kN.. with the same craft going prograde orbit, it was about 14kn.

My best with actual landing: 34:19. I wrote a kOS script to maintain a near perfect flight for nuclear engine types, much better than Mechjeb was doing. It sets throttle based on an estimate of orbital energy, and has a quite stable altitude control. I only used half the fuel so it may need a redesign. More in this album https://imgur.com/a/LPmim7w and video of kOS altitude maintenance and landing. I went into a few intentional spins to slow down to land: Similar thoughts here, and air speed appears to be the ultimate limit, so to get beyond that, as you said, is fast takeoff and landing. Good job on 30 minutes. I can post the kOS script as well if you want.

For anyone wondering how to do nuclear engines for this and approach the 33 minute range, here's a video of an ascent and getting auto throttle control. The craft is kinda cheaty, with the nuclear engine inside the main fuel tank, and was very unstable when the fuel ran out. The mechjeb autopilot can work for speed, but takes some babysitting to manage altitude.

Nice! That is a nice optimization to put everything inline and put the nuke backwards. There is another potential time save, by going into retrograde orbit instead of prograde, so KSC gets closer to you while in flight instead of farther. It means going ~340m/s faster relative to the air, and a harder ascent, but by rough calculations it would reduce time by 3 minutes. It would use more fuel but that is hardly a concern since while in orbit, the only loss is drag and mass doesn't matter very much.

The heat was a problem, but mainly the craft was too heavy to keep the height up. With a small redesign, I was able to get into "orbit" with help from rocket mode from the rapier engines. This orbit was ~2166 m/s surface speed at ~34k, so to go any faster it would have to thrust downward to keep from going into space. At this point I could use very little thrust to maintain speed. Just based on kepler's laws, it should be a significant amount faster than kerbin orbit in space). I did manage an actual run in about 35 minutes, though I got my altitude too high at some points, I overshot the runway by a lot, then sorta landed at 38 minutes, but this was mainly a test. I got decent results by using aircraft autopilot, hold vertical speed at 0 and hold speed at 2166, and manually adjusting occasionally to keep under 35k altitude. It also said I had about 3 hr - 1 day worth of fuel at this thrust level, so it can clearly get away with a lot less fuel. The majority of the fuel usage was getting to to orbit in the first 5 minutes, exactly as logic would say - this is like launching and maintaining the orbit of a low satellite. You can see me overshoot here

Not an official run (no command seat), just experimented with using nuclear engines and RAPIER. 57 minutes roughly. I used the nuclear engine to jump out of thicker atmosphere repeatedly (up to 35k), thinking it would allow higher speeds. The nuclear also helped quicken the initial ascent, as well as some spare oxidizer. I'd turn off the nuclear when the RAPIERS turned back on, and flew it all manually. The nuclear is tilted downward slightly, the theory being the plane could point forward and the nuclear would keep it up, but my assumption is probably wrong there. More pics: https://imgur.com/a/ODKV0IH Great job everyone else.

I did this at level 4, trying to be smart about it, using rhino engines for the majority of the burns (better ISP than vectors), and with ISRU on Gilly and on Eve. Used a powered descent to Eve, and using default game settings. For the initial launch from Kerbin, I took advantage of all the Vector engines needed for the eventual Eve ascent and could put some enormous tanks on. I took 3 kerbals, the big ore converter and 2 drills. I also took a module to allow a surface sample, though that didn't work out. Didn't do any docking so that meant taking more mass on the whole trip. I initially designed it around taking 3 kerbals. Should be 1700 points: Level 4: +1250, Mass 1361 tons: +100, Funds 815k: +100, Mission completed in 500+ days: +25, ISRU used: +225 First screenshot is the actual Eve landing stage with the Rhino engines activated. Not all the screenshots are from the actual run. The actual launch vehicle. Launch screenshots from a previous vehicle but pretty close to the one I used. It's asparagus staging with the huge tanks transferring to the main vehicle. Refuel at gilly with actual vehicle and had barely enough delta V to land and refuel for insertion and descent to Eve. Descending to Eve and transferring fuel to lower center of mass The Rhino engines had burnt of in descent but that was a good thing since I didn't need them anyway. The parachutes got me to about 8m/s and it was an easy landing. THIS DID NOT WORK. I wanted to use this thing to land on Eve for a surface sample, then shoot straight up, go EVA and parachute back to the main vehicle. Unfortunately I did not balance it well enough and I ended up shooting it off (without a kerbal of course). Eve liftoff after discarding ISRU equipment (can see one part to the left). Center stage has 7 vector engines, outer stages have 2 vector engines per side. Still going vertical on the central stage with 7 vector engines, and trying to balance the losses from air friction and gravity. Rhino stage for much better ISP in upper altitudes. Final stage is a NERVA engine that would finish the ascent from Eve take this home to Kerbin. Actually had a ton of delta V to spare. Landing at kerbin after intentionally burning up all the liquid fuel to lighten it. Might do it again and design it more for lightness and more delta V.

Found an old screenshot from 2014 in version .23, think it was meant to drop the orange fuel tanks on things.

After about 150 more attempts and lots of craft redesign, I got down to about 1:00.7 (judging from the first frame I got in the desired orbit). This was pretty hard to get. I used 4 "boosters" in onion staging, each consisting of 2 mammoth engines and 2 kerbodyne s3-7200 fuel tanks (plus 1 nose cone, 1 strut, 1 fuel line, and 1 decoupler), to accelerate off the ground really fast but still have a good amount of fuel. I used a more vertical launch profile, and also cut the engines for a few seconds while approaching the point to start thrusting sideways/downwards to get into orbit, because using delta V vertically in this region has minimal benefit on total time. The craft only had 56.7 seconds of thrust time, so it was critical to use it well and I just barely did it, with many failed attempts. In a basic theory, the best launch profile of this challenge is go almost straight up to get out of the dense atmosphere quickly, then at a certain point thrust down/forward at a ~45 degree angle, so that the following 4 parameters reach their needed value simultaneously: the vertical speed reaches zero, the horizontal speed reaches a bit above orbital velocity, the current altitude reaches > 70km, and the craft runs out of fuel. I used something close to this profile. This is stock version 1.7.3. Also I wonder if additional categories are needed. What I did here is going to be hard to beat. Perhaps categories <20 parts or <80 parts, or under a certain mass would be good.

The Kerbal budget meeting is in 2 minutes and you forgot to build any rockets all year. You need to get to a nice looking circular orbit as fast as possible to impress everyone. This is a fast challenge of piloting skills and quick thinking, and using a much different launch profile than you're used to. The circularization step is the hard part - a test of your understanding of changing orbits under pressure, as well as a game of "chicken" when to start circularizing, so you don't drop your periapsis or apoapsis below 70k in the process. It was inspired by various other challenges. Objective: Get into circular kerbin orbit (peri/apoapsis > 70,000m with eccentricity < 0.1) as fast as you can (based on time since launch). Use 40 or fewer parts (this helps level the playing field). Fewer parts is better. Provide uncut video of the whole attempt Stock game, no DLC parts, no part or physics mods, no cheats, no part clipping, no craft file editing type stuff (all the standard rules like that). You probably want Kerbal Engineer for convenient readouts. kOS and autopilots allowed, but note if you used them, and it should be considered a separate category. Finish time is the mission time in the upper left, when you achieve the orbit described in the first bullet point. Landing afterwards is optional, taking a kerbal is optional, it just adds a little weight. Limiting to 40 parts is mostly out of concern for framerates, and to level the playing field. Kerbal Engineer can display part count but this can go on the honor system. Kerbal Engineer is good for displaying orbital info, but the stock game can display eccentricity as well, (bottom left, in maneuver mode under advanced orbital info), just not the precision needed (e.g. it will display .1 when the actual eccentricity is .149). It can also be calculated from periapsis/apoapsis if you know how. But I am assuming you will use kerbal engineer. Here is my own best (1:26) after several attempts and I'm sure it can be done better. Instead of Mammoth engines I used groups of 4 vector engines on an adapter, and with onion staging, so there is definitely room for improvement. It's 40 parts exactly.

This looks kinda stock but is it? Looks cool anyway.

Did a mission to test the Vector engine landed on minmus. I used this funny looking craft which took off with 2 kickback boosters strapped to it. Coming back from minmus was where it got interesting, since I had only 200 m/s delta v in orbit of minmus which isn't enough to get back to Kerbin directly, so I used a mun gravity assist to get into a low kerbin orbit, so it took about 110 m/s instead of 300 m/s. Unfortunately due to bad time warps I had to revert it, but I got screenshots. Using mun to get to kerbin since I had almost no delta v.

Did a bunch of missions in the Jool system. I used the nuclear engines and I can't say I'm too fond of them, although they served their purpose and let me be lazy in maneuver planning. My main vehicle was a modification of one I landed on Tylo, so it had all the bells and whistles. The launch vehicle & staging. It's a mammoth engine and 8 kickback SRBs. My final launch had nosecones on the SRBs which stopped them from colliding with things upon decoupling. A decoupler on a structural support on the fairing was the attachment method I used. Bop refeuling after Pol. Some of a Bop -> Tylo -> Laythe capture maneuvers. My exit out of Jool SOI using Tylo (this is probably not the best way to gravity assist). Coming back to kerbin and burned about 5000 delta v slowing down (due to not planning too well - initially I came in at 5700m/s and needed almost a 20 minute burn to slow down), but at least the mission was faster for the kerbals. I had plenty of delta v, was able to land and got lots of funds, like 2-3 million.

I had problems with scatterer crashing in 1.7.3. Removed it and haven't had any crashes since.

I did the challenge in OP, orbit kerbin and return, but with 6 parts not 10. I used the biggest SRB, a decoupler, a swivel (for elec generation and gimbal), mk1 command pod and small parachute (best aerodynamics I found for takeoff). My initial orbit was a bit high but was able to land. The main challenge was getting the ascent right with only reaction wheels in the command pod, but after a bunch of tries I got it, pretty much hold right. For descent, I used the swivel to stay retrograde and also burn the engine so the parachute would activate. Fun challenge using only the 1.25m parts.

You mean this? The engineering sounds insane. I'm interested how well the stock electric props do, but I imagine solar panels could introduce a lot of drag which is something his ship tried to avoid.

Mission plan was a single stage from Kerbin orbit, land on Tylo and back, using ISRU on Pol first, then Tylo. I used 6 Terrier engines for the low TWR burns, because they're pretty efficient (345 ISP). For the tylo landing and low altitude "oberth effect" burns I had a single Vector engine (315 ISP). Since it was already pretty heavy, it was easy to stick all sorts of accessories on it. Delta V was about 4500 for terrier engines alone, and 4200 when adding the Vector. Landing on Tylo it's best to have a pretty high TWR so you can approach fast and not pick up too much vertical speed on the way down, and also take off fast. Pol was chosen for its low gravity and not a huge burn to Tylo (only 210 m/s or so to a Tylo gravity assist) and small inclination. Bop was beyond my patience and probably not a huge savings on delta V. Burn from Kerbin to Jool/Tylo Capture from Tylo and encounter with Pol next orbit. Not that efficient but couldn't pass it up. Pol landing and ISRU Pol to Tylo gravity assist to a future Tylo encounter at slower speed. Arrived at Tylo in a polar orbit, which was not a big deal since it rotates so slowly. For the Tylo landing I first used the Terrier engines to get to about 1600m/s, then switched on the vector engine and used mechjeb "land somewhere" - not the most efficient but Tylo was really hard to judge for starting a suicide burn. Landed near the equator for the future burn to Kerbin. I tested landing and takeoff a lot before committing to a mission, to make sure I'd have enough delta V to get straight back to Kerbin.. in retrospect it would have been smarter to go back to Pol for refueling - that way I burn to slow down at kerbin and land the whole craft. Tylo landing. Some delta V to spare and great TWR of almost 4. I had 1 large drill (balanced by some empty ore tanks and an experiment storage module), 1 large ore converter, 2 fuel cell arrays, 3 RTGs, 4 solar panels, and 6 antennas. Ladders on opposite side. A neat Jool-rise on the Tylo takeoff. Due to massive oversight, this was NOT a good way to re-enter kerbin at 4000 m/s and it would flip around and explode. Luckily I had included a decoupler just in case, and took all the 2500 science into the command pod for reentry. Was hoping to land the whole thing on Kerbin but didn't want to go through the trouble of gravity assisting to a reasonable speed. Original craft at launch

I did a straightforward mission to Ike and Duna which costed 260,000 for the vehicle and rewarded about 4,000,000. One of the 3 missions was transporting about 3000 ore from Ike to Duna which I planned into the mission. It also needed to support 11 kerbals for another mission. The main stage had enough fuel to circularize around Kerbin, but not enough for the burn to Duna, so I had filled all the ore tanks prior to launch, and converted ore to liquid fuel while waiting for a good transfer window to Duna, then converted the rest while on the way to Duna. The Ike and Duna landings were pretty simple and I had more delta V than needed. Might even be able to get it back to Kerbin in one piece cause the vector engine is so good. Vehicle at launchpad I clipped a vector engine into the fuel tank to allow easy landing in the main stage. Also you can see some ore has been converted to fuel at this point, with more to go, so delta V is lower than actuality. Ike landing Duna landing. With 8 main parachutes it wanted to fall at 30 m/s. One of the 3 missions completions. Also, you can see I put the ore tanks at the bottom to lower the center of mass. It didn't have much problem landing on slopes.

Finally got a very cheap first mission home from Jool, no ISRU and only about 3000 delta V at LKO, using mainly gravity assists to get to Jool and back. Didn't take screenshots of the first part, but I took the Kerbin-Eve-Kerbin-Kerbin route to get to Jool (seems to be the easiest), so the initial burn was only about 1000 m/s to get the initial Eve encounter from LKO. More delta V spent fine tuning encounters. Used Tylo to reverse gravity assist into Jool orbit, and was able to do science and crew reports at a few of the moons, resulting in a lot of experience and science for a cheap price (1000 science and 44 xp for the crew without landing, mainly from the Jool system, with 70,000 cost of launch vehicle). The more difficult part was getting back to Kerbin. I had a highly eccentric orbit of Jool and wanted to use Tylo for the large boost back to Kerbin . My first attempt was a failure, going into an extremely eccentric Kerbol orbit and attempting gravity assists off eve to return to Kerbin, but couldn't manage to get it to work. Tylo can give pretty extreme gravity assists from a highly eccentric Jool orbit, probably enough to get to the sun. What worked a lot better is shown below, where I time-warped to a standard transfer window from Jool to Kerbin (kerbin about 45 degrees behind Jool, which I just estimated visually), dodging the moons in the mean time, and finally setting up a Tylo assist to get the Kerbin encounter. The Jool escape burns used only about 100 m/s delta v total, much better than the 2800 m/s needed without assistance from the moons. I returned to Kerbin going 4500 m/s and aerobraked beginning at 52000 meters with NO heat shield, and using the remaining 1000 delta V I had to slow down and make the craft lighter. Due to not planning this mission very much, with only 4 small solar panels and no external batteries, I had to get out and push the craft to pick up some Jool area sunlight for reaction wheels to work. The original craft, only about 70,000 credits, with 45,000 of those in the main stage inside the Fairing, which circularized the Kerbin orbit and did the rest of the mission including landing back on Kerbin 20 years later fully intact. Final return to Kerbin, after several aerobrake passes beginning at 52000 meters with no heat shield, and burning the rest of the fuel (about 1000 m/s) to increase deceleration from drag, then doing a water landing. In addition to 1000 science from crew reports, the pilot gained a lot of experience, mostly from fly-bys of Jool moons. This kind of mission was quite hard the first time, since I couldn't find any guides to show how to set up all these gravity assists. However, one thing I realized is the Kerbin-Eve-Kerbin-Kerbin assist route is pretty consistent because once at the Kerbin-Eve transfer window, the future position of Kerbin after the Eve assist will be consistent so one can set up a the first Kerbin assist to get a 3 year orbit for a second a Kerbin encounter (again I cite bradley whistance who called this the K-E-K-K-J route in his Odyssey by Bill series), which will make the final Kerbin assist out to Jool possible with a large margin to get a Tylo reverse gravity assist into Jool orbit. Also I assume the initial Kerbin-Eve transfer window needs to roughly lined up with some Jool transfer window for the final Kerbin assist to get to Jool, but I think when starting a new game it is pretty close. My guess is there is there's a window for all to happen about every 3-4 years but I'd like to know if someone knows. It depends on the angular resolution or granularity of the Kerbin-Eve transfer windows, which I believe is about every 1.6 years or 144 degrees, but inclination is a big factor too. If this math seems intimidating, I feel the same way.