Prototype implementation of VK_EXT_descriptor_heap#2805
Prototype implementation of VK_EXT_descriptor_heap#2805HansKristian-Work wants to merge 24 commits intomasterfrom
Conversation
…ths. Triage branch for heap bringup. Production path needs to consider DB + heap paths together at least, which will complicate things a lot. Some things like descriptor QA and friends are not fully implemented on this branch either. Some CPU optimizations are also missing like custom vtables for known descriptor sizes.
|
Will you have to maintain 2 paths for both Buffers, and Heaps? |
|
It will likely be years before the DB path can die 100%. Legacy UPDATE_AFTER_BIND path is now on the chopping block however. Blockers for DB removal are Pascal support and tooling. |
|
its a prototype for a reason bruv |
|
@HansKristian-Work this PR is widely discussed on the internet, so please let us know what kind of feedback would be useful to you at this point to avoid further... misunderstandings ;-) |
|
We are aware there are bugs and we need to debug things on our end for now. This PR is not ready for wide testing yet. |
|
@HansKristian-Work Zenless Zone Zero refuses to just use vkd3d proton for some reason to launch zenless zone zero with dlss rtx dx12 you should use PROTON_USE_NVAPI=1 %command% -use-d3d12 but if you want to use sleepy launcher like i did you need to copy the vkd3d proton files to the prefix of the game. /.local/share/sleepy-launcher/prefix if you want to install zenless zone zero you would need to either get sleepy launcher from flatpak or get it from the aur. Please do try to resolve the issue thank you. |
@Bossiskeyboard This is likely your issue. Stable mesa doesn’t support
@ryzendew Plss check if your driver supports |
|
"Game that doesn't officially support D3D12 and requires command line argument doesn't pick up D3D12" isn't caused by this PR, it's 100% guaranteed to be an issue on your end (even if it's just something silly like also having integrated graphics where D3D12 device creation now fails). It's not actionable here. |
|
Black myth wukong also has this issue for some reason where it just
fallback to dxvk
…On Wed, Jan 28, 2026 at 2:26 AM Philip Rebohle ***@***.***> wrote:
*doitsujin* left a comment (HansKristian-Work/vkd3d-proton#2805)
<#2805 (comment)>
"Game that doesn't officially support D3D12 doesn't pick up D3D12" isn't
caused by this PR, it's 100% guaranteed to be an issue on your end (even if
it's just something silly like *also* having integrated graphics where
D3D12 device creation now fails). It's not actionable here.
—
Reply to this email directly, view it on GitHub
<#2805 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4YIK27SFGMCLW3H34FYU7L4I63XBAVCNFSM6AAAAACS4UARSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMBXGA4TGMRUGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
here is the proton log of black myth wukong |
|
Well yeah you're using a Proton build without the necessary winevulkan patches (there currently is none, needs upstream wine 11.1). Like I said, setup issue on your end, please keep those out of PR discussions. |
|
@HansKristian-Work thanks for the clarification! In such case, would it be possible to temporarily limit commenting ability only to project members and collaborators? @HansKristian-Work, @doitsujin I would also like to say BIG thank you for your amazing work, while I'm here BTW :) |
…n into descriptor-heap-test
…nto descriptor-heap-test
Fixes some issues on older DLSS dlls.
8 participants
Bringup implementation during spec development. This will have to be rewritten to work alongside at least descriptor buffer paths which will be a glorious mess ...
This branch can be used to compare existing DB with new heap paths for performance, correctness, etc. Once sufficient gains are realized, work to productize this stuff could happen.