•

CS:GO stuttering (Frame Variance?) on Manjaro Linux after several minutes of playing

Hey all, hoping that someone else might be able to shed some light on this particularly strange issue I've been experiencing. When playing CS, I typically get between 500-600 FPS and have a super smooth experience.

Recently, after about fifteen or twenty minutes of playing, my game will suddenly have the frame variance spike to 10-20 ms, FPS drops to 250-300, and everything feels like I'm playing at 10 FPS due to the stuttery mess the game becomes. The issue goes away immediately upon restarting the game. Weirdly enough, I have noticed after the issue starts that if I open the in-game console, everything behaves normally until I close the console again.

Any advice anyone can offer would be greatly appreciated; here's the specs for my system:

Operating System: Manjaro Linux
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.3.13-2-MANJARO (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 31.1 GiB of RAM
Graphics Processor: AMD Radeon RX 6800 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B650 AORUS ELITE AX

5 comments

MrHandyMan

•

Do you start the game with "-vulkan" parameter? If you use it, it could be this issue: https://github.com/ValveSoftware/csgo-osx-linux/issues/2901

captainsiscold

•

Good thought, I forgot to mention this in my original post. The issue is present both when using -vulkan and when not using it. The issue described in the link you provided looks similar, but I don't think it's the same issue I'm seeing.

captainsiscold

•

Late to the party, but I thought I'd update with some more info for anyone stumbling across this in the future. @MrHandyMan was at least partially correct in the assessment of the issue. In that thread, the launch option LD_PRELOAD="" %command% is recommended to alleviate the problem. In my experience, this was not particularly helpful, and actually prevented the game from launching sometimes.

However, based on discussion on the Github issue thread, it seems that the issue was (either wholly or in part) caused by me having the Steam overlay disabled for CS, which I had done in order to fix an unrelated crash that seems to have been fixed. Enabling the Steam overlay fixed the problem, and my game seems to be running as intended now.

vardogor

•

if you have steam overlay disabled, enable it. i had this problem as well until i did that

captainsiscold

•

I discovered the same thing; fortunately the game crash that was caused by having the overlay enabled seems to have been fixed, so enabling the Steam overlay seems to be the best recommendation to make now. Thanks for the suggestion!