Mantle (API)

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Mantle
280px
Developer(s) AMD, DICE[1]
Development status Beta
Operating system Windows, Linux (announced)[2][3]
Platform x86 and x86-64
Type API for rendering
License Proprietary & freeware
Website www.amd.com/mantle

In computing, Mantle is a low-level rendering API targeted at 3D video games.[4] AMD originally developed Mantle in cooperation with DICE, starting in 2013.[1] Mantle was designed as an alternative to Direct3D and OpenGL, primarily for use on personal computers, although Mantle supports the GPUs present in the PlayStation 4 and in the Xbox One.[1][5] According to AMD, Mantle will make a shift in focus after March 2015 to other areas since the Mantle-derived Vulkan API from the Khronos Group is largely replacing it in the gaming industry.[6] While supported in drivers for two years, the Mantle API itself was not made public until March 2015.[7]

Overview

The draw call improvements of Mantle help alleviate cases where the CPU is the bottleneck. The design goals of Mantle are to allow games and applications to utilize the CPUs and GPUs more efficiently, eliminate CPU bottlenecks by reducing API validation overhead and allowing more effective scaling on multiple CPU cores, provide faster draw routines, and allow greater control over the graphics pipeline by eliminating certain aspects of hardware abstraction inherent to both current prevailing graphics APIs OpenGL and Direct3D.[8]

CPU-bound scenarios

With a basic implementation, Mantle was designed to improve performance in scenarios where the CPU is the limiting factor:

  • Low-overhead validation and processing of API commands[9][10]
  • Explicit command buffer control[9]
  • Close to linear performance scaling from reordering command buffers onto multiple CPU cores[9]
  • Reduced runtime shader compilation overhead[9]
  • AMD claims that Mantle can generate up to 9 times more draw calls per second than comparable APIs by reducing CPU overhead.[11]
  • Multithreaded parallel CPU rendering support for at least 8 cores.[12]

GPU-bound scenarios

Mantle is also designed to improve situations where high resolutions and “maximum detail” settings are used, although to a somewhat lesser degree, as these settings tax GPU resources in a way that is more difficult to improve at the API level. While Mantle provides some built-in features to improve GPU-bound performance, gains in these cases are largely dependent on how well Mantle features and optimizations are being utilized by the game engine. Some of those features include:

  • Reduction of command buffers submissions
  • Explicit control of resource compression, expands and synchronizations
  • Asynchronous DMA queue for data uploads independent from the graphics engine
  • Asynchronous compute queue for overlapping of compute and graphics workloads
  • Data formats optimizations via flexible buffer/image access
  • Advanced Anti-Aliasing features for MSAA/EQAA optimizations[4][9]
  • Native multi-GPU support[4]

[13][14]

Benchmarks

Other claims

Lua error in package.lua at line 80: module 'strict' not found.

  • Easier to port from Mantle to Direct3D 12 than from Direct3D 11 to Direct3D 12[22]
  • At GDC 14 Oxide Games employee Dan Baker stated that Mantle would address fundamental development challenges that could not be addressed by a retrofit of an existing API. It is hard to optimize for the graphics device driver.[23][24][25]
  • At the AMD Developer Summit (APU) in November 2013 Johan Andersson, technical director of the Frostbite engine at DICE praised Mantle for making development easier and enabling developers to innovate.[26]
  • Mantle targets 100K[27]
  • Monolithic Pipeline[4]
  • Pipeline saving and loading[22]
  • Hybrid Resource Model
  • Generalized Resources
  • Control over resource preparation
  • Dynamic flow control without CPU intervention
  • Direct GPU control
  • Reduced runtime shader compilation overhead
  • Better control over the hardware.[11]
  • "All hardware capabilities are exposed through the API."[11]
  • Reduction of command buffer submissions
  • Data formats optimizations via flexible buffer/image access
  • Explicit control of resource compression, expansion, and synchronization
  • Asynchronous DMA queue for data uploads independent from the graphics engine
  • Asynchronous compute queue for overlapping of compute and graphics workloads
  • New rendering techniques

Support

The Mantle API is only available as part of AMD Catalyst, only for Microsoft Windows, but not for other operating systems such as Linux. AMD promised to support their Mantle API only for their graphics cards and APUs which are based on their Graphics Core Next microarchitecture, but not older products based on the TeraScale microarchitecture. As of July 2014 the implementation of the Mantle API is available for the following hardware:[citation needed]

  • certain Radeon HD 7000 Series GPUs
  • certain Radeon HD 8000 Series GPUs
  • certain AMD Radeon Rx 200 Series GPUs ("R7" and "R9")
  • all Steamroller-based "Kaveri" APUs: AMD A10-7000 Series and AMD A8-7000 Series
  • all Jaguar-based "Kabini" and "Temash" APUs: AMD E1-2000 Series, E2-3000 Series, A4-1200 Series, A4-1350, A4-5000 Series, A6-1450, A6-5200, Sempron 2650, Sempron 3850, Athlon 5150, Athlon 5350, etc.
  • all Puma-based "Beema" and "Mullins" APUs: E1 Micro-6200T, A4 Micro-6400T, A10 Micro-6700T, E1-6010, E2-6110, A4-6210, A6-6310, etc.

Game engines

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Video games

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Similar technologies

A set of recent OpenGL 4.4 features, coupled with bindless texturing as an extension, can also substantially reduce driver overhead. This approach, termed by the Khronos Group as "AZDO" (Approaching Zero Driver Overhead) has been shown to achieve substantial performance improvements, approaching those stated for Mantle.[35][36] Nvidia has extended OpenGL with a number of features that further reduce driver overhead.[37]

After details about DirectX 12 were made public, AMD has stated that they fully intend to support DirectX 12, but at the same time they claimed that Mantle "will [still] do some things faster." They have also claimed that due to similarities in the design philosophy of the two APIs, porting games from Mantle to DirectX 12 will be relatively straightforward,[38] and easier than porting from DirectX 11 to 12.[22]

Comments

<templatestyles src="Template:Blockquote/styles.css" />

Much of the work that drivers used to do on an application’s behalf is now the responsibility of the game engine. ... It also means that this work, which must still be done, is done by someone with considerably more information. Because the engine knows exactly what it will do and how it will do it, it is able to make design decisions that drivers could not.

— Firaxis on 2014-04-28, Why We Went With Mantle

Recording and FPS Overlay Software

PC gamers and professionals traditionally used programs such as Fraps and Bandicam to record gameplay, measure game FPS and display FPS overlay, but because Mantle is new, most traditional recording software does not work with new titles while using the new API.

In partnership with AMD, PC gaming community and game recording software maker Raptr have overhauled their client and have since re-branded it as the AMD Gaming Evolved client in conjunction with AMD's Gaming Evolved initiative in the PC gaming space. Out of the partnership, players who install and use the client while in-game can earn points to spend on digital items like games or computer hardware, chat with friends, keep their game library optimized, check for graphics card driver updates, stream their games to Twitch.tv and record gameplay of their own with a built-in GVR, a feature similar to Nvidia Shadowplay software in its own GeForce Experience software that allows users to define a custom buffer length in their game for retroactive game recording with the push of a button so no moment gets missed and users typically do not need expensive hard drive setups to record to. In late 2014, AMD updated the client to finally support the recording and streaming of titles using Mantle.[39] As of its initial update into the client, the Gaming Evolved software is still the only software to officially support the recording and streaming of Mantle enabled games.

Besides Raptr, D3DGear[40] is the only other commercial game recording software that supports Mantle API based games.

See also

  • Direct3D 12 – low-level API from Microsoft
  • Vulkan – low-level API from Khronos, developed from Mantle[41]
  • Glide – another low-level API, by the now defunct 3dfx
  • GNM – low-level API of the PlayStation 4
  • GNMX – high-level API of the PlayStation 4
  • Metal – low-level API for Apple iOS

External links

References

  1. 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 4.2 4.3 Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 9.2 9.3 9.4 Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 11.2 11.3 Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. 22.0 22.1 22.2 Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.