NVIDIA GeForce 337.88 WHQL Driver

nvENC is not the same thing as shadowplay, it performs much much worse and is a different subset of the encoding functionality.



Indeed it is.

proof? because i'm pretty sure nvenc is the same thing as shadowplay. you're using the built-in h264 encoder on your gpu when you use nvenc, which is what shadowplay does. performs exactly the same as shadowplay for me too. same performance hit, same quality.
 
proof? because i'm pretty sure nvenc is the same thing as shadowplay. you're using the built-in h264 encoder on your gpu when you use nvenc, which is what shadowplay does. performs exactly the same as shadowplay for me too. same performance hit, same quality.

Go google it, nvENC is the umbrella under which the subset that Afterburner/3rd party programs can access is encompassed in. Shadowplay has deeper access and performs far, far better. NVenc alone in Afterburner resulted in a 20% framerate hit for me across the board, while shadowplay results in a 2-4% loss depending on the game I've tested with. It's pretty common knowledge and you can find many topics discussing it at guru3d. One of the first results for "shadowplay vs nvenc performance" is this thread: https://obsproject.com/forum/threads/nvenc-giving-terrible-performance-vs-shadowplay.11448/
 
I check forums pretty regularly as my near-16,000 post count can attest, but I don't spend my days living on them during most time periods anxiously F5'ing for the newest driver releases,. You completely skipped the "shadowplay" portion there too, but it's still nice to get the notification if I haven't seen it yet. You're over-reacting justttttt a little.

Lol yeah, but its the internet, its my job to overreact. (still waiting on that paycheck...to buy another years worth of f5 keys)

The shadowplay certainly does seem like it could be useful.... for some folks. Can't think of a reason id use it personally.

I had a complete cow when ATI shoved CCC down my throat......


And just for grins I did actually install the geforce "experience". Wow. A yellow crash helmet appeared on my monitor!

Now I have evil sounding services running things called "NVIDIA Geforce Experience Backend" ....

Heh, yah that service kinda sums it on up don't it. Guessing the marketing guys didnt get a say in what the programmers called that one...
 
Immediate on-screen corruption with Valley 1.0 on my Titan. Flickering triangles about the screen at a low rate. I under-clocked my gpu and cpu, and it still does it, so I'm inclined to think it's the drivers / Valley.
 
Last edited:
Immediate on-screen corruption with Valley 1.0 on my Titan. Flickering triangles about the screen at a low rate. I under-clocked my gpu and cpu, and it still does it, so I'm inclined to think it's the drivers / Valley.

Oh definitely, I really appreciate the responses though. I rolled back and all was fine so I was just curious if it was the drivers themselves or something I was putting on top of them. For some reason I'm incapable of going to other websites lately to look for info. Well, I avoid it anyway. :D
 
People are afraid of what they do not understand :D

I have geforce experience on a few of my machines, I do not use it for graphic settings on my main rig, but I do use it on my daughters computer, and sometimes on my htpc for "best graphic settings". While I like to tweek settings and things, my 11 year old daughter just wants to play games. So it works well for that.

It doesn't force settings, unless you tell it to. Even if you tell it to, and you go in and make changes, the game will keep your changes and GFE will update to show that game is not optimized per Nvidia's recommended settings.
If Nvidia updates a games recommended settings, same thing happens, it will say this game is not optimized. you can then click the button to apply the new settings.
I can't speak on how editing config files would go, as I don't do that regularly.

it's really not a horrible program (nor is it the best). I don't even look at it half the time, but I do like shadowplay, and the driver update notifications are cool to me. It doesn't auto install any drivers for me, just says a new one is available.

But to each his own. It's not a requirement for anything, so if you don't want/like it. Don't download it.
I have had nothing but good experiences with GFE. Most recently it must have downloaded an updated profile for Watch Dogs yesterday because now the game is running really smooth when before I was getting a lot of choppiness. The difference in performance compared to the day before was surprising. Using SLI GTX 780s.

I would like to have a bit more transparency as to what the program is doing when optimizing settings, but I don't use that feature a whole lot anyway. I usually just take a look at the settings they recommend as a starting point when playing around with settings. Most of the time I can get a better experience myself in both image quality and framerate than NVIDIA does.

But again, it's a great platform for delivering driver profiles. If you're not using GFE then you're missing out for this very reason. You can choose not to use anything else if you want.
 
Immediate on-screen corruption with Valley 1.0 on my Titan. Flickering triangles about the screen at a low rate. I under-clocked my gpu and cpu, and it still does it, so I'm inclined to think it's the drivers / Valley.
Ran fine on my GTX 780 with these drivers... so it's not happening to everyone.

What settings / renderer were you using? Maybe there's something that sets it off.
 
Ran fine on my GTX 780 with these drivers... so it's not happening to everyone.

What settings / renderer were you using? Maybe there's something that sets it off.

1920x1200 full screen ultra (or whatever highest quality is called) and 4X AA
 
1920x1200 full screen ultra (or whatever highest quality is called) and 4X AA
Well, there's the first difference; I always run that benchmark in a window. I'll try it full-screen when I get home from work.

Were using the DX11 renderer, or one of the other options?
 
Well, there's the first difference; I always run that benchmark in a window. I'll try it full-screen when I get home from work.

Were using the DX11 renderer, or one of the other options?

For me, it's any combo of options using DX11. No flickering triangles with DX9 or OpenGL. I got 5 other cards here to try with, but I'm too lazy, lol.
 
Thought i would just randomly chime in about these drivers. I've been gettings worse frames with these drivers in bf4. I reverted back to the .50 drivers
 
Anyone else have an issue with this driver where you could be doing something on the Internet and have the computer seemingly freeze on you and force you to reset? I didn't have that problem before using the driver and I've never seen it again since rolling back to the previous driver.
 
Anyone else have an issue with this driver where you could be doing something on the Internet and have the computer seemingly freeze on you and force you to reset? I didn't have that problem before using the driver and I've never seen it again since rolling back to the previous driver.

A-HA! I had that happen on Thursday! And I was browsing [H] (w/Firefox) when it froze, lol. I didn't think about the recent nvidia driver installation. I think I'm going to roll back.
 
I might add that if you enjoy roaming around the island of Panau and blowing shit up, don't use these latest drivers.

There's a confirmed problem with black artifacts on leaves in Just Cause 2 with 337.88 and 7xx series GPUs.
 
Next beta is going to be interesting. Still... I see no problem just rolling back. A lot of the "software" I use is kinda... well... games that are old as shit. I don't really expect Nvidia to constantly be vigil and not break them. Not to say that Valley and Just Cause 2 are old but these things happen. Last WHQL was fantastic, imo.

This last set of drivers on the Red side was particularly interesting for people with OC monitors... kinda rare to get BSOD from video driver... it did not like the pixel clock patcher but ToastyX already fixed it.
 
There might be a better alternative to rolling back, you know...

Some of these issues are very-likely caused by the new shader-caching feature they just added. This feature can be disable on a per-game basis, so you might give that a try on the games you're having trouble with before rolling back the entire driver.
 
A-HA! I had that happen on Thursday! And I was browsing [H] (w/Firefox) when it froze, lol. I didn't think about the recent nvidia driver installation. I think I'm going to roll back.

That's a relief on my end. ;)

There might be a better alternative to rolling back, you know...

Some of these issues are very-likely caused by the new shader-caching feature they just added. This feature can be disable on a per-game basis, so you might give that a try on the games you're having trouble with before rolling back the entire driver.

Unfortunately the issue I had and the person I quoted above your quote here was not gaming related but good tip nonetheless. :)
 
How is it that the WHQL is remarkably worse than the prior beta, heh.
 
How is it that the WHQL is remarkably worse than the prior beta, heh.
More proof that WHQL means nothing. Even the drivers that were pulled a couple years ago because it let some Nvidia cards cook themselves were WHQL. Its always hilarious when I see people say they wont use beta Nvidia drivers and wait for WHQL drivers.
 
More proof that WHQL means nothing. Even the drivers that were pulled a couple years ago because it let some Nvidia cards cook themselves were WHQL. Its always hilarious when I see people say they wont use beta Nvidia drivers and wait for WHQL drivers.

I'm learning this lesson.
 
Back
Top