stibbons

So I've just published a new version of the plugin with (yet another) complete overhaul of how the plugin interfaces with a serial port. It's more robust and less laggy than the previous cross platform attempt. But it could use some more folks testing it out. I've tested this on my MacBook Air, and Linux gaming rig. It also doesn't (yet) work on Windows 10. But I think I know what I can do about that. Get it from http://spacedock.info/mod/850/KSP Serial IO (cross platform) , and let me know how it goes.

Maneuver nodes have only ever described an instantaneous change in velocity. I don't think it would be appropriate for the game to try to guess at how accurately or how much thrust you're going to put in to a burn to try to "correct" the node.

On the hardware side, I've been struggling all week to cut the parts I need for my enclosure. Have learned an awful lot about CNC milling in the process, and haven't slept nearly enough. Go figure. On the software side, I've been reading up on how C# does serial port access, and attempting to streamline the currently fairly kludgy way the cross-platform KSPSerialIO fork polls for new data. I've written a new asynchronous serial receiver for the plugin, that handles the serial receive side of things in a background thread instead of polling for new data every frame. It looks like I'll be able to get that working on OS X and in Linux. But my testing in Windows 10 is currently looking super weird, so my goal of having a single serial method across all platforms is still not quite there. Hoping to push out a new version of the KSPSerialIO cross-platform plugin by the end of the weekend.

Nice work! Sounds awesome, you should definitely post more pics. For the annunciator, one or more lights indicating whether it's safe to open parachutes is awesome. The game seems to base the status description on the Mach number, and some experimentation in the KSPSerialIO thread figured out that: VData.MachNumber > 0.85 corresponds to "unsafe" 0.85 > VData.MachNumber > 0.8 correspondes to "risky" VData.MachNumber < 0.8 corresponds to "safe"

HTTPS everywhere solves a different kind of problem. For sites that have HTTPS available it tries to make sure your browser prefers encryption by rewriting links. It doesn't do anything for sites that don't use HTTPS in the first place.

That's... the opposite of how geoblocking usually works. I may have just busted up the link. You can try searching for the book title in Google Books and then browsing to the Appendixes. But yeah, the Kindle version is surprisingly cheap for what amounts to a reference book with a bit of narrative.

It's an AGC specific instruction set. Composed in-house, and almost certainly heavily influenced by the fact that an AGC instruction word used only 3 bits for the opcode (although the Block 1 architecture did some weird tricks to run with 11 instructions instead of 8). The full instruction set, interrupts, registers and IO channels is listed online. But I really like that whole book, The Apollo Guidance Computer: Architecture and Operation by Frank O'Brien, for an accessible and thorough walk through of the hardware and software of the AGC. It's a great way to add context to the source code.

I love the mythological origin of the word "quiz". http://www.worldwidewords.org/qa/qa-qui1.htm

It won't work, and hasn't been updated for KSP 1.1 yet, so it's a few versions behind. I've been maintaining my fork and building releases for a little while, but also haven't updated for a few months. Expecting to get around to that pretty soon though!

Top to bottom, there's a sheet of 12mm MDF that I was trying to cut my part from. Under that is a 3mm sheet of scrap material. The big 18mm sheet below that is the CNC's spoilboard.

Inspiration struck this week and I started planning a new enclosure for this build. Now that I know all of the hardware that's in it, I can build something that's a lot more compact and I'm planning on taking the time to do a better job of it. Spent some time this week sketching up ideas and figuring out a new layout for the instruments I have. Today, with required dimensions sorted out, I was able to draw up designs and attempt to start cutting them. I'm planning on a split sloped and angled design. The left and right sides cut from the same MDF I used for the first enclosure, like this: The left and right are slightly larger, and the blue lines will be cut as grooves for the other faces to slot in to. The front and top faces will almost certainly be aluminium composite (Dibond). I was impressed with the finish Mulbin was getting on his panels, and am pretty sure it's rigid enough for large panels without sagging. The back and bottom will be MDF, but much thinner than the sides. The 12mm stuff I used for the last enclosure was massive overkill. The rest of the day was spent learning how to use the CNC at my maker space. These things are a lot more complicated than a laser cutter, but really really fun. It... did not go especially well. A couple of failed attempts, one very nearly broken spindle motor, some creative swearing. I learned a lot though! Hoping to get the side panels cut properly in the next few days.

I don't live in Sunnyvale, but I have family out on the Yorke. I kind of like it out there, but the area seems to be doing it pretty tough.

Hey, thanks for your contribution. I'm not sure how it applies to this discussion though. Would you care to elaborate a little?

Yeah, right again. I bring reason in to a discussion about how porting KSP to consoles will destroy everything, and I'm the one who's mad. You're on a roll.

You're right. We don't know. So it's unfair to have an opinion one way or the other. How does that tie in to "the way I am now about this"?

Which part of it was positive? And, for bonus points, which part of it was not an hilariously leading question?

Console critics don't make console games either. They play them. But I'm sure you were going somewhere relevant here.

No, you're right. You're not. Which part of this was positive?

So many people who don't play on consoles having an opinion about consoles.

I think that it's great that you're trying to build a community by preemptively trashing large portions of it. Great work, you.

It helps with startup time. I wouldn't expect it to make much difference at runtime, as assets aren't dynamically loaded. But running some tests yourself isn't too hard.

*wave* I'm from Sydney, which is pretty OK as long as you don't mind bottlos closing at 10.

My first year comp eng course ran right the way through. Started at boolean logic, and progressed to designing and building a simple 8 bit computer in a logic simulator. That was the mid-90s and my recollection of it is hazy at best, but I'm pretty sure I still have the textbook kicking around at home. Buy a book. Something like https://www.amazon.com/Elements-Computing-Systems-Building-Principles/dp/0262640686/ looks like it would be a good primer. Alternatively, my five minute skim of http://www.instructables.com/id/How-to-Build-an-8-Bit-Computer/ says that it seems to be an alright overview of basic overall design.

RemoteTech calls this a command station, and makes setting them up pretty hard. I eventually found the requirements in the probe core section of the user guide. Apparently you need an RC-L01 remote guidance unit, and six(!) kerbals on the craft for it to act as a command station. So it's possible, but definitely not with your current setup.

On a command line, `ckan list` will output installed mods with their version numbers.