Gloomy
Golden Member
- Oct 12, 2010
- 1,469
- 21
- 81
GSync's current behavior as it gets close to the monitor's refresh rate is worse:
http://www.blurbusters.com/gsync/preview2/
At the very least FSync will let you turn VSync off and suffer tearing or if you choose you can rely on a frame rate limiter. GSync just goes bananas
There's also the question of what people actually expected either technology to do once it hit the monitor's limit. It's not like they can overclock the monitor and get more Hz.
Why is there less lag in CS:GO at 120fps than 143fps for G-SYNC?
We currently suspect that fps_max 143 is frequently colliding near the G-SYNC frame rate cap, possibly having something to do with NVIDIA’s technique in polling the monitor whether the monitor is ready for the next refresh. I did hear they are working on eliminating polling behavior, so that eventually G-SYNC frames can begin delivering immediately upon monitor readiness, even if it means simply waiting a fraction of a millisecond in situations where the monitor is nearly finished with its previous refresh.
I did not test other fps_max settings such as fps_max 130, fps_max 140, which might get closer to the G-SYNC cap without triggering the G-SYNC capped-out slow down behavior. Normally, G-SYNC eliminates waiting for the monitor’s next refresh interval:
G-SYNC Not Capped Out:
Input Read -> Render Frame -> Display Refresh Immediately
When G-SYNC is capped out at maximum refresh rate, the behavior is identical to VSYNC ON, where the game ends up waiting for the refresh.
G-SYNC Capped Out
Input Read -> Render Frame -> Wait For Monitor Refresh Cycle -> Display Refresh
http://www.blurbusters.com/gsync/preview2/
At the very least FSync will let you turn VSync off and suffer tearing or if you choose you can rely on a frame rate limiter. GSync just goes bananas
There's also the question of what people actually expected either technology to do once it hit the monitor's limit. It's not like they can overclock the monitor and get more Hz.
