altruizine

Thanks for this. I'm still annoyed enough at my graphics stack (separate issue led to X crashes when loading large images in a browser. great, right?) that I still don't want to deal with it right now. And when I do, I'm not sure I'll be willing to downgrade Catalyst even farther. The xorg thing is ridiculous enough. Nonetheless thanks. Maybe I should get into mesa development just so I can learn what the heck is happening.

Mesa drivers on my distro are apparently incompatible with Steam in some way with nothing to do with KSP. The fact Steam can cause X to segfault promises to be enough of a headache that I'm just going to try things again in a few weeks and hope the bug maelstrom has worked itself out. Thanks for the help.

I tried setting steam's launch options for KSP to include LC_ALL but everything seems to work the same so I'm not sure I've actually done so. I'm not sure what you mean by "the segfault fix" - is it not linked in the OP here? Anyway this doesn't seem like a segfault, and I think I'm just using a 32-bit binary (at least, I keep seeing that _64 is experimental, and I haven't switched to it). Uninstalling fglrx and installing mesa is rather an ordeal but I suppose there's not much else to check.

Yo. Hopefully this is the place to ask for tech support. If it's not I can move this post and such. I'd been putting off buying KSP for a while because I figured it wouldn't work on my Arch Linux computer, but yesterday I grabbed the demo (0.18, I think?) and it went fine, so I sprung for the game on Steam. Unfortunately, the new version has not gone well. I think I'm having two separate issues. The probably simpler one is the game crashing when I go from the main space center screen to the launchpad. It doesn't seem to happen when I just move from the vehicle assembly building to launching. According to Player.log, this seems to be due to a NullReferenceException somewhere or another. The second issue is more important and makes the game unusable. It hangs at hard to understand points. Sometimes during the second menu screen (after "start game", I mean) and at two different points on the launchpad (gotten to directly from vehicle assembly to circumvent the above) before and after Jeb's face shows up. I haven't tested this second bug much because when I say it "hangs", I mean my entire system goes unresponsive. The fan spins up so I assume it's in some kind of loop, but I have no way of knowing, as the CPU monitor, rest of the screen, mouse, etc. are all inoperable. Can't even switch to console. Music seems to keep playing, however. The only way I can stop this is a soft reset of the whole computer, so I don't know what kind of logs are available. This bug report might be relevant? As I mentioned, the demo on Steam worked fine. The only issue I had was the font thing mentioned on the Arch wiki, but that didn't cause crashes or anything and was easily fixed. I've already tried throttling down the textures and other graphics effects, including disabling anti-aliasing, but no dice. I realize my system isn't officially supported, but I'd really like to play, and any support would be appreciated. Some system details: uname -a Linux Syadavaktavyah 3.14.6-1-ARCH #1 SMP PREEMPT Sun Jun 8 10:08:38 CEST 2014 x86_64 GNU/Linux CPU is 6x AMD FX-6350 Six-Core Processor GPU is AMD Radeon R9 200 Series I am using the fglrx proprietary driver, like in the bug report. Specifically, I am using Arch's "catalyst" repository. The control center reports a "Driver Packaging Version" of 13.251-131206a-166303C-ATI. Oh, and everything's updated as far as my distro goes as of a few hours ago. Thanks in advance.