The Vulkan Working Group recently #announced that the open-standard #OpenGL #successor will not hit the end of year release. Vulkan, which arose from AMD’s defunct Mantle API, was expected to roll out before the end of 2015.
Rather than explaining the details, here is the full update from the Vulkan homepage.
“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!”
While this is obviously a disappointment, it is not entirely. The delayed release shows development is close to, if not already finished and testing has to comply with individual companies respective drivers. A big deal for Linux and SteamOS and the negate reports regarding frame rate after launch.
This support is also a given for Nvidia but the more serious contender AMD, has struggled with graphics support to the point where an open-source driver initiative is being put into place.