Just to be clear, readers, as this can all get confusing pretty quickly.
For the GSYNC
enabled cases, if framerates permanently stay below the max Hz (60fps @ 240Hz), it's very hard for even an inaccurate cap to cause brief fluctuations of framerates all the way to 240fps necessary to trigger VSYNC ON or VSYNC OFF activating.
Those modes (
when GSYNC enabled) only applies when framerates hit GSYNC max-Hz.
If GSYNC
enabled,
-- Anything below 240fps, frames are given the GSYNC treatment.
-- Anything maxed-out 240fps, frames are given the VSYNC ON or VSYNC OFF treatment.
Framerates can fluctuates from a frame-per-frame basis. Caps pretty close to GSYNC, e.g. 239fps at 240Hz, there can still be small fluctuations near the cap. So there are still odds of random frametimes like 1/237sec and 1/241sec. One frame gets the full GSYNC treatment (no-delay refresh-cycle starts). The other frame gets the VSYNC OFF treatment (interrupts the currently scanning-out frame = tearline) or VSYNC ON treatment (a forced wait = input lag)
But a framerate cap of 60fps on a 240Hz GSYNC display? At that point, VSYNC ON versus VSYNC OFF doesn't matter if GSYNC is enabled,
repeating, GSYNC is
enabled. It's such a large capping margin.