Closed Avokadoen closed 2 years ago
Command buffers also seems to be living their own life beginning and ending recordings willy nilly repeatedly. This seems like a driver bug...
vkcube is also broken so it is probably safe to assume that this is a renderdoc or driver bug. A workaround is still required since renderdoc is kinda needed for debugging ... :')
Workaround: ignore texture view. Renderdoc can still be used to inspect memory and other debug functionality
The issue:![image](https://user-images.githubusercontent.com/26302304/163597120-3be5d6a2-40e2-4815-8383-8af5c8216878.png)
Tested on linux with gtx1650m and it works fine (with identical resources as the windows image below) so it seems like the amd hardware/driver is triggering a bug in the application
Interestingly the resources is very different between windows + gtx1080ti and linux + rx 6800xt (swapchain image count is probably a good thing to start investigating):