This session provides a comprehensive update on the Vulkan API, its ecosystem, and adoption across various platforms and industries. Ralph Potter, Vulkan Working Group Chair, outlines the release of Vulkan 1.4, which introduces significant core extensions, mandatory features, and raised hardware limits, aiming for a more consistent and ergonomic developer experience. He also details new initiatives to improve documentation, samples, and developer outreach, alongside a formal deprecation model for guiding best practices without removing legacy functionality.
Karen Gantz, LunarG CEO, then presents updates to the Vulkan SDK, highlighting additions like Slang, enhanced validation layers, and the new Vulkan Configurator 3. A major announcement is the development of the "Cosmic Crisp" driver, a Vulkan on Metal Mesa 3D graphics driver for Apple Silicon, which aims for full Vulkan conformance and faster evolution than existing portability solutions.
Andrew Garard discusses Vulkan SC (Safety Critical), a variant of Vulkan designed for applications where failure can be life-threatening, emphasizing offline compilation and strict memory management. Finally, Michael and Henrik from Autodesk showcase the integration of Vulkan into their VRAD and Alias products, demonstrating significant performance and quality improvements over their legacy OpenGL renderer, driven by a GPU-driven approach and hybrid ray tracing. The session concludes with a brief Q&A and a celebration of Kronos's 25th BoF.
Vulkan Ecosystem Update: Roadmap, Tools, and Industry Adoption
0:00 Introduction & Agenda: Ralph Potter (Samsung, Vulkan WG Chair) welcomes attendees, outlines the session: Vulkan updates, SDK, Safety Critical variant, Autodesk support, and Q&A.
1:43 Vulkan Overview & Influence: Vulkan is an explicit, cross-platform graphics and compute API focused on high performance and user control, now influencing future hardware development (with a 5-year outlook for changes).
2:55 Widespread Adoption: Vulkan is supported on all major GPU hardware, engines (Unity, Unreal), and is seeing strong growth in desktop, mobile, and professional graphics.
3:31 Vulkan 1.4 Release: Announced in Dec 2024 at Siggraph Asia, it integrated 16 extensions into core (e.g., dynamic rendering, local read for tile memory, host image copy for CPU-to-GPU streaming), refined floating-point control, and made previously optional features mandatory.
5:00 Raised Hardware Limits: For the first time since its 2016 launch, Vulkan 1.4 significantly raised minimum hardware capabilities, making 28 optional features and 31 properties mandatory to ensure a more consistent and predictable developer experience across platforms.
6:23 Development Cadence: Vulkan uses a two-year cadence for "Roadmap Profiles" (hardware vendors agree on future functionality) and "Core Specs" (integrating mature roadmap features). Vulkan 1.4 largely leveraged features from Roadmap 22 and 24.
9:10 Strong Adoption & MoltenVK: Vulkan 1.4 drivers are available from all major desktop and mobile vendors. MoltenVK (Vulkan on Metal) achieves a 98% pass rate for conformance, indicating strong functional support.
10:15 Android Ecosystem Shift: Vulkan is the recommended Android graphics API, mandatory for new SOCs. Android plans to replace native GLES drivers with Angle (an OpenGL emulation layer on Vulkan) in future versions, expecting improved driver quality.
11:38 Unity Momentum: 48% of new Unity titles now run on Vulkan on Android, as Unity has switched to opt-out Vulkan by default. WebGPU, when rolled out by Android, will also layer on top of Vulkan.
12:57 Enhancing Vulkan Ergonomics: The working group is actively making Vulkan more pleasant to use by designing ergonomic features (e.g., dynamic rendering, unified image layouts, shader objects) and addressing API complexity.
16:02 Improved Accessibility & Outreach: Efforts include a new docs.vulkan.site (integrating all documentation), modernized samples and tutorials, a "Vulkanized" developer event (Feb 9-11 in San Diego), a "Shading Languages Symposium," and an educators forum on Discord.
21:13 Unified Image Layouts: A new extension aims to simplify synchronization by making VK_IMAGE_LAYOUT_GENERAL performant in almost all cases, as many drivers already "no-op" traditional layout transitions.
23:47 Formal Deprecation Model: Vulkan is introducing a formal process to guide developers toward recommended best practices without removing existing functionality, ensuring backward compatibility. Deprecated features are tagged in the spec and flagged by validation layers.
28:53 Vulkan Video Extensions: Recent additions include VP9 decode and intra refresh, with FFmpeg 8 expected to support AV1 encode and VP9 decode using Vulkan. Intra refresh improves stable bit rates and reduces error propagation in video streams.
34:50 LunarG's Role & SDK Updates: Karen Gantz (LunarG CEO) highlights LunarG's role in developing the Vulkan ecosystem, supported by major sponsors like Valve and Google.
36:36 Key SDK Changes (Past Year): LunarG's SDK added Slang, timeline semaphore synchronization validation, Vulkan 1.4 support, auto-upgraded the Windows loader, provided GLSLang as a dynamic library, removed 32-bit libraries (except runtime), added Graphics Reconstruct for Mac, and improved validation layer error messages.
41:13 Vulkan Configurator 3: Released with an improved GUI, enhanced diagnostics, better loader logging, and advanced layer ordering/selection capabilities. It also absorbed the functionality of the older VKVIA tool.
48:48 Cosmic Crisp Driver Announcement: LunarG is developing "Cosmic Crisp," a Vulkan on Metal Mesa 3D graphics driver specifically for Apple Silicon, aiming for full Vulkan 1.3 conformance by Fall.
50:33 Cosmic Crisp Motivation: This new driver aims to achieve true Vulkan conformance on Apple platforms, enable faster driver development (leveraging Mesa's compiler stack), remove external project dependencies (like MoltenVK), and benefit from Mesa's existing framework and community.
53:41 Mac OS SDK Future: The Mac SDK will include both MoltenVK (for older hardware) and Cosmic Crisp, which will be discovered by the Vulkan loader, requiring a paradigm shift for applications that currently statically link MoltenVK.
57:38 Vulkan Safety Critical (SC): Andrew Garard introduces Vulkan SC, a variant for safety-critical systems (e.g., automotive, aviation) that require certification. It mandates offline compilation and pre-allocated memory to guarantee non-failure.
1:02:10 Vulkan SC Use Cases: Ideal for human-machine interaction and computer-accelerated systems where reliability is paramount, contrasting with general-purpose game development.
1:03:47 Migrating to Vulkan SC: Developers can adapt existing Vulkan code by moving compilation offline and pre-allocating all memory resources. Nvidia offers desktop support, and Kronos provides an emulation layer.
1:07:00 Autodesk's Vulkan Adoption: Henrik and Michael from Autodesk discuss their existing Vulkan projects (Pixar's Hydra Storm Render, Aurora) and recent integration into their VRAD and Alias products.
1:12:01 Motivation for Vulkan in VRAD: Autodesk sought to replace an aging OpenGL renderer in VRAD and Alias, which struggled with performance (costly precomputations, CPU dependencies, lack of modern features) and tight scene system integration.
1:13:41 Vulkan Implementation Goals: Key goals included handling high-geometry scenes efficiently, maintaining a forward rendering approach (for arbitrary BLF/shader models), and supporting new features like ray tracing.
1:14:46 GPU-Driven Rendering: Autodesk's Vulkan implementation uses a GPU-driven approach with indirect draws, limiting draw calls for high-polygon scenes and offloading visibility, frustum, and occlusion culling to the GPU.
1:16:17 Hybrid Ray Tracing Features: The first release includes hybrid rendering with ray-traced shadows (ambient occlusion, environment shadows) and single-bounce ray reflections, denoised with NRD or DLSS RR.
1:17:03 Significant Performance & Quality Gains: The new Vulkan renderer achieves much higher frame rates (60 fps vs 34 fps for OpenGL) with superior visual quality (ray-traced effects vs screen space ambient occlusion), closely matching full GI path tracing.
1:18:33 Future VRAD Vulkan Plans: Next steps include multi-GPU support (expecting ~1.8x scaling for VR/MR), moving post-processing effects from OpenGL to Vulkan, better handling of out-of-memory situations, and optimizing parallelization and rendering queue usage.
1:20:00 Q&A Session: Questions covered finer-grain synchronization (no concrete plans), Cosmic Crisp performance (too early, focusing on conformance), Cosmic Crisp implementation details (not Metal 4, public merge to Mesa in Fall upon 1.3 conformance), and hardware image decoding (no current plans but interested in use cases).
1:24:31 Closing Remarks & Celebration: The session concludes with thanks to speakers and attendees, an invitation to a networking event, and a celebration of Kronos's 25th BoF.