The Khronos Group have confirmed that Nintendo’s upcoming Switch system will officially support their next generation Vulkan API, in addition to OpenGL 4.5 and OpenGL ES; the updates come to us via their official website, where the Switch is now listed as an official ‘conformant product’ for all three APIs (via WCCFTech).

Vulkan API support in particular should come in handy for developers- Switch will apparently see a major hit to its GPU clock speeds when it is undocked, which means developers will need access to all the power and juice that they can get. A low level, highly efficient API like Vulkan might just be what the doctor ordered in that case.

The Nintendo Switch is currently due to release worldwide in March 2017; exact details about the system, including specifications, a lineup of games for the launch and beyond, price, release date, and more, are currently unknown, but should be revealed come January 12, when Nintendo will be hosting an event to officially take the wraps off of Switch.

Microsoft’s DirectX 12 appears to be the next generation PC gaming graphical API of choice- which makes sense, given the ubiquity of Windows when it comes to PC gaming, and DirectX’s deep integration with Windows. That said, however, there are now alternatives to DirectX, viable alternatives that developers could be using, and open ones, rather than closed proprietary solutions like DirectX is- such as Vulkan.

But possibly because of Windows ubiquity, and because of all the hooks that DirectX has with Windows, or maybe because of all the other pushes for DirectX adoption that Microsoft have made, such as the aggressive push for Windows 10, or bringing DirectX to Xbox One, the fact remains that more and more developers are supporting DirectX 12 over Vulkan, or any other alternative, for their PC games- and this is something that Axel Gneiting, engine programmer at id Software, doesn’t necessarily approve of.

Speaking on Twitter, Gneiting said that developers using DirectX 12 over Vulkan ‘literally makes no sense.’ Elaborating on his stance, and in response to some questions, Gneiting pointed out that with Windows 7 forming a major chunk of the PC gaming market, and with DirectX 12 being incompatible with Windows 7, using DirectX in an attempt to have ‘one codebase’ makes no sense, since developers would need to create two separate ones anyway. He pointed out that the argument that programming for Xbox One and Windows 10 becomes easier by using DirectX 12 is moot too, because DirectX 12 on Windows and on Xbox is very different, necessitating two separate code paths anyway.

He also made some observations about how a lot of the perceived benefits of DirectX 12 are not exclusive to it, noting that both Vulkan and DirectX give similar performance benefits anyway.

I guess my question here is- if that is the case, why does it bother him at all that DirectX is the preferred code path for developers over Vulkan? I suppose there is something to be said for pushing open solutions like Vulkan, over proprietary and closed ones like DirectX, which effectively trap developers in Microsoft’s development ecosystem, so I can see some of his reasoning. But then, I suppose that DirectX benefits because it is not open- it has Microsoft to evangelize it, because Microsoft have a vested investment in seeing it widely adopted. Vulkan being open by definition has no such custodian, and that is why there is no one to pitch it to developers to the extent that Microsoft do with DirectX.

I'm really getting annoyed by everyone adopting DX12 instead of Vulkan even for PC exclusives. This literally makes no sense.

— Axel Gneiting (@axelgneiting) July 1, 2016

@nlguillemot Availability is now not an issue anymore, you will need two code paths on PC for Win 7 compat making the Xbox stuff invalid

— Axel Gneiting (@axelgneiting) July 1, 2016

@nlguillemot Wider HW support? How so? HLSL is the only valid point I can understand

— Axel Gneiting (@axelgneiting) July 1, 2016

@nlguillemot @Isaboll12 This is complete FUD. Vulkan on Windows 7 has no higher driver overhead than on Windows 10.

— Axel Gneiting (@axelgneiting) July 2, 2016

@nlguillemot @Isaboll12 GPUs have virtual memory. All samplers into one giant desc set, index it by push constant, done.

— Axel Gneiting (@axelgneiting) July 2, 2016

@nlguillemot @Isaboll12 Memory residency is managed by WDDM. Page table is updated by driver, virtual addr stays the same. Problem solved.

— Axel Gneiting (@axelgneiting) July 2, 2016

@nlguillemot @Isaboll12 Mantle btw also supported bindless and this worked just fine on Win 7. Don't buy all MS propaganda.

— Axel Gneiting (@axelgneiting) July 2, 2016

@kenpex @baldurk @nlguillemot Fermi isn't supported with DX12 either, Intel Vk drivers are coming

— Axel Gneiting (@axelgneiting) July 2, 2016

@kenpex @baldurk @nlguillemot Xbox needs special path anyway. Xbox DX12 is not Windows DX12. At least not if you want full perf.

— Axel Gneiting (@axelgneiting) July 2, 2016

@AndrewLauritzen @nlguillemot @Isaboll12 I didn't argue that, I'm just saying that perf benefit of DX12 and Vk is massive even without it.

— Axel Gneiting (@axelgneiting) July 2, 2016

GamingBolt spoke to Neil Trevett, who is Vice President for Nvidia’s Mobile Ecosystem and President of the Khronos Group, about Vulkan. Trevett discussed the project’s growth over the past several years, engines like Source 2 taking advantage, it’s role in a cloud-based future, and much more.

"It has been an interesting design challenge to keep the level of abstraction low, but still provide portability across multiple architectures – but with the diverse perspective and expertise of the Vulkan working group we think we have succeeded."

Rashid K. Sayed: Mantle has apparently formed the foundation for Vulkan which has now grown to be something bigger. How did this transformation come about?

Neil Trevett: Mantle started the industry discussion around the need for more explicit 3D and compute APIs and strongly influenced the trio of new generation GPU APIs arriving in the industry: DX12, Metal and Vulkan. AMD also directly contributed Mantle to the Vulkan design process. All three share similar design goals to reduce driver complexity and overhead. Metal has chosen to provide less flexibility in some areas, for example memory management, in order to make programming simpler for mobile developers.

Vulkan is focused on providing maximum flexibility and performance to support advanced applications, middleware and engines. Overall however, they are similar enough that business concerns, such as availability on platform, portability and cross-platform support, will probably outweigh low-level technical considerations of API selection for most developers. Metal was originally designed to solely support AMD hardware but the Vulkan working group has substantially extended and adapted the original Mantle design to create an API that supports a wide diversity of GPU and OS architectures.

Of the three new generation APIs, only Vulkan is non-proprietary and royalty-free, providing application portability to any platform that wishes to support it. We expect that Vulkan will ship on Windows (including Windows XP, 7 and 8, not just Windows 10), Android, Linux and many other platforms. It has been an interesting design challenge to keep the level of abstraction low, but still provide portability across multiple architectures – but with the diverse perspective and expertise of the Vulkan working group we think we have succeeded.

Rashid K. Sayed: We know that Source 2 engine will take advantage of Vulkan. Can you talk more about this and how the API will influence its working?

Neil Trevett: Valve has been one the most active proponents and supporters of Vulkan and they have stated that Vulkan will be acritical component of SteamOS and future Valve games.The key design goals for Vulkan are to reduce driver complexity and overhead to provide a portable and predictable API platform with maximum flexibility and performance as demanded by advanced applications, middleware and engines – and so is an ideal fit for Valve’s needs.

Rashid K. Sayed: Vulkan’s nature as an OS agnostic API makes it extremely viable for mobile developers. Can you talk about the other advantages it presents?

Neil Trevett: Many key hardware trends are being driven from mobile devices and the single Vulkan framework is designed to support, mobile, embedded and desktop systems and there will be no need for a ‘Vulkan ES.’ Some of the key architectural considerations include: tiling renderers are common in mobile and have to be supported as efficiently as immediate mode architectures; a unified memory rather than a traditional PC with a PCI-Express bus between the CPU and GPU enables radically new memory management strategies; and multi-core devices are now very common and so it is essential that Vulkan enables effective multi-threading performance.

Rashid K. Sayed: The layered design of Vulkan enables multiple IHVs to plug into a common, extensible architecture for code validation, debugging and profiling during development without impacting production performance; this layering flexibility is expected to catalyze strong innovation in cross-vendor GPU tools.

Neil Trevett: It is also very significant that Vulkan and OpenCL 2.1 are now sharing a core intermediate language technology called SPIR-V, the Khronos Standard Portable Intermediate Representation, which is the first IR to natively support both graphics and parallel programming. SPIR-V splits the compiler chain, enabling high-level language front-ends to emit programs in a standardized intermediate form to be ingested by Vulkan or OpenCL drivers.

"Vulkan, a new generation explicit API, has simpler drivers which means reduced driver overhead resulting in higher performance for CPU-limited applications. For applications that are CPU limited, which happens on desktop, and even more on mobile, end users should notice better performing applications with less stuttering and halting. "

Eliminating the need for a built-in high-level language source compiler significantly reduces GPU driver complexity and will enable a diversity of language front-ends. Additionally, a standardized IR provides a measure of shader IP protection, accelerated shader load times and enables developers to use a common language front-end, improving shader reliability and portability across multiple implementations.

Rashid K. Sayed: What advantages does Vulkan present to current gen GPUS and CPUS? How will this improve the game development process as compared to writing code for Mantle and DirectX 11?

Neil Trevett: Vulkan will run on any GPU hardware that supports OpenGL ES 3.1 and OpenGL 4.X and up – so many devices and platform will see an increase in application and game performance with just a driver update.

Vulkan, a new generation explicit API, has simpler drivers which means reduced driver overhead resulting in higher performance for CPU-limited applications. For applications that are CPU limited, which happens on desktop, and even more on mobile, end users should notice better performing applications with less stuttering and halting.

There will also be fewer functional differences between multiple GPU vendors’ implementations for faster, easier ports. Another fundamental advantage of handing the application more control is that the driver has to do less ‘behind the scenes’ management – resulting in much more reliable and predictable performance which doesn’t hit unexpected road bumps as the driver undertakes complex housekeeping.

Rashid K. Sayed: In that regard, how does the multi-threading support of Vulkan present an advantage over current APIs?

Neil Trevett: In the end, the multi-threaded work creation was the one architectural aspect that was not fixable with OpenGL’s monolithic context management system. With Vulkan, developers can construct any number of graphics, compute and DMA command buffers in memory, with the application having the freedom to use any thread management and synchronization it wants, before command buffers get submitted to a command queue.

Note that Vulkan has a general graphics and compute queue model that can be extended to more heterogeneous processing capabilities in the future. This architecture enables multi-core CPUs to assemble much more work for the GPU: enabling the full power of the GPU to be unleashed in many more applications.

Rashid K. Sayed: There is a lot of confusion and discussion regarding how Vulkan is different from DirectX 12. My readers know that it’s platform agnostic but given that both are set out to achieve the same thing, why is there a need for a separate API?

Neil Trevett: The OpenGL family – which includes OpenGL, OpenGL ES and WebGL – provides access to GPU acceleration on billions of devices and platforms, but we welcome healthy competition between open standard and proprietary APIs as it pushes both forward. In general, independent software vendors benefit from having to code, optimize and support their applications, libraries and engines on a minimum number of low-level APIs.

Hardware vendors can also reduce costs, in general, by having to support a minimum number of low-level APIs. Hence the overall desire to prevent industry fragmentation through open standards – and the wide industry support for Vulkan from both the hardware and software communities. DX12 is only available on Windows, and only Windows 10.

"Yes, Vulkan and DX12 take a broadly similar approach. Both APIs mean that application developers have to take more control, which is more involved in some ways, but in the real world developers spend much of their development time battling driver inconsistencies and unpredictability…"

Rashid K. Sayed: We recently spoke to a developer who believes that it will benefit developers if Vulkan makes it way to the PS4. The PS4 already has his own custom API. Do you think Vulkan will eventually make it to the console? And what kind of benefits it could potentially have given that PS4’s API and Vulkan are built from the same foundation?

Neil Trevett: Khronos cannot comment on any console vendor plans – but I agree that Vulkan is potentially very interesting for consoles – especially if AAA games engines have optimized Vulkan ports – it will mean that considerable AAA content could come easily to a platform that supports Vulkan.

Rashid K. Sayed: Cloud gaming seems to be rage these days on consoles and PCs. Is Khronos doing something that area?

Neil Trevett: PC instances in the cloud need the same cutting edge APIs to drive the GPU as if the application is running games locally. The performance and efficiency of Vulkan is just as important in the cloud as on your PC or console.

Rashid K. Sayed: Staying on the topic on cloud, there is a theory that static hardware such as consoles can be made more powerful by offloading stuff to the cloud. For example procedurally generated terrain is one of the most complex rendering that a developer can implement. Do you think Vulkan can help in such a scenario?

Neil Trevett: Yes – that is an interesting area for research and innovation. Vulkan can provide the same API for graphics and compute on the local device and the cloud – simplifying sophisticated load balancing of apps between local and remote resources.

Rashid K. Sayed: Continuing on from DirectX 12’s performance increase over DX11, how do you think AMD can equip Mantle in the coming days to offer a significant bump in performance compared to its current state?

Neil Trevett: AMD are not evolving Mantle as a production API – they are focusing all their effort on Vulkan and DX12 and have advised developers to do the same (head here for more information).

Rashid K. Sayed: DirectX 12 gives the developers plenty of control regarding how they want their applications to run. But this also means that there is a lot of top level stuff that the developer has to decide and implement. Does Vulkan work the same?

Neil Trevett: Yes, Vulkan and DX12 take a broadly similar approach. Both APIs mean that application developers have to take more control, which is more involved in some ways, but in the real world developers spend much of their development time battling driver inconsistencies and unpredictability – and in that respect that a Vulkan app could be actually easier to get fully debugged, and reliably performing across multiple platforms. For developers that don’t need all of Vulkan’s flexibility, there will be utility libraries and engines that that will layer over Vulkan to provide a much higher and familiar level of programming.

"Vulkan is the future of cross-platform graphics and compute – but Khronos is firmly committed to fully support and evolve the existing OpenGL, OpenGL ES and OpenCL APIs for as long as there is an industry need and demand."

Rashid K. Sayed: What is Apple’s reaction to Vulkan? Do you think they will drop Metal in favour of Vulkan?

Neil Trevett: Apple is a Khronos member but we cannot comment on whether Apple plans to support Vulkan on iOS or MacOS though they are free to do so if they wish. No application developer will be able to use Metal exclusively unless their business needs are met by shipping only on Apple and not on any other platform.

Rashid K. Sayed: What’s on the cards next for Vulkan? Could you tell us about any upcoming features you’re currently working on?

Neil Trevett: Because time is of the essence, we are ensuring that Vulkan 1.0 delivers all the essentials for a new generation API and sets a firm foundation for future evolution – but deferring any non-essential features to future versions. In any case we need real-world experience and feedback from Vulkan 1.0 to make data driven decisions for potential new features.

Rashid K. Sayed: What can we expect to hear more information on the API? Furthermore are there any plans to reveal any hard data and benchmarks results?

Neil Trevett: Vulkan is on schedule to have specs and implementations before the end of the year. Benchmark data will start to appear once first public implementations are available. The Vulkan working group started work in June 2014 when it became clear that industry was ready for a ground-up re-design of GPU APIs. There is a lot of energy and effort going into defining Vulkan – it is not a normal, multi-year, standardization effort – it will be completed much faster than that…

Rashid K. Sayed: Is there anything else you want to tell our readers before I let you go?

Neil Trevett: Vulkan is the future of cross-platform graphics and compute – but Khronos is firmly committed to fully support and evolve the existing OpenGL, OpenGL ES and OpenCL APIs for as long as there is an industry need and demand. These APIs are pervasively available on billions of devices and will ship for many, many years to come. With Vulkan, Khronos has now added to a rich mix of technologies so that we can evolve the roadmap for open standard graphics and compute. Khronos is dedicated to continuing to ensure that developers are able to access APIs with cutting edge capabilities and wide portability to help maximize the commercial success of their applications.

Even as Microsoft is gearing up to launch DirectX 12, and to hopefully make it the industry standard API for game development, especially on PC and Xbox platforms, OpenGL, which has steadily gained in popularity as non Microsoft platforms have correspondingly become targets for game development- such as PlayStation, Nintendo, Mac, Linux, and mobiles and smartphones- has continued to make strides. Now, the next major update to OpenGL is due to be unveiled (and presumably go head to head with DirectX 12 in a battle of the APIs), and Valve will be the one to unveil it at GDC next month.

We know this because of the panel titled glNext: The Future of High Performance Graphics, which Valve will be presenting.

“Join us for the unveiling of Khronos’ glNext initiative, the upcoming cross-platform graphics API designed for modern programming techniques and processors. glNext will be the singular choice for developers who demand peak performance in their applications,” they say.

“We will present a technical breakdown of the API, advanced techniques and live demos of real-world applications running on glNext drivers and hardware.”

So, of course, assuming that the next iteration of OpenGL is as accomplished and capable as DirectX 12 is, then the ball should be right back in Microsoft’s court.

All of this said, I do hope that this does not take away from Valve’s Steam Machines, which are allegedly due for a (yet another) re-reveal at GDC. We’ll see.