razark

Have you taken into account the environment it's meant to be used in? Insulation, cooling, heating, hardened electronics, redundancy, over-engineering for safety, etc?

Current #1 reason that KSP is not like NASA: I'm still able to play KSP...

It affects a lot more than national parks. Government agencies are running with only "essential personnel", with everyone else sent home. No business is to be conducted, except for work that ensures safety and health of people. http://www.cnn.com/interactive/2013/09/politics/government-shutdown-impact/index.html?hpt=hp_t1 It's like two spoiled children, fighting over a toy. Each one realizes that he can't have it to himself, so to keep anyone else from playing with the toy, they burn the place to the ground.

I'm going to work in a bit so they can tell me to go home. The last email we had yesterday said that our company might allow us to use our vacation time to cover hours.

What got me interested in spaceflight? Nothing did. I have no abnormal interest in space. I grew up a stone's throw from Johnson Space Center. My mother worked for a contractor. My father was a civil servant. He started on Apollo-Soyuz, and moved on to Shuttle. I had to learn the Orbiter Vehicle numbers, because he didn't know them by name. There were always friends and coworkers around talking shop. Our entire neighborhood was NASA people, except for the college professors that lived across the street. Shannon Lucid lived one street over, so I went trick-or-treating at an astronaut's house. Our house was full of pictures and artifacts. I remember the piece of Columbia's tile encased in plastic; there was also a large chunk of title sitting on the shelf. During a mission, the TV was tuned to the NASA channel. I was nine when we lost Challenger. Onizuka was a friend of my father, and his daughter was on my sister's soccer team. T-38s were a constant sight in the sky, and a constant sound. I remember that we'd have a fire drill every time one of the shuttles was being transported through so we could all go out and see it. It made sense; nearly all the kids a school were NASA kids. And now, after going away to college and moving back, I am working for a contractor at JSC. So, yeah. Spaceflight isn't something one has an interest in. It's just what people do. It's as natural as breathing.

0.15, I think. They're on the surface, and they're still alive:

Nope. Look again. The set.. to commands are in the log file you are modifying, so you are never trying to print a quote, you simply append a command that tells it to print a concatenated group of variables. The variables just happen to each contain a string of length 1, so you are building your string without ever using a quote. Yeah, just tested it. testmod.txt contains: log "print h + e + l + l + o." to log. log.txt contains: set h to "h". set e to "e". set l to "l". set o to "o". >run testmod. <Program ended. log.txt contains: set h to "h". set e to "e". set l to "l". set o to "o". print h + e + l + l + o. >run log. <hello <Program ended. As I said, it's a pain, but it is doable.

If it's labeled stock, it should be stock. Not knowing what you're talking about, though, is it possible someone forgot that they had a mod part on it? Honestly, no offense meant because I realize that we all play this game differently. I just cannot fathom why you would build something that you don't intend to fly.

It's a pain, but: In the modifying program: log "print h + e + l + l + o." to modified. In the modified program: set h to "h". set e to "e". set l to "l". set o to "o".

I stick a couple Sepratrons on my lander. Bind an action group to decouple the port and activate those engines, point the stack in the right direction, and be done with it.

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.