Who you gonna call? The Blur Busters! For Everything Better Than 60Hz™
https://forums.blurbusters.com/
If you use G-SYNC with 360Hz, use a 355fps cap with the Overwatch in-game capping feature.Periphery_OW wrote: ↑23 Nov 2020, 15:42I'm curious on anyone else's opinion that has gotten a 360hz. which configuration do you prefer? (Overwatch player here). Motion is clearer with G sync however there is definitely a slightly "muddier" feeling to my click inputs compared to 400fps uncapped which in turn feels a bit "twitchier". I'm torn on which configuration to use.
I recently discovered some newly Nvidia Reflex enabled games that I play (Destiny2, Apex Legends) force an auto cap to 225 on 240hz when you activate Vsync (Game or NCP) with Gsync. I presume its the NCP frame limiter capping alongside Gsync but there is no way to stop it other than don't turn on Vsync.Chief Blur Buster wrote: ↑24 Nov 2020, 23:15If you use G-SYNC with 360Hz, use a 355fps cap with the Overwatch in-game capping feature.Periphery_OW wrote: ↑23 Nov 2020, 15:42I'm curious on anyone else's opinion that has gotten a 360hz. which configuration do you prefer? (Overwatch player here). Motion is clearer with G sync however there is definitely a slightly "muddier" feeling to my click inputs compared to 400fps uncapped which in turn feels a bit "twitchier". I'm torn on which configuration to use.
The muddy feeling will diminish greatly.
The problem is when a game tries to exceed the framerates of max Hz in G-SYNC, there's a sudden increase in input lag as the monitor switches to VSYNC ON operation.
For 360Hz, a 5fps-below margin is recommended. The latency difference between 355fps and 400fps is negligible in the worst case scenario -- a mere 317 microseconds difference from the math of (1/355)-(1/400) -- but you also avoid the approximately few-millisecond latency increase effects of an uncapped G-SYNC framerate trying to exceed G-SYNC max Hz.
You can use G-SYNC + VSYNC OFF, but regardless, use an approx 355fps cap to keep framerates ranges completely inside G-SYNC ranges for more consistent feel.
The other move is to completely disable G-SYNC so that VSYNC OFF feels more consistent through the entire framerate range; but obviously one prefers to try to optimize G-SYNC as much as possible.
I discovered the same yesterday when I was playing with some settings in Valorant.TTT wrote: ↑25 Nov 2020, 04:00I recently discovered some newly Nvidia Reflex enabled games that I play (Destiny2, Apex Legends) force an auto cap to 225 on 240hz when you activate Vsync (Game or NCP) with Gsync. I presume its the NCP frame limiter capping alongside Gsync but there is no way to stop it other than don't turn on Vsync.
If this stays the case the only way to limit closer to the max hz is not use Vsync at all alongside Gsync. (Just Wondering if you were aware of this.)
Its an auto driver cap when using Gsync+Vsync to stop you hitting the Vsync latency wall if you exceed your refresh.Neblinio wrote: ↑27 Nov 2020, 23:30I discovered the same yesterday when I was playing with some settings in Valorant.TTT wrote: ↑25 Nov 2020, 04:00I recently discovered some newly Nvidia Reflex enabled games that I play (Destiny2, Apex Legends) force an auto cap to 225 on 240hz when you activate Vsync (Game or NCP) with Gsync. I presume its the NCP frame limiter capping alongside Gsync but there is no way to stop it other than don't turn on Vsync.
If this stays the case the only way to limit closer to the max hz is not use Vsync at all alongside Gsync. (Just Wondering if you were aware of this.)
I have a Ryzen 3600 + GTX 1660 Ti + AOC G2590PX (144 Hz gsync compatible).
So, with Reflex "on", vsync off, and fullscreen 1920x1080 video mode, I entered "The Range" practice map, and found a place where I usually would have about 260 FPS (I cap to 141 FPS via in-game limiter). In this spot, my "game latency" (according to Valorant's built in metric) is about 11ms @141 FPS.
When I enabled vsync (doesn't matter if in-game or nvcp), my FPS were automatically capped to 138 and my "game latency" metric went down to 6ms.
I really don't understand what happened here. At 141 FPS in a spot where my system can reach 260, I shouldn't be GPU bound at all. So why is my 11ms "game latency" being reduced to 6ms when I enable Reflex?
Am I understanding something wrong? What kind of metric is this "game latency"?
I totally understand both options. I did find that even at 355 fps cap, it seems like I manage to spike to 360hz so with that (in part with my OCD) I settled with 350 fps to be safe. I think I've settled with 350 fps cap in game, g sync on, v sync on in game. I'm running a pretty beefy system (9900k 5.1, 3700mzh cl14 32g w/ a 3080 plus windows and latency tweaks) and hitting the 400 fps cap with extreme consistence. As you said, the clarity you get from g sync still outweighs the 317 microseconds difference, especially when I remind myself that Overwatch only runs a 60hz tickrate.Chief Blur Buster wrote: ↑24 Nov 2020, 23:15If you use G-SYNC with 360Hz, use a 355fps cap with the Overwatch in-game capping feature.Periphery_OW wrote: ↑23 Nov 2020, 15:42I'm curious on anyone else's opinion that has gotten a 360hz. which configuration do you prefer? (Overwatch player here). Motion is clearer with G sync however there is definitely a slightly "muddier" feeling to my click inputs compared to 400fps uncapped which in turn feels a bit "twitchier". I'm torn on which configuration to use.
The muddy feeling will diminish greatly.
The problem is when a game tries to exceed the framerates of max Hz in G-SYNC, there's a sudden increase in input lag as the monitor switches to VSYNC ON operation.
For 360Hz, a 5fps-below margin is recommended. The latency difference between 355fps and 400fps is negligible in the worst case scenario -- a mere 317 microseconds difference from the math of (1/355)-(1/400) -- but you also avoid the approximately few-millisecond latency increase effects of an uncapped G-SYNC framerate trying to exceed G-SYNC max Hz.
You can use G-SYNC + VSYNC OFF, but regardless, use an approx 355fps cap to keep framerates ranges completely inside G-SYNC ranges for more consistent feel.
The other move is to completely disable G-SYNC so that VSYNC OFF feels more consistent through the entire framerate range; but obviously one prefers to try to optimize G-SYNC as much as possible.
While I have you, I am remaining 100% cpu bound here. I have noticed through the new nvidia performance monitoring that having reduce buffering on brings my render latency from 2-3ms to less than 1ms. Traditionally, reduce buffering is used only when running fps beyond your refresh rate as far as I understand. Which would you use in my use case?Chief Blur Buster wrote: ↑24 Nov 2020, 23:15If you use G-SYNC with 360Hz, use a 355fps cap with the Overwatch in-game capping feature.Periphery_OW wrote: ↑23 Nov 2020, 15:42I'm curious on anyone else's opinion that has gotten a 360hz. which configuration do you prefer? (Overwatch player here). Motion is clearer with G sync however there is definitely a slightly "muddier" feeling to my click inputs compared to 400fps uncapped which in turn feels a bit "twitchier". I'm torn on which configuration to use.
The muddy feeling will diminish greatly.
The problem is when a game tries to exceed the framerates of max Hz in G-SYNC, there's a sudden increase in input lag as the monitor switches to VSYNC ON operation.
For 360Hz, a 5fps-below margin is recommended. The latency difference between 355fps and 400fps is negligible in the worst case scenario -- a mere 317 microseconds difference from the math of (1/355)-(1/400) -- but you also avoid the approximately few-millisecond latency increase effects of an uncapped G-SYNC framerate trying to exceed G-SYNC max Hz.
You can use G-SYNC + VSYNC OFF, but regardless, use an approx 355fps cap to keep framerates ranges completely inside G-SYNC ranges for more consistent feel.
The other move is to completely disable G-SYNC so that VSYNC OFF feels more consistent through the entire framerate range; but obviously one prefers to try to optimize G-SYNC as much as possible.
