Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Now i'm on Windows 10 and eerything is fine.
I've never had an issue even on my older system. 22H2 even fixed some stuttering and added good features. Windows 11 is quite stable besides 23H2 and there's no need to resist change calling it very bad out of box. There are many examples of Windows 11 being better than windows 10 when VBS is disabled but thats another topic.
The thing here is just this available update is probably still in development and there's no hotfix for the problem I had besides going back. Community and valve should know so I opened a discussion for someone to find it if they feel lost.
(Also f u reddit r/globaloffensive autodeleting the post I made since it sounded personal to automoderator)
Yeah glad it worked for you, r/globaloffensive literally didnt let me post this, big L.
I've tried to go back up to 22h2 after downgrading from 23h2 (windows iso I installed was 21h2 and it is lacking many useful features I normally use for work) and got the same problem after manually upgrading to 22h2 too. So I'm going to do a fresh 23h2 install to see if the problem persists (there goes another weekend)
How will vsync fix sudden fps drop from 800+ to 8? Its like putting a bandaid over someone that got hit by a nuke.
I didnt wanna be rude but I'm literally a computer engineer.. Getting "turn on vsync" to a "possible fix for a problem more people may face in the near future" kinda offended me.
Vsync would only work if your fps drop value is above your refresh rate. And 8 fps, lets round it up for your sake and say 10fps. That means 100ms of wait time and when that drop happens even a 60hz vsync setup will have 6-7 frames lost. It will be a lot more noticable on higher refresh rate monitors because it will flow better until it stutters. Plus input lag is worse than stutter because with stutter you can actually play for about 3-5 seconds until the fps drop happens and game's stuck for about 100ms~ which is better than buttery crosshair.
---FINAL UPDATE---
The main problem was not with 23H2, the problem begins when you update from an older version of windows 11 (21H2 to 23H2 and 21H2 to 22H2 both caused stutters). I've made a clean install of 23H2 and I'm no longer having any stutter issue.
Fresh install of 23H2 was okay but it got ruined when I did extra updates. I made a recovery point before I turned updates on so reverted back to that.
What update? I have newest windows 11 version with optional updates and no issues.
Is it something super specific you updated?
And a bit confused how you have 800 fps and then only 200 for 1% fps.
Shouldn't it be like 650 fps for 1% ??
Mine 1% fps is = to my fps - 100-150
Major 23H2 update. After updating that and enabling normal updates that are available only for 23H2 really random 3-5 second interval stutters appear. I've tested it on my old pc and it seems fine as you mentioned. There's something weird going on with the software/hardware relations but I havent found it yet. Looking forward to some kind of bios or windows update that might fix it in the future but I will have updates disabled until then.
Basic specs:
i9 14900KF
RTX 4070TI
2x16 GB DDR5
2+2 TB 7000MB/s SSD
Depends on the game. Really well optimized games will have more consistent frametimes.
But for cs2 there are many variables that might spike frametimes.
%1 lows means the average of lowest %1 of frames. So lets say with a 800 fps game this only checks about 10 of those frames where you might have slightly longer frametimes. And %0.1 lows means average of lowest %0.1 of frames which only shows about a few lowest frames in that whole 800.
Also 200fps is around 5ms for each frame to generate. And 100fps is around 10ms for each. So since the average fps is around 800 I can assume that most of the frames get generated between 1-2 ms but some minority of them can take about 5 to 10 ms which is not perfect but really difficult to notice.
Here's an example benchmark (1:32);
https://youtu.be/XMVu3pB4DI0?si=1KXl5yO6l3ti-LEZ&t=74