2016/11/02 17:52:58
FattysGoneWild
Scarlet-Tech,
 
In the Nvidia control panel. They had V-Sync set to on by default setting. So that is why things never went over the refresh and was locked on. I believe these last 2 updates or so. Nvidia went back to default setting of Using 3D app again. So that is why you are seeing what you are seeing now. You can go back and change it to the old default way again if you like. How Nvidia had it before. You just put V-Sync back on in control panel from using 3D app. Or if you want to remain using the updated default they went back to. Cap FPS @135 for 144Hz or use in game vsync with gsync to lock things together with the refresh rate. demo23019 pretty much covered it well. 
2016/11/02 18:01:41
FattysGoneWild
demo23019
nvidia put vsync on globally before so it capped your frames at your monitor refresh with gsync.  IDK when last time you updated your drivers but they stopped this like 3 drivers ago and set vsync to use app setting so now you have to turn vsync on in game when using gsync if you want it like it was before. 
OR do it proper way set cap limit gsync and not use vsync at all as its not need and only adds lag .





 
Have you seen this? https://www.youtube.com/watch?v=MzHxhjcE0eQ (11:30 mark on) not to start a debate. Its quite interesting. High fps gsync+vsync had less leg then with vsync off. Its weird. I have been reading and reading up on this. It seems to me. Nvidia made gsync+vsync go hand in hand together and how it suppose to work by design. I don't know....  I love gsync talk. Makes my head spin every time. 
2016/11/02 18:28:13
Sajin
Flicker on desktop at 144Hz still isn't fixed. Artifacts in videos/gifs appear to be fixed.
2016/11/02 18:31:14
Scarlet-Tech
FattysGoneWild and Demo. Thank you both greatly. I had no idea they had changed Vsync to off. It all makes sense now, and if I am going to use GSync, I will remember to enable frame cap or vsync. I sincerely apologize for the first few posts where I didn't understand what was being said, and appreciate you all for helping.
2016/11/02 19:07:54
wirerogue
haven't tried the new driver yet but, the flickering for me goes away by changing to 120 and then back again to 144.
 
it will stay fixed for a while, even in between restarts, then every 3 or 4 days the flickering returns.
 
weird
2016/11/02 22:13:01
arestavo
These completely broke the ability to fold on my 1080. It loops downloading a new WU, fails before it actually does any work (even at stock settings), the starts the loop again.
 
5:11:50:WU01:FS01:Started FahCore on PID 14060
05:11:50:WU01:FS01:Core PID:16640
05:11:50:WU01:FS01:FahCore 0x21 started
05:11:51:WU01:FS01:0x21:*********************** Log Started 2016-11-03T05:11:51Z ***********************
05:11:51:WU01:FS01:0x21:Project: 11709 (Run 3, Clone 118, Gen 37)
05:11:51:WU01:FS01:0x21:Unit: 0x000000338ca304f357f594cf76181d1e
05:11:51:WU01:FS01:0x21:CPU: 0x00000000000000000000000000000000
05:11:51:WU01:FS01:0x21:Machine: 1
05:11:51:WU01:FS01:0x21:Reading tar file core.xml
05:11:51:WU01:FS01:0x21:Reading tar file system.xml
05:11:51:WU01:FS01:0x21:Reading tar file integrator.xml
05:11:51:WU01:FS01:0x21:Reading tar file state.xml
05:11:52:WU01:FS01:0x21:Digital signatures verified
05:11:52:WU01:FS01:0x21:Folding@home GPU Core21 Folding@home Core
05:11:52:WU01:FS01:0x21:Version 0.0.17
05:11:56:FS01:Paused
05:11:56:FS01:Shutting core down
05:11:56:WU01:FS01:0x21:WARNING:Console control signal 1 on PID 16640
05:11:56:WU01:FS01:0x21:Exiting, please wait. . .
05:11:56:WU01:FS01:0x21:ERROR:exception: Error downloading array interactionCount: clEnqueueReadBuffer (-5)
05:11:56:WU01:FS01:0x21:Saving result file logfile_01.txt
05:11:56:WU01:FS01:0x21:Saving result file log.txt
05:11:56:WU01:FS01:0x21:Folding@home Core Shutdown: BAD_WORK_UNIT
2016/11/03 16:13:25
Scarlet-Tech
arestavo
These completely broke the ability to fold on my 1080. It loops downloading a new WU, fails before it actually does any work (even at stock settings), the starts the loop again.
 
5:11:50:WU01:FS01:Started FahCore on PID 14060
05:11:50:WU01:FS01:Core PID:16640
05:11:50:WU01:FS01:FahCore 0x21 started
05:11:51:WU01:FS01:0x21:*********************** Log Started 2016-11-03T05:11:51Z ***********************
05:11:51:WU01:FS01:0x21:Project: 11709 (Run 3, Clone 118, Gen 37)
05:11:51:WU01:FS01:0x21:Unit: 0x000000338ca304f357f594cf76181d1e
05:11:51:WU01:FS01:0x21:CPU: 0x00000000000000000000000000000000
05:11:51:WU01:FS01:0x21:Machine: 1
05:11:51:WU01:FS01:0x21:Reading tar file core.xml
05:11:51:WU01:FS01:0x21:Reading tar file system.xml
05:11:51:WU01:FS01:0x21:Reading tar file integrator.xml
05:11:51:WU01:FS01:0x21:Reading tar file state.xml
05:11:52:WU01:FS01:0x21:Digital signatures verified
05:11:52:WU01:FS01:0x21:Folding@home GPU Core21 Folding@home Core
05:11:52:WU01:FS01:0x21:Version 0.0.17
05:11:56:FS01:Paused
05:11:56:FS01:Shutting core down
05:11:56:WU01:FS01:0x21:WARNING:Console control signal 1 on PID 16640
05:11:56:WU01:FS01:0x21:Exiting, please wait. . .
05:11:56:WU01:FS01:0x21:ERROR:exception: Error downloading array interactionCount: clEnqueueReadBuffer (-5)
05:11:56:WU01:FS01:0x21:Saving result file logfile_01.txt
05:11:56:WU01:FS01:0x21:Saving result file log.txt
05:11:56:WU01:FS01:0x21:Folding@home Core Shutdown: BAD_WORK_UNIT




 
Same on my 980ti's.  I only kept it for a few minutes and then removed it.  The last two drivers are NOT good for folding at all.
 
373.06 is working perfect though.  2m ppd across the one 1070 and two 980ti's 
2016/11/03 16:20:21
lebel
Off topic, just checked my 980ti's Asic quality, rather blown away 85.8%
2016/11/03 16:23:10
Scarlet-Tech
lebel
Off topic, just checked my 980ti's Asic quality, rather blown away 85.8%


Which brand gpu?
2016/11/03 16:35:56
lebel
Scarlet-Tech
lebel
Off topic, just checked my 980ti's Asic quality, rather blown away 85.8%


Which brand gpu?

GM200
edit: Evga 980ti FTW

Use My Existing Forum Account

Use My Social Media Account