KhronosGroup / KhronosGroup/Vulkan-ValidationLayers

08608 could be more descriptive

Open
#11,929 5 comments 0 reactions 1 assignee Claimed by @spencer-lunarg View on GitHub
Bug
Dominant language
C++
Stars
1k
Forks
504
Avg merge
11h 35m
Merged PRs (30d)
224

Description

```
VUID-vkCmdDraw-None-08608: vkCmdDraw(): VkPipeline 0x19620000001962 doesn't set up VK_DYNAMIC_STATE_DEPTH_BOUNDS|VK_DYNAMIC_STATE_STENCIL_COMPARE_MASK|VK_DYNAMIC_STATE_STENCIL_WRITE_MASK|VK_DYNAMIC_STATE_STENCIL_REFERENCE|VK_DYNAMIC_STATE_DEPTH_TEST_ENABLE|VK_DYNAMIC_STATE_DEPTH_WRITE_ENABLE|VK_DYNAMIC_STATE_DEPTH_COMPARE_OP|VK_DYNAMIC_STATE_DEPTH_BOUNDS_TEST_ENABLE|VK_DYNAMIC_STATE_STENCIL_TEST_ENABLE|VK_DYNAMIC_STATE_STENCIL_OP, but since the vkCmdBindPipeline, the related dynamic state commands (vkCmdSetDepthBounds, vkCmdSetStencilCompareMask, vkCmdSetStencilWriteMask, vkCmdSetStencilReference, vkCmdSetDepthTestEnable, vkCmdSetDepthWriteEnable, vkCmdSetDepthCompareOp, vkCmdSetDepthBoundsTestEnable, vkCmdSetStencilTestEnable, vkCmdSetStencilOp) have been called in this command buffer.
The Vulkan spec states: If a pipeline is bound to the pipeline bind point used by this command, there must not have been any calls to dynamic state setting commands for any state specified statically in the VkPipeline object bound to the pipeline bind point used by this command, since that pipeline was bound (https://docs.vulkan.org/spec/latest/chapters/drawing.html#VUID-vkCmdDraw-None-08608)
```

This should say exactly which state/command is affected.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.