NVIDIA Posts First DirectX 12 Ultimate Driver Set, Enables GPU Hardware Schedulingby Ryan Smith on June 24, 2020 9:45 AM EST
- Posted in
- DirectX 12
NVIDIA sends word this morning that the company has posted their first DirectX 12 Ultimate-compliant driver. Published as version 451.48 – the first driver out of NVIDIA’s new Release 450 driver branch – the new driver is the first release from the company to explicitly support the latest iteration of DirectX 12, enabling support for features such as DXR 1.1 ray tracing and tier 2 variable rate shading. As well, this driver also enables support for hardware accelerated GPU scheduling.
As a quick refresher, DirectX 12 Ultimate is Microsoft’s latest iteration of the DirectX 12 graphics API, with Microsoft using it to synchronize the state of the API between current-generation PCs and the forthcoming Xbox Series X console, as well as to set a well-defined feature baseline for future game development. Based around the capabilities of current generation GPUs (namely: NVIDIA Turing) and the Xbox Series X’s AMD RDNA2-derrived GPU, DirectX 12 Ultimate introduces several new GPU features under a new feature tier (12_2). This includes an updated version of DirectX’s ray tracing API, DXR 1.1, as well as tier 2 variable rate shading, mesh shaders, and sampler feedback. The software groundwork for this has been laid in the latest version of Windows 10, version 2004, and now is being enabled in GPU drivers for the first time.
|DirectX 12 Feature Levels|
(Introduced as of)
|NVIDIA: Maxwell 2
|NVIDIA: Maxwell 2
|Variable Rate Shading
|Raster Order Views||Yes||Yes||No|
|Typed UAV Load||Yes||Yes||Yes|
In the case of NVIDIA’s recent video cards, the underlying Turing architecture has supported these features since the very beginning. However, their use has been partially restricted to games relying on NVIDIA’s proprietary feature extensions, due to a lack of standardized API support. Overall it’s taken most of the last two years to get the complete feature set added to DirectX, and while NVIDIA isn’t hesitating to use this moment to proclaim their GPU superiority as the first vendor to ship DirectX 12 Ultimate support, to some degree it’s definitely vindication of the investment the company put in to baking these features into Turing.
In any case, enabling DirectX 12 Ultimate support is an important step for the company, though one that’s mostly about laying the groundwork for game developers, and ultimately, future games. At this point no previously-announced games have confirmed that they’ll be using DX12U, though this is just a matter of time, especially with the Xbox Series X launching in a few months.
Perhaps the more interesting aspect of this driver release, though only tangential to DirectX 12 Ultimate support, is that NVIDIA is enabling support for hardware accelerated GPU scheduling. This mysterious feature was added to the Windows display driver stack with WDDM 2.7 (shipping in Win10 2004), and as alluded to by the name, it allows GPUs to more directly manage their VRAM. Traditionally Windows itself has done a lot of the VRAM management for GPUs, so this is a distinctive change in matters.
At a high level, NVIDIA is claiming that hardware accelerated GPU scheduling should offer minor improvements to the user experience, largely by reducing latency and improving performance thanks to more efficient video memory handling. I would not expect anything too significant here – otherwise NVIDIA would be heavily promoting the performance gains – but it’s something to keep an eye out for. Meanwhile, absent any other details, I find it interesting that NVIDIA lumps video playback in here as a beneficiary as well, since video playback is rarely an issue these days. At any rate, the video memory handling changes are being instituted at a low level, so hardware scheduling is not only for DirectX games and the Windows desktop, but also for Vulkan and OpenGL games as well.
Speaking of Vulkan, the open source API is also getting some attention with this driver release. 451.48 is the first GeForce driver with support for Vulkan 1.2, the latest version of that API. An important housekeeping update for Vulkan, 1.2 is promoting a number of previously optional feature extensions into the core Vulkan API, such as Timeline Semaphores, as well as improved cross portability support by adding full support for HLSL (i.e. DirectX) shaders within Vulkan.
Finally, while tangential to today’s driver release, NVIDIA has posted an interesting note on its customer support portal regarding Windows GPU selection that’s worth making note of. In short, Windows 10 2004 has done away with the “Run with graphics processor” contextual menu option within NVIDIA’s drivers, which prior to now has been a shortcut method of forcing which GPU an application runs on it an Optimus system. In fact, it looks like control over this has been removed from NVIDIA’s drivers entirely. As noted in the support document, controlling which GPU is used is now handled through Windows itself, which means laptop users will need to get used to going into the Windows Settings panel to make any changes.
As always, you can find the full details on NVIDIA’s new GeForce driver, as well as the associated release notes, over on NVIDIA’s driver download page.
Post Your CommentPlease log in or sign up to comment.
View All Comments
Jiai - Wednesday, June 24, 2020 - linkI don't own a Navi or Turing GPU, but since Minecraft and Quake 2 are the only games with real benefits from RT, because it is just too slow, I don't expect to see modern games really using it before Nvidia 4000 / Radeon 7000
Destoya - Wednesday, June 24, 2020 - linkThere's quite a few other titles that benefit. It's still kind of the situation where you're paying $50 extra for a functional tech demo but it's not just Quake and MC. Control is not really playable at 1440p with high graphics settings on a 5700/5700XT, but DLSS is basically magic and means you can upscale to 1440p with no significant quality penalty, plus run full RT effects even on the 6GB 2060. Metro looks fantastic with RT turned on as well.
Jiai - Wednesday, June 24, 2020 - linkI saw videos of all RT games, and I failed to see a meaningful upgrade, an improved reflect here, better shadows there...maybe if I owned Control and Metro,I would see a difference. Lightning improvement in Q2 and MC just feel like complete new games.
DLSS 2.0 impressed me on the other side, I can imagine so much applications with the same concept (photo, music, etc...)
lilkwarrior - Thursday, June 25, 2020 - linkYour comment is kinda laughable. Of course you don't notice a difference if you don't own a game that doesn't use the revolutionary features. That said, AMD lack of support & the delay of Next gen consoles for them to catch up definitely limited the effectiveness of Turing ironically.
Most PC games are console ports; of course most of the dramatic amount of support for next-gen gaming by Turing wouldn't be really noticed till next-gen console games release
nievz - Wednesday, June 24, 2020 - linkYou should fire up your ryzen rig and run your benchmarks to know the difference with HAGS. +
Assassin's Creed Oddeysey is now at 97% utilization from 90-92% previously. I'm psyched!
Before: min fps 29, avg 51
Now: min fps 46, avg 74
2070s, 3700x at 4.25ghz, 3600 CL16
david slayer - Wednesday, June 24, 2020 - linkhi. is it true hardware accelerated gpu scheduling is only for 10 series+ nvidia gpus ? ~ i only got a 970. :(
lilkwarrior - Thursday, June 25, 2020 - linkIt's a DX12 Ultimate feature, so of course 970 doesn't have it. Turing and Amphere were made in conjunction w/ Microsoft to finally realize DX12's original vision that's Windows 10+ only.
Maxwell was supposed to be the swan song of rendering DX11 games really well till proper rendering slowed down by Windows 7 being still prevalent.
Things like variable shading & so on are things your GPU won't support either. That said, you were wise to adopt a TI owner's usual upgrade path of buying every other generation this time around.
Dribble - Monday, June 29, 2020 - linkNot a massively helpful reply. Simple answer is hardware scheduling works on Pascal+, so not just Turing/Amphere, it works on Nvidia 10 series or newer. The rest of what you wrote is not relevant.
06GTOSC - Wednesday, June 24, 2020 - link"At this point no previously-announced games have confirmed that they’ll be using DX12U, though this is just a matter of time, especially with the Xbox Series X launching in a few weeks."
I'm sorry what now?
Ryan Smith - Wednesday, June 24, 2020 - linkSorry. I keep forgetting I'm in the timeline where the Xbox Series X doesn't launch until the fall. Typo corrected!