Comments Locked

39 Comments

Back to Article

  • Daniel Egger - Friday, September 19, 2014 - link

    Meh! With the new drivers I lost the ability to get multichannel sound over HDMI, it's only stereo now.
  • willis936 - Saturday, September 20, 2014 - link

    I've had the opposite experience. My 770 now talks to my sony receiver in multichannel without fiddling whereas in the past it's always needed fiddling (unplug/replug hdmi, power cycle receiver, etc.)
  • Daniel Egger - Saturday, September 20, 2014 - link

    It seems they've changed something. Well, after going back to a previous version and forward to this one + a run of the speaker setup it's now back to a multichannel setup. Luckily reinstalling the driver is pretty painless nowadays, most of the time I do not even need to reboot...
  • ltcommanderdata - Friday, September 19, 2014 - link

    A note with these drivers is that they are the first WHQL drivers to drop support for DX10 GPUs.
  • JarredWalton - Friday, September 19, 2014 - link

    Oh yeah -- forgot to mention that. Thanks! :-)
  • Patrese - Friday, September 19, 2014 - link

    And still no fix for the lack of full RGB range over DP and HDMI on NVIDIA cards. My next card will be an AMD because of that. :(

    This post describes the issue: http://forums.anandtech.com/showpost.php?p=3647169...
  • coburn_c - Saturday, September 20, 2014 - link

    Hahaha, that post is incredibly ignorant. Using a smaller colorspace to send 4K over HDMI 1.3 is not NVIDIA's doing, it's the only way to do it. As for the dynamic range setting, that is a video player override. The player should be deciding the range to use, MPC HC does it full range by default, VLC abbreviated range by default, both allow you to change it. The setting in the control panel is to override a video player... hence the radio buttons for "use player settings" or "use NVIDIA settings". Either way you set it, in the player on with the override, the range setting works fine over HDMI. I must reiterate, you and that posters are absolutely misinformed and misinforming.
  • sidspyker - Sunday, September 21, 2014 - link

    Incredibly ignorant is it? Well funny that a Nvidia rep has confirmed that this IGNORANT bug will be fixed by the end of this year then.
  • coburn_c - Sunday, September 21, 2014 - link

    There is no bug, there isn't even a problem. Where is this confirmation? Link it.
  • sidspyker - Sunday, September 21, 2014 - link

    There is a bug related to the Full range, just not the one pointed out in THAT post. The bug I am referring to is not related to video rendering but everything displayed. The difference can be seen just by changing your monitor from HDMI to DVI and back. It was introduced in one of the driver releases in 2012 and since then hasn't been fixed

    Anyway, the confirmation from ManuelG that this issue will be fixed by the end of this year:
    http://forums.guru3d.com/showthread.php?p=4880360#...
  • coburn_c - Sunday, September 21, 2014 - link

    A vague comment on a third party forum? You must be shitting me. There are hilarious forum posts about this that tell you to use their registry hack... THAT IS AN EXE. Registry changes are never done with an executable. Not one post about this on laptopvideo2go. You know why? Because that is a forum full of knowledgeable people. You know whats even more hilarious? The 0-255 range they all talk about in these posts? That is a YUV range, that's why it's a video rendered setting, it's talking about the YUV to RGB conversion. These morons are talking about 0-255 as if it's an RGB range. You're all spreading lies and disinformation and I think you should have your posting rights revoked.
  • sidspyker - Sunday, September 21, 2014 - link

    "A vague comment on a third party forum" yes, by a well know and verified NVIDIA rep throughout the internet. You can also look at the official Geforce forums, there's a thread there too.
    https://forums.geforce.com/default/topic/648176/ge...

    Yes an exe that makes registry changes, who said you can't do registry changes using an exe? The exe comes from a well known videogame modder for Dark Souls called Durante at that, for ease of use.
    http://blog.metaclassofnil.com/?p=83

    RGB HAS FULL AND LIMITED RANGE JUST LIKE YCbCr. You're the one that needs an education in matters you only known of partially. Video encoding has nothing to do with this, everything you see on your monitor - Desktop, Games, Applications, etc all are affected.
    Example DVI v HDMI(respectively):
    http://i58.tinypic.com/35avk0p.jpg
    Monitors of the same brand, models etc etc.

    Seeing as you're a huge idiot you're probably gonna try to bring the argument that they're two different monitors with different colour calibrations. Well I can't do anything about someone who has a foolish superiority complex based on his little knowledge on a subject and dismisses anything that doesn't fit his narrative or say that ManuelG, a very well known NVIDIA rep is "just a moderator". Suit yourself, I'll enjoy my Full Range RGB and wait for them to finally fix it after 2 years while you can go and dismiss the issue as nothing.
  • coburn_c - Monday, September 22, 2014 - link

    There is no such thing as limited RGB range. The difference in those images is the gamma setting.

    Any limited range setting for RGB only has to do with converting YUV to RGB.

    RGB uses gamma, from 0 to 1, not luminance, from 0-255. These people have no idea what they are talking about, and any adjustments they make would have to effect gamma as that's all RGB has. Gamma is a calibration like any other, and can not be limited in its range as they suggest.
  • Mem - Thursday, September 25, 2014 - link

    All info you need on full RGB and limited range RGB here https://pcmonitors.info/articles/correcting-hdmi-c... ,sooner Nvidia allow full RGB range the better,tried of using the third party workaround software to fix the issue,yes my monitor has settings options for limited and full RGB range.
  • coburn_c - Monday, September 22, 2014 - link

    If you will not accept the science of the matter, then how about anecdotal. You seem to love anecdotal.

    I am using and HDTV connected over HDMI at this moment. I open MPC HC and change the output range of my YUV>RGB conversion to 16-235 and watch the luminance range of the video change. The blacks become gray. That could not happen if my output was already limited. I also adjust my gamma and watch whites become blown out. I also apply a custom resolution as they suggest and watch nothing change.

    The science does not support you. The experiment does not support you. Your supporting information has no test or calibration data to prove its efficacy. Your sources lack credibility. Your rhetoric shows a fundamental lack of understanding of the subject.

    Please read about how these work so that you can understand your mistake.

    http://en.wikipedia.org/wiki/RGB_color_space
    http://en.wikipedia.org/wiki/YCbCr#YCbCr
  • coburn_c - Sunday, September 21, 2014 - link

    Here, get an education. http://www.calibratedsoftware.com/supportlibrary_v...
  • coburn_c - Sunday, September 21, 2014 - link

    I'm going to go on to drive the stake through this nonsense. These complaints and claims all imply that the blacks aren't black and whites aren't white. Again this is a YUV (YCbCr/YPbPr) issue. These video encoding methods carry luminance (Y, brightness.....) separately, and that is the range compressed to 16-235. The chroma adds the color of red and blue and the difference makes green. RGB carries red green and blue color chromacity info, a white point and a gamma curve.. There is no bit range to the luminance. This entire argument is asinine.
  • coburn_c - Saturday, September 20, 2014 - link

    Furthermore, that range setting has nothing to do with what is sent over the interface, it only effects video renderers. Just such ignorance...
  • jwcalla - Saturday, September 20, 2014 - link

    I keep hearing about this "problem". Am I the only one running HDMI that has had no issues with Full Range?
  • rms141 - Sunday, September 21, 2014 - link

    Displayport is not affected by this bug. Only HDMI.
  • coburn_c - Sunday, September 21, 2014 - link

    There is no bug. RGB doesn't have a luminance range. RGB has a gamma range.
  • hpglow - Saturday, September 20, 2014 - link

    How is DSR different than super-sampling? The granddaddy of AA where a scene was rendered in a higher res then down-sampled? It often produced blurry content, and the performance hit was horrible. But it dates way back, N64 had it as did the Geforce3 (although the performance was so bad it was unusable).

    Also what is Dynamic about it? I have read the blurbs about it in every 980 and 970 review but none go much farther than telling us that it is a scene rendered at a higher res then scaled down.
  • JarredWalton - Saturday, September 20, 2014 - link

    DSR basically exposes a higher "virtual" resolution in the drivers that the games see as a real resolution, and that resolution gets scaled down via a 13 tap Gaussian filter to whatever resolution you set (usually your native LCD resolution, though it doesn't have to be).

    So as an example, say you have a game like Dark Souls II and you're running on a 1080p display. You could set a DSR resolution of 3840x2160 (4K or 4x 1080p) and the game will just think you're playing on a display that runs at that resolution. However, the drivers know your actual display is a 1080p panel and so they'll take the rendered game image and down-size it to 1080p. You could also set the DSR resolution to other values, like 2560x1440, 2752x1548, or whatever other options NVIDIA has (I'm not sure what exact values are supported).

    Contrast that with supersampling where the game generally has to be aware of the feature, or if it's forced on through the drivers it's still not quite the same. See, SSAA has to be a specific whole integer multiple of the resolution, either 2X or 4X typically, so if you're running at 1920x1080 and use 2x SSAA then internally the game renders at 3840x2160 and that gets resized to 1080p -- not much difference here, although I think the 13 tap Gaussian filter is different as SSAA traditionally just used bilinear filtering (or maybe bicubic filtering). With DSR it's possible to use 1.5x, 2.5X, 3.2X, etc. AFAIK. But yes, it's mostly just a refinement of SSAA, and it was interesting how careful NVIDIA was to never actually use the phrase "supersampling" when talking about DSR.

    As to your assertion that SSAA produces blurry content, well, it might be slightly blurry as it has to remove jaggies, but in general SSAA produces better quality image than MSAA; it's just far more computationally intensive. TXAA on the other hand can look quite blurry in my experience, and the same goes for some variants of FXAA.
  • Oxford Guy - Saturday, October 4, 2014 - link

    FXAA is awful. It looks like a screen smeared with butter.
  • coburn_c - Saturday, September 20, 2014 - link

    I believe they call it dynamic because the card has dedicated hardware that does the downsampling. It doesn't take a performance hit to scale. That and they made the settings idiot proof.
  • D. Lister - Saturday, September 20, 2014 - link

    No, actually it is just your last sentence, nothing else. Manually, you can do this on any reasonably modern GPU. AAMOF there is a very good DIY tutorial at Nvidia's official website.
  • frenchy_2001 - Saturday, September 20, 2014 - link

    The reason for that new AA method is that simple super does not work anymore with modern engine using deferred rendering.
    You are right that this is an equivalent to the older AA technique, it's just that this technique does not work anymore.
  • JarredWalton - Saturday, September 20, 2014 - link

    SSAA should work with deferred rendering -- it's MSAA that doesn't work. SSAA after all is just rendering internally at a higher resolution and downsizing, though it's done in a slightly different fashion the DSR.
  • n13L5 - Saturday, September 20, 2014 - link

    Its the new snake oil, rather than the old snake oil ;-)

    Just kidding, I saw some videos that looked like great improvement and some others where you were hard pressed to tell the rather unexciting difference.
    Distant Grass becoming stable, rather than flickering in and out of existence was pretty damned cool.
  • chardyman - Saturday, September 20, 2014 - link

    Heads up.
    These new drivers appear broken with my GTX 570 under Win8.1.
    BSOD - rolled back to a restore point.
    Contacted nvidia - no response yet.
  • StealthGhost - Sunday, September 21, 2014 - link

    Working fine for me so far. 570 and Windows 8.1. I would try Guru3d's driver cleaner (or something similar) and redownload and install.
  • ellroy80 - Saturday, September 20, 2014 - link

    Jarrod, can you go into more detail about the compatibility issues you encountered with the 970?
  • CrystalBay - Sunday, September 21, 2014 - link

    Please respond Jarred or Ryan !
  • JarredWalton - Sunday, September 21, 2014 - link

    Ryan would have to confirm, but I think the issue might be that for some reason the drivers didn't play well with GTX 970 on his LGA2011 test bed. Most users are on LGA1150/1155, so it may not have been experienced by other sites. Anyway, it sounds like 970 is now working for Ryan so the review/performance will be up likely in the next day or so (and probably a slightly better explanation of what went wrong).
  • StealthGhost - Sunday, September 21, 2014 - link

    Glad to hear about the 334.16 update addressing the GTX 970 issues, hopefully Anandtech's review will be up soon then.

    I for one would love to know about the OC ability and SLi scaling for the GTX 970 if possible. I know the OC ability was in the 980 review and it makes me want to compare it to the 970.
  • Senti - Sunday, September 21, 2014 - link

    And the OpenCL is still broken (since 332.21). Way to go, nVidia, instead of implementing 1.2 you managed to break the once working 1.1.

    There are some OpenGL issues too, but they can be worked around unlike OpenCL ones.
  • Senti - Sunday, September 21, 2014 - link

    Edit: I meant 332 was the last working series.
  • croc - Tuesday, September 23, 2014 - link

    Just a wee note... The versions of the new driver are 344, not 334. And for anyone using an ENB graphics mod for your game, beware the geforce experience 2.1.2.x for the moment. It seems to have broken something.
  • Inventor14 - Saturday, September 27, 2014 - link

    https://secure.myBookOrders.com/order/zvonko-pavlo...

Log in

Don't have an account? Sign up now