[Vulkan] Image barriers cause some images to become incorrectly trashed

[JuanDiegoMontoya]

[Vulkan] Image barriers cause some images to become incorrectly trashed

[baldurk]

Thanks for verifying, sounds like it is indeed the same AMD driver bug I've seen before. Unfortunately I'm not aware of any workaround on RD's side that would be feasible so this needs to be fixed on their side.

[baldurk]

I believe this is an AMD driver bug I've seen reported before. The patterns you are seeing are not done (directly) by RenderDoc which is why they are inconsistent and not fully and clearly filled with UNDEFINED but a trashed version (if you see the bottom half of the image for example).

Could you do a test and change any barriers which have the same layout before and after, and duplicate them into two barriers that go A -> B and B -> A where B is any other layout that would be valid for the image? If this is the same bug, it only happens when using sync2 and identical-layout transitions. I was going to try and compile your program to test that myself but it doesn't build for me.

[JuanDiegoMontoya]

Thanks for the quick response, and apologies for the app not building.

I tried your suggestion and it worked for both the cases I showed. Transitioning to a different layout and back makes the images not lose their contents. I suppose I can work around this in my abstraction by simply emitting a VkMemoryBarrier2 instead of VkImageMemoryBarrier2 when the old and new layouts are the same.