
Olivia
Published
Had several random lag spikes
The game (but not the UI) turned black after alt-tabing out and back in
The game stopped taking keyboard input
The game (but not the UI) turned black after alt-tabing out and back in; made the game unplayable
Had to switch to proton to get past the cutscene at the start, but unlike some of the other games in the series, it's not playable long-term with proton either
Super flaky starting
I regularly run into https://github.com/ValveSoftware/csgo-osx-linux/issues/2815#issue-1028076575, but I've never been able to find a consistent fix for it. Manually adding the missing library lead to architecture mismatching, but then removing it again magically made it work?
It does work from time to time, but far too often, it fails due to libctmalloc-minimal missing. There are workarounds mentioned in the GitHub issue, but from experience, they aren't guaranteed to work. Extremely disappointing that this hasn't been fixed in spite of being known for years
Native and proton both borked (CS2)
Proton crashes immediately after clicking "play". Proton 6, 8, and experimental are all borked. Didn't attempt to check other versions, because there's too many to bother, and these are the main versions
Native starts to the splash screen, but never gets past it. It also causes unrelated windows (read: discord and firefox, though I doubt it's limited to these specifically) on my second screen to flash between the windows themselves and my desktop several times per second.
Didn't have any of these problems with CS1
Had to force experimental to install, but works fine after that
I can't seem to change the audio settings, but it's equally borked on native Windows, so not a proton problem. Reduced the application volume in the OS instead. Otherwise all good
Couldn't install without forcing the use of proton, but after that, the game installs fine and runs beautifully.
I switched to the native version a while ago, and it worked fine, but it suddenly broke today (I have not played for a few days though, so it probably didn't break today). Had to switch from native back to forced experimental proton to make it work.
Also, for some reason, the native version downloads Windows files? Might be why it's broken, but I have not looked into it. Can't be bothered, proton works fine, and has worked for ages
Crashed before reaching the menu
Had to do two passes before it did anything. On the first pass, it was stuck on a loading menu. On the second pass, it crashed before reaching the menu. Wasn't able to get any other behavior, and none of my tinker attempts led anywhere.
Achievements do not appear to work.
Initially thought achievements didn't work, but the first achievement just didn't trigger when I expected it to. Not a proton problem
Enhanced edition doesn't start
The intro cinematic plays (unskippably), and the game freezes during or after it
Native: scrollwheel to switch weapons didn't work
Switching to proton experimental wiped my save; take backups before switching
The native version runs fine, but has significant stability problems. Running in proton sees signfiicant performance drops, particularly on cutscenes for some reason?
Native: The game started crashing when getting deeper into the campaign. Regularly crashes when trying to load it for the first time. Switching to proton appears to have sorted out most of them, though at the expense of performance problems
Native: gamma doesn't work, gameplay seems unresponsive for some reason I can't quite put my finger on
It's worth emphasising that the native stability issues mainly grew as I got further into the game. I got a few hours out of it before it became unplayable
Occasional static noises; I've been noticing this in all games across all versions of proton after my distro switched to pipewire
I have a 144Hz monitor. Proton games occasionally get treated as a pseudo-60Hz monitor. I consistently run at 47 frames on an RTX 3070. This is not a graphics-intensive game.
Also weird, it doesn't seem to actually do vsync. In some scenes, it's all the way up at 66FPS (as measured by steam). On that note, it looks like it's heavily CPU-bound. Maybe the source game is poorly optimised?
I had to roll back all the way to 3.7-8 to get the game to stabilise. TL;DR:
- Hotfix, experimental, 9.0, 8.0: Borked, crashes immediately after start
- 7.0: Starts (music starts playing), the window is a copy of my second monitor
- 6.3-8: starts (music starts playing), the window refuses to open, and minimises immediately
- 5.0-10 down to (but not including) 3.7-8: Starts, but crashes within a few minutes
Only 3.7-8 appears to be stable enough to run the game on my machine. No major problems after that, aside running significantly slower than it should be, but that isn't breaking for this game
Not sure why, but I've observed crackling with other games as well. I suspect this is a weird interaction between my system and pipewire. Didn't use to have problems like this with any games prior to switching to pipewire
Had to force Proton 9.0-3 (might be the default anyway?). Borked on experimental, and cannot install without forcing a version of proton
-vulcan
Windowed refuses to stay windowed on 1920x1080 for some reason
Occasionally refuses to take mouse input - I have to alt-tab out and back in to get it to work again. mainly happens after switching back to the game by clicking
Refuses to start without proton experimental, and seemed to refuse clicks without -vulcan
(the alt-tab stuff with mouse input appears to be unrelated to that)
Had to switch to a legacy proton for the game to start. It didn't want to run on experimental
Doesn't run
On experimental, I don't get past the EA launcher. On 6.3-8 or whatever it was again, I don't get past the first install script
When launching, the game claims the .exe can't be found. Fixed with forced experimental. Works great when launched