razark

Unless you want to copy code over before sending your ship on a long voyage. For example: copy, modify and run the launch program, then delete it and load software for landing before heading to Duna.

Go scrounge the videos, the forum, the readme, the blog. Read the source. Gather all the information. Package it all up into a nice manual. Wait a week. Do it again. That's the best way to get a manual. This is a project that's in constant development, and it's hard to pin down documentation for something like that. For example, have you read the KSP manual? Edit: Mr. Laity: Thank you for all the hard work you've put in on this. It truly is an amazing bit of work.

How far through the program does it get?

This is true, but if the probe is too far away to get a signal, it's too far away to get a signal. Which is why I'd like to see RemoteTech play with this. Setting up networks with combinations of dishes and antennas to get a signal where you need it.

If you have an antenna and are in range, you should be able to switch to and copy from/to the archive. If you are out of range for your antenna, or have no antenna, you should not be able to switch to or copy from/to the archive. However, he's only blocked the switch, not the copy.

It never even occurred to me to even try that. If it's so far out that you can't switch to archive, you should be too far away to copy from it.

I'd love to see the two work perfectly together. It could be interesting, if you fail to debug: >LIST SATELLITES. [i]CommSat1[/i] [i]CommSat2[/i] [i]CommSat3[/i] [i]CommSat4[/i] >UPLOAD [i]newprogram[/i] TO [i]satellite[/i] [i]satellite2[/i] [i]satellite3[/i] [i]satellite4[/i]. >REMOTE RUN [i]newprogram[/i]. >LIST SATELLITES. Error: No Commsats found.

I've never had a problem switching to archive and copying to 1.

But one of the notes in one of the capsules specifically mentions having eaten all the snacks. Therefore, we do know that they eat.

I pretty much only have "SAS OFF." lines in my programs. Pretty much any time there's a maneuver to be made, I turn it off, just to make sure. That's why I wrote a little program just to check if SAS could be used as a boolean condition. I've never had a problem with not unlocking steering. I do turn SAS on at the end of most programs, but I don't think I've ever used "unlock steering" or "unlock throttle". It appears to me that control is released when the program ends.

Try "Plugins/PluginData/Archive"

until 0 { if RCS { print "RCS on." }. if SAS { print "SAS on." }. wait 1. clearscreen. }. This works, so yes.

Just to be sure, do you have the terminal window in focus when testing this?

Yes it would. Try around post #662. http://forum.kerbalspaceprogram.com/showthread.php/47399-kOS-Scriptable-Autopilot-System-0-5?p=645614&viewfull=1#post645614

Just add MODULE { name = kOSProcessor } to any part you want. I've added it to all the capsules and probe cores.

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.