Redemption80:

Off to test these and also find out what variable rate super sampling is as that sounds interesting.

Do you have a VR headset? Will probably be even better with a VR headset that has eye tracking, so that the highest amount of SS is applied to where you look instead of lens center.

Nicked_Wicked:

Same here but with 1185Mhz on a 2070S, bit of a bummer but otherwise a really smooth feeling driver.

I switched back to 450.99 and the 2080ti idle´s at 300mhz again. I guess there will be a hotfix any day 😉

No problems with idle clock speeds here. Will do some testing though on some specific games and see how the driver performs! 🙂

I was looking forward to new drivers but apparently control panel sharpening is still broken on these... Can't remember the last time I had to skip so many drivers but oh well, another skip.

no high idle clocks here, all seems well and stable here so far .

Johannah:

For me its stuck at 1350mhz idle with these drivers. 2080ti

What apps do you have running in the background? How many monitors are connected to your graphics card?

ManuelG:

What apps do you have running in the background? How many monitors are connected to your graphics card?

Only one monitor (lg38gl950g). I turned off: msi afterburner, razer app, iCUE, anti malware, samsumg magican, discord, world of warcraft app. It was still the same. No problem with 450.99 tho.

Johannah:

For me its stuck at 1350mhz idle with these drivers. 2080ti

Yep same here. Stuck on 1350 on my 2080. Usually it's above 1500...defo needs a hotfix here.

Thank you! Stable with clocks here too.

ManuelG:

What apps do you have running in the background? How many monitors are connected to your graphics card?

MSI Afterburner and Corsair iCUE running here. Only one display.

Pinstripe:

How can Nvidia claim this driver has official Windows 10 May 2020 support but still runs on WDDM 2.6?

jwb1:

They are counting on most people not knowing or caring, which is probably true.

nevcairiel:

Who ever claimed WDDM 2.7 was mandatory? Will it not work on Windows 10 20.04?

From the "What's new":

Our Game Ready Driver also provides support for Microsoft's release of the Windows 10 May 2020 update, which is now starting to roll out to users. The new Windows update brings a wide variety of new features, ranging from the GPU temperature being shown in Task Manager, to the introduction of the new DirectX 12 Ultimate graphics API.

Without WDDM 2.7, nVidia's above statement is a complete lie, as this driver does NOT provide support for build 2004, but the other way around: Windows' build 2004 brings support for old drivers. So yes, Pinstripe's question is 100% justified. FYI, Intel's current official stable driver has been WDDM 2.7 complaint for some time now.

Stable here, mem clocks normal... have adaptive set in CP, not performance.

So, nvidia sharpening never going back to how it was? Still broken. Last version where it worked correctly and in all games was in 442.74. Haven't tested the insider ones though. Loved using sharpening on older games.

No issues while playing a little Red Dead 2, Control, or GTA V.

Mistajista:

Clocks stuck at max on my GTX 1080. Can't remember the last driver where they weren't. Tell a lie, 450.99 idles as normal.

139Mhz here.

No issues to report here, GPUz shows idle clock speed of 135mhz. I only tested WoW Classic so far and all seems good.

No idle issues here with my 2080Ti.. drops to 330Mhz at idle which I believe is the expected idle for a 144Hz also running Dual-Monitor. But I did have to reboot once to get sound working again using HDMI out for audio.

Maybe @ManuelG will tell us why WDDM 2.7 isn't included?

Here's the full list of things that are still broken in new Windows 10 May Update: Difficulty connecting to more than one Bluetooth device Windows 10 devices with certain Realtek drivers might be unable to connect to more than one Bluetooth device. Errors or issues during or after updating devices with Conexant ISST audio drivers Devices with affected Conexant ISST audio drivers might receive an error or have issues with Windows 10, version 2004. Errors or issues during or after updating devices with certain Conexant audio drivers Devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen. Issues using ImeMode property to control IME mode for individual text entry fields Some IMEs for certain langauges might have issues using the ImeMode property with certain apps. Variable refresh rate not working as expected on devices with Intel iGPU Enabling VRR on affected devices will not enable the VRR for most games, especially games using Direct X 9. Stop error when plugging or unplugging a Thunderbolt dock Devices using Thunderbolt docks may receive a stop error when plugging in or unplugging the dock Errors or unexpected restarts for some devices using Always On, Always Connected Devices with more than one Always On, Always Connected capable network adapter might have issues. No mouse input with apps and games using GameInput Redistributable Affected apps and games using both GameInput Redistributable and Windows 10, version 2004 might lose mouse input. Issues updating or starting up devices when aksfridge.sys or aksdf.sys is present Devices with apps or drivers using certain versions of aksfridge.sys or aksdf.sys might have issues updating or starting Issue with older drivers for Nvidia display adapters (GPU) You might have issues if you are using an Nvidia display adapter (GPU) and drivers with a version below 358.00. LOL so much for nVidia's "new" 446.14 driver.

jwb1:

Here's the full list of things that are still broken in new Windows 10 May Update: Issue with older drivers for Nvidia display adapters (GPU) You might have issues if you are using an Nvidia display adapter (GPU) and drivers with a version below 358.00. LOL so much for nVidia's "new" 446.14 driver.

I think that's more related to very old GPUs which are no longer supported on the 445-446 series drivers. Like very old Geforce 400/500 series cards last supported driver is 391.35 - https://www.nvidia.com/Download/driverResults.aspx/132845/en-us