[dogma1138]

Because DX12 gives you support for 2 out of the 3 major AAA platforms. Sony seems to have no inclination of supporting Vulcan as a native API for the PS4/PS4pro.

Vulkan is also not Mantle, it's similar to the original Spec which was written by Johan Andersson from DICE. AMD did give Khronos the spec but there isn't some shared code implementation for Vulkan that is based on Mantle, there isn't a common shared library in general as the implementation for each IHV/System is proprietary.

Vulkan is still a camel, not as much as OpenGL but a camel nonetheless, it's currently quite behind DX as far as featureset goes and Vulkan Next which would add needed features such as mGPU support seems lag into late 2017.

Vulkan is a good alternative but it already shows some signs of getting it self into the same position that OpenGL found it self.

It's also worth noting that DX12 development has nothing to do with Mantle, it's a continuation of the Xbox 360 API and effectively the mature version of the API developed for the Xbox One.

[Tuna-Fish]

> It's also worth noting that DX12 development has nothing to do with Mantle, it's a continuation of the Xbox 360 API and effectively the mature version of the API developed for the Xbox One.

... significant parts of DX12 are a carbon copy of Vulcan. Are you saying they ended up with the exact same solutions, including things like error codes that are entirely arbitrary choices, by accident?

DX12, and the Xbox One API was NOT developed from the Xbox 360 API. It's based on Mantle. As is Vulkan.

[dogma1138]

Vulkan was influenced by DX12 designs not the other way around, Vulkan is currently lagging behind. Mantle was written by Johan Andersson and as a result of DICE working on FB3 for the XboxOne.

The Vulkan spec diverges quite a bit from Mantle and is considerably closer to DX12, and again this isn't because DX12 somehow copies Vulkan, but because quite a few of the people involved like Niklas Smedberg and Aras Pranckevicius have been working with the XboxOne/PS4 for quite a while.

[XzetaU8]

https://twitter.com/repi/status/446718535616585730

Direct3D 12 blog with some more details: http://blogs.msdn.com/b/directx/archive/2014/03/20/directx-1... … You may recognize the design ;)

https://twitter.com/renderpipeline/status/581086347450007553

I had a déjà vu while reading in the #DirectX12 specs… #mantle

[dogma1138]

Look into the history of Mantle, why Johan Andersson wrote the spec as it was, gamedev is a good place to start.

[XzetaU8]

While you'll keep repeating unfounded vague claims, and I'm talking for your original claim that DX12 influenced Vulcan/Mantle I'll keep posting links that prove the exact opposite.

> We’ve spoken to several sources with additional information on the topic who have told us that Microsoft’s interest in developing a new API is a recent phenomenon, and that the new DirectX (likely DirectX 12) will substantially duplicate the capabilities of AMD’s Mantle.

https://www.extremetech.com/gaming/177407-microsoft-hints-th...

[XzetaU8]

Stop spreading misinformation, Vulkan was not influenced by DX12.

> Vulkan is derived from and built upon components of AMD's Mantle API, which was donated by AMD to Khronos with the intent of giving Khronos a foundation on which to begin developing a low-level API that they could standardize across the industry, much like OpenGL.

https://en.wikipedia.org/wiki/Vulkan_(API)

[dogma1138]

It's not misinformation, AMD delivered the mantle spec to Khronos, but you are ignoring the fact the mantle spec was nearly single handedly written by Johan Andersson and was derived from his work on building Frostbite for consoles. Vulkan then was influenced by quite a few other people from Unity, Epic and Valve.