Skip to content
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

Use correct device feature in multi draw indirect sample documentation #1271

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions samples/performance/multi_draw_indirect/README.adoc
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
////
- Copyright (c) 2021-2023, Holochip Corporation
- Copyright (c) 2021-2025, Holochip Corporation
-
- SPDX-License-Identifier: Apache-2.0
-
Expand Down Expand Up @@ -49,7 +49,7 @@ Each command contains the vertex offset, index offset, and index count.
To control whether a sub-mesh is drawn, the instance count is set to either 0 or 1.
Alternatively, the draw command could be completely removed from the array.

If = device supports multi-draw indirect (`VkPhysicalDeviceFeatures2::bufferDeviceAddress`), then the entire array of draw commands can be executed through a single call to `VkDrawIndexedIndirectCommand`.
If the device supports multi-draw indirect (`VkPhysicalDeviceFeatures2::multiDrawIndirect`), then the entire array of draw commands can be executed through a single call to `VkDrawIndexedIndirectCommand`.
Otherwise, each draw call must be executed through a separate call to `VkDrawIndexIndirectCommand`:

[,cpp]
Expand Down
Loading