MaxL_1023

A change like this would be almost as significant as switching to numerical N-body simulation, if not more so. Implementing this would be worthy of a new game release - a true sequel. I would expect to see it eventually, as KSP seems to be selling enough to justify a sequal or at least a bunch of copycats. Axial tilt would also make the game quite incredibly annoying for newer players, with every interplanetary ejection orbit putting you onto a different solar inclination and also messing up gravity assists and all transfer burns. Mechjeb's porkchop plot could probably handle it, but it would turn into a near-necessity for interplanetary travel.

The main issue is air drag. You can never be sure how much you will run into and it varies according to nonlinear relationships involving altitude and speed, among other things. What I used to do was use a somewhat overpowered liquid engine, so I could reach the minimum speed before the minimum altitude. Then, I would throttle down until I was very slowly accelerating, reaching the target speed at the bottom of the altitude range. Then, trigger your Hammer (or hit the test button). If you have to activate it through the staging sequence, you could have two as radial boosters and use your liquid core to lift them up. It is not efficient for launching (obviously) but if all you want to do is test them it should work. Just make sure to use the Swivel so you have throttling as well as thrust vectoring. It would be almost impossible to do with pure solid rockets - an iterative approach would be as effective as anything considering the complexity of calculations.

Now streaming the design, launch and occupation of Kerbal-kinds first permanent space station!

Pale Blue Pixel Episode II: The Kerbnik Series Kerbal science is strange - their government even more so. Idealistic to a fault, Kerbal researchers tend to obsessively focus on any area which is currently providing new data. The space program is no different. When the Kerbal series returned the first scientific data from the upper atmosphere, dozens of talented (and somewhat unstable) scientists flocked to Wherner Von Kerman's research lab. Every single one of them wanted to research some aspect of space travel. At this point, low hanging fruit was still available. Basic electrical technology and improved guidance computers were already present in aircraft and ground-based infrastructure. All that was needed was some reprogramming, debugging and hardening against the conditions found in near-vacuum. Before long, the Kerbal 2 provided the final push needed by the research program, sending back information from beyond Earth's atmosphere. The proof that space existed, was reachable and was survivable by the use properly protected equipment (as opposed to riding a firecracker using a command seat) led to a crash program to develop technology known as "Early Orbital Rocketry." According to the now overexcited Kerbals, these engines had a chance of pushing an object so hard that it could reach orbit. The Kerbnik program was born. The amount of kinetic energy required to put something in orbit dwarfs that needed to merely peek above the atmosphere. When Wherner first calculated the launch requirements, he discovered that using the engines then available (The V2 engine and the small Wac-Corporal sustainer) launching anything larger than a can of soda to orbit would need a launcher so large that Earth was more likely to orbit it as opposed to the other way around. Such was the tyranny of the rocket equation. Better engines were needed. The first design was named the RD-103 - a more powerful descendant of the venerable V2 engine. Burning the same re-purposed home-brew (however at an industrial scale, or at least that of a medium sized fraternity party) it provided enough thrust to lift impressively heavy rockets off the ground. Its small profile assisted in engine clustering, and the improved turbopump control system reduced the damaging thrust oscillations found in its older cousin. The disadvantage of the RD-103 was its terrible fuel efficiency, providing barely 200 seconds of ISP on the pad and not much more when in Vacuum. Lifting its own weight to orbit would be difficult. Competing Kerbal designers provided a new engine design, called the Vangaurd Booster. It burned refined jet fuel, leading to somewhat better efficiency. This engine pioneered the gas generator cycle, where small amounts of fuel were burned separately from the main combustion chamber in order to drive the main turbopumps. While somewhat unreliable, the elimination of a third propellant and the superior controlability provided by the generator suggested myriads of future applications for this engine topology. The drawback of this design was its relatively low thrust, being only about one third as powerful as the competing RD-103. It was not strong enough to support an orbital launcher at a scale useful to the space program. A third engine design was developed by the poor Kerbals in charge of cleaning out (mostly) empty fuel tanks which were littered around the test stands. They used a rather overpowered leaf blower to push any remaining fuel or contaminants out of the tanks. By connecting an overfilled balloon to a straw which then emptied a small bulb of water, the idea was formed to pressurize the fuel inside reinforced tanks, proving enough energy to eliminate the need for a turbopump. These pressure fed engines were ideal for small scale, restartable designs - especially those using hypergolic fuels which only needed to look at each other to ignite into a propulsive inferno. The result of these labors was the first of the AJ10 series. While far too small to life anything practical off the ground, it was the safest and most efficient of the available engine designs. However, no engine currently available was capable of meeting the requirements of the Kerbnik program. The breakthrough came when a bored intern was playing with a sketchily-constructed model rocket. Using solid fuel, it normally could only rise about 50 meters before burning out. However, when this one was lit off (with the intent of scaring the local wildlife) a defect in the rocket body caused the bottom half of the rocket to fall off shortly after launch. Thankfully, the combustion point had already risen past the break. The rocket kept rising - at an accelerated rate. No longer dragging the heavy bottom assembly, the remaining piece (while somewhat unstable) managed to reach nearly 100 meters before falling back to the ground. This gave the intern an idea - what if they took a big rocket, then launched a smaller rocket from the top of it? After some rather sketchy concept art, staging was discovered. It was decided to use the AJ-10 as the final stage, igniting in vacuum to provide the final push to orbit. The payload and AJ-10 stage would be lifted from the middle atmosphere by twin Vanguard boosters. This larger assembly would be de-lithobraked by a cluster of three RD-103 engines. Operating in series, the resulting design could theoretically put a reasonably sized science package into low Earth orbit. Enter Kerbnik I. The Kerbnik I was many times larger than anything previously constructed. Standing over 30 meters tall, it represented the efforts of hundreds of Kerbals, thousands of snacks and several rapid dissassemblies (both planned and unplanned). Early one morning, the Kerbals first attempt at an orbital launcher was rolled out to the pad. When the time came, the trio of RD-103s were lit. When they built up to full thrust, strain gauges within the four symmetrical launch clamps triggered their release. Kerbnik 1 began to slowly rise into the morning sky, on launch managing roughly 5 m/s2 of vertical acceleration. As fuel drained from the tanks, this figure quickly rose. After barely a minute of flight, Kerbal 1 had reached higher than any air-breathing craft, travelling at 3 times the speed of sound. At this point, all became quite. Fully spent, the first stage was dropped to fall into the Atlantic ocean. After separation was verified, the Vanguard engines were ignited. A trickle of kerosene and pure liquid oxygen were fed into a small chamber, where a spark ignited them into a miniature version of the engine itself. While woefully insufficient for lifting purposes, this process provided enough energy to push a flood of propellant into the main combustion chamber. There, the first gas-generator engine was ignited, continuing Kerbnik I's flight. Not as voracious as the previous engines, the second stage pushed the Kerbnik I onto an ever lengthening ballistic arc. Designed to burn for 3 and a half minutes, this stage was quickly the fastest object ever created by Kerbals. Travelling onwards and upwards, the second stage pushed itself to an eventual apogee of nearly 280 Kilometers. When it was finally spent, the velocity gauge showed 4.7 km/s relative to Earth's center. While not fast enough for orbit, it was far beyond anything previously seen. The spent second stage was detached, to eventually land somewhere in the Eastern Tropical Atlantic. At this point, pent up pressure in the final-stage fuel tanks was allowed to vent through the AJ-10. On contact, the propellants ignited, producing a relatively gentle push. While nowhere near as strong as the earlier stages, the now much lighter assembly continued to quickly accelerate. Barely 3 minutes later, the velocity gauge reached the critical value of 7800 m/s. From now on, Kerbnik I would not fall back to Earth. Instead, it world circle the globe, potentially for hundreds of years. The designers of the Kerbnik I packed a little more fuel than was absolutely necessary, being unsure how the relatively untested engines and guidance software would perform during their first true test. Therefore, mission controllers were pleasantly surprised to find that the little AJ-10 was still burning away after orbital velocity was reached. When it finally ran out of fuel, the third stage and attached payload had reached 8357.8 m/s - fast enough to travel on an elliptical path which reached a point 3000 kilometers above the South Pacific. For the first time, a Kerbal-made object was high enough to see the entire Earth as the blue globe it was. Sadly, Kerbnik I did not have a camera, having as of yet no way to get pictures back to the ground. However, the Geiger Counter, Micrometeorite Detector, Thermometer, Barometer and the control core still provided valuable information spanning all of low Earth orbit. With a final bust from onboard attitude Jets, Kerbnik I raised its Perigee high enough to clear the last remnants of the atmosphere, ensuring that it would ensure as a testament to Kerbal engineering for thousands of years to come. While the Kerbnik I was the first object to reach orbit, it would not be the last. The moon has beckoned Kerbalkind for thousands of years (or at least since they figured out it was not a floating dinner plate), and Jebediah really, really wants to try this "rocket launch" business out for himself. The Pale Blue Pixel Space Program will strive to make his dream a reality. Video Links: https://www.twitch.tv/maxl_1023/v/110989438

That Kerbal is now a pancake - you need a pretty specific range of trajectories to have a survivable re-entry (under about 12-15gs peak deceleration).

The Pale Blue Pixel Space Program is now live on Twitch: https://www.twitch.tv/maxl_1023 This time, I am going to try and launch a small metal object in such a way as to end up circling Venus, hopefully determining once and for all whether or not female Kerbals actually originate there.

Inclination matching is more complicated than launching at a heading matching the suggested inclination. Assuming you launch when you are directly under the space station, you have to match two velocities: 1. The Prograde orbital velocity (the component in the east/west direction) 2. The Normal orbital velocity (the component in the north/south direction) If you hyperedit your spaceship to the stations radial altitude, find your relative velocity and cancel it, you will end up in the same orbit. However, this is not how you normally launch into orbit. The vector you need to cancel your relative velocity (assuming a gravity turn in the radial direction gets you to the right altitude) will NOT be equal to your target inclination. The planet's rotation will give you an initial velocity which you need to take into account. Over time, this initial velocity will deflect your course away from the proper heading. My rule of thumb is to try and launch from the latitude matching the inclination of the target - this lets you launch due eastwards and match inclinations once per planetary day. This is why you can launch to the moon from Cape Canaveral fairly easily (at least at certain times) - the moon almost passes over that latitude at its farthest northward excursion from the equator. If you are at 37 north and your target inclination is 45 degrees, you should launch about 9 degrees south of east when the station passes overhead (and is approaching its decending node). Burning at -8 will put you a little under 45 degrees of inclination due to the extra starting velocity from Duna's rotation - you need to burn a little farther southwards to cancel this out. Matching just after the ascending node will be more expensive and require a launch significantly north of east, with more of a normal component than the alternative path. I try to put space stations in polar orbits - it is a little more expensive to get into that orbit but much easier to rendezvous and allows any surface site to have two equal launch windows.

Had some tech trouble with my audio - stream is fixed and back up. The good news - I got to the moon. The bad news - nobody could have heard me get there. Next up is a Kerballed Lunar Orbit.

The Pale Blue Pixel Space Program is now live on Twitch: https://www.twitch.tv/maxl_1023 I am planning to do "Moon Stuff."

Pale Blue Pixel Episode I : Explosive Beginnings https://www.twitch.tv/maxl_1023/v/110516999 After the horrors of the second world war (theorized to have been fought primarily over snacks, as is everything else when Kerbals are involved), a brave group of visionaries sought to turn swords into plowshares. They re-purposed military rocket technology, seeking to initiate the peaceful exploration of space. Either that, or Pilot Jebediah Kerman just saw his best chance to ride a controlled explosion into what lay beyond. The engineers and scientists believed they had the technology (referred to as the "Start Node") to make an attempt at breaching the atmosphere. After several minutes of intensive design and construction, the Kerbal I was born: The Kerbal I was a humble design, consisting of a re-purposed V2 rocket engine. This engine conveniently ran on 75% Ethanol, allowing it to burn moonshine confiscated from the astronaut barracks. While the engine was not efficient enough to make a serious attempt at orbit, it was powerful enough to lob a reasonable payload onto an exo-atmospheric parabola. A guidance unit, biological sample container (filled with mice caught in the fields near mission control), a thermometer and barometer were duct-taped to a parachute, then enclosed in a fairing. The ensemble was completed with all-moving control fins (as gimbals were a pipe dream at this point) and the mandatory launch clamps. The rocket was rolled out to the launchpit (as a pad had not yet been built) and scheduled for a morning liftoff. At the appointed time, the Kerbal 1 leaped into the air. However, the lack of wind tunnel testing, general aerodynamics knowledge and the possibility of the entire engineering team being a bunch of basement hobbyists lead to a rather unstable ascent. An attempt to override the guidance unit and take manual control lead to the primary rocket body breaking up at roughly 15,000 meters. The payload persevered, held together by industrial strength tape (kerbal joint reinforcement) and KerbalGlue (autostrut). While the final altitude was within the range of sounding balloons and a few intrepid aircraft pilots, the data obtained from the biological payload provided valuable information on the ability of living organisms to withstand the rigors of a rocket launch. Long story short - 15 G's of deceleration is survivable by a Tardigrade, but not much larger. Learning from their mistakes, the design team spend several additional minutes in the revision cycle. The payload was unchanged, having performed admirably despite near worst-case conditions. However, the fuel tank was lengthened slightly, the control fins were replaced with less extreme models (no more all-moving insanity) and the launch program was debugged. The Kerbal 2 was rolled out to the pad. This time, a near vertical ascent was planned to minimize aerodynamic stress on the still embryonic piloting and guidance equipment. With only 203s of liftoff ISP, this design had no chance of slipping the bounds of earth completely. However, it was hoped that this iteration would finally prove once and for all that Earth was NOT surrounded by a glass sphere which kept all the air from escaping. Hopefully, it would travel high enough to at least make those Flat-Earther Kerbals have to come up with better conspiracy theories. In any case, the liftoff was more successful. While control difficulties were again encountered (likely due to the offset between the control point and the center of thrust) the Kerbal 2 made it to engine burnout. In fact, it picked up enough vertical velocity to reach a final altitude of over 250 kilometers. Backlit by the blinding sun (with no atmosphere to attenuate its hard radiation) valuable science data was obtained from the domain known as near-Earth space. The barometer insisted that it was in a Vacuum, doing so at any altitude exceeding roughly 140 Kilometers. Therefore, scientists theorized that gravity alone confined the atmosphere - Aristotle Kerman must be spinning in his grave. The thermometer was not of much use - alternating between completely frozen and over 100 degrees Celsius based purely on whether or not it was facing the sun. Measuring the temperature of space is more complicated than we thought. It also turns out that bats don't do too well in microgravity. After spending several minutes in space, the science payload re-entered the atmosphere. The large cross-sectional area of the guidance unit protected the remaining equipment, while ending up only slightly melted. It is theorized that conditions would be much more severe re-entering from orbit - additional technology is likely needed for anything to survive this trip. After falling back to Earth on parachutes (found by the side of the road and/or stolen from the local skydiving enthusiasts) the science data recovered was sufficient to bankroll additional research. More powerful and efficient engines were coming down the pipeline, with lightweight guidance units and long range antennas. Unanimously, the Kerbals decided that their next objective was to launch something up into space, then sideways so fast that it missed Earth when falling back down. They call this phenomenon "orbit".

I have updated my mod folder - I have removed Testflight, added a bunch of small mods and also have added Fog of Tech. No more 2000s era rocket tech visible on January 1st, 1950! With these new settings, I am planning to restart my career this evening, with the plan to have all my engines actually work as opposed to randomly breaking after 30 seconds of flight time. I know it is less realistic, but in this case I think it is excessive given the general game infrastructure. The stream will be up momentarily - time to see if I can get to space using Wac Corporals and V2 engines!

Testflight is the most annoying mod I have ever installed. "Lets have your orbital insertion stage randomly fail halfway into the burn!" - I guess it makes you pay for trying to orbit with 1950s level technology.

Using the time travel capability known as "previous version steam beta" the universe defined by the realism overhaul suite has been recovered. This thread documents the progress made by our brave Kerbals in exploring the Sol system, from humble beginnings involving V-2 engines and Aerobees to potential crewed interplanetary flight. Live Streams of career progress are found here: https://www.twitch.tv/maxl_1023 Highlights and eventual edited videos will be posted here: https://www.youtube.com/channel/UC0QP0BvaZg2x2z1YK3tt3AQ I am separating this thread from my 1.21 GPP stream ("Bringing Debris to the Masses") , as it uses a completely different KSP installation and I do plan to play both in parallel over the next few weeks. I will also add highlight screenshots directly to this thread, and post replies to announce my stream (as I both want someone to watch it and have no idea how else to do it). The main modlist: - Realism Overhaul - RP-0 - Real Solar System - TAC Life Support - Remote Tech (Without signal delay for now) - Dmagic Orbital Science and Scansat - Whatever visual enhancement mods I can get working - Many more minor mods for parts, etc.

I'm back - I will continue with my 1.21 GPP stream. However, I am also in the process of trying to set up a 1.13 install with RO/RP-0. I will be playing both assuming I can get them working.

Thank you guys - I will probably just wait for RO then, as trying to mess with those configs is more likely to make my pods randomly explode given my current knowledge in the area. I will need to learn more about these modules and how they are configured.

Hello, Are there any mods besides the realism overhaul suite which allow a lifting re-entry by offsetting the command pod's center of mass? I am currently playing a 10x scale game in 1.2.1 with SMURFF, as RO is not ready for 1.2 yet. Also, which mod within RO allows this? I might be able to install it into 1.2 by itself. I am having some G-forces trouble doing purely ballistic re-entries (have the crew unconsciousness enabled) and can't seem to perform the maneuvers I could back when playing RO in 1.13. Thanks, Max

Try sigma scaling your career - in 10x a class E was 3 million tons.

I am playing a 10x career - I scaled planetary radii by 10, all orbits by 11 and terrain by 0.25. I scaled atmosphere by 1.25 and atmosphere top by 1.5, putting the top of Gael's atmosphere at about 130km. Most of the other configurations I left as default.

I will not be streaming until the 27th most likely - currently visiting in an area without enough internet bandwidth. It will give the crew enough time to figure out how to get the 300 ton propulsion module to dock with the 300 ton orbiter/lander vessel.

Is there a mod out there which has 5m or 7.5m command pods following the normal conical shape? I have ran into a few applications in my career games where I would like to carry more than 3 or 4 Kerbals, and having a hitchhiker disrupts the re-entry stability of my ship. I would be looking for something like a 5m base with a 2.5m top node, basically a Mk 1-2 pod with all dimensions doubled. I also play 10x scale often, so I could use the larger pod to fit with larger ships in general.

Now streaming the launch and orbital assembly of the second crewed mission to Niven!

Live-Streaming Ceti Mining and a follow up Niven mission!

So based on this theory, modding KSP might cause my computer to collapse into a black hole and/or turn Jeb into a hologram. I will keep installing away in order to test this prediction.

The turbo-machinery for each is about the same size - the nozzle and support structure makes up most of the size difference. It is also a balance trade-off between thrust and efficiency. If the upper stage engines were more powerful there would be little reason to use the lifter engines - it would be better to use the upper stage engines as ground-lit sustainers and strap some soilds on to get you off the ground. Atmospheric pressure drops off fast enough that (at least in RSS scale games) it is often better to use a Vacuum engine quite low in the atmosphere - they often exceed the performance of lifter engines by 10,000m or so. Dirt-cheap SRBs can get you that high in under a minute.

Live-Streaming Space Station Shenanigans!