Page 1 of 1

Cryptomatte changes all the time

PostPosted: Wed Aug 04, 2021 3:35 pm
by doca
Hi guys,

Whenever we update render version from octane cryptomattes change(no changes in materials or geometry being made)

I'm talking CryptoMaterialNode in this specific case.
When we render same file on two different PC's we have different cryptomattes.

It is rather irritating for compositing artist to have to pick masks on each render update.

Any clue why that happens and is there any solution to it or expected bug fix if this is a registered bug at all?

Thanks.
Ivan

Re: Cryptomatte changes all the time

PostPosted: Wed Aug 04, 2021 3:36 pm
by doca
...and this happens on Windows under Octane 2020.2.4

Re: Cryptomatte changes all the time

PostPosted: Thu Aug 05, 2021 7:21 am
by bepeg4d
Hi doca,
quoting from the devs:
you should not use crypto passes "CryptoMaterialNode" and "CryptoObjectNode", but instead "CryptoMaterialNodeName" or "CryptoObjectNodeName".

The reason for that is that the crypto matte passes "CryptoMaterialNode" and "CryptoObjectNode" generate a unique ID/colour using the material/object layer node names and unique node ID. Every time a new node is created inside a node graph it will get a new unique ID. When you restart rendering, the plugin deletes all existing nodes and recreates them, resulting in new unique IDs, which is then causing the cryptomatte ID to change as well. On the other hand, the render passes "CryptoMaterialNodeName" and "CryptoObjectNodeName" use only the names of the material/object layer nodes, resulting in reproducible cryptomatte IDs, even after a render restart.


ciao Beppe