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

  • jeffkibuule - Saturday, February 7, 2015 - link

    Right, it's a secret to the public, not so much to the engineers.
  • Jumangi - Friday, February 6, 2015 - link

    MS is a much bigger company so the resources they have give a big edge. I also suspect while AMD publicly still supports Mantle they probably aren't doing much for the future as they are smart enough, or I hope they are smart enough, to realize DX 12 makes Mantle irrelevant.
  • toffty - Friday, February 6, 2015 - link

    I wouldn't say Mantle is irrelevant since Directx12 is Windows 10 and Xbox One only. Mantle is for Window < 10, linux and OSX. It will be competing against OpenGL in that space, true, but if it's easier to port applications made with Mantle to Xbox One, Mantle will have a leg up on OpenGL. Mantle also needs to becomes open and nVidia supports it too.
  • Penti - Saturday, February 7, 2015 - link

    There is no mantle for anything else than Windows. PS4 uses it's own API's, Nintendo uses it's own API's, X1 doesn't straight up run the same runtime or API as DX on Windows and already have low-level features, D3D11.X is a superset of D3D/DX11. Games are normally DX/HLSL to begin with, so you don't need to mess around with shaders that much and converting formats. Converting GLSL to HLSL is practical though. Many engines also has their own shader languages and systems making stuff like Mantle's shading language similarities irrelevant. Most will design for something else as their first path than Mantle.
  • Jumangi - Saturday, February 7, 2015 - link

    Fanboys can get mad but Linux and OSX are irrelevant for mainstream gaming. So yes Mantle has no real future and will be forgotten about in a couple of years.
  • bloodypulp - Sunday, February 8, 2015 - link

    Keep on dreaming, Nvidia fangirl. Mantle is coming for SteamOS(Linux). Count on it.
  • yannigr2 - Friday, February 6, 2015 - link

    Mantle was the catalyst to bring DX12 closer. No reason for AMD to spend much resources on Mantle now. Job is done.
  • Notmyusualid - Friday, February 6, 2015 - link

    More or less my thinking too. Best to keep us all on the same page, so to speak.

    Respect to AMD, but let us all join the DX12 train together....
  • AnnonymousCoward - Saturday, February 7, 2015 - link

    Not necessarily. How do you know it wasn't MS's idea even? Look at Khato's post above.
  • tipoo - Friday, February 6, 2015 - link

    What's the support status of Intels chips which are going to get it? I think all Iris models will, and a few of the higher end HD Graphics series parts will. Are they currently supported?

    It would be interesting to see if this could push the Iris Pro 5200 any further. Though this is more for the flip situation of a weak CPU with a strong GPU, rather than this strong CPU with a modest GPU.

Log in

Don't have an account? Sign up now