The State of Mantle, The Drivers, & The Test

Before diving into our long-awaited benchmark results, I wanted to quickly touch upon the state of Mantle now that AMD has given us a bit more insight into what’s going on.

With the Vulkan project having inherited and extended Mantle, Mantle’s external development is at an end for AMD. AMD has already told us in the past that they are essentially taking it back inside, and will be using it as a platform for testing future API developments. Externally then AMD has now thrown all of their weight behind Vulkan and DirectX 12, telling developers that future games should use those APIs and not Mantle.

In the meantime there is the question of what happens to existing Mantle games. So far there are about half a dozen games that support the API, and for these games Mantle is the only low-level API available to them. Should Mantle disappear, then these games would no longer be able to render at such a low-level.

The situation then is that in discussing the performance results of the R9 Fury X with Mantle, AMD has confirmed that while they are not outright dropping Mantle support, they have ceased all further Mantle optimization. Of particular note, the Mantle driver has not been optimized at all for GCN 1.2, which includes not just R9 Fury X, but R9 285, R9 380, and the Carrizo APU as well. Mantle titles will probably still work on these products – and for the record we can’t get Civilization: Beyond Earth to play nicely with the R9 285 via Mantle – but performance is another matter. Mantle is essentially deprecated at this point, and while AMD isn’t going out of their way to break backwards compatibility they aren’t going to put resources into helping it either. The experiment that is Mantle has come to an end.

This will in turn impact our testing somewhat. For our 2015 benchmark suite we began using low-level APIs when available, which in the current game suite includes Battlefield 4, Dragon Age: Inquisition, and Civilization: Beyond Earth, not counting on AMD to cease optimizing Mantle quite so soon. As a result we’re in the uncomfortable position of having to backtrack on our policies some in order to not base our recommendations on stupid settings.

Starting with this review we’re going to use low-level APIs when available, and when using them makes performance sense. That means we’re not going to use Mantle in the cases where performance has clearly regressed due to a lack of optimizations, but will use it for games where it still works as expected (which essentially comes down to Civ: BE). Ultimately everything will move to Vulkan and DirectX 12, but in the meantime we will need to be more selective about where we use Mantle.

The Drivers

For the launch of the 300/Fury series, AMD has taken an unexpected direction with their drivers. The launch driver for these parts is the Catalyst 15.15 driver, AMD’s next major driver branch which includes everything from Fiji support to WDDM 2.0 support. However in launching these parts, AMD has bifurcated their drivers; the new cards get Catalyst 15.15, the old cards get Catalyst 15.6 (driver version 14.502).

Eventually AMD will bring these cards back together in a later driver release, after they have done more extensive QA against their older cards. In the meantime it’s possible to use a modified version of Catalyst 15.15 to enable support for some of these older cards, but unsigned drivers and Windows do not get along well, and it introduces other potential issues. Otherwise considering that these new drivers do include performance improvements for existing cards, we are not especially happy with the current situation. Existing Radeon owners are essentially having performance held back from them, if only temporarily. Small tomes could be written on AMD’s driver situation – they clearly don’t have the resources to do everything they’d like to at once – but this is perhaps the most difficult situation they’ve put Radeon owners in yet.

The Test

Finally, let’s talk testing. For our benchmarking we have used AMD’s Catalyst 15.15 beta drivers for the R9 Fury X, and their Catalyst 15.5 beta drivers for all other AMD cards. Meanwhile for NVIDIA cards we are on release 352.90.

From a build standpoint we’d like to remind everyone that installing a GPU radiator in our closed cased test bed does require reconfiguring the test bed slightly; a 120mm rear exhaust fan must be removed to make room for the GPU radiator.

CPU: Intel Core i7-4960X @ 4.2GHz
Motherboard: ASRock Fatal1ty X79 Professional
Power Supply: Corsair AX1200i
Hard Disk: Samsung SSD 840 EVO (750GB)
Memory: G.Skill RipjawZ DDR3-1866 4 x 8GB (9-10-9-26)
Case: NZXT Phantom 630 Windowed Edition
Monitor: Asus PQ321
Video Cards: AMD Radeon R9 Fury X
AMD Radeon R9 295X2
AMD Radeon R9 290X
AMD Radeon R9 285
AMD Radeon HD 7970
NVIDIA GeForce GTX Titan X
NVIDIA GeForce GTX 980 Ti
NVIDIA GeForce GTX 980
NVIDIA GeForce GTX 780 Ti
NVIDIA GeForce GTX 680
NVIDIA GeForce GTX 580
Video Drivers: NVIDIA Release 352.90 Beta
AMD Catalyst Cat 15.5 Beta (All Other AMD Cards)
AMD Catalyst Cat 15.15 Beta (R9 Fury X)
OS: Windows 8.1 Pro
Meet The Radeon R9 Fury X Battlefield 4
Comments Locked


View All Comments

  • OrphanageExplosion - Wednesday, July 8, 2015 - link

    Anti-aliasing is required for the same reason that no AA still sticks out on 3D titles on an iPad, but in my experience with a 32-inch 4K Asus, post-process AA (SMAA, FXAA) does the job just fine.
  • Oxford Guy - Thursday, July 9, 2015 - link

    "the OS uses 3 GB to 3.5 GB"

    That's insane bloat.
  • Nerdsinc - Monday, July 13, 2015 - link

    I sincerely hope the Overclocking limitations are related to software, a $1000 card with liquid cooling ought to be able to pull higher clocks than that...
  • yhselp - Saturday, July 18, 2015 - link

    Out of curiosity, is it really possible for an Xbox One/PlayStation 4 game to take up over 4GB of memory just for graphics, since just 5GB total are usable for games?
  • Refuge - Thursday, July 23, 2015 - link

    When ported to PC yes. That is because we usualyl get enhanced graphics settings that they do not.

    PC ports are also less efficient because of low budget ports. Which just compounds the issue more.

    Computers have to be more powerful than their console counter parts in order to play equivalent games due to sloppy coding, and enhanced visual options.
  • ludikraut - Thursday, July 23, 2015 - link

    Lack of HDMI 2.0 support totally kills the card for me. Who the heck wants to look at 4K at 30Hz? Guess I'll be sticking with my GTX 970 for a while.

  • eodeot - Friday, July 31, 2015 - link

    You didn't even mention AMDs poor power consumption while idle with multiple monitors or while playing back a video of any kind.

    For some reason AMD thinks that playing back 240p Youtube video requires 3d clocks and thus 3d power consumption, even if the video is paused.

    AMD failed to address it for the past 5 years and you failed to mention it yet again. Nvidia fixed this long ago...
  • JJofLegend - Friday, October 14, 2016 - link

    I recently got an AMD Fury X, but I'm running into an issue with my games. I've tried with Battlefield 4, Crisis 3, Quantum Break, ReCore, The Division, and they all have the same distortion. Any ideas or anyone that can make suggestions? I don't know how to trouble shoot this.
    Here is a screenshot of Crisis 3:

Log in

Don't have an account? Sign up now