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!
I’ve had issues on stock x11 PopOS using nvidia. Decent fps, but bigger drops and frametime consistency seemed horrible. I have to turn off my (mismatched) 2nd monitor for my proper refresh rate to work, but it still looked very microstuttery. I miss VRR, but I think there’s a bigger underlying issue than vsync/VRR not working. Haven’t tried Wayland yet.
The problem is that the game developers at Valve don’t know or care about their own platform. CS2 on Linux is an afterthought, possibly even ported by other people within Valve. CS2 had a lengthy beta period on Windows, with the formal CS2 release, the beta cycle on Linux just started.
Fwiw, I’ve had no issues playing CS2 on either with my old (3700x/1080ti) or newer setup (5800X3D/7900XTX) with PopOS. The first doesn’t seem too far away from your rig, have you tried switching the Nvidia driver you’re on? I think Turing is fine with 560?
Good point,it hadn’t crossed my mind yet. I’m assuming it’s using the proprietary nvidia drivers. I’ll give that a go.
I remember the frame time issue happening but it fixed itself and I can’t remember the cause. Try changing the refresh rate of your monitor, it might kick something which fixes it.
Performance should definitely be mostly on par with Windows.
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.
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
The game is set to run full screen ( as windowed fullscreen caps the framerate to 60, while the screen supports 144 ).
In case your game also doesn’t launch on the main screen you can try setting the monitor to a different position on the virtual canvas:
https://github.com/ValveSoftware/csgo-osx-linux/issues/3282#issuecomment-1969271416
I’m only using one screen at the moment, but thanks for the input! Maybe it helps someone else, or me if i decide to hook up the other screen again :)
Did you install Steam via flatpak or normally?
I’ll check tomorrow. It came preinstalled with nobara. I’m assuming its native, but can’t confirm right now
