Who you gonna call? The Blur Busters! For Everything Better Than 60Hz™
https://forums.blurbusters.com/
Forgive me for taking this off topic for a moment, but what would you set this variable to with a G-Sync monitor? In game it defaults to "0", but I always change it to "1".Chief Blur Buster wrote: ...Set "Max pre-rendered frames" to 1
It seems more fluid when I set it to 1. I swear I saw stutter at 0 which I believe is equal to 3 pre-rendered frames. These are set in an INI file for my game (Assetto Corsa). Sorry for the HijackChief Blur Buster wrote:At the drivers, 0 and 1 seems to be the same for VSYNC ON, as far as I am aware (0 rounds up to 1). But I haven't tried the difference during GSYNC mode, so I'd just leave it alone (keep it at 0) during GSYNC mode. Are you noticing any difference?
And what about triple buffering ? How does it affect input lag in the best case scenario (VSYNC ON) that you just desribed ?Chief Blur Buster wrote: VSYNC ON Input lag goes down significantly when:
- Using a higher refresh rate such as 120Hz instead of 60Hz
- Set "Max pre-rendered frames" to 1
- Setting an in-game framerate cap a very tiny bit below Hz
Example: In Counter Strike:GO, enter "fps_max 119" or even "fps_max 119.8" at the console
(Important note: Driver capping, or any other external capping, will always have more lag than in-game capping, due to the way things work).
Doing all the above massively reduces input lag for VSYNC ON (and even helps GSYNC a bit too, for the capped-out situations). It does not eliminate all of it. But 80% to 90% of the VSYNC ON lag penalty disappears when all three techniques are done simultaneously.
Triple buffering usually has less lag. But triple buffering has pros and cons. It introduces microstutters caused by the framerate-refreshrate match. If you are prioritizing motion clarity over input lag, then you need to use double buffered VSYNC and a powerful-enough GPU to maintain the framerate-refreshrate sync.mello wrote:And what about triple buffering ? How does it affect input lag in the best case scenario (VSYNC ON) that you just desribed ?
the type with two backbuffers? yea that would reduce lagChief Blur Buster wrote: Triple buffering usually has less lag.
There is no difference between 0 and 1 since technically it must always be in process of rendering the next frame.Cooknn wrote:It seems more fluid when I set it to 1. I swear I saw stutter at 0 which I believe is equal to 3 pre-rendered frames. These are set in an INI file for my game (Assetto Corsa). Sorry for the HijackChief Blur Buster wrote:At the drivers, 0 and 1 seems to be the same for VSYNC ON, as far as I am aware (0 rounds up to 1). But I haven't tried the difference during GSYNC mode, so I'd just leave it alone (keep it at 0) during GSYNC mode. Are you noticing any difference?
Congratulations on the new monitor rob_IDDQD! It must be amazing
That is quite true. I was very impressed with the image quality on my VG248QE compared to my old monitors, though it needed some significant calibration to get there. Unfortunately nVidia's drivers do not allow forcing color profiles in games so I only get the best colors on the desktop.ManuelG_NVIDIA wrote:It is not mentioned much but colors on this monitor are so much better than my old 3D Vision Asus 27" monitor. TN panel image quality sure has improved a lot over time.
Tripple buffering will always increase lag by at least one frame. The kind of triple buffering the Chief is talking about, which actually reduces lag, is not used anymore in games. It was last used about 15 years ago or so. These days, triple buffering means just one more render-ahead buffer compared to double buffering.mello wrote:Chief Blur Buster wrote:And what about triple buffering ? How does it affect input lag in the best case scenario (VSYNC ON) that you just desribed ?