-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vkquake doesn't launch but triggers interesting errors/limitations.. #4
Comments
Thanks for testing. The limited number of sampler descriptors per heap is difficult to handle for D3D12 and it will probably be a roadblock for all/most commercial applications. I'm not really sure how to fix it, still hoping to find some 'loophole' inside the vulkan spec to implement descriptor heaps better. There certainly is the possibility of emulating command buffers and calculating the required numbers of descriptors at the end with corresponding copies but that's something I would like to avoid. |
Perhaps something to be improved in some future D3D12 version/revision with new samplers per heap tiers with upgraded required minimums.. maybe you should post this issue you are facing on directxtech forums which Microsoft DirectX engineers monitor.. |
Kind of but still would need to support hardware with only a limited number of sampler (looking at nvidia). I personally prefer descriptor heaps (dx12) over descriptor pools (vulkan) as it reflects the hardware better afaik. I'm working on descriptor pool handling for samplers atm, it won't be optimal but that's not priority for now, but rather be target of extensions. |
Fixed on latest master, vkQuake currently blocked on recording command buffers in parallel (software commands buffers in work) and missing dynamic descriptors. |
Can run the menu at least (hearing some sound), but lacking input attachment support (among other stuff). So only a black screen for now |
Hi @msiglreith, unrelated but also note I tested last week UWP and is working well.. thanks.. thanks.. |
yes, my local copy includes the fix. Currently trying to get any debugger working with this example.
Not planned, doesn't seem very high priority to me. I don't think it's used very often.
thanks for testing!
Will try to look into it again, but can't promise anything atm /: |
Hi just testing vkquake..
maybe interesting in the kind of errors it triggers..
I run and see:
but code really continues up to hitting an assert in this code and see( num was 2049) so made a dirty hack I replaced with allocator.alloc(num-1); and continues further see below:
The text was updated successfully, but these errors were encountered: