baldurk / renderdoc

RenderDoc is a stand-alone graphics debugging tool.
https://renderdoc.org
MIT License
8.88k stars 1.33k forks source link

Missing geometry only in Renderdoc 1.33 #3346

Closed LiamTyler closed 3 months ago

LiamTyler commented 3 months ago

Description

Hi there! I have a small application. It simply draws a red + blue gradient to a render target in a compute shader, and then draws a green cube ontop of that using a mesh shader. The application seems to work fine, no validation errors or anything, whether I launch it through Renderdoc or not. When I take a capture and open it however, the cube is gone. I confirmed this does not happen with Renderdoc 1.31 or 1.32, only in 1.33 so far. Here are some comparison images between 1.32 and 1.33 for me:

rd_1_32 rd_1_33 rd_1_32_mesh_viewer rd_1_33_mesh_viewer

Steps to reproduce

Attached is a zip file of the application, and the assets needed to run it. You should just be able to unzip the folder, and double click the application to run it, and the cube should be immediately infront of the camera upon launch. I also included a capture using 1.32 and a capture using 1.33. When I open the 1.32 capture while using 1.33, it does work. But 1.33 with 1.33 does not.

Environment

Repro.zip

vblanco20-1 commented 3 months ago

This is something ive been able to confirm on my end, on renderdoc 1.33 vkguide codebase even at chapter 4 is broken . Caused for some reason due to grabbing vertex data from a buffer device address. Its not just mesh shader but all mesh types, happening on both indirect and "normal" drawing, it also doesnt matter if the pass before is a compute gradient.

LiamTyler commented 3 months ago

Thanks vblanco! Good to know I'm not the only one seeing it. And I'm sure you recognized the compute gradient haha😄