KevinLaity

This is one of the things I considered, basically serving your terminal over telnet or maybe even doing an HTML page with an editor that works over websockets.

Let me know if this helps: Imagine laying on your back facing the sky. But you realize that, oops, your head is pointing southward so you spin yourself around 180 degrees. Since you're facing up, that's akin to an aircraft rolling 180 degrees. Now yaw yourself 70 degrees east. That method is relative. We may need an alternate option for having a more aircraft like system where you're navigating by heading relative to north and by pitch relative to angle of the surface. EDIT: Come to think of it, if I were to put in an expression for NORTH, I think you could express the same direction as something like NORTH + R(20,90,0). Although not sure offhand if the pitch or yaw would be applied first.

The bus part: I'd rather not if I can avoid it. At one point I tried automatically forcing new partmodules onto all the ship's parts at launch time and assigning them id's. It worked great except they wouldn't be reloaded with the ship. No, you can't program in the VAB. I had thought about that and having people save their programs along with their vessel prototypes. I couldn't find a way. Vessel prototypes basically just keep track of the fact that a part is there, and can't save any configuration of that part. I prefer not to overwrite behavior of someone else's part, including stock parts. However, we may see a kOS unit that also acts as a probe part.

When a program ends, any temporal commands you've issued within the scope of that program are discarded, including ON. I recommend putting a WAIT statement at the end of your program, and give it a criteria that matches when you want the program to end.

Yes. The screen will go blank if it runs out of power. If power is then restored it will reboot.

There isn't a way yet to access subelements of R(). It will probably be something like PROGRADE:ROLL, RETROGRADE:YAW etc.

Awesome thank you! I didn't even notice that setting before. I realize now that it's a mip-mapping issue. A fix for this will be in the 0.4 release.

Yes, no ETA on that. No, but there will be commenting. Probably the same style you see there. I can't think of a good reason not to use double slashes. Yes, and so does ON. But I'm pretty sure ON should be re-triggerable and possibly WHEN.. THEN too. Thoughts? Let me get back to you on that.

I feel awful reading this, because I can see how hard you've worked on it. 0.4 is actually going to have archive files stored in plaintext in a folder. I tested it last night and it does maintain synchronicity with the filesystem at all times. The arc format will be discontinued. I can only hope that your project can easily be changed into something that is helpful with editing files offline in the new system which should be released in the coming days.

Yes, I had envisioned different parts with different hard drive sizes, speed of CPU, tonnage, and cost. Even expansion parts that offer a volume and no CPU. However I don't know yet if anybody needs or wants that.

I've tried replicating this problem and can't so far. The lowest resolution I can go down do is 1024x768, and the fonts appear fine. If anybody can offer help replicating this bug, it would be appreciated!

This is correct. UP means "directly away from your current body of influence."

Actually, you should be able to quicksave and save the contents of your onboard volume. Although I have heard that this may not be working 100%. More volumes: you can actually add more kOS units to your craft. Each terminal can see all the attached volumes. This is for transferring programs when craft are docked.

Unless you're compiling from source, you don't have the ability to use variables inside R() expressions yet. This will be fixed in 0.35

Sure, I'll update the readme at some point. The 180 is never strictly necessary, but if you don't have it your craft will flip around to match the 0 degree roll you're asking for (unless you flipped it yourself in the VAB first). The 180 is just to make the takeoff look less ugly. I've tried to find ways of making it ignore roll, but that's significantly harder than it sounds.

While I will be checking this thread, the main source of news is here.

Logging is a maybe, I can see the usefulness. I'd love to interact directly with parts, including statuses, fuel levels, and even issuing commands.. (automated fuel transfer! individual engine throttles!) Unfortunately, the road block I've hit with that is that while KSP does give a unique ID to every part, that ID gets thrown away when the ship unloads, and a new random one assigned later. Which means if you write a program for your ship that addresses an individual part, that program becomes useless later. I have some ideas on overcoming this, but not sure when I'll get to it.

Actually you have the option of assigning 1 to SAS like this SET SAS to 1. In fact, I think you can say "SET SAS to True." but I can't remember right now if I actually tested that. SAS ON is just a shortcut. The small font texture is intentional, I'm going for a pixellated look. And people are already having trouble in lower resolutions with the size that the textures are, I actually need to cut them into quarters to fix their issues.

I'm going to give you the benefit of the doubt and assume you missed the first part of my sentence where I mentioned the configurability I need.

Unfortunately, Unity's built-in text controls don't give me the configurability that I need, or the look that I want. I will be looking into this issue soon. I believe I can improve the situation by cutting the textures into smaller pieces.

I'd like to weigh in this one. While I'd be flattered to have the devs include it in the game (and they have my full support if that's what they want!) I do not expect them to do that, and I don't know that it really makes sense as anything other than a mod. I think if the devs were to include it, it would be a huge liability in a lot of ways. They would have to offer support for it, and while nobody's forcing you to use it, scripting would then become 20% of what it means to play KSP. It's probably a huge divergence from their current plans for the game. If the devs (and other users) have fun playing with it on their off hours, my mission is complete. (And if Scott Manley reviews it.)

It's not a top-priority item, but this will probably exist in some form at some point.

Anytime that I have not put anything in the What's new section it's because there are bugfixes only.

Sorry to everybody using resource tags, this feature was not ready to go and I mistakenly released the documentation with it in there.

I suspect this is why periods have never been used as terminators in other languages. But it works fine. The rule is that whenever a period has a numeral directly after it, it is considered a decimal point. Any time it has any other character (or no character) after it, it is considered to be a statement terminator.