About a year and a half ago AMD kicked off the public half of a race to improve the state of graphics APIs. Dubbed "Mantle", AMD’s in-house API for their Radeon cards stripped away the abstraction and inefficiencies of traditional high-level APIs like DirectX 11 and OpenGL 4, and instead gave developers a means to access the GPU in a low-level, game console-like manner. The impetus: with a low-level API, engine developers could achieve better performance than with a high-level API, sometimes vastly exceeding what DirectX and OpenGL could offer.

While AMD was the first such company to publicly announce their low-level API, they were not the last. 2014 saw the announcement of APIs such as DirectX 12, OpenGL Next, and Apple’s Metal, all of which would implement similar ideas for similar performance reasons. It was a renaissance in the graphics API space after many years of slow progress, and one desperately needed to keep pace with the progress of both GPUs and CPUs.

In the PC graphics space we’ve already seen how early versions of Mantle perform, with Mantle offering some substantial boosts in performance, especially in CPU-bound scenarios. As awesome as Mantle is though, it is currently a de-facto proprietary AMD API, which means it can only be used with AMD GPUs; what about NVIDIA and Intel GPUs? For that we turn towards DirectX, Microsoft’s traditional cross-vendor API that will be making the same jump as Mantle, but using a common API for the benefit of every vendor in the Windows ecosystem.

DirectX 12 was first announced at GDC 2014, where Microsoft unveiled the existence of the new API along with their planned goals, a brief demonstration of very early code, and limited technical details about how the API would work. Since then Microsoft has been hard at work on DirectX 12 as part of the larger Windows 10 development effort, culminating in the release of the latest Windows 10 Technical Preview, Build 9926, which is shipping with an early preview version of DirectX 12.


GDC 2014 - DirectX 12 Unveiled: 3DMark 2011 CPU Time: Direct3D 11 vs. Direct3D 12

With the various pieces of Microsoft’s latest API finally coming together, today we will be taking our first look at the performance future of DirectX. The API is stabilizing, video card drivers are improving, and the first DirectX 12 application has been written; Microsoft and their partners are finally ready to show off DirectX 12. To that end, today we’ll looking at DirectX 12 through Oxide Games’ Star Swarm benchmark, our first DirectX 12 application and a true API efficiency torture test.

Does DirectX 12 bring the same kind of performance benefits we saw with Mantle? Can it resolve the CPU bottlenecking that DirectX 11 struggles with? How well does the concept of a low-level API work for a common API with disparate hardware? Let’s find out!

The Current State of DirectX 12 & WDDM 2.0
Comments Locked

245 Comments

View All Comments

  • Stuka87 - Friday, February 6, 2015 - link

    Very promising from the looks of it. Should help out a lot with some of these newer games.

    One thing I wish you would have done was to show kernel times on the CPU graphs. Would be nice to know how much of that CPU was userspace, and how much was kernel.
  • unacomn - Friday, February 6, 2015 - link

    Very promising results for future games.
    I would love to see a test with AMD CPUs as well, curious if the architecture of the current AM3+ and FM2 CPUs benefits much in terms of performance from this.
  • Stuka87 - Friday, February 6, 2015 - link

    For Mantle they benefit more, as they are a larger bottleneck. With my old AMD system (965BE @4GHz with an HD7950) BF4 was unplayable with DirectX11, but with Mantle it ran pretty decent.
  • mikato - Friday, February 6, 2015 - link

    It seems really strange to read that you couldn't run BF4 with those specs. I play the newest Call of Duty games with my 965BE (not overclocked) and my HD6950 unlocked to 6970. Settings are turned down a bit with my 1920x1200 resolution, but it runs well enough to play as twitchy fast as I need to be. I am in the market for an upgrade soon though so I can turn the settings back up.
  • shing3232 - Friday, February 6, 2015 - link

    BF4 are way more demanding than COD because there are too much object in MP especially when you playing a 64 player server.
  • XFR - Friday, February 6, 2015 - link

    Are these articles edited or proofread?
  • JarredWalton - Friday, February 6, 2015 - link

    Sometimes. I did make a reading/editing pass after this was posted, so if there are still errors let us know.
  • Jtaylor1986 - Friday, February 6, 2015 - link

    My only question is how is Mantle still in beta at this stage of the game? Microsoft seems to have developed DirectX 12 much more quickly than AMD has developed Mantle
  • jeffkibuule - Friday, February 6, 2015 - link

    It's more likely they were unknowingly developed side-by-side, but DirectX 12 was unveiled much later. Certainly if there were new DX12-only features that require special hardware, some AMD engineers would have wondered why Microsoft was requesting XYZ when developing the Xbox One SoC vs. PS4 (not that those two groups or general engineering teams would have been able to compare notes).
  • Khato - Friday, February 6, 2015 - link

    FYI - public announcement comes a long, long time after the initial specification. More importantly, directx is more of a collaboration between the players involved (Microsoft, Intel, NVIDIA, AMD) any more, not something that Microsoft develops in secret and only shares once it's finalized. Which is to say that AMD has known about the direction for directx 12 for over 2 years now.

Log in

Don't have an account? Sign up now