Open TanJeremy opened 3 months ago
Issue synced internally to ARNOLD-15243
Hi @TanJeremy , could you please provide a repro scene for this issue ? (the exported usd file would be a good start). If you kick the usd file it goes through the same code path as when rendering in Maya. So it really depends on the node names in the usd side.
Hi @sebastienblor, here an exemple usd file (make sure to use the renderlayer usd file to render) cryptomatte_path_manifest.zip
here is our kick command
".../htoa/htoa_gcc11.2/htoa-6.3.2.1_r92cc36e_houdini-20.0.724/scripts/bin/kick" -nstdin -dw -dp -i ".../cryptomatte_path_manifest/renderlayers/example_v01_masterLayer.usda" -frame 1 -v 4 -set options.abort_on_license_fail true
Describe the bug When rendering a usd file (generated by Houdini) with kick , cryptomatte manifest are saved with the primitive name as key instead of the primitivepath
To Reproduce Steps to reproduce the behavior:
Expected behavior like when rendering from maya, we want to keep the path of our object or material in our cryptomatte maybe i'm missing something but there is no documentation for cryptomate in solaris or i can't find them.
Screenshots
Used Software Versions