


gamemoderun %command%

-w 1920 -h 1080
DO NOT USE PULSEAUDIO, you have to use pipewire for the game to work. I was stuck on red valve logo until I switched, after that everything worked perfectly, actually better than windows since I don't get random stutterings anymore

LD_PRELOAD="" PROTON_ENABLE_WAYLAND=1 game-performance %command%
no audio after playing a while
Only when viewing the scoreboard

Worked oob with some minor problems. If the stuttering continuous it can be annoying for ranked
Had no audio at the start, a restart of my pc fixed it
Had frequent stuttering for around 5-10s. I'd say every 2 rounds it happens. Is definitely annoying when you're playing MM

CS2 is stuck on loading screen when launched natively, it can launch with proton just fine but I can't join any servers because of VAC.
On wayland it doesn't work currently

Overall performance wise the game runs fine but the issues that I had with the game crashing my computer are nearly unbearable.
MANGOHUD=1 GAMESCOPE_FRAME_DURATION=1 LD_PRELOAD="" gamescope -w 1920 -h 1080 -r 144 -f --adaptive-sync --hdr-enabled --force-grab-cursor -- vulkan-game -novid -vulkan -nojoy
Stretched Resolution 4:3 did not work for me. Broken menus after switching.
Game crashes around every 45 minutes - 1 1/12 hours of playtime.

Flawless
Works great on Wayland (Hyprland :D). Works OOTB and native is nice

Works flawlessly out of the box. 4:3 stretched resolution, smooth alt-tabbing, good performance, and no need for launch flags or manual tweaks.

only showes me the GIGANTIC THICC RED ValvE logo and quits.
bruh :C

Unplayable
LD_PRELOAD="" %command% -vulkan +mat_queue_mode 2 -threads 4 -forcepreload 1
Screen goes black after loading into main menu. If you manage to make it into a game, severe performance issue show up.
Yes, I played competitive ranked and it works fine, hosting lobbys too, mods, etc.

-w 4988 -h 2100 -fullscreen -noborder -nojoy -novid
Weird Problems with Wayland...
I run custom stuff, so its expected. If you aren't expierienced, don't use WAYLAND
LD_PRELOAD=1 %command%
Frame Drops at Dying or viewing long distances

Cannot play due to borked UI
Changed the resolution and toggled fullscreen mode off.
Literally unplayable.

gamemoderun %command% -vulkan -high +mat_queue_mode 2 -threads 8 -forcepreload 1
Honestly haven't noticed any difference in gameplay from vanilla launch to my settings, it just runs like butter.

After a bit of tweaking, this game runs smoother than on Windows. Game also runs fine on Native Res without Gamescope.
gamescope -W 1920 -H 1440 -S stretch -f -r 240 --force-grab-cursor --adaptive-sync --immediate-flips -- %command% LD_PRELOAD="" -fps_max 0 +exec autoexec.cfg mangohud %command%
Gamescope runs well with no stutters, but cursor sometimes appears on second monitor and all mouse movement is halted in the game. This can be fixed by simply turning off the second monitor while playing.
VAC unable to verify game session.
This happens when you try to launch CS2 using gamescope. Fixes using this command: sudo setcap -r /usr/bin/gamescope and rebooting.

game-performance %command% +cl_forcepreload 1 +fps_max 300 -novid -threads 9
Im using borderless fullscreen 1280x1024 without gamescope. Might be settings bug, but its a good one.

LD_PRELOAD="" %command%
Had to waite around 40 seconds and then i was able to press ALT + Enter to switch to Fullscreen
Add the Command in Launch options change the cs2.sh file and switch to Wayland and waite around 40 seconds and then Press ALT+ENTER to switch to fullscreen and then itÅ› Playable

LD_PRELOAD="" %command%
The launch option is necessary to avoid frame drops when moving the mouse after about an hour of gameplay. So if you experience that issue too, this might be the solution.

SDL_VIDEO_WAYLAND_ALLOW_LIBDECOR=0 %command%
Without any changes I had weirdly low FPS and stuttering issues that seemed to mostly resolve themselves, unsatisfyingly, after forcing my monitor from 144hz to 120hz, then back to 144hz. Forcing Steam Linux Runtime 3.0 may improve average framerate a bit, but I don't have a good way to test that beyond "I noticed a bit more FPS, I think". "Normal" OOB performance on a Wayland environment only has periodic microstutters.
Experimental wayland support can be turned on by changing cs2.sh -- change export SDL_VIDEO_DRIVER=x11
to export SDL_VIDEO_DRIVER=wayland
. This may crash on startup without SDL_VIDEO_WAYLAND_ALLOW_LIBDECOR=0, as it did on my setup. Microstutters went away almost entirely after this.
With wayland support enabled you will likely have to tab out, then tab back in for full fullscreen.
Had unexplainable 4x slowdown on my system accompanied with halved CPU utilization from normal, that went away after changing my display refresh rate to 120hz and then back to 144hz again. Forcing high clocks with CoreCTRL also did not fix this. Other potential explanations -- AMD gpu not forced to "high" performance mode (this can be forced with echo "high" > /sys/class/drm/$yourcard/device/power_dpm_force_performance_level
, if you suspect this issue), funkiness with multi-monitor, magic faeries messing with you.
I tend to have weirder issues than most Linux users seemingly, so hopefully you don't have to do the same workarounds I needed to.
If you're using CoreCTRL to force high clock speeds, make sure you set up your fan profile properly or just leave it at automatic -- I had a system crash due to GPU overheating after a deathmatch because of my fumbling. Oops. Probably not a CS:2 issue, but thought it'd be useful to have known.

SDL_VIDEODRIVER=x11 LD_PRELOAD="" gamemoderun %command% -stretchaspect -w 1920 -h 1080 -vulkan
Everything to low with only dynamic shadows and all shadows enabled.
Some vegetation textures like palm leaves on DD2 are jittering.
After playing for some time the input lag spikes high slowing the whole game rendering pipeline. This resolves either by itself after some time (1-3 minutes) or a game reset is needed.
Overall I can play fine but these weird graphical issues and input lags can be annoying. This might be the GPU driver issue but during my investigation I didn't find any evidence for this thesis.

game-performance gamescope -W 1920 -H 1080 -w 1440 -h 1080 -S stretch -f -r 144 --force-grab-cursor --adaptive-sync --immediate-flips -- %command% LD_PRELOAD="" -novid -nojoy -sdlaudiodriver pipewire
Mild FPS Stutters
Recent updates have made me finally switch over to Linux full time for this game. Playing with stock launch options works just fine but I prefer playing in 4:3. The provided launch options work great for me. With the launch options the game launches in Gamescope in a wayland window, cursor doesn't leave the game, alt-tabbing is seamless, framerate is excellent, input latency is good, and I never experienced any major dips or stutters in two premier games. Might just be my hardware but sometimes close encounters with heavy spraying can cause some FPS drops but nothing unplayable.
runs as expected. did not notice any performance difference to windows

mangohud gamemoderun %command%
No audio during instance, reloading game fixed it.
Ran natively out of the box

Runs fine OOTB
The native default setup works fine. No artifacts, no audio issues, no input issues, no stutters. Don't have metrics to compare to native Windows performance, but it was well above playable.

gamemoderun mangohud %command%
Had to unplug my second monitor in order to stop it from going out of focus and going to the other screen. Fullscreen opens the game in a small window at the top left corner of my screen at start when it's set to 4:3. Changing to fullscreen windowed always launches the game normally. Could also switch to fullscreen windowed and back to fullscreen to resize it but it doesn't matter in my case.
My sensitivity is split in half. On Windows it used to be 1.2 in game, on Linux I had to put it to 2.4 for the same effect.
Fewer FPS than on Windows but still runs perfectly.
The game runs fine. No need for Proton because it's Linux native. I've tried Proton anyway and wouldn't recommend using it because of worse performance and other little bugs that make it annoying to deal with. I play 4:3 stretched and it works out of the box. Just select the resolution you want and you're good to go. I don't know what you would have to do, if you wanted 4:3 black bars. If you want to play fullscreen, make sure you disable "Allow screen tearing in fullscreen" in display settings if you have KDE. You can read about all the issues I had above and how to fix them. I almost thought I would have to setup dual booting just to play CS2 but gladly I don't have to.
`LD_PRELOAD=""` makes the game performances acceptable. Without it, the frame drops and input delay is unbearable for a competitive game.
LD_PRELOAD="" gamemoderun %command%

Gamescope made it playable for me, without it theres constant stuttering and running at a reduced framerate.
LD_PRELOAD="" gamescope -W 2560 -H 1440 -f -r 120 --backend wayland --force-grab-cursor --adaptive-sync --immediate-flips -- gamemoderun %command% -width 2560 -height 1440 -sdlaudiodriver pulseaudio -vulkan -nojoy -novid
Textures sometimes dont load, mostly weapon skins
The anti-cheat doesn't work me. I don't know why. I tried using both Proton and Native version. But no hope. :(
gamemoderun mangohud %command%

-dx11
The game window did not center itself when trying to run at 4:3 resolutions, just sits at the left 2/3 of the screen. Mouse inputs were also not accurate - had to have the mouse about an inch or so to the right of the button that I wanted to click on in the menus.
Standard 16:9 and 16:10 resolutions work normally.
- Minor stutters in main menu, goes away after a few minutes
- Lost about 20% framerate compared to Windows - game hovers around 180-200 FPS compared to 220-260 on Windows
- Choppy framerates during gameplay, likely what caused the input lag feeling I noticed
Consistently got VAC authentication errors when trying to queue a game using Proton Experimental and 9.0-4, went away once I switched back to my default Proton version.
Originally tested the game at 4K max settings with the listed hardware. Also lowered the video settings to the "medium" preset but it didn't change or resolve the performance issues that I experienced.
The -dx11 launch option isn't necessary, tested with and without it and didn't notice a difference in gameplay experience. It appears other people have reported that it has made a difference for them, so this may depend on your hardware.

LD_PRELOAD="" gamemoderun game-performance %command% -dx11
Finally runs fluently. -dx11 command is key here. game-performance is a CachyOS only command to get the pc in performance mode when a game is started. Runs flawlessly with these tinker steps. :)

LD_PRELOAD="" game-performance %command% -sdlaudiodriver pulse
audio completely cuts out unless the sdlaudio flag is added
Plasma 6.3.5 KDE Frameworks 6.14 Qt 6.9 wayland this shit can't fullscreen and gamescope completely fucks up inputs
gamescope fucks everything.
fucking unplayable on an hdd what the fuck valve
Valve. fix, now. unplayable on hdds
Lot less Avg. FPS compared to windows, yet I think better smoothness (higher one percent lows)

LD_PRELOAD="" gamemoderun gamescope -f -W 1920 -H 1080 -w 1440 -h 1080 -r 60.0 -S stretch --force-grab-cursor --adaptive-sync --immediate-flips -- %command% -sdlaudiodriver pipewire -high -novid
Loses audio when some games are also running at the same time (e.g. Balatro).
Trying to play on a stretched resolution without gamescope caused a lot of windowing issues and input inaccuracy. Native resolution works fine.
Using gamescope to make the game run in a stretched resolution causes a bit of input latency. Playable, but not ideal.
FPS randomly go from ~170 to 50 for around a minute seemingly without explanation. Some maps (e.g. Grail) won't even go over 40 FPS. Happens with and without gamescope.
Tested on GNOME 48.1 under Wayland.

Zero issues, great performance. One thing I dont like personally is how the game (on KDE) will minimize when I focus a window on my other monitor, I fixed this by setting the game to windowed mode and turning off the title bar.

Runs without tinkering. Plays normal.
No tinkering needed.

AMD_VULKAN_ICD=RADV %command%
As of the "Mission Possible" update back on May 7th, CS2 runs incredibly well, at least on Nobara Linux 42. The random crashes and freezes I used to have previously are gone.
mangohud gamemoderun %command%