CS:GO ingame vs nvcp frame caps (240hz monitor). Read description
CS:GOs ingame frame limiter seems broken and won't keep a consistent framerate even if your pc could easily provide the performance. The nvidia control panel limiter does the job better. This video also shows that you should cap your frames to an integer multiplier of your monitor hz to avoid tearing (x1 = 240; x2 = 480 etc), as found by calypto (https://www.youtube.com/watch?v=_73gFgNrYVQ). This results in a noticeably smoother experience in any game. In-depth video might be coming soon. The video was recorded at 240 fps and slowed down to 30 fps. Change playback speed accordingly. 0:00 ingame fps_max 230 massive tearing 0:58 ingame fps_max 240 frame drops resulting in worse tearing 1:44 ingame fps_max 470 frame drops resulting in worse tearing 2:27 ingame fps_max 480 frame drops resulting in worse tearing 3:13 nvcp cap 480 (fps_max 0) noticeably smoother but one line of crawling tearing (which we will eliminate in coming video) Limitations: nvcp and ingame cap are active simultaneously which could result in unwanted behavior. The point of the video is not affected by this. Eliminating the crawling tearing line at nvcp cap 480 is the goal (might just be caused by non-native, not exact 240hz resolution). Nvcp (and other limiters like rtss) might add latency, which is why the ingame cap should be fixed by Valve for an optimal experience. The net_graph fps counter could be inaccurate due to showing averages, thus being misleading at higher frame rates. External counters and 0,1%s should be used.
CS:GOs ingame frame limiter seems broken and won't keep a consistent framerate even if your pc could easily provide the performance. The nvidia control panel limiter does the job better. This video also shows that you should cap your frames to an integer multiplier of your monitor hz to avoid tearing (x1 = 240; x2 = 480 etc), as found by calypto (https://www.youtube.com/watch?v=_73gFgNrYVQ). This results in a noticeably smoother experience in any game. In-depth video might be coming soon. The video was recorded at 240 fps and slowed down to 30 fps. Change playback speed accordingly. 0:00 ingame fps_max 230 massive tearing 0:58 ingame fps_max 240 frame drops resulting in worse tearing 1:44 ingame fps_max 470 frame drops resulting in worse tearing 2:27 ingame fps_max 480 frame drops resulting in worse tearing 3:13 nvcp cap 480 (fps_max 0) noticeably smoother but one line of crawling tearing (which we will eliminate in coming video) Limitations: nvcp and ingame cap are active simultaneously which could result in unwanted behavior. The point of the video is not affected by this. Eliminating the crawling tearing line at nvcp cap 480 is the goal (might just be caused by non-native, not exact 240hz resolution). Nvcp (and other limiters like rtss) might add latency, which is why the ingame cap should be fixed by Valve for an optimal experience. The net_graph fps counter could be inaccurate due to showing averages, thus being misleading at higher frame rates. External counters and 0,1%s should be used.