Driver 595.71: OMM validation is broken

Gaming and Visualization Technologies Visualization OptiX
1

Hello,

I recently updated the driver to 595.71.

Originally I noticed that a sample program with OMM in my OptiX wrapper library fails to build a GAS when enabling the OptiX validation.
Then, I tried optixOpacityMicromap sample in the SDK with validation (I needed to modify the code a bit to always enable validation since DEBUG definition is not active in Windows even in debug build)

I got the following message and the program crashes:

[ 2][VALIDATION_ERROR]: [OMM_USAGE_COUNTS_MISMATCH] App-supplied OMM usage count histogram does not match the OMMs found in build inputs. Either: 1) Per-OMM entries in an OMM array build do not add up to the histogram, or 2) OMMs linked to triangles in a BLAS build do not add up to per-geometry histograms
    geometry index: 0
    OMM format: OC1_2_STATE
    OMM subdivision level: 0
    count in histogram: 32
    count in build inputs: 0
    current operation:
        type: build
        object type: BLAS
        object address: 0x130da01400

Thanks,

My environment:
OptiX 9.1
13.1
Driver: 595.71
Geforce RTX 4080
Visuals Studio 2022 17.14.27
Windows 11 Pro 25H2 26200.7922

2

Confirming this is broken for me too. We’re looking into it, and into why we didn’t catch it. Thank you for the report! I’ll post more info if I hear about any workarounds.

–
David.

3

Same here on D3D12, using NVAPI. The validation layers return completely wrong histogram values : 2 state instead of 4 state, unusually high count in build inputs, or invalid subdivision level. I do not know what’s the result on the DXR version however.

4

We have a fix in the works for a future driver version. It might not make the very next driver release, but will at least be fixed in the one after that. Again, thank you for reporting this.

–
David.

1 Like