Feature request : add DispatchMeshIndirect & DispatchRaysIndirect support

Question

Feature request : add DispatchMeshIndirect & DispatchRaysIndirect support

THISISAGOODNAME opened this issue 3 years ago · 6 comments

Or more universal api like dx12 ExecuteIndirect .

:)

Answer 1 · 2021-03-27T07:52:53.000Z

I thought about ExecuteIndirect, but unfortunately Vulkan does not have such api. VK_NV_device_generated_commands can be the equivalent of ExecuteIndirect, but it is not a final version yet, for example there is no DispatchRaysIndirect. I prefer to wait for KHR version.

Answer 2 · 2021-03-27T07:57:00.000Z

Another limitation is that Vulkan do not provide count version for all indirect calls. It does not allow emulating subset of ExecuteIndirect.

Answer 3 · 2021-03-27T08:00:21.000Z

Anyway, thank you for your feature request. I will add DispatchMeshIndirect/DispatchRaysIndirect support.

Answer 4 · 2021-03-27T11:06:02.000Z

DirectX 12 and Vulkan have different memory layout for arguments. D3D12_DISPATCH_MESH_ARGUMENTS vs VkDrawMeshTasksIndirectCommandNV and D3D12_DISPATCH_RAYS_DESC vs VkTraceRaysIndirectCommandKHR. It will require arguments patch on the gpu side.
Sorry, I want to postpone this feature request until there is a way to do it without arguments buffer patching.

Answer 5 · 2021-03-27T12:07:31.000Z

I created KhronosGroup/Vulkan-Docs#1486 I hope it affects something.

Answer 6 · 2021-03-27T13:27:51.000Z

DirectX 12 and Vulkan have different memory layout for arguments. D3D12_DISPATCH_MESH_ARGUMENTS vs VkDrawMeshTasksIndirectCommandNV and D3D12_DISPATCH_RAYS_DESC vs VkTraceRaysIndirectCommandKHR. It will require arguments patch on the gpu side.
Sorry, I want to postpone this feature request until there is a way to do it without arguments buffer patching.

Thank you anyway.