Starwhip

Negative One.

Oh, why am I doing this to myself... Damn you, Google. You too, Bing. Well, at least the second image is relevant: EDIT: OOOH! KSP+Starwhip gives me this image! I remember that one.

I say that Starstreaker III is my nicest. Why don't I have any screenshots of it without the UI? I like whistleheads' itty-bitty SSTO.

Spare us defectors a chance. One.

Let's not! Zero.

I want to give you some rep so bad, but I've given too much out lately... Still, this is awesome. First full-stock podracer I've ever seen. (The others use KAS and other things)

Yes, I used to have to do this. But there is a solution: Go into your computer's BIOS on startup, generally F2 or F10 (Really spam these the moment you hit the power button!), and there's an "Action Groups" option. Turn it off to switch the functionality: Now, F1 will do what the program running says F1 will do, and Function + F1 will do whatever the computer says it should do, in my case, bring up Windows Help. Totally useless.

Bad Rune! Bad! Go make your own tail! And you're both behind me: Anyway, this looks really nice! Much more compact than mine.

These things just keep popping up like weeds. Merge, perhaps? http://forum.kerbalspaceprogram.com/threads/111365-COM-COT-COL-hard-to-use?p=1751436#post1751436 http://forum.kerbalspaceprogram.com/threads/110290-Center-of-Mass-Marker-Overhaul

Have you ever seen this one before? KSP, don't do this to me!

Negative One!

That's not something you see every day! Useful things to know for taking screenshots: V: Switches camera. There are several modes which might please you. The arrow keys work for rotation. "+" and "-" zoom in and out. Holding down the mouse wheel pans the camera when you move the mouse. (Why is there no key to reset this? ) "M" goes to map view, and comes back if you're already there. "C" goes to IVA and back. Changing to map view, or IVA and back, might fix the panned camera. I have not tried it, nor noticed it before, but I haven't been paying attention to that in particular.

There is a harder challenge, but you would be crazy to take it up: Descend to 0 meters on Jool, then back up to orbit. Anyways, this seems to be largely answered, and as I've done neither, I'm afraid I'll be of little help.

No, they're not. This is an example of the rotor itself. You attach wings and SAS to it, spin it, and it gives you thrust.

Zero.

Like 1.0 is supposed to be? We'll see. Anyways, there are some interesting responses here. And it seems that this has turned into "How should SQUAD fix their bugs?", rather than a discussion on the thruster ports, which it was supposed to be. So, let's assume that, magically, it would work. Should they have them then?

Oh, look, the desert temple! Very cool.

Off on moderating business. Now, where did Vexx run off to?

Negative One.

Oooh. That'll get me using it again! The reason I want it is because of this: lock oxidizer to round(ship:oxidizer,2). lock liquidfuel to round(ship:liquidfuel,2). lock intair to round(ship:intakeair,3). lock apoapsis to round(ship:apoapsis). lock periapsis to round(ship:periapsis). lock apeta to round(eta:apoapsis,1). lock peeta to round(eta:periapsis,1). lock alt to round(alt:radar,1). lock vertspeed to round(ship:verticalspeed,1). lock surfspeed to round(ship:surfacespeed,1). lock jfloxratio to round(((liquidfuel / 0.9) / (oxidizer / 1.1)),3). lock impacttime to round((alt/vertspeed),1). until false{ clearscreen. print "Apoapsis: " + apoapsis + " m ETA: " + apeta. print "Periapsis: " + periapsis + " m ETA: " + peeta. print "Radar Alt: " + alt + " m". print " ". print "Liquid Fuel: " + liquidfuel. print "Oxidizer: " + oxidizer. print "Jet Fuel / Lox Ratio: " + jfloxratio. print "Intake Air: " + intair. print " ". print "Vertical Speed: " + vertspeed + " m/s". print "Surface Speed: " + surfspeed + " m/s". print " ". print "Notifications: ". if alt < 1000 and alt > 10{ print "CAUTION: LOW ALITUDE". if vertspeed < 0{ print "Impact in: T- " + impacttime + " seconds". } } if liquidfuel < 50 and liquidfuel > 0.05{ print "CAUTION: LOW LF". } if oxidizer < 50 and oxidizer > 0.05{ print "CAUTION: LOW OX". } if intair < 0.2 and intair > 0.05{ print "MASTER CAUTION: LOW AIR". } if jfloxratio <= 1.2{ if jfloxratio <= 1.05 { print "MASTER WARNING: JET FUEL/LOX RATIO". } else{ print "MASTER CAUTION: JET FUEL/LOX RATIO". } } wait 0.1. } When I had it also displaying thrust and flameout conditions of engines, the engine lines would flicker because of the for loop that was required to check all of the engines. (Without hardcoding, of course. But that's a bad habit. )

One again.

Yeah. Especially the phasing bit.

This one in particular.

Nein! How about tetryds?

Should go in the Addon Requests section. Seems like a cool idea, and doesn't look that hard to make.