razark

From what I've seen, it's reading off the bottom of the ocean. Close to shore you will get a positive reading, but once the sea floor falls off, it goes to -1. Either way, it's not a valid altitude, but if you're over water close to shore, your trick will fail. Just something to be aware of.

When you open the terminal, what version does it give? kOS Operating System Build 34562 KerboScript v0.5 Proceed.

It's called Yakety Sax, and it's been suggested many times in every one of these threads that comes up.

*looks at poll options* You, uh, got some problems there, don't you? Did you mean as teammates, or as equipment?

Here? No. Thread should have ended on July 25th, when people stopped posting to it. Or a week ago, when one person posted to it.

Nothing in this restricts what anyone can build. It just asks that they describe what they build. It's less a request for an "aircraft standard" than an "aircraft description standard". It makes sense to explain what your aircraft can do in a standard manner. Makes comparison easier.

Julius FuÄÂík's Entry of the Gladiators or John Cage's 4'33"

Sorry, it was the only thing I could think of. The only other thing that comes to mind is a conflict with another mod or a bad install. Have you tried a clean install of kOS? I can agree with this. Any volunteers to write the textbook/reference?

It's not the capitalization. Note the part that said "Program runs fine on it's own...". The code is actually lowercase.

You can, but I was having problems with it. http://forum.kerbalspaceprogram.com/showthread.php/47399-kOS-Scriptable-Autopilot-System-0-45?p=633912&viewfull=1#post633912 Program runs fine on it's own, but steering and throttle commands have no result when run from another program.

TARGET:DISTANCE is in there. (Edit: Really? Do we really have to parse in emoticons in the middle of words?) Square root is x ^ 0.5

Except he's not using <liquidfuel>, he's using stage:liquidfuel, which should work. Panichio: Try: wait until stage:liquidfuel < 0.01.

If I run a program from inside another program, the steering and throttle commands don't seem to respond. For example: //Program1 ... IF [i]condition[/i] { RUN [i]program2[/i]. }. ... //End Program1 //Program2 ... PRINT "Prograde". LOCK STEERING TO PROGRADE. LOCK THROTTLE TO 1. PRINT "Burning.". ... //End Program2 When condition is met, program2 runs. It will print "Prograde", but the ship never turns. Likewise, the "Burning" message is printed, but the throttle never activates. SAS is off. I'm trying to set up a menu system, and I'd rather not stick all my code into one program. Any ideas?

Yay, a new version! And they're all wrong, except mine. Yeah, I did mean the ones on the left. Is it my imagination, orisitmissingsomething?

Looking for something that can do something like "if target is set". Also, is there a "not equal" operator that I missed?

When I try and launch, my command pod is nailed in space. I fire full throttle, and the ship goes nowhere. I stage, and the second stage burns for all it's worth. Stage again. There's a pile of rocket stages below my ship now, but I haven't so much as moved upwards. I'm on my final stage; it burns out and is staged onto the pile. Nothing to do now but abort. Push that big red button, watch those sepratrons burn, pushing my capsule... nowhere. My rocket spent, all propellent gone. The stages lie in a heap on the pad, and Sherbas Kerman calmly looks out the window, and sees that his glorious spacecraft has moved not a damned inch, and now hangs stapled to the sky. Ah. Thank you. I didn't know we had exponents. Do we have a full list of which mathematical operations we have?

We've got latitude and longitude. If you take two of those, separated by a known time, you should be able to determine surface direction and velocity, yes? I'm not up on the math for that, though. I'm guessing it probably involves some trigonometry we don't have right now.

Requests: I'd like to have access to the orbital period of the vessel. The game clock would also be useful.

Very strange indeed. I've tried a few things. It doesn't seem to like your variable name. Try renaming it something that doesn't use "orbit" in the name, and make sure you initialize it before trying to use it. It doesn't seem to have anything to do with blank lines, because I stripped everything out except the print statement, and a SET..TO line.

You might try running "copy program to Archive." by name instead of number after writing your program. I've seen archive show up as volume 1 before (multiple computer units on the vessel).

Yes, I just downloaded the new version this morning.

I'm not having that problem here. I'm seeing lines with multiple variable and literal strings printing fine. print missiontime + ": Stage 1 separation.". print "MECO: " + missiontime + " " + altitude. print missiontime + ": " + status + " " + body. print alt:apoapsis + " x " + alt:periapsis. All of these have worked fine.

As long as the ability to turn it off (or set custom settings for it) is coming, I can live with it. I'm just picky about my indenting style. Got drilled into me by an early professor, and anything else just feels wrong, and the inconsistent way tabs are displayed across programs irks me as well. Sounds good. I like not accidentally overwriting my files. Edit: Can you start your line numbering at 0? kOS starts at line 0, so when it reports an error on a line number, it would be nice to look at the same line number on kIDE.

What is the "Smart Indent"? Does this mean that the code will automatically indent certain sections of the code? If so, can this be an option that we can turn off, please? Also, it would be really, really nice if it would detect that the file has been updated and either alert us, or alert us and offer to refresh to the new version. Because, you know, saving over stuff kinda sucks. (Or maybe I should just edit from either KSP or this awesome IDE instead of both...)

What I'd love to see with regard to RT and kOS integration is the ability to enter a program, hit an "Upload" routine to load the program to the ship. The length of path and length of program would determine the time needed to complete the upload. Once you had uploaded programs to the ship, you could send run commands to those programs, and they'd execute at the appropriate time. Results would arrive after the delay as well.