Throughout this year we’ve looked at several previews and technical demos of DirectX 12 technologies, both before and after the launch of Windows 10 in July. As the most significant update to the DirectX API since DirectX 10 in 2007, the release of DirectX 12 marks the beginning of a major overhaul of how developers will program for modern GPUs. So to say there’s quite a bit of interest in it – both from consumers and developers – would be an understatement.

In putting together the DirectX 12 specification, Microsoft and their partners planned for the long haul, present and future. DirectX 12 has a number of immediately useful features in it that has developers grinning from ear to ear, but at the same time given the fact that another transition like this will not happen for many years (if at all), DirectX 12 and the update to the underlying display driver foundation were meant to be very forward looking and to pack in as many advanced features as would be reasonable. Consequently the first retail games such as this quarter’s Fable Legends will just scratch the surface of what the API can do, as developers are still in the process of understanding the API and writing new engines around it, and GPU driver developers are similarly still hammering out their code and improving their DirectX 12 functionality.

Of everything that has been written about DirectX 12 so far, the bulk of the focus has been on the immediate benefits of the low-level nature of the API, and this is for a good reason. The greatly reduced driver overhead and better ability to spread out work submission over multiple CPU cores stands to be extremely useful for game developers, especially as the CPU submission bottleneck is among the greatest bottlenecks facing GPUs today. Even then, taking full advantage of this functionality will take some time as developers have become accustomed to minimizing the use of draw calls to work around the bottleneck, so it is safe to say that we are at the start of what is going to be a long transition for gamers and game developers.

A little farther out on the horizon than the driver overhead improvements are DirectX 12’s improvements to multi-GPU functionality. Traditionally the domain of drivers – developers have little control under DirectX 11 – DirectX 12’s explicit controls extend to multi-GPU rendering as well. It is now up to developers to decide if they want to use multiple GPUs and how they want to use them. And with explicit control over the GPUs along with the deep understanding that only a game’s developer can have for the layout of their rendering pipeline, DirectX 12 gives developers the freedom to do things that could never be done before.

That brings us to today’s article, an initial look into the multi-GPU capabilities of DirectX 12. Developer Oxide Games, who is responsible for the popular Star Swarm demo we looked at earlier this year, has taken the underlying Nitrous engine and are ramping up for the 2016 release of the first retail game using the engine, Ashes of the Singularity. As part of their ongoing efforts to Nitrous as a testbed for DirectX 12 technologies and in conjunction with last week’s Steam Early Access release of the game, Oxide has sent over a very special build of Ashes.

What makes this build so special is that it’s the first game demo for DirectX 12’s multi-GPU Explicit Multi-Adapter (AKA Multi Display Adapter) functionality. We’ll go into a bit more on Explicit Multi-Adapter in a bit, but in short it is one of DirectX 12’s two multi-GPU modes, and thanks to the explicit controls offered by the API, allows for disparate GPUs to be paired up. More than SLI and more than Crossfire, EMA allows for dissimilar GPUs to be used in conjunction with each other, and productively at that.

So in an article only fitting for the week of Halloween, today we will be combining NVIDIA GeForce and AMD Radeon cards into a single system – a single rendering setup – to see how well Oxide’s early implementation of the technology works. It may be unnatural and perhaps even a bit unholy, but there’s something undeniably awesome about watching a single game rendered by two dissimilar cards in this fashion.

A Brief History & DirectX 12
Comments Locked

180 Comments

View All Comments

  • Badelhas - Monday, October 26, 2015 - link

    Great article but... This is all very nice and everything but what I really miss is a PC game with a graphics breakthrough, like Crysis when it was lauched back on 2007. None of the games I saw in meantime had that WOW factor. I blame consoles.
  • tipoo - Monday, October 26, 2015 - link

    Star Citizen maybe? Pretty good at bringing top systems to their knees. Though yeah, nothing is the singular leader like Crysis in 2007 was, but that's also a product of every engine getting up to a good level.
  • Nfarce - Monday, October 26, 2015 - link

    My thoughts exactly. The jump from games like HL2 and BF2 to Crysis was like a whole new world. Unfortunately it was such a big hit on performance only the most deep pockets could afford to play that game at full capability. I wasn't able to do it until 2009 when building a new rig, and even then wasn't able to get 60fps at 1080p.
  • Marc HFR - Monday, October 26, 2015 - link

    Hello,

    In AFR, isn't the (small) difference between AMD and NVIDIA on the rendering annoying ?
  • PVG - Monday, October 26, 2015 - link

    Most interesting would be to see results with new+old GPUs. As in, "Should I keep my old card in tandem with my new one?"
  • extide - Monday, October 26, 2015 - link

    With AFR, no. If they do a different type of split where each card gets a different set of work to do, and one card gets more than the other, then yes.
  • Refuge - Tuesday, October 27, 2015 - link

    I was under the impression that it had to be DX12 compatible to work.

    That cuts out 90% of the older GPU's out there.
  • DanNeely - Tuesday, October 27, 2015 - link

    Most of the make it faster stuff in DX12 will work on DX11 capable hardware; the stuff that needs new hardware is relatively incidental. AMD intends to support all GCN cards, NVidia as far back as the 4xx family (excluding any low end rebadges). I'm not sure how far along they are with extending support back that far yet.
  • Refuge - Tuesday, October 27, 2015 - link

    These new Multi-GPU modes will require full DX12 compliant cards though correct?

    And thank you for the info, I was unaware of how far back support was going. I'm pleasantly surprised :D
  • rascalion - Monday, October 26, 2015 - link

    I'm excited to see how this technology plays out in the laptop space with small dGPU + iGPU working together.

Log in

Don't have an account? Sign up now