• Content count

  • Joined

  • Last visited

Community Reputation

1,385 Excellent

About steve_v

  • Rank
    Grumpy Sparky

Contact Methods

  • Skype Skype? Is that some kind of delicious biscuit?
  • Twitter I am not a twit.

Profile Information

  • Location Chasing magic smoke

Recent Profile Visitors

3,590 profile views
  1. Thinking of switching to Linux.

    Apparently, dual booting with secure boot enabled is possible. In an odious "your linux distro needs to have their kernel image (or a shim) signed with a Microshaft key" kind of way. This obnoxious behaviour is (and was) enough to make me simply format my windows drive and use it for something more useful... like cat pictures. If you are okay with Microsoft unilaterally dictating what you can and cannot boot on your PC, by all means use secure restricted boot and Windows 10. I wouldn't touch the thing with a 40' pole.
  2. How does three-phase electricity works?

    Try dropping a spanner across the battery posts... Actually, don't try that. Huh, wish it were so over here. The extra line charges murder the efficiency savings at household loads, so only commercial / industrial premises tend to have 3-phase.
  3. Patch 1.4.3 to be released next week!

    Sorry I missed this, and thanks for the workaround. Multiplying the crash tolerance my 10 isn't really a "fix" though, it simply sacrifices a gameplay element (landing legs can be broken on hard landings) to conceal a bug. Balderdash. Defending a buggy release because it's only buggy on one of the 3 supported operating systems is defending a total lack of QA on that supported system. If a bug were occurring only on Arch Linux, with a particular graphics card and driver version, I'd be more than willing to forgive not catching it before release. If it affected the majority of Linux systems, hell no. In the case of the "joysticks don't work on Linux" issue (which is specifically not mentioned for 1.4.3), it's a problem with the game engine that has been known about for nearly a year, and yet Squad went ahead with a release without even attempting to address it. I don't know how anyone can describe this as anything but flat-out "not giving a crap about GNU/Linux users". I, for one, am properly tired of this. @SQUAD: There's going to be a 1.4.4 to address the lack of proper joystick support on GNU/Linux, right? I'd like to buy your DLC, but I won't if I can't use my joystick with it.
  4. Patch 1.4.3 to be released next week!

  5. Thread to complain bout stuff

    Apple lost the plot right after this one. Then they lost the PowerPC CPU that was the only thing keeping them from being just overpriced Wintels in a shiny case. As of 2018, there's no reason at all to buy a mac - if you are one of those odd people who like MacOS 10, just build a hackintosh for half the price instead.
  6. How does three-phase electricity works?

    Likewise. Over here, we inherited the MEN system from the poms. Frankly, I find the US electrical system to be a bit... dodgy. But that's just me. I have heard this before, but not from a sufficiently credible source as to put any faith in it. 50Hz mains, 60Hz mains, both will kill you stone dead if you fail to respect them. The zero-crossing is kinda important (and the reason straight DC electric fences are illegal in most countries), as it gives you a window to regain control of your muscles and let go of the live thing. Personally, I find DC to be considerably scarier than AC of the same voltage and current capacity - not only does the zero-crossing make it somewhat less directly lethal, it also aids in extinguishing the arc in the case of a flashover. Less severe burns are generally a good thing. True, but unless you work in the industry (or fall prey to a real cowboy in such) you're pretty unlikely to find yourself as a conductor between two phases. The vast majority of shocks are to ground.
  7. Patch 1.4.3 to be released next week!

    Ooh, me me me! I've seen these things more often than I like, in both software and hardware systems. Races that the additional cpu cycles consumed by logging processes break, noise voltages that vanish into the input impedance of your instruments, equipment that works flawlessly as soon as you remove the covers to get at test points... These things are not rare, and not the exclusive domain of PC-coders. As much as I would love to continue this argument, digressing into SCADA systems running on commodity hardware, operators installing spotify on CNC control machines, IT minions swapping out hardware under automation networks without warning... I think it's time to get back to the topic at hand, and to point out the large grey pachyderm in the room: The bug that is attracting all the heat here is not some hard to reproduce end-user-configuration-dependent transient anomaly. It's quite the opposite - as far as I can glean from the forums, the majority of users here are experiencing it. The same may be said for my other favourite 1.4.x bug as well.
  8. Patch 1.4.3 to be released next week!

    No need, I wasn't offended. I on the other hand, probably offend people all the time. Sometimes I even do it unintentionally. There's a lot to be said for a good argument, and this one's a cracker.
  9. Make these two female Kerbals stock

    And all the other heroic pilots through the ages as well, regardless of their gender? It'd only be fair... Agreed. Furthermore, I fail to see the point of naming any kerbals after famous historical humans at all. Indeed. There are well-rehearsed checklists for both single-engine landings and cabin decompression. Landing on a river, with no power at all, from ~3000ft... not so much.
  10. How does three-phase electricity works?

    That video is pretty good. Why 3 phase? Efficiency, and things that spin. The things in the kitchen that run on 3 phase power will almost certainly be doing so because they have motors in them, and you can't make a nice quiet efficient induction motor without at least 2 phases (or inefficient tricks with capacitors to split phases). Three-phase systems aren't inherently more dangerous, they just tend to be found where more power (and therefore higher fault currents) are available. You don't take chances with any electrical system, and the more energy available, the bigger the boom when the smoke escapes. Even the lowly 12v car battery can vaporise steel.
  11. Patch 1.4.3 to be released next week!

    Nobody I am aware of asked for them to be rolled into (and hold up) a critical bugfix patch.
  12. Patch 1.4.3 to be released next week!

    Haven't got my flight stick set up, because Unitys joystick support on GNU/Linux is still completely FUBAR. Apparently I am going to have to wait for some future (or never, as it's sounding like) patch after this one before basic usb-hid input functionality is restored. What will make me happy is the ability to play the game (preferably with the DLC), with landing legs that don't explode and a joystick that works. Like in 1.3.1.
  13. Patch 1.4.3 to be released next week!

    As do I, if I assume that that is what they are doing... As opposed to tweaking the new and unasked for content while the base game remains borderline unplayable.
  14. Patch 1.4.3 to be released next week!

    If KSP was a DOS program circa 1988, you wouldn't have all those handy OS facilities and abstraction toolkits to do half the work for you. Win some, loose some. Again, "It's complicated" isn't an excuse for releasing code with major regressions. It might, to some extent, explain how they happened in the first place, but that's beside the point. Ed. FWIW, neither is your average CNC system. The last one I worked on had 4 cpus and 3 monstrous FPGAs scattered around in various locations, each running their own code, in different languages, and communicating with at least 3 different protocols, not counting the various microcontrollers. And that one was built in 1988. They're even worse now, as they tend to run on Windows PCs with a stack of large and obscure proprietary co-processing PCI cards. Despite all this complexity, (and running the frontend control software on Windows, of all things) somehow the manufacturers manage to find time to test them sufficiently that they neither produce defective parts, nor kill their operators while swinging 10+ ton components around at 1500RPM.
  15. Patch 1.4.3 to be released next week!

    As someone who has spent some time digging around in the low-level code of (usually decrepit) CNC machines, I can assure you that it is. A CNC is a computer. It has an operating system, it runs user code. It usually has bugs. It has difficult to predict hardware issues to make finding the bugs more fun. That is ridiculous. Computers, and the code they run, are logical and deterministic systems. There is no voodoo, no astrology, and unless you try quite hard to create it, no true randomness. Sure, the code in a game like KSP is complex and there are many places bugs can creep in, but it's not magic, it's not alive, and it certainly doesn't react to the phase of the moon. One does need to test on a variety of hardware configurations, that's simply the nature of supporting the "PC compatible" architecture. It's annoying, but that's how it is. "It's complicated" does not excuse buggy code. It might make people more understanding of delays finding the bugs, but they're still bugs, and they still need to be fixed.