No, it’s currently not public. A video link has been posted before:
It explains the underlying problem but they explicitly state that all of the work is currently not public, and no details will be published at this point of time. So at least the problem is well understood and developers are working on it.
Here are some timestamps extracted via AI:
| Timestamp | Description |
|---|---|
| 00:27:30 | Introduction to the new heap-based descriptor model. |
| 00:27:35 | Mention of recently receiving approval to discuss the topic. |
| 00:27:40 | Statement that the extension/details have not been publicly released yet. |
| 00:30:05 | Note on Khronos release timelines and the focus on “getting it right.” |
So the idea is to only publish the details after they got “things right”. And that’s probably a good idea to not get early bad implementations by early adopters. Since NVIDIA is a gold sponsor, I’d expect that NVIDIA is involved in this discussion - and they neither would publish any details here just yet. So we don’t even have to ask about it. It’s coming “soon-ish” - that probably means somewhere during Q1/Q2 2026. I’m pretty sure Valve will push this, too. And NVIDIA has always been pretty fast implementing new Vulkan extensions in the Vulkan developer driver. So by the end of year, we may get it in the stable driver including support in DXVK and vkd3d.