Vulkan Causing Flickering Rendering on AMD GPUs

[genusistimelord]

Description
The bug causes anything Rendering on Vulkan to Flicker. This does not seem to Affect Opengl or DX12. This happens when using this AscendingCreations/AscendingMapEditor@6049f73 Commit which upgrades WGPU 25 to WGPU 26. IT seems to only Affect AMD APU's currently from my understanding and has affected the AMD Ryzen 7 5800H APU. cwfitzgerald said this issue seems to go away when he enabled the Vulkan Validation Layers. I will attempt to get more information when I can.

Repro steps
Just run this on Any system that has a AMD Ryzen 7 5800H APU within Vulkan mode and it will flicker.

Expected vs observed behavior
to not flicker at all but does currently Flicker as shown in the Gif link in Extra Materials.

Extra materials
https://cdn.discordapp.com/attachments/1205140247638450316/1392883148131401769/animated.gif?ex=68712705&is=686fd585&hm=d27da834f6f1f27393ab6a4f3ece15639352fae3f9a2f71b990e6e2d41893e62&

Platform
WGPU 26.0.0
Windows 11

[genusistimelord]

first capture.zip

Render docs capture from the AMD APU. but shows nothing wrong even though it captured the grey screen?

[cwfitzgerald]

Renderdoc also introduces a large amount of synchronization, so can hide sync bugs like that. In the settings you can change "replay optimization" and see if that affects anything, though make sure to change it back.

[genusistimelord]

good rename as it also is affecting my RX 7900XT. finally tested it at home. And it is not affecting the NVIDIA at my work.

[genusistimelord]

20250711-2225-55.2351594.mp4

here is what its doing with replay optimizations off in render docs but still showing no errors.

[genusistimelord]

here is the commit that causes the issue currently. 2d73eb3

If you revert just these changes back the issue goes away. Not entirely sure why. Maybe it is killing the framebuffers too fast? @cwfitzgerald

[sotrh]

here is the commit that causes the issue currently. 2d73eb3

If you revert just these changes back the issue goes away. Not entirely sure why. Maybe it is killing the framebuffers too fast? @cwfitzgerald

Can confirm, using the commit before this fixes the issue.