steve_v

Who's this "administrator" guy anyway? Sounds like he has a lot to answer for. A patch should only mess with files belonging to the game in question... and there's certainly a distinction between game files and OS files, at least on any system I've ever used. Really? I've sure never needed to run any of GOGs patches as root, nor let them muck with anything outside the game directory... I'd certainly not be running a patch that buggered about with the OS. Work the game:patch ratio dude, it's not rocket science.

Indeed, this is most irritating. I have, and I'm more irritated that I cannot participate there. Key word: Finally. My point is that this should have been fixed quite some time ago, if it had been we wouldn't be having this discussion, nobody would be left out, and I would not be irritated at all. Just as the savegame checker/updater was only implemented after a rush patch full re-download was needed to fix save breakage, the patcher will be fixed after it's brokenness has already forced the opt-in to be steam only. Do these people do any forward-planning at all?

If you say so, not 5MB, but bear in mind this is a 6.8GB game: Patch 3.00 2.03 (gog-13) -> 3.00 (gog-14) 593 MB <-- major release Patch 3.01 3.00 (gog-14) -> 3.01 (gog-15) 16 MB <-- bugfixes Patch 3.02 3.01 (gog-15) -> 3.02 (gog-16) 35 MB <-- bugfixes And that's a Unity game too. If you're still not convinced, I could xdelta KSP... say 1.0 to 1.05? I'll put money on it being significantly smaller than the 5x ~600MB it would take to DL each version complete.

Ouch. Gotta love that arbitrary segregation of your customers, makes people real happy and all.

How about the same service steam users get, or a transfer to steam? that would be, oh, I don't know, fair and equal treatment of all paying customers. If your game patch does any of the above, especially "mess around with files on your OS", get out of software development right now, you're a hazard to all and sundry. None of the issues you mention need affect KSP, provided someone with more than 3 brain cells sets it up. Do you have to re-install your OS for every minor patch? No? You do realise this is a far more complex task than updating a single application, right? I can't actually recall ever having had an update bork my system, at least not unexpectedly. Then again I don't run windows, I hear that kind of thing happens over there. The size of a patch is the size of the changes - that's the point. Do you really think each build is going to change half the game data so radically that you can't get a useful delta? Squad must have a great many code monkeys to be generating that, either that or they're planning on replacing all the assets every time they fix a bug. The last patch I downloaded was ~200MB... for a ~6GB game. Totally not worth patching OFC, I've got 5.8GB of DL traffic and a few hours to burn. ---- Whatever deals Squad made with Steam are their problem. The fact is, I paid for the game just the same as someone who bought it on steam... yet I get inferior service and exclusion from testing. Same product? apparently not... and this is not disclosed before purchase. --- Ooh look, a patch for PoE on GOG... game size: 6.8GB, patch size: 593MB. Smooth install, system and game unharmed. I rest my case.

No. Outside it is cold and dark. Also, are you implying you are not a real person?

A working updater would allow every player to check the new version, if they want to. Yup, I also remember having to re-download the whole damn game for each one, in one case without even the basic courtesy of a version bump or any obvious way to identify which build I'm downloading. Of course, if you're properly lazy, you could just let steam handle all that updating malarky and everybody who doesnt't use it can go fish, whether they bought the game or not. Seriously, every other game I have played in the last ~10 years has had post-release patches of some kind, and none required me to re-download the entire game every time. I see the KSP site has a huge "Purchase KSP" banner directing you to the store... What it doesn't have, is any warning that by doing so you forgo the functional update system and access to pre-releases that you get if you buy on steam. You also get no way to correct that "mistake" after the fact. The pre-release is good, for the reasons mentioned. The pre-release only on steam is a plain old slap in the face, squarely aimed at those who tried to support squad by buying directly from them. On top of the no-patcher electron wastage and slow downloads we already have to put up with for every update. @SQUAD: Steam key please, or a patcher that works.

Avoiding this is what patches are for. Aside from the initial download, no different from a normal release, the changes will be small and patches equally so. This is not a particularly difficult thing to set up, and the computational load is minimal as the diff needs generating only once for each build. Xdelta is free, as is rsync. ^ this. Fix the updater and the "we don't have the bandwidth" excuse vanishes in a cloud of sanity. Why anyone would distribute a "still in development" game without a working patching/updating system is beyond me, is squad trying to waste bandwidth?

True, that. I stand corrected.

Well, they did - but only to those who bought it prior to release on steam. I'm SOL because I bought a copy ~1 month too late... with no warning that I would be shafted later on for this apparent blunder.

Now there isn't, this particular horse has already bolted. But please, stop leaving the stable door open. SQUAD set themselves up for this, and get no sympathy from me. Sharpen those pitchforks folks. Or give store purchasers a steam key. Anyone have a valid technical reason for this "Only if purchased before x/y/z date" BS?

Off the top of my head, not leave important features such as a patching system (or a save updater for that matter) broken or missing for so long that you have to upset a significant number of customers, because those features are not there when you actually need them.

Well, give me a steam key then. Admit your store is excrementse, and move everyone over to steam if it's so much better. As it stands, I'd have to buy the game again to get what steam customers get for free... steam users even get decent speeds & updates to boot. I wouldn't actually mind buying the game again mind you, but look - I'd have to pay twice as much as well - I effectively have to triple my original purchase to get decent customer service. All because ("distributing multiple ~1GB builds" being the stated hurdle) nobody can be arsed fixing the updater, which has been acknowledged as completely broken for something like a year now. And here I was thinking exactly this: --- Indeed, but do you really think being left without an updater for a year and being shut out of the pre-release makes me want to give SQUAD more money? I put in testing time for free on several projects, if I also had to pay double the going rate for the privilege I simply wouldn't bother.

Thing is, I've been waiting for 1.1 for quite some time already, a couple of weeks more isn't that big a deal. What annoys me is that I'm getting second-rate service for buying the game direct from SQUAD. 1. Broken updater, causing wasted bandwidth on both ends. Appears no motivation to fix. 2. Secret patch, compounded by 1, = more wasted time and bandwidth. 3. Generally slow downloads, this is actually okay by me - except when exacerbated by 1 & 2. 4. Excluded from "opt-in" pre-release testing, ostensibly because CBF fixing 1. ---- Ooh look, a Linux native code crash, and me with debugging experience and several Linux boxen to test on... Shame that.

Thanks SQUAD, for rewarding my faith in your little store. Remind me not to buy games from indie stores again, clearly doing so makes me a second-rate customer. I have a day job too, but testing and debugging new software is something I'll often find time for - if given the opportunity. Shame, I would have liked to spin up the 1.1 prerelease (RC1?), even have a few different rigs/OSs to test on atm. Oh well.

right-shift takes over alt, left shift as usual. I don't immediately recall which key is duplicate in the editor (as I haven't played in a while), but it certainly worked for me a month or 2 ago (Debian 8) - I'm pretty sure it's right-shift... Yeah, that's real helpful. Maybe the OP should replace the entire computer too? Perhaps a different coloured chair would help? Do you see an 'fn' key on the keyboard in that picture? no? Neither do I.

Fix your damn "patcher" then - this is exactly what it's suited for. As it stands the KSP launcher/patcher is utterly pointless... and it's been that way for ~a year now.

Alt becomes right-shift on the GNU/Linux build, as alt combos are often used by the window manager. There's no menu for it, but you can rebind if needed by editing the settings file.

The "patcher" built into the launcher has been broken for quite some time now. Seems there's little interest in fixing this glaring flaw, so unless you bought the game on steam (which has a working updater) you'll need to re-download the entire game to 'update' it.

Performance. Dinky little 30-part mun flybys are fine and all, but docking late-game spaceplanes to large stations, or building surface bases at <10FPS is not really all that fun.

Looks like the answer was in the logs after all, in plain english even. FWIW, you can use *nix pipes (|) and redirects (<>) with any CLI application, e.g. 'lspci > /tmp/lspci.txt' to save output to a text file, 'lspci | nc termbin.com 9999' or 'lspci | pastebinit' to upload it to a pastebin etc. Not sure on the browser slowness though, I don't use Chrome. If disk / cache is the bottleneck, you might try mounting /tmp as tmpfs (if it isn't already) and possibly chrome's profile / temp directories too. Here's a lazy link to the Arch wiki on the subject.

Could be that, it's happened before.

Check fan for damage, hot bearings etc. Ensure HSF assembly properly seated. Remove the HSF, clean, grease (or replace pads) and re-install.

It's not really the radiation that's the problem for atmospheric usage... it's the difficulty of producing a compact 'fallout-free' fission device, 'cause too many radioactive particles in the atmosphere is a Bad Thing. Attenuating the gamma to safe levels requires a large-ish exclusion zone, but it's not too far-fetched... after all, atmospheric fission devices have been tested before. I guess it all depends on your "acceptable losses". If diverting an extinction level asteroid means 2 people get cancer from fallout... yeah, ok. Not so good for replacing chemical boosters on LEO runs though.

One more thing worth mention: Pick a distro to work with, (i.e. the liveUSB you are using) and tell us what it is. Ordinarily I'd suggest something common like Debian stable or Ubuntu LTS (particularly for older hardware) but in this case it may also be worth trying Arch Linux or an Arch-based distro, as it appears Arch still includes the SiS driver. --- Do try the ideas posted so far, but TBH I think the easiest course of action is going to be installing a supported video card. Almost anything else would be less hassle and should cost practically nothing. If you want to persevere with it, you may find someone else who has this hardware if you ask about your chipset on the appropriate forum for your distro. If that distro happens to be Debian, I'll be over here from time to time too... but be sure you ask Smart Questions, because: