-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Gsync but still have tearing cs:go
- Thread starter geordiejc
- Start date
Seems to be a problem with more recent drivers since the introduction of FastSync. If you have V-Sync off, G-Sync on and a framerate cap depending how the framerate cap is implemented you can end up with some frames generated very fast and rendering outside the G-Sync window despite the average frames being capped to within the G-Sync window. (not sure why this didn't exhibit itself on pre-FastSync drivers).
Enabling FastSync can solve this but can result in occasional stutter and higher input lag than V-Sync off.
Enabling FastSync can solve this but can result in occasional stutter and higher input lag than V-Sync off.
Soldato
- Joined
- 25 Nov 2011
- Posts
- 20,679
- Location
- The KOP
Instead just deleting messages why not put how you fixed it? Someone else might find it interesting.
he probably had tearing because of vsync on, and as rrof said fastsync should solve it
Soldato
- Joined
- 25 Nov 2011
- Posts
- 20,679
- Location
- The KOP
That makes no sense? Vsync Removes screen tearing.
lol not when you have g-sync monitor...
Soldato
- Joined
- 25 Nov 2011
- Posts
- 20,679
- Location
- The KOP
It doesn't change anything, vsync will keep Gsync within refresh rate of the monitor.
Vsync + Gsync is the recommended setup for Gsync. All Gsync does is removes the downside of vsync input lag and frame stutter.
Soldato
- Joined
- 25 Nov 2011
- Posts
- 20,679
- Location
- The KOP
from experience ill say just that you are wrong
Then explain too me why Gsync released with Vsync forced On?
It's only recently that Nvidia allowed the user to disable vsync...
Nvidia themselves have stated the correct way for Gsync is with Vsync.. So is Nvidia wrong?
Vsync on in the NCP and GSync is the best way for GSync to do its thing. You are correct. Just make sure you have VSync off in game.
from experience ill say just that you are wrong
He is correct!
vsync removes stutter but creates tearing and latency, thats the trade off.
isn't vsync automatically disabled when running Gsync ( within supported refresh rate ) ?
Soldato
- Joined
- 25 Nov 2011
- Posts
- 20,679
- Location
- The KOP
Am not sure you understand the biggest reason why we have Gsync and freesync but if you want to believe that then fine
Thanks Greg
VSync (on) removes tearing and increases latency. It may also induce stutter if you are jumping between different refresh rates.
As I understand it, having VSync enabled in NVCP prevents the frame rate exceeding the monitor's refresh rate (144hz), which prevents possible tearing (I have seen this with VSync disabled). I`ve read this can cause input lag, but I haven't noticed any problem (probably because my input lag is a lot worse
).i had solved the issue prior to anyone replying and it wasnt a gsync issue hence reason i edited the first post.
This video is the best for understanding how gsync works with input latency,
anyone playing cs:go should either disable gsync and fps_max 0 OR if you want to use gsync, enable gsync, vsync off (NVCP) and fps_max 142.
gsync works best if you can use an ingame fps limiter with vsync off
most games gsync on + vsync on prevents the card rendering un-used frames and adds input lag, like 20ms and ofc the gsync benefit itself (synchronised frames)
This video is the best for understanding how gsync works with input latency,
anyone playing cs:go should either disable gsync and fps_max 0 OR if you want to use gsync, enable gsync, vsync off (NVCP) and fps_max 142.
gsync works best if you can use an ingame fps limiter with vsync off
most games gsync on + vsync on prevents the card rendering un-used frames and adds input lag, like 20ms and ofc the gsync benefit itself (synchronised frames)
Last edited: