Using G-sync

Soldato
Joined
3 Dec 2012
Posts
2,858
Location
Northern Ireland
First up I have been using G-sync for almost 2 years so I understand the concept (I think). However I recently upgraded from a 970 to a 1080 and can now run most of my games around 144fps which I wasn't really able to do before without turning the settings down significantly - I have an Acer XB270HU. One thing I have noticed lately (I've been playing Far Cry 4 steady for the last couple of weeks) is that I am still getting tearing at or above 144fps - I can't say I have noticed this too much in other titles however GTA V would be doing well to hit the ceiling anyway and my others are entirely racing games.
What is the best way to avoid tearing above the ceiling? I have read varying opinions from enabling V-sync in-game, enabling it in the NCP, enabling fast sync to enabling triple buffering.
Is there a hard and fast rule or does it differ from game to game? Given the choice between tearing and any micro stutter caused by a v-sync implementation I'd rather have the tearing but is there a way out of it above 144fps/hz?
 
Download MSI afterburner and that also installs rivastatistics. Use the riva program to limit your FPS to 143 and enjoy your high and silky smooth gaming
 
Gsync doesn't work over your monitor refresh rate.

Don't enable Vsync anywhere, fast sync is also only for when you are pushing 2-3x fps than your screen can display.

Do what he said ^ and just limit your fps, or if you are getting solid frames above 144hz just turn Gsync off.
 
Thanks for all that. I tried the Rivastatistics thing but it seemed to just make things worse. I am pretty sure Far Cry is just poorly optimised - even though it's an 'Nvidia' game. Loads of threads about enabling the proprietary Nvidia Ambient Occlusion and AA where the game just becomes a stuttering mess, mine was the same. I don't seem to have any major issues with my other games at present.
 
some games get stutter with fps limiters. i just use vsync set in the cp, works great. haven't played any games which felt laggy at the cap.
 
Depending on how the framerate limiter works you might find that individually there are cases where the gap between one frame and the next is so short you get tearing despite the average framerate over the sample size (1 second) being clamped by the limiter - in some cases it might enforce the minimum frametime between frames to prevent this but then you can run into rounding errors, etc. which result in the odd frame tearing and other complexities so you need to clamp framerate a bit below the target refresh rate so as to never see tearing i.e. 135fps is a popular one for 144Hz panels when using G-Sync with V-Sync off and a framerate limiter.

Also note that the V-Sync option in the nVidia control panel will change how it works when G-Sync is enabled - enabling V-Sync On or Fast will work to prevent the framerate exceeding the max refresh rate while still using G-Sync behaviour at framerates below - the Fast option additionally allows you to reduce latency by rendering faster than the refresh rate in the background and then using the closest appropriate complete frame available but can result in stutter.

Make sure that any V-Sync option ingame is disabled as this can complicate things due to some games having their own additional functionality connected to that setting, etc.
 
In this comparison, you can still see some tearing on the G-Sync monitor on the left. Is that normal for G-Sync?


If you have it all set up properly there should be 0 tearing and it should be smooth. The tearing is something the tester has set up, not an issue with the monitor

That monitor has a factory overclock built in to 165hz though as well.

Thats the reason I bought a gsync 240hz, just max your game and let it run free, on most games I'm not going to go anywhere near the cap so I don't need to limit fps or do anything. Also it's one of the cheapest gsync monitors at the moment if you get it on offer!
 
Back
Top Bottom