razark

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.

With "ON AGx SET variable TO value." type of stuff and loops, I could see input being done in a primitive way. I haven't tried it, but I wouldn't mind knowing how it was done.

But they're using some sort of mod. If you look up at the top, you'll see they have some sort of short orange tanks.

Saw the readme/changelog updates and video earlier, but just got home. Haven't had a chance to play with the new version yet. So: does radar altitude function at any altitude, or does it only register when close to the ground? Edit: I can verify this isn't working. Edit2: "wait until stage:liquidfuel < 360" causes execution to hang. "print stage:liquidfuel." prints correct value. Edit3: "print alt:radar." outputs a "-1.00" over deep water. I'm guessing it has an upper limit in the 3000 range (like the dial), but it's reading from the sea floor, not the water surface.

I'm running these two, and haven't noticed such an issue.

You could go edit the .cfg files to add the functionality to probes (and capsules, if desired). Edit: Would it be possible to have more than one terminal available? I can see the value of running a program on one while working on another, or using one to display flight data.

No, thank you.

I'll see your radar altitude and raise you current values of any scientific instruments. And more robust expression handling.

Yeah, that occurred to me. I tried to turn off most of the power consumption so that it would drain slowly. I don't know how accurate the numbers on the resources display are. The display has two decimal point, but is that how accurate it is internally? Does it go from 20.01 to 20.00, or is it going in even smaller steps, making the polling window even smaller? WHEN (<ElectricCharge> - 20) < .01 THEN PRINT "TEST". I wonder if we can have an absolute value operation?

WHEN <ElectricCharge> = 20 THEN PRINT "TEST". This doesn't give an error, but it doesn't seem to trigger, either. I'll try the stage:electriccharge next flight. I'm trying the reentry program now. And so it did. Right after popping the chute. Watching that power drain as it approached deployment altitude had a nice pucker factor. I either need a quicker reentry or I need to keep the service module longer.

I haven't tried anything with solid rocket boosters. But it should be working with everything in the resources section. Hey... that means we can add coding to open the solar panels when electricity runs low? Would that work? (Ignoring the incorrect syntax, and assuming AG1 opens the panels...) Run a "WHEN <power> < 5% { TOGGLE AG1. }." and then have other programs running in the background? Edit: This should work, correct? WHEN <ElectricCharge> < 20 THEN PRINT "TEST". It gives me: Unrecognized term: ''. Also, does the computer itself draw power?