To start, as my OP showed, there doesn't appear to be any benefit to G-Sync + v-sync off + fps limit over G-Sync + v-sync on + fps limit, at least if you're looking for a 100% tear-free experience.MT_ wrote:So 55fps in game cap with V-sync off is still showing some occasional tears on the bottom of screen and once in a while somewhere in the middle.
Is that a guideline that I should probably even go lower if I want V-sync on with no latency? I feel there are random times where input latency differ still, I guess this happens when the tear would occur in the middle of the screen when Vsync is off.
The in-game cap just fluctuates a lot, especially when assets are being loaded or the engine stalls.
Seems 54~fps is much safer.
With G-Sync + v-sync off, you're going to get tearing, period. That, and you have to lower the fps limiter a considerable amount more, just to have less (bottom) tearing, when compared to G-Sync + v-sync on, which only needs 2-3 frames below the display's refresh rate limit to avoid v-sync-level input latency, and it's tear-free.
As for frametime spikes during asset loads (etc), that's unavoidable with virtually any configuration. I also don't see how a lower fps limit would help in these situations, as the framerate is lowering, not raising during these spikes.
That said, while no syncing method (or lack thereof) is immune to frametime spikes, I assume certain methods allow the framerate/frametime delivery to recover from these instances more quickly.
So yes, it's possible in certain instances, that the frametime compensation G-Sync implements during frametime spikes (to avoid tearing) could cause slower recovery after a frametime spike when compared to G-Sync + v-sync off, or standalone v-sync off.
