Okay then. [This [1]](https://steamcommunity.com/app/239140/discussions/0/611698195154676908/) [may [2]](https://steamcommunity.com/app/239140/discussions/0/606068060819458509/) [not be a Linux-exclusive issue[3]](https://steamcommunity.com/app/239140/discussions/0/604941528466976965/), in the patch notes for 1.4.0 they didn't put this fix to the Linux section but just to "Graphical Bugs". I'll check this out on my home rig after work.

View this comment - View article - View full comments

Hey, that's an old issue that was already fixed once! I remember having super-blurry wall signs at the tower at the very start while having high textures otherwise. IIRC, it's a caching issue of sorts like they provided a prebuilt texture cache with lowres versions.

Look here [External Link] in "Graphical Bugs" section: "Extremely low resolution textures on certain objects regardless of texture quality settings. - Fixed by Patch 1.4.0 [External Link]"

Maybe clearing the shader cache would help? Just guessing.

View this comment - View article - View full comments

Could this be a port forwarding issue? I only played multiplayer once, it was before the performance patches. Then I couldn't connect to anyone always disconnecting right after entering the online session.

View this comment - View article - View full comments

So many memories after watching the trailer! Dying Light (despite me calling it "Dying Hope" considering the state of the Linux version, now much better than it was initially) is definitely a game to remember. Such lovely characters, lazy summer atmosphere with nice ambient and even a good story, unusual things for a zombie game. It's time to return and kick some zombies in the head!

Too bad many good characters won't be there for obvious reasons (no spoilers though).

View this comment - View article - View full comments

Daily dose of Natural Selection 2 and also some Europa Universalis IV. Surprisingly good soundtrack in the latter and of course deep and complex gameplay. This thread suggests me to jump into Saints Row IV asap and I feel like I can't just decline.

View this comment - View article - View full comments

Yes, these issues are annoying and should be fixed. Some day. Until then, there are workarounds that allow me to play on a daily basis without any troubles. Try them!

Sticky/repeating/not responding keys issue: something is wrong with handling the ibus input method [External Link]

Frequent random crashes: try to reduce the "texture handling" value [External Link]

Crash on startup or having no sound due to sound initialization error: symlinking your system libasound.so could help [External Link]

As with many other Linux ports you may have all sorts of weird issues if your system locale isn't en_US.UTF-8 or en_GB.UTF-8, I suggest setting it in the Steam startup script.

View this comment - View article - View full comments

Quoting: FraaarghIf it's fixed, they should tell Virtual Programming how they did it because they have kinda the same bug in Dirt Showdown chere cars' wheels are transparent ! https://github.com/virtual-programming/dirtshowdown-linux/issues/4 [External Link]

These issues are unrelated. Well, they're similar in that regard that usually it's a broken shader that doesn't compile or run. Because of that no pixels are rendered by that shader and you have a transparent (or filled with black/white/other color) piece of mesh. But knowing what exactly was wrong with this shader wouldn't help much fixing the Dirt's one. It's like getting miscalculations in Excel and MathCAD, they're both errors, yes, but they happen in different apps because of different reasons and they should be dealt with via different means.

View this comment - View article - View full comments

Hmm, you should have your reasons to use the stable Debian as a desktop system, especially if it's also a gaming rig... I don't know why it's so important and just happy with testing. Gaming on Linux often requires very fresh software like NVIDIA driver and other components as well so stable is often just not enough. But well, you know better. At least we've tried. You may try to just disable and kill PulseAudio and use pure ALSA. This way it won't use that crashing module and should give you sound. You don't have it because PA grabs audio exclusively.

View this comment - View article - View full comments

I see. You've said you're on Jessie which is the stable branch. Could you upgrade libasound2:i386, libasound2-data and libasound2-plugins:i386 to testing (1.0.29-1)? It's hard to check the library version in the Steam Runtime but I expect it to be older that that in testing hence the symlink might not actually matter in your case. You may also verify this claim by comparing the backtrace with and without the symlink.

View this comment - View article - View full comments

Is that really everything it outputs? For me the last line was about assertion failure in async.c. If you want to help debugging the issue, try to get a backtrace with GDB.

View this comment - View article - View full comments