Anyhow, Vulkan will survive for the same reason as Linux; no one truly trusts MS, Apple, Sony, etc...
Anyhow, Vulkan will survive for the same reason as Linux; no one truly trusts MS, Apple, Sony, etc...
Somehow there is this urban myth about Sony caring about Khronos APIs, when they only did such a thing with the Playstation 1, using GL ES 1.0 + Cg as alternative to their own API, as the adoption was very low, they eventually dropped it.
Even on the Switch, if you want all the low level features, you are better served using NVN.
By the way here is one of the public sources on the matter,
> Vulkan API: We recommend targeting Vulkan as your primary graphics API for best performance and battery life. If you use an engine like Unity or Unreal, enabling Vulkan in your build for all users will result in the highest performance/longevity. (Note: Proton includes a DirectX-to-Vulkan translation layer. If your game or engine has high-quality DirectX support but no Vulkan support, it's likely that this automated translation layer will exceed the performance of doing a custom Vulkan implementation.)
https://partner.steamgames.com/doc/steamdeck/recommendations
Programming with Vulkan is like asking everyone to be a device driver developer and a GPU hardware engineer.
The recent webinar on profiles felt like a joke, manually jungling JSON files to generate bindings for specific profiles, meanwhile on proprietary 3D APIs that is a simple set of API calls.
Khronos still doesn't get what is a productive SDK development experience.
Yes, that's the point. To use a programming language analogy, OpenGL is C++ and Vulkan is LLVM.
Portable game code has survived with middleware for ages.
Vulkan is basically a bullet point on the API plugin selection dialog.
That doesn't add up. The PlayStation came out in 1994, and was followed up by the Playstation 2 in 2000. OpenGL ES 1.0 wasn't released until 2003.
Engine is a totally different topic as they do have experts to just support both in parallel.
And when you look how DirectX is the default for tons of games on windows you wouldn't say what you said.
The DirectX sdk and documentation is also really good.
Generally, Vulkan yields better performance than directly-equivalent DirectX code. Even since the early days of commercial Vulkan use (2016), the performance uplift has been a notable upside. However, Vulkan code is generally more difficult to write than DirectX (or even OpenGL and Metal, AFAIK), which is part of the price you pay for portability. High-level libraries were expected to paste over these issues, but this infrastructure is still in it's infancy. Ironically, one of the best uses for Vulkan right now is acting as a sort of intermediate representation for DirectX/Metal API calls.
Consoles are far from a driving factor for Vulkan other than the need for these engines to abstract anyway.