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

[0.4] Fix depth attachment transitions #459

Closed
kvark opened this issue Jan 15, 2020 · 1 comment
Closed

[0.4] Fix depth attachment transitions #459

kvark opened this issue Jan 15, 2020 · 1 comment
Labels
help required We need community help to make this happen. type: bug Something isn't working

Comments

@kvark
Copy link
Member

kvark commented Jan 15, 2020

[2020-01-15T18:03:41Z ERROR gfx_backend_vulkan] 
VALIDATION [VUID-VkImageSubresource-aspectMask-parameter (0)] : vkCmdPipelineBarrier(): Depth-only image formats must have the VK_IMAGE_ASPECT_DEPTH_BIT set. The Vulkan spec states: aspectMask must be a valid combination of VkImageAspectFlagBits values (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-VkImageSubresource-aspectMask-parameter)
object info: (type: IMAGE, hndl: 60)

[2020-01-15T18:03:41Z ERROR gfx_backend_vulkan] 
VALIDATION [UNASSIGNED-CoreValidation-DrawState-InvalidImageLayout (0)] : Submitted command buffer expects VkImage 0x3c[]  (subresource: aspectMask 0x2 array layer 0, mip level 0) to be in layout VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL--instead, current layout is VK_IMAGE_LAYOUT_DEPTH_STENCIL_ATTACHMENT_OPTIMAL.
object info: (type: COMMAND_BUFFER, hndl: 94914754889856)

[2020-01-15T18:03:42Z ERROR gfx_backend_vulkan] 
VALIDATION [UNASSIGNED-CoreValidation-DrawState-InvalidImageLayout (0)] : Submitted command buffer expects VkImage 0x3c[]  (subresource: aspectMask 0x2 array layer 0, mip level 0) to be in layout VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL--instead, current layout is VK_IMAGE_LAYOUT_DEPTH_STENCIL_ATTACHMENT_OPTIMAL.
object info: (type: COMMAND_BUFFER, hndl: 94914754886576)

This is very likely not a problem in master, but we need to make a patch for the released version.

@kvark kvark added type: bug Something isn't working help required We need community help to make this happen. labels Jan 15, 2020
@kvark
Copy link
Member Author

kvark commented Jan 20, 2020

I think it's actually a consequence of #458 bug. Once the STORAGE usage is correctly identified, I'm no longer seeing these errors.

@kvark kvark closed this as completed Jan 20, 2020
kvark pushed a commit to kvark/wgpu that referenced this issue Jun 3, 2021
459: Fix typo r=cwfitzgerald a=JMS55



Co-authored-by: JMS55 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help required We need community help to make this happen. type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant