Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by robalm, Aug 1, 2017.
these drivers make my cpu run hotter than 382 for example
Maybe its not the drivers and more linked its summer and you are running a 3,4ghz CPU to 4,4ghz
yea i've got 7700k with 1080ti now and its 62 outside
Apparently this is the way to go.
I've read several different things but according to what you all say then this is the correct setup:
G-sync (NVCPL) : Enabled for Fullscreen only
V-sync (NVCPL) : Enabled
V-sync (ingame) : Disabled (or enabled if NVCPL doesnt engage V-sync ingame)
RTSS or equivalent : Enable framerate Limiter 2fps below monitor's refresh rate
Play all games in Fullscreen mode.
So far the best driver out of all r384, stability wise, etc.. they're a little faster by dx api tests too.. gonna keep these for a while.
Tj, are you on the creators update or anniversary?
Hey, normal retail release creator update - RS2?
OK cheers, I'll give them a whirl. Fresh install, here I come.
You can't just say 2 fps, it's more like 5-10% below max refresh rate, monitor fps and adjust until hitting the sweet spot, what you want to avoid is getting any fps spikes beyond the set refresh rate.
You can do that without syncing at all, and when all set you can enable g-sync and v-sync.
As example, if your running 60Hz you want to get as close to 60fps as possible without ever going above.
Dependent on game engine this can be a fps limit up to 10% below set refresh rate, some engines manage to spike more beyond the set limit than others.
There is a discussion around the topic here: http://forums.guru3d.com/showthread.php?t=415020&page=4
This is correct.
If you have like 144/165hz you may try 3fps below refresh rate just in case.
Wonky game engine FPS limiters that are not stable could possible hit vsync ceiling.
so...I think you miss the main point, I said that having Vsync ON or OFF there is no difference due to the fact that all who know how to use properly a fps limiter will limit their fps BELOW monitor's refresh rate and will be IN gsync's range 30-144.
Ok you may say that what I wrote before was "only" for monitor IN gsync's range but ...was this the confusion about?
'cause..how many people are able to achieve more fps than gsync's range..?
Nobody missed your point.
The point is that your statement is incorrect.
You will still get tearing even in gsync range.
That's why you enable vsync and set a fps limiter together.
You should read that article so you can clearly understand how gsync works.
You should reread this main point here.
G-SYNC module compensates for frametime variances output by the system (which prevents tearing at all times. G-SYNC + V-SYNC “Off” disables this behavior; see G-SYNC 101: Range
Enough said, AA01 nailed it.
anyone on windows 7? any improvements?
I'd like to thank those of you having the whole G-sync, V-sync, & frame limiter discussion because I've not been doing it right and had tearing or lag. Will read articles and other discussions linked here and try again.
Thanks for the link, I'll check it out.
It's another topic but I still wonder why some games don't give a rat's ass about forced Vsync through NVCPL. Must be something in their specific engine I guess.
Just in this driver where is the nv_cache folder?
Dont found it anywhere.
So i remember when i first went gsync , in driver settings (after new driver install) vsync was set to ON by default when you enabled gsync. In later drivers this was no longer the case it is now use 3d application settings. If its true we need vsync with gsync to prevent tearing (even withing the gsync fps range) why would nvidia change this setting? If tearing is caused by frames being rendered between refreshes and gsync prevents this happening why would it tear? I notice no tearing ingame without vsync
Because when gsync was released people were complaining about their FPS being capped to refresh rate hence the option was changed.