afaik gsync needs vsync enabled but only though the nvcp and not in games to work properlyI thought gsync was vsync anyway of sorts, thought the whole ideal of gsnyc was to stop the tearing, games without vsync enabled look bad to me.
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.
afaik gsync needs vsync enabled but only though the nvcp and not in games to work properlyI thought gsync was vsync anyway of sorts, thought the whole ideal of gsnyc was to stop the tearing, games without vsync enabled look bad to me.
That's the idea, you cap fps just below refresh rate. Never goes over or hits the refresh rate so no tearing and no vsync input lag.arent you meant to set it on anyway so gsync syncs your frames without tearing? or are you setting your fps and refresh so low it doesnt tear?
I thought gsync was vsync anyway of sorts, thought the whole ideal of gsnyc was to stop the tearing, games without vsync enabled look bad to me.
I didnt know this. So for a slow game like The Long Dark, i can set to 60fps and bask in the money saving. but for Rocket League i can crank upto 144.
Thx for that post and youtube channel info, cheersG-Sync will act like V-Sync, but without the latency and V-Sync frame rate multiplier penalties, up to the max G-Sync range frame rate which is usually the same as the monitor max refresh rate - G-Sync itself does not limit frame rates like V-Sync does. If you render faster than the G-Sync range you will get tearing unless V-Sync is enabled. In some cases it is better to cap frame rate slightly below the max G-Sync range to minimise any latency rather than use V-Sync w/ G-Sync.
nVidia did tweak how G-Sync + V-Sync work together more recently which can remove some of the potential latency issues so sometimes capping frame rate might not be necessary.
EDIT: YouTube channel Battlenonsense covers a lot of it in detail with advanced testing - some of the mainstream tech media have got the wrong end of the stick or inaccurate results on G-Sync.
Thx for link.![]()
G-SYNC 101 - Blur Busters - Page 14
G-SYNC Module The G-SYNC module is a small chip that replaces the display's standard internal scaler, and contains enough onboard memory to hold and process a single frame at a time. The module exploits the vertical blanking interval (the span between the previous and next frame scan) to...blurbusters.com
arent you meant to set it on anyway so gsync syncs your frames without tearing? or are you setting your fps and refresh so low it doesnt tear?
I thought gsync was vsync anyway of sorts, thought the whole ideal of gsnyc was to stop the tearing, games without vsync enabled look bad to me.
Actually, you need to activate both Gsync AND Vsync, and then set a framerate cap 3 or 4 fps below your monitors refresh rate.Yep I can confirm. On my 120Hz G-sync monitor I get the best results by choosing a framerate limit in the Nvidia Control Panel at 100fps (110 or 115 would also work but I like round numbers), G-sync on, V-sync off. No tearing, no extra latency, reduced coil whine.
Only need to turn the framerate limit off when setting benchmark high scores![]()
I have literally never had screen tearing with V-sync disabled, G-sync on and 100fps cap under my 120Hz monitor refresh rate. So what is the advantage of turning V-sync on?Actually, you need to activate both Gsync AND Vsync, and then set a framerate cap 3 or 4 fps below your monitors refresh rate.
Best method would be to do all of the above within game settings cause it adds less input latency, but not all games have the option to framecap, so do it from nvcp. So Gsnyc on, Vsync on, fps cap at 116 for 120hz monitors.
Only activating Gsync even with a framecap still causes tearing cause of frametime variance. You need vsync on to solve that, and since you framecaped the game you don't get any added latency from vsync
Nothing. G-sync changes your monitor's refresh rate to 70Hz when you have 70 fps, and 53 Hz when you have 53 fps.The whole G-sync thing is so damn confusing, turn v-sync on or off at the ingame settnigs?
if my monitor is set to 120hz but the gpu can only render say 70fps, what happens to the missing 50 frames
Well for a start games look so much better graphics wise with V-sync on, with it off the graphics don't look so crisp to me, very obvious to me.I have literally never had screen tearing with V-sync disabled, G-sync on and 100fps cap under my 120Hz monitor refresh rate. So what is the advantage of turning V-sync on?
The definition of adaptive sync is this:The whole G-sync thing is so damn confusing, turn v-sync on or off at the ingame settnigs?
if my monitor is set to 120hz but the gpu can only render say 70fps, what happens to the missing 50 frames
The whole G-sync thing is so damn confusing, turn v-sync on or off at the ingame settnigs?
if my monitor is set to 120hz but the gpu can only render say 70fps, what happens to the missing 50 frames
Having read the 5 year old article you linked I still cannot find a reason to complicate things by turning V-sync on with G-sync. Maybe on LCD monitors it makes things clearer. I haven't used one for a while since I found that they made everything look washed out and blurry. On OLEDs the image is perfectly sharp and smooth with the settings I described. I have never heard anywhere else that V-sync makes an image look sharper: that sounds more like the monitor was having issues or another setting was being disabled when you turned V-sync off.Check out the link I posted, don't do what Icewolf said, the link actually has the science behind it, not anecdotal evidence.
![]()
G-SYNC 101 - Blur Busters - Page 14
G-SYNC Module The G-SYNC module is a small chip that replaces the display's standard internal scaler, and contains enough onboard memory to hold and process a single frame at a time. The module exploits the vertical blanking interval (the span between the previous and next frame scan) to...blurbusters.com
Having read the 5 year old article you linked I still cannot find a reason to complicate things by turning V-sync on with G-sync. Maybe on LCD monitors it makes things clearer. I haven't used one for a while since I found that they made everything look washed out and blurry. On OLEDs the image is perfectly sharp and smooth with the settings I described. I have never heard anywhere else that V-sync makes an image look sharper: that sounds more like the monitor was having issues or another setting was being disabled when you turned V-sync off.
If you find that it helps you then by all means go ahead and enable V-sync as well, but as several people have said, what matters most is the frame cap under your max refresh rate and having G-sync enabled, both via the Nvidia Control Panel.
The answer is frametime variances.
“Frametime” denotes how long a single frame takes to render. “Framerate” is the totaled average of each frame’s render time within a one second perio
At 144Hz, a single frame takes 6.9ms to display (the number of which depends on the max refresh rate of the display, see here), so if the framerate is 144 per second, then the average frametime of 144 FPS is 6.9ms per fram
In reality, however, frametime from frame to frame varies, so just because an average framerate of 144 per second has an average frametime of 6.9ms per frame, doesn’t mean all 144 of those frames in each second amount to an exact 6.9ms per; one frame could render in 10ms, the next could render in 6ms, but at the end of each second, enough will hit the 6.9ms render target to average 144 FPS pe
So what happens when just one of those 144 frames renders in, say, 6.8ms (146 FPS average) instead of 6.9ms (144 FPS average) at 144Hz? The affected frame becomes ready too early, and begins to scan itself into the current “scanout” cycle (the process that physically draws each frame, pixel by pixel, left to right, top to bottom on-screen) before the previous frame has a chance to fully display (a.k.a. tearing
G-SYNC + V-SYNC “Off” allows these instances to occur, even within the G-SYNC range, whereas G-SYNC + V-SYNC “On” (what I call “frametime compensation” in this article) allows the module (with average framerates within the G-SYNC range) to time delivery of the affected frames to the start of the next scanout cycle, which lets the previous frame finish in the existing cycle, and thus prevents tearing in all instance
And since G-SYNC + V-SYNC “On” only holds onto the affected frames for whatever time it takes the previous frame to complete its display, virtually no input lag is added; the only input lag advantage G-SYNC + V-SYNC “Off” has over G-SYNC + V-SYNC “On” is literally the tearing seen, nothing mor
For further explanations on this subject see part 1 “Control Panel,” part 4 “Range,” and part 6 “G-SYNC vs. V-SYNC OFF w/FPS Limit” of this article, or read the excerpts below…[e.s.).r.e.d.xcerpts below…