Dispatch Indirect 2.0 ? #1467 - KhronosGroup/Vulkan-Docs - GitHub

Skip to content Dismiss alert {{ message }} KhronosGroup / Vulkan-Docs Public

• Notifications You must be signed in to change notification settings
• Fork 524
• Star 3.2k

• Code
• Issues 339
• Pull requests 16
• Actions
• Projects
• Wiki
• Security
• Insights

Additional navigation options

Dispatch Indirect 2.0 ? #1467New issueCopy linkNew issueCopy linkOpenOpenDispatch Indirect 2.0 ?#1467Copy linkAssignees

Description

Eichenherzopened on Mar 9, 2021Issue body actions

Hello ! I'm working on a personal game/graphics engine. I don't have mesh shading capabilities so I have to do GPU culling with more "labor". Basically I got a few culling stages: objects -> meshlets -> triangles. The issue I'm encountering is related to different workloads/dispatch sizes: 1 obj_stage thread/invocation will write 1 VkDispatchIndirectCommand which will run for all the meshlets of said object. The thing is that I can't indirectly pass the instance/obj idx like it would be possible for DrawIndirect. So I would like to propose this:

void vkCmdDispatchIndirect( VkCommandBuffer commandBuffer, VkBuffer buffer, VkDeviceSize offset, uint32_t stride ); ``` Thanks in advance !Reactions are currently unavailable

Metadata

Metadata

Assignees

• TomOlson

Labels

No labelsNo labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

You can’t perform that action at this time.