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

Vulkan: Fix the attachment image layout tracking #2455

Merged

Conversation

Qining
Copy link
Contributor

@Qining Qining commented Dec 13, 2018

The loadAttachment and storeAttachment subroutine should not be labelled
with @spy_disabled, as we need to track the attachments' layout

The loadAttachment and storeAttachment subroutine should not be labelled
with @spy_disabled, as we need to track the attachments' layout
@@ -1482,8 +1482,7 @@ func (sb *stateBuilder) createImage(img ImageObjectʳ, imgPrimer *imagePrimer) {
attBits := VkImageUsageFlags(VkImageUsageFlagBits_VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT | VkImageUsageFlagBits_VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT)
storageBit := VkImageUsageFlags(VkImageUsageFlagBits_VK_IMAGE_USAGE_STORAGE_BIT)

isDepth := (img.Info().Usage() & VkImageUsageFlags(VkImageUsageFlagBits_VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT)) != 0
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isDepth was used for debugging depth/stencil image priming by rendering. It does not imply depth stencil images with TRANSFER_DST_BIT set can not be primed by buffer copy.

@Qining Qining closed this Dec 13, 2018
@Qining Qining deleted the fix-image-layout-tracking-for-attachments branch December 13, 2018 15:19
@Qining Qining restored the fix-image-layout-tracking-for-attachments branch December 13, 2018 15:19
@Qining Qining reopened this Dec 13, 2018
@Qining Qining merged commit de6e30f into google:master Dec 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants