Get different result of Opacity MicroMap in Frame Debugger and Graphics Capture

Developer Tools Nsight Graphics
1

Hi,
I’m trying to use Nsight Graphics to visualize my BVH with OMM, but I got two different result on Frame Debugger and Graphics Capture.
image
To reproduce this issue, I ran the NVIDIA OMM sample and attempted to visualize the acceleration structure:

a2f530714171a33fc820240f1f8cfd26
a2f530714171a33fc820240f1f8cfd261920×1114 297 KB

image
image1920×1141 274 KB

Clearly, the Frame Debugger (first image) provides the expected visualization where I can access the bit array and descriptors, which are essential for understanding the OMM structure. On the other hand, Graphics Capture does not show these details correctly.

This inconsistency has been holding me up for a whole day because initially, I relied on Graphics Capture and obtained incorrect results.

Could anyone help explain why there is such a difference and how to resolve it?

2

Hi, thanks for the report. Sorry for the inconvenience this caused! You’ve encountered a bug in 2025.3 that is already fixed for the next release. There is a workaround you can use in the meantime: it should work if you open the Ray Tracing Inspector after starting Live Replay. You have to make sure that you haven’t opened the RTI at all in that session before starting Live Replay. (In the next release it will work without requiring Live Replay.)