372.70 + Gsync

[Dirk Diggler]

System:

5930k
980ti SLI
X34a

Since updating to the latest Nvidia driver (372.70) I see that the default setting for Vsync in the NCP is "Application controlled" and fps hits the hundreds in games whereas before, it was always set to "On" and fps would cap at my monitor refresh rate (99fps).

Why the change?
Do I leave it at default with the high frame rates?
Is Gsync working at higher frame rates?

Totally confused.

 

[Five.Stars]

Pretty sure it wont be working above the refresh rate, although at 100+ fps tearing is more difficult to spot. I switch vsync off on an application basis usually and use rivatuner to cap at 144fps. I am unsure if this is the "right" way of doing things, and tbh Nvidia aren't really helping with their constant tweaking of the behaviour of gsync.

I still don't like gsync being 'active' all the time. Using my ROG Swift the LED would usually be white, and would change to red in-game to signify gsync was active and working. Now it is red all the time, so I need to look out for signs that gsync is possibly not working. Annoying.

 

[RichardH754]

I have noticed this too, I now enable it in game v-sync

 

[Dirk Diggler]

I was getting judder and screen tearing when I capped at 99fps which is 1fps below monitor refresh, so Gsync was definitely disabled even though my monitor LEDs indicated that it was enabled. I've uninstalled and went back to 365.10 and it's all working fine again.

Nvidia have been failing miserably with drivers for a while now. It's getting to the stage where I'm apprehensive about switching from 365.10 at all, and that's also putting me off buying any new titles because at best there won't be an SLI profile and at worst the game will CTD or refuse to load (BF1) if I haven't upgraded to the "game ready" driver.

Given the cost of the cards and the Gsync monitors you'd think they could put some decent effort into the software. People who aren't aware of the idiosyncrasies will be inadvertently putting up with second rate performance for a top dollar layout.

 

[Dicehunter]

Just set either V-Sync to on or Fast-Sync to on, Once the frames go beyond your monitors refresh rate G-Sync will not be working.

 

[Dirk Diggler]

Just set either V-Sync to on or Fast-Sync to on, Once the frames go beyond your monitors refresh rate G-Sync will not be working.

I didn't have the option for fastsync, and as mentioned above when I tested it, it turns out Gsync wasn't working below refresh rate let alone above it.

 

[BluD]

I switch it to on then cap the FPS like before so it never actually uses vsync but gsync seems to work fine still.

 

[Dicehunter]

I didn't have the option for fastsync, and as mentioned above when I tested it, it turns out Gsync wasn't working below refresh rate let alone above it.

Maybe it's an issue with SLI ?

I'm running 1 x 980 Ti and if I switch the G-Sync indicator overlay on through Nvidia Inspector it shows just fine.

 

[Dirk Diggler]

I switch it to on then cap the FPS like before so it never actually uses vsync but gsync seems to work fine still.

I used to do the cap, but I'm pretty sure Gsync does the cap for you in 365.10 driver because my fps is always 99 but my refresh is 100. So I leave the NCP at default which is Vsync "on" and disable Vsync in-game. The result is silky smooth, which is why I noticed the new driver had messed it all up.

 

[Dirk Diggler]

Maybe it's an issue with SLI ?

I'm running 1 x 980 Ti and if I switch the G-Sync indicator overlay on through Nvidia Inspector it shows just fine.

Could be mate. I know it took them an age to get SLI+ Gsync+DSR working properly.

I'm back on the older driver now and all is good, so I'll keep an eye on the driver thread and see if Nvidia can code a decent one in the near future.

 

[wunkley]

I had trouble with the latest few driver releases String too (980ti SLI and x34). Gsync was definitely bust in a few games I tried.

I'm using 368.39 now and they seem to be fine. As long as no games I get *need* a new driver I'm only going to update with caution from now. Nvidia seem to go through phases of really bad releases, and I think this is another one of those times.

 

[Rroff]

G-Sync has been problematic (sometimes in small ways that are hard to notice) in the last few drivers if you are paying attention and/or notice the input latency and framerate behaviour you'll notice in quite a few games it is behaving like old V-Sync and/or will drop out either entirely or in places back to V-Sync behaviour.

I had to put DX:MD into V-Sync off (while using G-Sync) and cap framerate rather than using FastSync or V-Sync on or otherwise it was behaving like 60Hz V-Sync and despite rendering upwards of 60fps still had the heavy input latency feel of 60Hz V-Sync :|

 

[hyperseven]

G-Sync has been problematic (sometimes in small ways that are hard to notice) in the last few drivers if you are paying attention and/or notice the input latency and framerate behaviour you'll notice in quite a few games it is behaving like old V-Sync and/or will drop out either entirely or in places back to V-Sync behaviour.

I had to put DX:MD into V-Sync off (while using G-Sync) and cap framerate rather than using FastSync or V-Sync on or otherwise it was behaving like 60Hz V-Sync and despite rendering upwards of 60fps still had the heavy input latency feel of 60Hz V-Sync :|

, playing Deus ex, overwatch and bf1, not noticing any issues.

 

[Dirk Diggler]

I had trouble with the latest few driver releases String too (980ti SLI and x34). Gsync was definitely bust in a few games I tried.

I'm using 368.39 now and they seem to be fine. As long as no games I get *need* a new driver I'm only going to update with caution from now. Nvidia seem to go through phases of really bad releases, and I think this is another one of those times.

Using Nvidia inspector, would it be possible to extract the SLI bits from the latest driver and import into an older driver?

 

[Rroff]

, playing Deus ex, overwatch and bf1, not noticing any issues.

Doesn't seem to be affecting everyone/everyone the same and in some cases can be really hard to notice i.e. you might catch some screen tearing briefly once every 5 minutes and its working the rest of the time, etc.

 

[wunkley]

Using Nvidia inspector, would it be possible to extract the SLI bits from the latest driver and import into an older driver?

I think so aye. I've not done it for a while but have tried that trick with some success in the past though my memory of how and why is a bit sketchy.

 

[Five.Stars]

G-Sync has been problematic (sometimes in small ways that are hard to notice) in the last few drivers if you are paying attention and/or notice the input latency and framerate behaviour you'll notice in quite a few games it is behaving like old V-Sync and/or will drop out either entirely or in places back to V-Sync behaviour.

I had to put DX:MD into V-Sync off (while using G-Sync) and cap framerate rather than using FastSync or V-Sync on or otherwise it was behaving like 60Hz V-Sync and despite rendering upwards of 60fps still had the heavy input latency feel of 60Hz V-Sync :|

I have noticed some mild tearing in Battlefront, mostly when in the aerial vehicles.

I think they have tried to do too much with Gsync and instead of perfecting what was a fantastic tech, they have ended up breaking it in certain ways. The lack of visual indication now is very annoying, for example.

 

[wunkley]

I have noticed some mild tearing in Battlefront, mostly when in the aerial vehicles.

I think they have tried to do too much with Gsync and instead of perfecting what was a fantastic tech, they have ended up breaking it in certain ways. The lack of visual indication now is very annoying, for example.

Agreed. Annoys me how nvidia can basically **** up essential functions that have been working fine (like Gsync) with a simple driver update. Very very poor geek work by the Nvidia peeps at the moment.

HOWEVER - YOU CAN HAVE A VISUAL GSYNC INDICATOR Not many people know about this....

I've reverted to making sure Gsync is 'ON' by using the setting in the NV control panel...

It's really not obvious, but you need to launch the NVCP and click:

- Display setting on the left
- click on "set up GSYNC"
- then on the top menu nav click on "Display" and select "GSYNC indicator" (the top nav menu is context sensitive depending on what you select on the left!)

Doing this places an opaque "GSYNC" OSD 'tab' about 1/3 down from the top left of your monitor when running games *IF GSYNC IS RUNNING* properly. Also, as a kind of backup and extra thing - if you like to run your games in fullscreen like me make sure that in gsync settings you have "enable gsync for full screen mode" clicked. Then you know you're in proper fullscreen mode AND gsync is running. Full screen is always the best anyway, especially if running SLI.

On my X34 monitor I find this the only way to be sure now. The red light LED function along the monitor underside that's supposed to be a Gsync indicator if you select "MNT STATUS" in the monitor osd just does not work (It's always red now, which must be a driver fault!) and cannot be relied upon to show if gsync is properly active.

 

[Dirk Diggler]

Wunkley, you never fail with these things!

Do you leave Gsync to cap the frame rate, or do you cap a couple of FPS below the 100?

 

[Rroff]

I usually use fastsync now - with a few games configured with V-Sync off and where possible framerate capped ingame as this seems to produce the lowest latency after V-Sync off uncapped while not tearing.