AHowes

bdogg454
I will check this when i get home. when destiny 2 first came out, everything was butter. No tearing, ran perfect, It still runs great now, but some minor vertical tearing started showing up here in the past few days or so. 
 
I have v-sync on and using a G-sync monitor, so no tearing should be present.

You sure you should have v-sync also on when using g-sync?

V-sync attempts to sync your monitor's graphics card with the current refresh rate of the monitor. This means it would try to update the frame every 0.00694 seconds, or 7 ms, instead of when the graphics card is finished rendering. This causes input lag, and if you're running much lower than the monitor's refresh rate, stuttering.

If you are using a GeForce card with G-SYNC it literally makes V-Sync pointless, there's no reason to have it on so long as you're using G-Sync, as G-Sync does V-sync's job but better. It makes the panel update *as soon* as the card has a new frame, not when the monitor refreshes. This eliminates screen tearing entirely, which is the only reason V-Sync exists, and (most of the time) stuttering.

You want VSYNC set to OFF if you are going to be using GSync, period. There's no reason to use both at the same time.

Optimal G-SYNC Settings*

• Set up G-SYNC > Enable G-SYNC > Enable G-SYNC for full screen mode.
• Manage 3D settings > Vertical sync > On.

• Use “Fullscreen” or “Exclusive Fullscreen” mode (some games do not offer this option, or label borderless windowed as fullscreen).
• Disable all available “Vertical Sync,” “V-SYNC” and “Triple Buffering” options.
• If an in-game or config file FPS limiter is available, and framerate exceeds refresh rate:
  Set 3 FPS limit below display’s maximum refresh rate (57 FPS @60Hz, 97 FPS @100Hz, 117 FPS @120Hz, 141 FPS @144Hz, etc).

• If an in-game or config file FPS limiter is not available and framerate exceeds refresh rate:
  Set 3 FPS limit below display’s maximum refresh rate (see G-SYNC 101: External FPS Limiters HOWTO).

Snipes7
It has been discovered that applications polling gpu-power via nvapi are causing an overall delay visible as stuttering. Those applications include EVGA XOC among others (AIDA64, HWinfo, GPU-Z, MSI-A, etc.).
 
For those of you that are affected, the simple solution for now is to disable monitoring of the gpu power reading. This is where it's located in XOC:
 

 
Hope it helps!

squall-leonhart

HeavyHemi

Snipes7
It has been discovered that applications polling gpu-power via nvapi are causing an overall delay visible as stuttering. Those applications include EVGA XOC among others (AIDA64, HWinfo, GPU-Z, MSI-A, etc.).
 
For those of you that are affected, the simple solution for now is to disable monitoring of the gpu power reading. This is where it's located in XOC:
 

 
Hope it helps!

It has been discovered...may we inquire who made this discovery?

Me
 
(jks)
 
a guy on a forum somewhere we both used to frequent.
But its been confirmed by multiple people, myself included and accepted as a bug by ManualG.

HeavyHemi

squall-leonhart

HeavyHemi

Snipes7
It has been discovered that applications polling gpu-power via nvapi are causing an overall delay visible as stuttering. Those applications include EVGA XOC among others (AIDA64, HWinfo, GPU-Z, MSI-A, etc.).
 
For those of you that are affected, the simple solution for now is to disable monitoring of the gpu power reading. This is where it's located in XOC:
 

 
Hope it helps!

It has been discovered...may we inquire who made this discovery?

Me
 
(jks)
 
a guy on a forum somewhere we both used to frequent.
But its been confirmed by multiple people, myself included and accepted as a bug by ManualG.

Or maybe it's this?
 
http://steamcommunity.com...details/?id=1186784066

AHowes

cloiselle1
Yeah. It’s nothing to do with a bad instillation you guys really need to get past that.

Ddu doesn’t fix issues deeply embedded within the driver and it’s not actually a solution for anything. It’s just a feel good method for noobs to think they fixed something. 😂

Ain't got nothing to do with fixing crap it's just about making sure nothing is left over from prior drivers to eliminate that potential issue is all.

If someone is stating there issue is the same brought on from known past drivers then doh.. make sure that crap is wiped clean before install a new set.

un4givn85

Gawg36

Snipes7
Well I leave the nvidia settings at default which is "let the application decide". And in-game if there is no limiter I turn on v-sync, if there is a limiter you can turn v-sync off in the game. So I don't have to deal with v-sync when running benchmarks like 3DMark.
 
When paired with a G-sync enabled monitor V-sync (even if enabled) is only engaged after the fps exceed the maximum refresh rate of the monitor and works as a frame cap to prevent tearing from happening.
But this is also when you are faced with the higher latency introduced by V-sync. In order not to be faced with the drawback of V-sync like the increased latency you preferably want to cap the framerate slightly below the max monitor refresh rate.
 
Just beware, using a third-party tool for frame capping like nvidia inspector etc. will not achieve the same low latency as an in-game option or config file mod would. So an in-game approach for capping the frame rate is the way to go.
 
Here is an in-depth analysis of the different options:
 FPS Limiter Lag Analysis For G-Sync & V-Sync

And SAIJIN wrote:
 -------------------------------------------------------------------------------

Optimal G-SYNC Settings*

*Settings tested with a single G-SYNC display on a single desktop GPU system; specific DSR, SLI, and multi-monitor behaviors, as well as laptop G-SYNC implementation, may vary.
Nvidia Control Panel Settings:

• Set up G-SYNC > Enable G-SYNC > Enable G-SYNC for full screen mode.
• Manage 3D settings > Vertical sync > On.

In-game Settings:

• Use “Fullscreen” or “Exclusive Fullscreen” mode (some games do not offer this option, or label borderless windowed as fullscreen).
• Disable all available “Vertical Sync,” “V-SYNC” and “Triple Buffering” options.
• If an in-game or config file FPS limiter is available, and framerate exceeds refresh rate:
  Set 3 FPS limit below display’s maximum refresh rate (57 FPS @60Hz, 97 FPS @100Hz, 117 FPS @120Hz, 141 FPS @144Hz, etc).
• -----------------------------------------------------------------------------

 
I am so glad people with a bit of "forum clout," have posted this. I've known it for years, but been flamed to death on another nameless forum (which I left) for posting this.
 
Here is a brief history why the lack of understanding exists. (although a lot of it is just people assuming they know without validating it.)
 
So, when G-Sync first came out (it was full screen only) Nvdia clearly stated what Saijin said, and explained in a similar way to Snipes 7. On a g-sync monitor for the majority of games the only purpose of V-Sync is to prevent going over the refresh, say 144Hz. Below that it does nothing. And contrary to popular opinion G-Sync and V-Sync on in NVCP, V-Sync off in game.
Just repeating the above posts.
 
The poo really hit the fan when a very small amount of games (Doom 4 is the main one) require everything to be left at application controlled, only G-Sync full screen should be enabled. This first happened way before Doom 4 release but it's the best example I can think of.
 
Anyway, NV chickened out and pulled down the page which clearly said all this due to all the people messing up, flaming etc. It's no longer prominent (last time I checked).
So everyone did what they thought should be done, then argued viciously about it. Nvdia (stupidly) never cleared it up with an easy to find instruction/article etc for best G-Sync settings on the vast majority of games. The handful of games that this rule doesn't apply to often have a few setting in Bold on the NVCP. If not anyone with a pair of functional eyes will realize something is wrong and adjust as appropriate.
 
So I think NV get most of the blame here, but even if they were clear about it there are a few kids who think they know best.
 
G-Sync is something I really appreciate, and with the wrong V-Sync settings it will still give benefits in many cases. But not to the full. The settings are simple and the two posts above lay this out as clear as can be. Thank you gents!

So what is the purpose of having v-sync on at all if you use a frame limiter?
I have been using the built in frame limiter in RTSS since I first got my G-Sync screen, with v-sync off. Never had any issues. And I limit it to 143fps (144hz screen), also never had issues, why the 3fps buffer?

mhijazi
Hello,
 
I think there will be stuttering if the app is running. I tested with GTA V and Unigine Superposition benchmark. If OSD is on , it will stutter, if OSD is on and without power reading it will not sutter. If you turn off OSD , it will stutter. I don't think it is related to this specific driver. It was happening at least 3-4 previous drivers as well.
 
Edit: It will stutter regardless if I turn off power reading or not. I just doesn't like the application running in the background. when the application is off, it runs smooth. There will be this occasional stutter in a scene or two. I am really sure if this happened before with previous versions. I run on the latest drivers 388.43.
 
I also have this annoying micro stuttering while playing games, for instance BF 1, FPS averages 80+ most of the time but every now and then I get this 20-30 FPS dip for less than a second . I really don't know what might be the reason. It's happened with 980 Ti's and it is still happening with 1070 SC's.
 
Not sure if it is related to SLI ?!