• Content count

  • Joined

  • Last visited

Community Reputation

943 Excellent


About stibbons

  • Rank
    Extreme IFR

Recent Profile Visitors

7,960 profile views
  1. ksp update

    No. If you bought the game through Steam, then you can only update it through Steam. But you can learn how to use Steam! The properties pane for each game has an Updates tab with options to control automatic updates. It looks like this: You can disable automatic updates for all of your games and manually update KSP. Or you could set KSP to be High Priority so it gets downloaded first, and disconnect afterwards. Or you could even disable background downloads for everything except KSP and launch some other game - Steam will go ahead and download the KSP update in the background.
  2. Flight Sticks for KSP

    Couple things worth checking with controllers in KSP: Previous versions of KSP have had issues with the settings getting messed up if you start the game without a controller present. In that case, it's worth wiping all of your settings by removing settings.cfg from the root KSP folder, then starting the game with the controller plugged in. Controllers don't seem to work at all in KSP 1.4.0 and 1.4.1 on Linux. There appears to be some workarounds, but the best bet is probably to wait for a new release. See this thread for details.
  3. Happy Pi day

    Ten. The fact that I used a 10-digit calculator in high school is related.
  4. Why April?

    The original announcement from SQUAD after the absurd hissy fit that resulted in free DLC is at . Note this bit: So, end of April 2013 was chosen as the cutoff because that's when they announced it. Nothing more, nothing less.
  5. You can tell this is true by the fact that this post was removed.
  6. Great to hear that's working properly. Keen to see how you get on with the full setup. Soon.
  7. To be honest, I for one wouldn't mind seeing an active maintainer just... start a new OP.
  8. Mea culpa. I didn't properly test the throttle handling after adding it, so of course it was hideously broken. I've fixed the handler so that the plugin is at least able to receive and process throttle packets. But working my test rig (a 10k potentiometer hooked up to an arduino ) I was still getting erroneous values. Unfortunately I'm going to have to bust out the logic analyser to get to the bottom of that. But in the interest of releasing early and releasing often, version 1.2.5 is now out. Throttle packets are now received and handled. Probably incorrectly. With "verbose" set to true in the config file, the plugin will log the contents of every throttle packet received. Work is still progressing on the throttle, after that I'd like to make the handlers and their logging a little bit more robust. Don't expect to be adding very many user-visible features on the plugin end for the next little while, sorry. And adding insult to injury, it looks like the Arduino Library Manager updater hasn't been crawling new releases of the Simpit Arduino library. Right now installing through the Library Manager will get you version 1.0.0, while the most recent is 1.1.3 (and is definitely worth using instead). Still trying to get to the bottom of what's wrong, but the best I can suggest right now is making sure you install the library from
  9. Happy Pi day

    I think what you're looking for is the 3rd of Qawl, or 25th of November.
  10. It's a minor thing, and I'd have to think hard about how a "no really I know what I'm doing when I'm setting version requirements" feature would work. Would much rather continue playing around with Xamarin.Mac.
  11. Thank you for confirming it. I'll take a closer look when I'm home from work this evening. Better logging is already on my todo list for the next (real) release, the fact that people apart from me are starting to use this plugin is pretty good motivation to do some more work on it soon.
  12. That's mildly disappointing. Thanks for looking in to it.
  13. Happy Pi day

    This is where I get mildly grumpy because there's precisely one country in the world that localises dates as <month>.<day>. We get where you're coming from, but it just doesn't work for me. And this is why the 22nd of July is the one true Pi Day.
  14. I set `ksp_version_strict` to true in my netkan. Does setting compatible version in the CKAN client override that flag, or does it just influence what the client considers as "generally recognised" compatible (ie, only influence behaviour when ksp_version_strict is false)?