HtoA Cryptomatte Broken in Nuke

[mgenehoffman]

I've read many versions of "make sure you're rendering to a batch instead of through the render view," which I am. The EXR files render and contain Cryptomatte passes, but they are all separated out into 4 channels per AOV.

For example: crypto_asset, crypto_asset0, crypto_asset01, crypto_asset02

instead of just crypto_asset

Then the mattes that come out of this are all wrong. Selecting a material creates a mask with many materials in it, etc.

I double checked and AOV's from Redshift come in as expected, only show the one name in the Nuke dropdown and selections work correctly.

I thought Fusion read them correctly, but it also does not produce correct mattes from them.

Any ideas? This is Latest Houdini and Arnold as of 3-21-20 and Nuke Studio 12.1v1, Cryptomatte v 1.2.6.

Attached is what the Crypto passes look like in the Nuke dropdown.

[Anonymous]

That's normal, you have to download cryptomatte for Nuke, to be able to use them
link here:
https://github.com/Psyop/Cryptomatte
like this:

[mgenehoffman]

I have the Cryptomatte gizmo, I've used it for years with other renderers. It's just the Arnold Houdini renders that don't produce correct mattes.

[Anonymous]

work fine for me, here is the the hip file with : asset, material,abject and custom
HtoA_cryptomatte.zip
edit: try to download the latest cryptomatte for Nuke here:
https://github.com/Psyop/Cryptomatte

[t.przydatek_j.studio]

Maybe you have to use Arnolds driver for writing files. It was the source of my problems. The documentation says it's required for Cryptomatte output.

See section "Arnold product type":

https://help.autodesk.com/view/ARNOL/ENU/?guid=arnold_for_houdini_solaris_ah_Arnold_Render_Settings_...