Is anybody here playing cs2? The game runs natively on Linux, but its more laggy than it was on windows for me. If i run cs2 in proton it works better than natively on Linux, but I’m unable to play competitive that way.
My issue is the following: the game just hangs/freezes occasionally. The duration is random. Could be 3-5 seconds, could be 10. Could be that I’d have to restart the game.
This occurs sometimes in the warm up before a match or when the bomb explodes.
It happens most consistently when i press the escape button in-game.
I’m running it on nobara/KDE. I’ve got the latest graphics drivers, tried validating the game files.
The game is set to run full screen ( as windowed fullscreen caps the framerate to 60, while the screen supports 144 ).
I can add more hardware info if required. The PC is 4 years old so its not ancient, but also not latest and greatest ( amd CPU+nvidia rtx 2080ti ).
Anybody else ran into this behaviour and ( hopefully) found a solution for it? Googling only left me with sites telling me to upgrade my gfx drivers on windows or 6 year old threads of CS:GO on windows.
Switching between wayland and x11 didn’t really seem to make a lot of difference. It feels a little bit better on x11, but negligible.
There isnt really anything running on the backgroudn except discord.
Thanks!
Hmm, I wonder if that was it. It didn’t really seem to have anything to do with menus though.
It was in my case. Issue completely vanished overnight. I had a working work around where I lowered certain settings and it only occurred sometimes at round ends or when I pressed tab to view the scoreboard. Usually alt-tabbing resolved it.
After they released that fiz everything worked like normal again.
Very interesting. I changed my IO scheduler to kyber for unrelated issues… Maybe between that and the processing power (7950X + 7900 XTX)… my hangs were just sub second.
The issue was related to the Linux scheduler. So if you had a different scheduler than what moet distributions have as default, you might not have experienced that issue.
There are a few people in the comments that reported that they compiled a different scheduler and that the issue completely disappeared
