razark

Range safety would step in if the flight was going off course. They didn't wait for it to get close to hitting anything. Even the shuttle had range safety devices, which destroyed the SRBs (and would have destroyed the ET) after Challenger. How about something that you can tie into the abort action group? Have a trigger with a half-second delay, then push the button, get the crew clear, and blow the rest of the stack. That's why KSC (the one in game, and the one in Florida) are built on the east coast. (And hopefully the fuel would have burned out before it reached the surface. There would be a large quantity of oxidizer in the area, so rapid combustion is pretty much ensured, and the rocket would be destroyed before it got very far off course.)

Pencil, paper, and start adding them up. I did this for liquid fuel the first time. So how long until someone posts a video of a Munshot using only this system?

Excellent. I think that there's room for both single-shot and repeatable triggers. I'm not in any hurry. The three day weekend isn't for a few more days. I was just reading through the document, and it struck me that it was the one node info we seemed to be missing.

See post #149. Glad to hear both of these. This whole thing is great. Now for some more requests/clarifications... Can we get the AND, NOT, and OR at least? In the readme file, it shows what looks like comments. Does the system actually treat these as comments? The WHEN.. THEN sets up a one-time trigger, correct? We have access to some maneuver node information. Can we get burn time information as well?

Awesome. Ok, looking at that now. Everything has access to v0, and each part adds a numbered volume. Are you planning to do more sizes of the kOS units, or a radially attached version that could work on any size vehicle?

Thanks for verifying. I figured that's how it worked, so I've been doing mostly that. I saved my programs to v0, then copied them to v1 and made edits for the specific vehicle I'm using. More than two volumes would be useful, though.

Finally having a chance to muck about with this. I like it a lot. Right now, I've got it running on the other monitor, looking out the window of a one-Kerbal capsule, watching the horizon drift by. Does this save programs between flights?

The mod author dropped in a while back and stated that a "." followed by a number would be interpreted as a floating point number. My brief testing tonight shows this to be the case. Edit: Post #65 http://forum.kerbalspaceprogram.com/showthread.php/47399-kOS-Scriptable-Autopilot-System-0-35?p=615644&viewfull=1#post615644

The instrument does the same thing, the same way, every time. If you are surprised by this, then you need to learn to use the instrument. You were the one talking about pointing at a marker and burning without understanding what you were pointing at. When an instrument operates a certain way, and does so consistently, not checking the clearly marked mode indicator before you begin using the instrument is not your best option. Didn't say it did change the "problem". It was in response to your comments of "I can't see ANY circumstances in which someone would use target mode on the navball from the map view..." and "Shouldn't the fact that I'm on the map view be a good enough clue to the game that I'm not trying to dock yet?" and "...but if I stay on the map screen that's a pretty good indication I'm still operating orbitally." If cars were KNOWN to switch, and KNOWN to do it under certain conditions, and you KNOW there is a possibility that you are subject to those conditions, and yet you fail to check the very clearly marked indicator before flooring the gas pedal, it's not an instrument problem. You'd have a point if the mode indicator were located on a different part of the screen, or if it wasn't shown, or if it only showed up in IVA. But it's clearly printed right above the navball, where you really can't help but see it if you bother to look at the numbers. I don't know how you can fail to know what mode you're in unless you are purposely refusing to look at it.

Nothing says you would be forced to use something like this if it were added to the game. They added plane parts to the game, and I've only mucked with planes two or three times. Never used the ion engines, either. Adding something like this to the base game provides options, not requirements.

You're talking about programming here. It's not a question of "if". It's only a matter of time before someone builds a GUI program editor and compiler for it.

So, you can use a value between 0 an 1, as long as you don't use ".". Ouch. Even if it wasn't for the entrenched use of semicolon, the above makes it necessary. Edit: Watching video 3 now, and I'm seeing decimal points used: set tVal to tVal - 0.02. Hrm...

Well, they are Kerbals... Does the RUN command mean that we can call a stored program as a subroutine? And is there any information on how this mod plays along with RemoteTech? I must question your definition of "decimal". Also, in the "Tips & Tricks" video, he demonstrates the throttle being set to "1 - Alttude/15000" or something like that, so it can take a non-integer value.

This looks like it could be fun. But it needs a GOTO. Every language should have a GOTO.

Awesome, thank you.

I would be grateful if someone could make a Kerbalized version of this one:

If that's what you feel qualifies as a base. I wouldn't call it a base, but then I use certain mods and don't use other mods, so some people would say I'm playing the game "wrong". Sounds to me like it could be a mobile base for robotic explorers.

A base is whatever you consider a base. It might not match another's definition, but you're playing your game, not theirs.

I would love to have the black meatball shirt. I'd even have to break with tradition and wear a T-shirt to work one day.

I have a Loner Kerman. He's currently orbiting a single-Kerbal craft around Kerbin at 80+million km.

Call it what it is. If a pilot flies its airplane into the ground because it misread the instruments, it's called "pilot error", not "instrument error". It is your responsibility as the operator to know what your instruments are telling you, not to blindly follow them. If you want the machine to tell you what to do, why not just use an autopilot in the first place? And I for one quite frequently do my close maneuvers (down to 1 km or less) on the orbital map, using the navball in target mode. Edit: If you're driving your car in reverse and look at your speedometer, do you assume the car is moving forward just because the meter isn't reading a negative number?

I place Sepratrons directly on the capsule. Abort mode shuts down all engines, fires any retrograde Sepratrons on the vehicle, decouples the capsule, and fires the abort Sepratrons. If the abort engines are unused when the capsule reenters, I fire them on the way down to help slow down. I tend to use three most of the time, but I've been known to use two on the small capsule, or four on the big one. Or a lot more, to abort with a capsule/crew pod.

No way to tell, except that it says "Target" instead of "Orbit"? And if automatic switching is such an issue, how come no one is complaining that it switches from "Surface" to "Orbit" on the way up and "Orbit" to "Surface" on the way back down? It's simply a matter of learning to use the instruments you have, and if you're looking at the velocity, you're already looking at "Target" or "Orbit".

They're about the only ones that do on a regular basis, but an E6B is kinda limited in what it does. (Not that it's not great at what it does, it's just great at a very limited set of tasks.) Now I'm wondering how useful it could be in KSP.

Depends on how you define "work for". There are also people that work for contractor companies that are not directly involved in agency work. Individual companies' HR departments or IT workers, for example. Some employees even have to track whether they are doing agency or company work at any specific time. Edit: What he said.