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
  12_2
(DX12 Ult.)
12_1 12_0
GPU Architectures
(Introduced as of)
NVIDIA: Turing
AMD: RDNA2
Intel: Xe?
NVIDIA: Maxwell 2
AMD: Vega
Intel: Gen9
NVIDIA: Maxwell 2
AMD: Hawaii
Intel: Gen9
Ray Tracing
(DXR 1.1)
Yes No No
Variable Rate Shading
(Tier 2)
Yes No No
Mesh Shaders Yes No No
Sampler Feedback Yes No No
Conservative Rasterization Yes Yes No
Raster Order Views Yes Yes No
Tiled Resources
(Tier 2)
Yes Yes Yes
Bindless Resources
(Tier 2)
Yes Yes Yes
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.

Source: NVIDIA

POST A COMMENT

61 Comments

View All Comments

  • Oxford Guy - Wednesday, June 24, 2020 - link

    Companies are really dropping the ball with product naming.

    Once upon a time, if a serious revision occurred it would be coupled with a clear name change.

    DirectX 10 became DirectX 10.1

    But, now everything is "super" and "awesome" and "ultimate". It's both asinine and confusing.
    Reply
  • DigitalFreak - Wednesday, June 24, 2020 - link

    You forgot "turbo" and "extreme". Reply
  • tamalero - Wednesday, June 24, 2020 - link

    GT, ULTRA, DELUXE, GOLD, PLATINUM, XT Reply
  • Byte - Thursday, June 25, 2020 - link

    Millenium, XP, Vista 8.1 Reply
  • close - Thursday, June 25, 2020 - link

    Half of your examples make no sense, Windows Me was named as such for the anniversary of the millennium. That was the whole point, it makes sense. And 8.1... came after 8, pretty straight forward. Vastly different versions, vastly different names. Windows Vista wasn't just called XP Ultimate.

    But I would argue that when it comes to operating systems, brands lasting upwards of a decade, it matters a lot less. The brand-name of the OS is intentionally used as such so it's easily recognizable by regular people and not a confusing mess of 12_1_2.35 type versions. And from 7 on (so for over a decade) it's more than clear, 7>8>8.1>10, with 10 having versions clearly based on launch date (1503, 1909, 2004).

    Now Direct X 12 Ultimate is most definitely not in the same category.
    Reply
  • FlukeLSX - Thursday, June 25, 2020 - link

    lol, I seriously have never met or talked to anyone in the IT field who referred to windows me in a positive way. Reply
  • close - Thursday, June 25, 2020 - link

    You still haven't. I was clearly talking about the chosen *name* and the occasion for which it was chosen. I have to ask, if someone did speak highly of Windows Me are you sure you would have understood what they meant? ;) Reply
  • NZLion - Friday, June 26, 2020 - link

    It could be argued that even if Millennium made sense as a name for the successor to Win98, it only got called that because the ball was dropped in renaming NT5 to release it as 2000. Both Windows lineages would have made better sense from a naming perspective if 2K/ME were switched.
    '95 > '98 > 2000 makes sense. NT, ME, XP are all 2 letter names that would have worked as a set.
    Reply
  • eek2121 - Sunday, June 28, 2020 - link

    Windows 2000 represented a huge attempt to unify Win9x compatibility with the NT line. They did a fantastic job as well. I ran it on my desktop for years with little issue. I expect that they were force to cut a release early for continued business support, while they needed extra time to make the additional improvements that went into XP. They renamed XP from a year because quite frankly it would have been confusing to have Windows 2000 and then Windows 2001.

    Honestly, we need another Windows 2000 right now. A slim, stable, fast Windows-Based OS without any BS.
    Reply
  • MFinn3333 - Friday, June 26, 2020 - link

    It introduced System Restore to the Windows family. Of course, one could argue it introduced the need for it as well. Reply

Log in

Don't have an account? Sign up now