Vulkan specification complete, release imminent

Great news! The Khronos Vulkan Working Group just announced that the specification is complete (and has entered the legal review process) and the release is imminent.

Though the initial time frame of 2015 was missed (by a bit), this should mean that Vulkan will be ready for launch in early 2016. This will include SDKs for all supported platforms, production ready drivers from several IHV, resources, tools, demos, examples and much more.

Here’s the statement from the official Vulkan page :

Vulkan Working Group Update - December 18th 2015

We have some good news and some bad news.  The year-end target release date for Vulkan will not be met.  However, we are in the home stretch and the release of Vulkan 1.0 is imminent!

Here is a more detailed update…

The Vulkan specification is complete and undergoing legal review and final polishing. The Vulkan conformance tests are being finalized and multiple member companies are preparing drivers for release. Implementation feedback is the vital final stage of making any Khronos specification ready for primetime, and the Vulkan 1.0 specification will be published when the first conformant implementations are confirmed.

Work is also progressing to complete Vulkan SDKs for Windows, Android and Linux. Google has upgraded to Promoter membership and is now on the Khronos Board to help steer Vulkan strategy for Android and the wider industry.

There is considerable energy driving the work to bring you Vulkan. We are planning Vulkan sessions and demos at key industry events throughout the year. We are excited about the emerging Vulkan ecosystem that will create new business opportunities for the graphics and compute industry.

Vulkan will set the foundation for graphics and compute APIs for years to come and so Khronos is taking the time needed to do this right – and the Vulkan 1.0 release is near!

The Khronos Vulkan Working Group

If you’re doing something related to Vulkan please feel free to add your links to the resource page via the Khronos git repository.