kotuster wrote: ↑08 Jan 2020, 08:41
I've seen the interesting test's blur busters did on G-Sync + V-Sync. I don't really get why I'd want to turn on V-Sync in the fist place though. So far I have seen literally 0 screen tearing (mb I missed it, but it's minor either way) with only G-Sync enabled.
Regarding G-SYNC + V-SYNC, read entry #2 here:
https://www.blurbusters.com/gsync/gsync ... ttings/15/
G-SYNC only works
within the refresh rate; any time your FPS exceeds the refresh rate with G-SYNC on + V-SYNC off, G-SYNC isn't doing anything. That said, the higher the refresh rate, the harder it is to see tearing, as the opportunity to tear becomes less and less as the max refresh rate increases:
https://www.blurbusters.com/gsync/gsync ... ettings/6/
kotuster wrote: ↑08 Jan 2020, 08:41
Now if I leave G-Sync on and V-Sync off, is there still a reason I would want to cap my FPS to 238? That seems to be the one comparison that is missing in all the tests
Yes, to keep G-SYNC within it's range, and not revert to standalone V-SYNC OFF. This is covered here:
https://www.blurbusters.com/gsync/gsync ... ettings/2/
kotuster wrote: ↑08 Jan 2020, 08:41
I guess whenever my FPS go above 240 I'll get slightly lower input lag in that non-capped scenario, right? Will that result in more screen tearing every time the FPS go above 240, too, since G-Sync is turned off? I guess I won't need NULL or anything similar either way, probably just G-Sync and the 238 cap or no cap.
At 240Hz,
slightly lower input lag at much higher than refresh rate framerates (see:
https://www.blurbusters.com/wp-content/ ... -240Hz.png), so long as the increased framerate doesn't max out your GPU usage, at which point you'll get GPU input lag from a sustained increase in the pre-rendered frames queue.
As for more screen tearing, no, the higher the framerate above your refresh rate, the "smaller" the individual tears will be.