PDCWolf

Never cheated. By the way, both in hyperedit and mechjeb you have to press a button to go to orbit, unless you made a really crappy and uncontrollable rocket, so how comes one is cheating and the other isn't?. Anyways, before anyone gets mad, I like to believe that definition of cheating is just for this thread and not in general, even if people agrees with it outside the thread.

Well, my first thread on this section and it is about Conqueror-1, my Nth mission to Mun. I've already done Apollo style missions before but never recorded them, so I though this would be a good opportunity to do so. As you can see, the video has "reduced version" in the title, that's because the entire flight took an hour and I managed to reduce it to 10 understandable minutes. I hope you liked it and thanks for watching.

Just for this thread. No RCS, No ASAS, With deadly reentry. Click to enlarge. Liftoff After separation Target set Landing Flag Getting Home Splashing West of KSC

This is the same as saying "Germany is going down because most germans are jews"

Not really, since the real-life concept for SSTO with nowadays non-experimental technology will be to go as high as possible with jet engines and then start your rockets, not reaching orbital speeds while in atmosphere as our SSTOs do, which in real life is just stupid (look at x43 and x51, they just go for 30 seconds and then burn themselves to pieces). About reentry heat, it'll obviously add a layer of realism to the actual game that lacks it a lot (I mean, come on, don't even try to think KSP is realistic in its actual state). About reducing the reentry heat, you just need to enter at less angle, a good practice is putting your periapsis at 55 km and place it around 170km before your actual landing target (this is talking with an apoapsis of 70/75km) and that should solve all your heating problems.

Go higher than 30km so that LOD takes effect, then you'll see the horror. Also works in map view.

I like how someone exposes a bug and you just go "HAPPENED BEFORE LOL" You are supposed to fix bugs with versions, not keep them.

Thanks for giving me the winning hand. As I could have saved myself the insults by "thinking more", they could have done the same by testing more. Going back to what I said, we are talking opinions here, except for a one or two coherent remarks that seem to be objectively centered.

They could waste time and save themselves the insults and save the devs 2 pages of bug reports (that's 2 pages without including cloned threads) by testing the game more intensively or maybe with a bit more time (I mean, come on, there were bug reports right at the time the update was launched).

"A small minority" is what filled 2 pages of reports in the bug/support section, not only doing threads but commenting as well. The update was supposed to make the game work better. The only thing that made the game "work better" -in quotation marks because it's really not measurable- was making the game uglier. The oceans are made of lag now and on top of that they removed (or didn't include) a layer of customization options needed for people to fix this by themselves. Just imagine how the amount of complaints would have decreased if they had put an option to keep the old planet textures or use the blurry new ones, same goes with the water. On top of this comes the pushed back features like resources and plain badly designed stuff like making the seats an unmanned part instead of a creweable one. AND on top of that comes the horrible work made by the "Excellent QA Team" that didn't notice any of this or the exploding flags or the forever lost underground rovers/bases. If you still want to mix the bad stuff pot, throw in the fact that they only took what already had been made for kspx and addded 2 ivas as in "no effort was put". Just my opinion, nothing to get mad about.

130. (there are 2 128) We do lithobraking with full big orange tanks and steel platforms.

107. Our spaceplanes travel at multiple times the speed of sound without burning. (x43 and x51)

No, it wouldn't. All my exams are on this week, and those are really important exams. Bombing only one will make me lose 2 years of progress. Srsly.

NERVAs have an ISP of 800, being the most efficient engines in vacuum.

I remember having an orange tank with only one NERVA and 4 probes docked to it through a docking ring. I took that thing to Eve. On top of that, I forgot to put one of those small x16 tanks on the bottom, so not only it took loads of PE kicks because of the TWR, but also because I had to burn at mid throttle or less to avoid overheating.

I only put instruments according to the mission, I mean, why would I need the extra drag and weight caused by atmo pressure and temp instruments when going to Gilly for example. In this case I included them all, and it turns out Jool has only 7.something m/s² of gravity, which is less than kerbin.

LEADERBOARD UPDATED I'll be doing a video too, I seriously hope I get a 100 this time.

Following the events of my First mission to Jool and as soon as the phase angles were right, JASP took off the launchpad at KSC. JASP - Jool's Atmosphere Surveyor Prove - was a one time only probe developed to be destroyed under what our scientist though was below Jool's clouds. The mission objective was to get readings on temperature, gravity and atmospheric pressure at different heights, till the predicted destruction took place. Given the probe's weight (around 500 kilos) JRO's launcher was used once more and with excellent results. at T+209:12:56 we began aerobraking and separation operations. After some minor corrections, JASP separated from the interplanetary stage. JASP opened it's antennas, getting a less aerodynamic profile and falling behind the LV-N stage. Once reentry heat dropped down, chutes opened in their drogue mode. Here's a pic from one of the probe's cameras. At this point, our instruments detected our altitude above "something". That gave us the idea to take our readings at certain heights instead of doing it on time intervals as we originally planned. This is our first reading, taken at 50000 meters above the ground. The second one, took at 25000 Third one at 10000 Fourth reading at 5000 Fifth reading at 2500 After that, the chutes deployed completely, leaving us falling at the worrying speed of 0.8m/s . At this point our scientist started joking saying that "we were going to fully stop in the atmosphere". We were approaching our supposed "last reading" at 10 meters, here it is: After that, everyone went crazy because we were going "below the ground". We took our last reading at -25 meters. Some seconds later, everything blew up. The last readings were "15.75 atmo pressure - 1000 degrees celcius", and thus, operation JASP came to an end.

it's from the default altimeter, so that would be sea level. I tried that, and the probes ripped the rear half of my spaceplane so I couldn't pull up in time.

Guys, yes, those saying "the learning curve will keep them away", you are forgetting about mechjeb.

Thats why the parachute is there. it's just so that you can switch vessel and look where it landed. If you used mods (like those cameras for example), then no. Otherwise, you got 100 points.

That moment when you have the perfect planetary injection with aerobraking included, then you fast forward till you are inside the atmo and do something wrong, you press quickload and you are back at the launchpad.

Right now, all arguments are pointless. The real thing will show up as soon as there is career mode (thank god devs don't want to include achievements, just imagine "the madenings" that will bring) where using mechjeb or any other autopilot could be considered cheating.

That's because you are getting 2.5 km away from them before they touch the ground, try flying more slowly.

Time for a fun challenge! This one's about, as the title says, precision bombing. How to participate: •You can either use an existing spaceplane or create a new one •Attach the bombs (see design below) to it. You can attach as much as you want but only your best try will be scored. •Take it to the runway and take off. •Fly above the launchpad and drop your bombs (you can either drop all or one at a time, this is up to you). Scoring system: •Each bomb will be scored separately, and only your best shot will be taken into account for the leaderboards. For score data, refer to this picture: Validating your score: For your score to be valid your post needs to have the following: •A picture of your craft on the runway. •A picture of your craft dropping the bomb (see rules below for more specific information). •A picture of the bomb landed on the target area. (see how to get this one below) •A picture of the plane landed on the runway after dropping the bomb. Rules: •No mods (that includes non-physical mods such as mechjeb or any other autopilot). •Bombs have to follow the presented design or, at least, the basics of said design. •Bombs HAVE to be dropped from above 100 meters. •Absolutely no vtols, helicopters or hovercrafts. •The spaceplane, after dropping the bomb, has to be returned and landed safely (Safe as in there's more than 5 remaining pieces of the spaceplane) on the runway. •You have to land on runway 27 (that would be the "wrong" way). This is to avoid one of the multiple ways of falsifying your attempt. BOMB DESIGN Keep it simple, I used a design I already had available (those are supposed to be hydrophones dropped from an airplane, I modified the concept a bit and ended with this challenge) The bombs are made of: •OKTO core •MK16 Parachute •2 Z100 Batteries •2 OX-STAT panels •1 comunotron 16 You don't need the antenna, batteries or the panels, but you need the core so that it is saved as a flight and you can take a pic of where it landed without much effort. To make the challenge valid, here's my attempt: At the runway Dropping the bomb Where it landed - as you can see, it's more on the ramp than on the top, so that would be 80 points. The plane landed -LEADERBOARDS- 1- Kerbies_are_my_minions - 100 pts 2- Jonv4n - 100 pts 2- Read have Read - 90 pts 3- PDCWolf - 80 pts 4- 5- 6- 7- 8- 9- 10-