Skip to content

Clarify location to call vkCmdBindDescriptorSets - #93

Merged
Overv merged 1 commit into
Overv:masterfrom
ElieDeBrauwer:patch-2
Jun 25, 2018
Merged

Clarify location to call vkCmdBindDescriptorSets#93
Overv merged 1 commit into
Overv:masterfrom
ElieDeBrauwer:patch-2

Conversation

@ElieDeBrauwer

Copy link
Copy Markdown
Contributor

The call to vkCmdBindDescriptorSets() needs to happen before vkCmdDrawIndex() otherwise runtime errors might appear like:

Validation(ERROR): msg_code: 62: Object: 0x555e4d0ebac0 (Type = 6) | VkPipeline 0xe uses set #0 but that set is not bound.

Add some extra context to make this more explicit.

The call to vkCmdBindDescriptorSets() needs to happen before vkCmdDrawIndex() otherwise runtime errors might appear like:

Validation(ERROR): msg_code: 62: Object: 0x555e4d0ebac0 (Type = 6) | VkPipeline 0xe uses set #0 but that set is not bound.

Add some extra context to make this more explicit.
@Overv
Overv merged commit 79e46b8 into Overv:master Jun 25, 2018
@Overv

Overv commented Jun 25, 2018

Copy link
Copy Markdown
Owner

Thanks, you're right that it should be clarified.

Overv added a commit that referenced this pull request Mar 8, 2023
Clarify location to call vkCmdBindDescriptorSets
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants