this post was submitted on 05 Aug 2024
20 points (95.5% liked)
Linux Gaming
15462 readers
196 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME
away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah, I have issues with random really poor frame times. I'll be sitting at 144 FPS then get some frames that take 45ms to render each/severe stuttering.
I "fixed" it using the proton version of the game though I've heard some people say that doesn't work with match making... Haven't tried that yet.
I was thinking about trying the -vulkan launch option to see if that does anything if my proton install doesn't work.
EDIT: They were right ... VAC doesn't work via Proton. I retried playing the native version and it seemed to run fine this time with or without -vulkan ... so I'm not really sure what's going on anymore.
Maybe some things have been fixed either on the Linux/Mesa or on the Valve side.
They fixed an issue. They broke something in an update in July and fixed it a week or 2 ago.
https://github.com/ValveSoftware/csgo-osx-linux/issues/3803
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