KhronosGroup / KhronosGroup/Vulkan-ValidationLayers

BestPractices-ImageBarrierAccessLayout not clear if AccessMask or ImageLayout

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

Description

```
Validation Warning: [ BestPractices-ImageBarrierAccessLayout ] | MessageID = 0xf35d019f
vkCmdPipelineBarrier2(): pDependencyInfo->pImageMemoryBarriers[4] image is VkImage 0x130000000013[Depth] and accessMask is VK_ACCESS_2_COLOR_ATTACHMENT_WRITE_BIT|VK_ACCESS_2_DEPTH_STENCIL_ATTACHMENT_READ_BIT|VK_ACCESS_2_DEPTH_STENCIL_ATTACHMENT_WRITE_BIT, but for layout VK_IMAGE_LAYOUT_DEPTH_STENCIL_ATTACHMENT_OPTIMAL expected accessMask are VK_ACCESS_2_DEPTH_STENCIL_ATTACHMENT_READ_BIT|VK_ACCESS_2_DEPTH_STENCIL_ATTACHMENT_WRITE_BIT.
Objects: 1
[0] VkImage 0x130000000013[Depth]
```

When using Depth Resolve Image this message becomes unclear if issue is the access mask or the layout

This should provide a better message

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.