thewonderidiot

Done! I just realized that there's a bit of wonky brace-formatting in the Util.parseTo() -- I thought I had all of the format settings right in Visual Studio but it looks like I missed one, and it reformatted stuff on me right before I committed. Got that fixed now. And I just noticed that you added in a GLOBAL_SPEEDACCURACY -- thanks!

Hmm, okay. I'm probably going to make a branch that just uses floats for all of the values, so if you ever change your mind (or have some update in the future that breaks backwards compatibility anyways), it'll be there. Anyways, I've never used C# or built a plugin for KSP before, so I started off with something fairly simple -- I added support for hex and binary literals pretty much everywhere a user can use a number in their program (all using a generic function as a wrapper around the various Convert.ToXXX methods). I tend to think in hex a lot, so being able to load immediate hex numbers is nice. I pushed the changeset out to my fork, and, depending on how you like to do your project management workflow, can issue a pull request for it if you would like.

Whoops, double post. Ignore.

Ah, that makes sense! © kind of sucks though. Sounds good. I really like the idea of having one fuel sensor per tank idea, but it would probably fill up your serial interfaces really quickly -- maybe there could be a dedicated fuel sensor controller that would interface over serial to ProgCom, which collects and passes along information from all fuel sensors on the vehicle. That way you would only need to take up a single serial line (just thinking out loud here... ) Yep, that would be perfect! You could just check for some type of valid boot record at the beginning of the nonvolatile memory and use it if it's there

Hey there, I just found this mod yesterday and have to say, it's amazing! Exactly what I've been hoping for in a mod. I've got a few questions (these may have already been answered before the Great Forum Crash of 2013, so forgive me if I'm making you repeat yourself): 1) Why do the speed/velocity measurements have a separate, hardcoded scale factor? Is there any reason why we can't adjust it like we can the position/attitude factor? 2) I agree that a fuel level sensor would be very nice to have -- is this the sort of thing you think would be done with the serial interface, or would it be better memory-mapped along with the attitude/altitude/velocity information? As a followup, if you think it would be better with serial, what's the dividing line between memory-mapped values and external serial-interfaced values? 3) Can we get the ability to specify a startup program? It would be pretty great to have the computer load a default program without having to type "load run xxxx" every time. 4) And finally, are you accepting pull requests on github? I wouldn't mind taking a whack at some of this stuff.