this post was submitted on 05 Aug 2023
2 points (100.0% liked)

Counter Strike

11 readers
2 users here now

# Counter Strike - Counter Strike Official Blog m/cs is the home for the Counter-Strike community on Kbin and the Fediverse and a hub for the discussion and sharing of content relevant to Counter-Strike: Global Offensive (CS:GO), and the upcoming Counter-Strike 2 (CS2). Counter-Strike enjoys a thriving esports scene and dedicated competitive playerbase, as well as a robust creative community. This is the largest and most active CS sub on Reddit.


Socials - Discord

founded 1 year ago
 

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

all 4 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 1 year ago

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.

[–] [email protected] 1 points 1 year ago (1 children)

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

[–] [email protected] 1 points 1 year ago

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!