Counter Strike 2 - Huge performance loss compared to Windows client #3325
Comments
|
One temporary solution could be compiling the game against DXVK and adding "-dxvk" launch option until native Vulkan implementation matures enough. In both screenshots the game is GPU limited, everything at low except for model and texture at very high, FSR disabled, AA set to CMAA2 and the game is running with RX6800 |
|
I have the opposite (nvidia gpu, map: Mirage). DX11 Vulkan |
|
This appears to be limited to AMD GPUs on Linux. I also get about 50% better FPS on Win10 vs Arch with AMDGPU and x11, and there are also graphical bugs (#3287) with AMD and Linux that do not occur on Windows or with Nvidia on Linux. R9 390 GPU load is always at 100%, Ryzen 3500x CPU between 20-40% on all cores. |
what GPU ? and what resolut/setting you on? even when i set my game to 1080p and settings to low i get sub 200fps on my Nvidia 3080 and really bad frame pacing spikes into the 40-80ms randomly but often so like from 200fps to 30-60fps for a split second |
|
I have the same issue with a 7900x+7900XT on Arch and Hyprland. I average about 150 with bad stutters and max around 220. The whole time the game is rendering on Linux, my GPU is pegged at 100% usage. With the same settings i am locked to 400 most of the time on Windows. However, I also had poor performance with DXVK through Proton when trying during the beta. I'm not sure if anything has changed since then. |
|
Same issue here: OS: Ubuntu 22.04 jammy I get around 170fps with drops to ~100fps from time to time. On my 2nd SSD I habe win10 and there I get 350-400fps with drops to like 280fps. |
Does your console show something like
while its stuttering? |
No, there are no errors in my game console. And also not sure what changed, but now I am only getting ~20 FPS in game without it utilizing more than about 30% of my GPU. Edit: actually just changed from rt kernel to mainline and I'm getting 400 FPS now. Not sure if an update happened, but I was also getting bad FPS on mainline kernel yesterday. Edit again: back down to 30-100 FPS in game while still on mainline kernel. No change on my system |
It is not. With nvidia proprietary drivers and no launch params I observe significantly lower avg framerate and common stuttering (a few times a second) compared to Windows 10. With |
|
#3325 (comment) Which card and which driver version ? |
GTX 1050 4GB (notebook), 535.113.01 |
Well non RTX nvidia card have bad vulkan support so that would not be surprising. They lack some vulkan extensions, VKD3D also suffers bad performance with pascal nvidia cards. |
Is that true? I played csgo with -vulkan with updated dxvk binaries (v2.2) and I had better avg framerate than with opengl. Also, considering that others with newer nvidia cards have the same issue, I don't think it is due to bad vulkan support. |
DXVK is not VKD3D, it doesn't suffers bad perf on pascal cards and yes opengl has bad perf. For the rest I can't say, the rest of the thread was claiming that nvidia cards was not impacted. |
I have a turing card (GTX 1650) which has all the required extensions and I can comfortably say that the performance is definitely not the same |
Interesting... But that should not matter in this case since vkd3d isn't being used. I have seen comments of people in r/linux_gaming with turing and higher nvidia cards that had the issue and of people that had pascal cards and had no issues. Seems quite random whom it affects. |
|
I performed a rudimentary static benchmark between different backends on Windows and Linux. Benchmarks
Note: The brightness for Windows Vulkan is only borked on screenshots, it was OK in-game. TL;DRWindows Vulkan performs up to 11% worse than Windows DirectX. SoftwareGame Build: Sep 28 16:47:43 HardwareProcessor: AMD Ryzen 5600X NvidiaDRM enabled: In-game settingsResolution: 2560x1440 stretched to 3440x1440 MiscGlobal CPU scaling governor: Launch parameters: Related system-wide environment variables: export NVD_BACKEND="direct" # VA-API backend
export LIBVA_DRIVER_NAME="nvidia" # VA-API driver
export PROTON_HIDE_NVIDIA_GPU=0 # Report as Nvidia
export PROTON_ENABLE_NVAPI=1 # Enable NVAPI library
export VKD3D_CONFIG="dxr" # Enable DirectX Raytracing |
|
these bugfixes don't fixed performance for me |
wonder if there is a debug tool to record the stutter to see what exactly causes it? |
|
I used in-game benchmark tool to record some stats. They were recorded in Inferno with same spawn location as a T player. The game is GPU limited in all scenarios, with same in-game graphics settings using an RX6800. Launch arguments used to start a benchmark: Performance loss for Linux Vulkan vs. Windows DX11: 40,93% Windows DX11: Windows Vulkan: Linux Vulkan: |
|
@MacTavishAO that frame time on Linux Vulkan is exactly what i am seeing that makes it unplayable, trying to find out if there is some kind of tool to profile the performance some how to find the reason for it so Valve can fix it or maybe they already know Linux Vulkan |
|
Shader stutter workaround for AMDVLK:
Most shader stutters are eliminated this way. It's night and day. |
|
It is performing quite badly on my 6750XT.
https://flightlessmango.com/logs/4453 Will try the Fossilize workaround posted above to see if it helps :/ |
Make sure you launch the game using amdvlk. |
How exactly do I ensure this? |
|
Most if not all distro's come with mesa drivers, amdvlk is AMD's own open source driver, you need to install it manually. |
|
How large is the parc file? |
It depends on your GPU and amdvlk version. It was bigger than 1.3 GB for me. |
|
positive way - did not test AMDVLK, only Mesa mesa 24.0, rx6600, 5600g My "Bench": T side Mirage, unlimited ammo, smoke, frag grenade and ak. Hit record and then I try to throw smokes and he grenades at the same spots and do some spraying, look at the smokes, and go on. Back at the start i stop the benchmark.
|
|
I will try to check that. An improvement of 10% through Mesa 24 would be awesome. |
In a positive way. Took a quick glance and below were my FPS more or less on 5700X, RX6800 system running Plasma 6 RC2. Vulkan renderer still needs more work but it's better than it was before I'd say. Inferno Mid;Windows DX11: 450~ Nuke T Base;Windows DX11: 640~ I changed back and forth between x11 and wayland SDL_VIDEO_DRIVER by editing cs2.sh. Default is x11. |
|
It seems to perform better at the start of a match but at least in my case (RX 6600, R5600X, Mesa 24.00, plasma 5.27 on ubuntu 23.10, steam installed via official .deb ) the gpu utilization starts fluctuation more and more the longer the game has been running and the framerate seems to worsen as well (and my GPU is nowhere close to temperature throttling and works fine under full load for other apps so it's not that). Seems I'm not the only person noticing some issues with gpu utilization: No idea if this is a driver problem or a game issue. Tested with wayland sdl driver but that seemed to screw up the colors so not sure it's properly functional yet. |
I have a similar issue, and I'm running Nvidia on X11. So I think it's more likely a game issue, or the game's implementation of vulkan. |
|
R5 5600 + RX6800 After todays patch, I wanted to try if I can see any performance improvement. I deleted my shader cache and started the game, went to de_ancient and to my surprise, MangoHUD reported over 400fps with peaks into ~460fps. GPU was working overtime, and I was even able to hear slight coil whine for the first time with this card in CS2. When running though water, fps only dropped to about ~360fps. Previously I had about 200-220fps with drops to 140fps in the water. When going into another map (de_nuke) fps were all of a sudden the same as before (200-250fps). GPU not stressed anymore, and no more coil whine. So I loaded a 3rd map (de_inferno) and also, everything was as bad a ever. I have no idea why fps were so good when loading the first map. I had absolutely no shader generation stutters, everything was buttery smooth. Will try again later if it was because of deleted shaders. |
|
Just from some quick testing it seems that there being other players on the map is having a drastic effect performance in some way (seemingly causing a bottleneck somewhere that's at least not showing up as either gpu utilization or close to maxed out cpu cores) even if they are not visible and maybe even if they're dead? Loading into an empty dust2 map with no other players using the console and kicking the auto-added bots I get GPU limited with my RX 6600 and R5 5600X as expected and the performance is in the 400s fps range. Bot match with 10 people in it drops me closer to 300-350, joininga deachmatch on the same match puts me closer to 200 on average though it varies a lot. The fps and gpu util also drastically goes up at the match end screen. FPS on Default DX11 renderer on windows is actually a bit lower than on linux when running around dust2 with no other players but doesn't suffer nearly the same hit and bottlenecking when joining a server with other players on it or adding bots. Vulkan renderer on windows seems to have similar behaviour as on linux, with high fps and the gpu being utilized if you load a map on your own (fps was about the same as with dx11 on empty dust2) but gpu utilization is nowhere near full and fps a fair bit worse than dx11 mode if joining a deathmatch and may or may not get lower over time. |
|
Finally got around to testing it on an arms race game. Game drops to 90~ and stays there. No matter what you think, 5700X paired with RX6800 shouldn't drop to 90s. Weak APUs on Windows manage to hold higher FPS. Unacceptable. |
|
do you still have this with the
update? |
|
Low performance. I had this kind of issue with games that are Playstation ports. |
|
To be honest, I think many of us are mainly unhappy with how movements feels way less smooth in cs2 compared to cs:go. I installed cs2 on my windows install, hoping to be able to play again, but was disappointed to find it still feels like I have 40 fps the entire time, despite my frame rate being perfectly fine. |
No, not me. Please don't include me in your statement if it's just your personal opinion. |
|
"I think" and "most of us" should indicate I didn't state you were. |
No, you are wrong, at least in my case and I think in many others too. |
|
Y'all can't read. I said the frame rate was fine on my windows setup. Linux does have lower frame rates indeed, and the issue is real, but part of it also comes from the less smooth movement of cs2. That's all. |
objectively wrong, just check the frame pacing on linux vs windows, people have posted graphs..... on windows its way way more stable and smooth on linux it spikes to 80ms+ constantly and its all over the place, on windows it does not do this and is perfectly smooth not going from 300+fps to sub 10fps random stutters that happen all the time |
|
That complies to what I said? |
|
No improvements with the latest update. |
|
On the latest update: https://steamcommunity.com/games/CSGO/announcements/detail/4199120329626448731
This could be useful for cs devs to know the cause of the insane stutters (we already know its shader compilation) than what we already have (? |
|
I'll take a look and try to provide a gist later. |
|
Arms race matches on the shoots maps seems to be one of the worst offenders when it comes to microstutter if people need suggestions on something to test quickly. Whether the stutters are still long enough to trigger this effect I don't know, as one or two of the recent updates that fixed some thread stuff seem to have made the impact a little less but it's extremely noticeable. |
|
This output is printed to console right after a game of Arms Race on Shoots. I had to set cl_frametime_summary_report_detailed to true to get additional information to display. FPS starts off high and drops to around a third of it by the end of the game. |
|
So I have played another game of Arms Race on Shoots to upload performance metrics recorded by mangohud at 1000ms intervals: https://flightlessmango.com/games/4777/logs/5280 It's still not adequate enough to show performance issues so I'm leaving gists of raw recordings too: https://gist.github.com/MacTavishAO/efea87313030ff986dc2697e52d9546b As can be seen on CSV recordings, CPU utilization starts at mid-20s and climbs all the way up to mid-40s and settles there whilst GPU utilization starts high (98+) but it slowly goes down to as low as 55% by the end. This results in significantly lower FPS after a while. I should also mention that this game only took 5 minutes for someone to win. Performance impact would've been much worse otherwise as I have seen sub 90 on longer games. |
|
Having just switched back to Linux after being on Windows for a few years, the performance is very apparently worse on Linux. It's unplayable, I'll just boot up Windows when I want to play CS for now. Valve pls fix. |
|
I know this is a pretty undetailed report, but I switched from a 12900K to a 7800X3D yesterday and the performance difference is HUGE. The frame times are incredibly consistent and spike free on the 7800X3D, unlike the Intel. |
That's really interesting. On my 13900HX, I have pretty bad frame times, which are slightly improved when disabling my e-cores. Note that I'm using the latest kernel (6.9.5) on Arch/KDE/X11 with an RTX 4090 Mobile. On Wayland, cs2 is borderline unplayable. |
|
Just to expand for those who may be interested, after extensive testing I've found that KDE performs better than Gnome by a small margin and X11 outperforms Xwayland (and forced native Wayland) by a large margin. |
How can I force native wayland? I'd like to give it a try. TIA. |
in the game dir, find cs2.sh and change export SDL_VIDEO_DRIVER line. either change to wayland or comment it out. |
and others
Your system information
Steam->Help->System Information) in a [gist](https://gist.github.com/):Please describe your issue in as much detail as possible:
Below are the screenshots from native linux client with vulkan and CS2 running through Wine + DXVK, respectively.
I've played the Limited Test on Windows and there seems to be performance loss of anywhere between 40 to 60% compared to Windows client.
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: