You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
using any scene in houdini with a some hierarchy in Solaris
add some rendersettings to render Cryptomatte
render with kick
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
Arnold: 7.2.5.0 to 7.3.2.1
OS: Windows 10
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: