steve_v

It has:

I suspect there's more crossover between electronics nerds and programming nerds. How much free stuff is available for GNU/Linux is directly proportional to how many GNU/Linux users want to help write it.

Free beer is not free speech. I prefer the latter where available.

Indeed. However there are reasons: Primarily CAD until FreeCAD is properly usable. If you have specialised needs you have specialised needs... And those applications you mention are very specialised. Most home users don't need to simulate lateral loads on structural piles.

If you're getting a copy of windows, it's got to come on something. Either that's a DVD (and you don't have an optical drive, right?) or a USB drive you could wipe and use to install any OS you please. LibreOffice does spreadsheet just fine. So does Calligra Sheets, so does Gnumeric.There are may others. My preference is the first, for it's superior format compatibility. I don't actually use spreadsheets much, if I'm working with large numeric data sets I'll use a specialised application such as QTIPlot. Sure. I run QCAD for 2D stuff & BricsCAD when I need bigger guns. Eagle PCB gets a bunch of use too, though I'm trying to transition to KiCAD for the electronics stuff, since autodesk bought eagle and I refuse to pay a subscription fee for something I bought outright. There are also Draftsight, VariCAD & FreeCAD. The latter is totally free and coming along nicely, but it's still a little unstable. Should be a worthy (and totally free) contender soon.

I will admit, that level of idiocy usually doesn't even occur to me. You can of course break anything if you try hard enough. That said, I wouldn't actually rate web-browser-as-root that high a risk, in the grand scheme of things. Modern browsers sandbox web content... at least ones worth using do. Still a pretty dumb thing to do though. IME, the quickest way to get owned on a *nix box is running a poorly secured ssh, web/SQL or remote access server... And the number one way to end up there is following random blogs rather than reading the manuals. 'nuff said. User-installed rootkits can generally be avoided simply by using the distro repositories. Maintainers matter, something that commercial app-stores have yet to understand.

Seriously? An 8GB USB drive is going to cost you $5. If that's your excuse, I don't know what to say. The drivers for many popular keyboard controllers are readily available, making X11 keymaps is easy, and the electronics to build such an idiotic thing as an emoji keyboard is mostly drudgery wiring up all the buttons. Frankly, I'm beginning to suspect that your idea of "low-level" is anything without a click-and-drool GUI. I've never had any kind of virus, or a need for antivirus software. Mainly because, for practical purposes, there are no viruses that run on GNU/Linux. I get to update what I want, when I want, how I want. I actually find it somewhat entertaining to examine windows malware and shady email scams, secure in the knowledge that the executables won't run on my system. Of course one should never click the obvious tracking links in spam mails, unless one wants more spam.

Boot a GNU/Linux install disc / USB drive and follow the instructions? Most of the major "easy" distros have a very user-friendly graphical installer these days, and there will be an "install bootloader" step. If you just want GRUB and nothing else, boot a livecd and 'man grub-install'. I have no idea what an emoji keyboard has to do with installing an OS, or why anyone would want one. Whatever that guy is up to, I guarantee one can do the same on GNU/Linux with sufficient motivation. Not sure what you're on about here, TBH. If you mean Windows permission management is screwey, I heartily agree.

Just fine... Unless you want to use a joystick with 1.4.x, as Squad completely borked it with the last unity "upgrade" and don't appear interested in fixing their mess. AFBW still works fine though, and it's way better than stock input handling anyway. I'd hesitate to call it a Linux "Linux specific bug", it's never Linux's fault and it appears to be completely random which idiotic regressions Squad introduces with a new release.

For myself, I'll take fewer commercial applications over inbuilt spyware and not fully owning my system any day. It's a small price to pay for your computing freedom, and if software vendors don't support GNU/Linux, I'll not support them. In 20-ish years of near-exclusive Linux use, I've found no critical windows applications without a cross-platform replacement that satisfies my needs. Hell, I haven't even needed wine for a game in ages, and games are hardly a deal-breaker. Dual booting is still easy, the only thing that has changed is the introduction of secure restricted boot, if you want to dual-boot with Win 10, your distro will need a signed (usually by microsoft ) shim. Considering that it's in exactly the same "users are stupid, only M$ can be trusted" vein as forced updates, it's fairly obvious whose self-serving idea that particular "feature" was. If you don't intend to boot Windows Spyware 10, just disable it in the CMOS setup, you almost certainly don't need it. This kind of thing has been around forever, it used to be called "loadlin". As far as I am aware, it's neither a true dual-boot nor a native-filesystem install, so performance will probably suffer. Installing GNU/Linux properly is not hard, it's never been hard unless you remember booting the kernel from floppy disk... and even then it simply required reading the manual.

Well blow me. If this is the kind of crap micro$oft is pulling on it's users these days, I'm even more glad than usual that I dumped their products. Never would I use an operating system that decides to modify itself, reboot, or do anything else funny without my say-so, or without my explicitly commanding or scheduling the action in the first place. A PC is a tool. Tools do what the user tells them. What's next, Windows rental contract? Monthly payments? Remote bricking clause? "I can't do that, Dave"? Why do you people put up with this anyway?

What Harry said. particularly this bit: The poll is illogical. The question itself is illogical. Buying KSP multiple times is illogical. The KSP launcher will not update the game at all. Updates are free. There are already polls re. where you bought the game, which is the only question yours could possibly pose. We don't really need another. We have already discussed your multiple-purchasing claims, I have no idea what more you think you will achieve with a new thread, let alone a poll.

You edited your post. $274.9 was the original figure, so either you miscalculated or you're making it up. If you actually spent $199.95 buying all the releases from 1.4 to 1.4.4, you would have saved yourself considerable money by reading the terms (or FAQ) when you bought it the first time. Updates are free. I suggest contacting squad via the contact form on the store site and explaining the situation, they may be understanding. For some bizarre reason, the KSP store allows you to buy products multiple times, without warning, even if you are logged in. @SQUAD You might want to fix this, it's kind of a trap. Also, Please do not necropost. This thread is ancient and the topic is long dead.

Uhhh... KSP updates don't cost anything, as far as I am aware. I bought it in 2013 and haven't paid a cent since then. Just go to your account on the KSP store and download the latest package, you'd need to create another account to buy it again, so I have no idea how you managed to do so enough times to rack up $274.9. Then again, the number does seem to be getting mysteriously smaller... 2 x 39.99 doesn't equal 199.95 either. Are you just making up numbers or what?

Looks like it to me, cheers mate.

To be fair, hyperedit is pretty well known for breaking the universe. KSP is a delicate beast at the best of times, and inserting huge numbers into the physics calcs doesn't often end well. Hyperedit probably caused an overflow somewhere in the physics engine, and the error propagated until the universe went poof. Don't poke the NaN Kraken, it's tetchy enough already.

Yes, libgdiplus is compiled with cairo. Cheers for th suggestion though. Think I'll stick with "toolkit sucks" until I see some evidence to the contrary TBH. The most charitable thing I can say for mono+winforms is: It gets something on the screen, most of the time. Sometimes it even looks half-way presentable. Please excuse the formatting, this editor is garbage on mobile.

Of course you don't. The OP asked for a mod to do a certain thing, and I directed him to it. Nothing to do with thrust vectoring or cheating. No, you don't need TCA to build a shuttle. It does make one easier to control however, and has a lot of other uses besides. Why some need to imply that using it is somehow unfair, suggest that the OP (and me, by the sound of it) is doing it wrong, or drop by to show off their designs, is entirely beyond me. Question asked, question answered. While the OP may find this useful, I do happen to know how thrust vectors work. I also know how to build a shuttle, though personally I consider it an excessively complex and expensive way to do what a rocket or SSTO spaceplane can do better. I have no idea why you're trying to explain this to me. Of course it does. But again, you're directing it at the wrong person.

Squad decided to use and to keep using Unity. Squad decides which Unity versions to target, when to ship releases, and which bugs are acceptable for release. Of course they get a share of the blame for the recurring wheel problems. As the old saying goes: A poor workman blames his tools.

I tried this out in 1.4.5, and for some reason the radial tanks (and only the radial tanks) crash the game when picked in the part menu. Nothing at all appears to be logged when this happens. I'd understand if a plugin was involved... Are there any known incompatibilities that would affect part-only mods like this?

So do I . Using 15GB of memory (and requiring me to install as much) is still ridiculous though. Thank Dog for boards with 8 DIMM slots.

That board does support 32GB (4x8). You could add another 2x8GB, or even 2x4GB. The real question is whether or not you can an you find some DDR3 DIMMS at a price that makes it worthwhile. Personally I wouldn't buy new RAM for a board that old, but I see some second-hand ripjaws going for ~20USD per 8GB on my local buy-sell. In your position, I'd buy it. Only on the KSP forums do we see "16GB is not enough"

You do have a point. Though a smaller overall footprint might help to keep the address space within 32bit limitations... Oh no, it's bitten me too. I put up with SystemD and the developers attitude to bugs for a couple of years before my patience expired. I'd probably be more willing to deal with said bugs if I agreed with the architecture. Also, Lennart is a complete jerk.

Everything on my system works fine and respects system fonts and colours regardless of UI toolkit - except for mono applications, which use some horrible defaults. As I have done nothing strange to mono, I can only conclude that it's mono being strange. ¯\_(ツ)_/¯ If you don't want to use a toolkit that doesn't suck, what am I to do, apply all the Debian patches and hope that fixes it? On the other hand, upgrading to mono 5.14 (and no other changes) did fix the crashing file dialog, so you might imagine where the "mono being mono" attitude comes from. Run another distro just for CKAN? You have to be joking.

I absolutely second this. Every major version release seems to change wheel behaviour, and lately this results in unpredictable sliding and fishtailing on landing. Aircraft that I landed easily in 1.3.1 are deathtraps in 1.4.5, with no changes to design or wheel settings. And then there's the self-amplifying bouncing... It'd sure be nice if Squad stopped screwing up wheel physics every major release, it's been going on for years now. I'm not saying that landings should be easy, or that the craft (mine or stock) are perfect. But needing to learn a new set of workarounds for janky wheel physics and rebuild all your craft every release is infuriating. Friction should be dependent on the materials in question and the forces between them, not some setting added as a workaround for the lousy wheel-collider. Nobody had to muck with friction settings in 0.90, why do we need to now? Can't we at least have a workaround that works the same in each new release?