Cryptomattes change when Renderque is interrupted

[henningricke]

Hi, I think I found something I would consider a bug:

When rendering via C4D Renderque and the rendering gets stopped, to be continued afterwards, the Cryptomattes get messed up.

I seems, they get a new seed value assigned, which results in a complete change of colours inside the matte.
This of course causes problems when compositing.



C4d Version S26
Octane Version: 2021.1.6-(R4)

[aoktar]

Which passes are you using? Named... crypto passes are static always. Others are not and I don't advice to use these for animations.

[henningricke]

In my case I was using the Material Pass.

Is there no way to keep it constant?
This pass is extremely useful. Would be a shame to not to able to take advantage of it.

[bepeg4d]

Hi,
yes, Material passes are supported, but you should not use crypto passes "CryptoMaterialNode" and "CryptoObjectNode", but instead "CryptoMaterialNodeName" or "CryptoObjectNodeName".

For a more detailed explanation please have a look at here:
viewtopic.php?f=24&t=73140&p=374642&hil ... me#p374642

ciao,
Beppe

[KeeWe]

Maybe a hint inside the menu would be nice. Or get rid of the none named passes altogether.

[henningricke]

Hi,
yes, Material passes are supported, but you should not use crypto passes "CryptoMaterialNode" and "CryptoObjectNode", but instead "CryptoMaterialNodeName" or "CryptoObjectNodeName".

For a more detailed explanation please have a look at here:
viewtopic.php?f=24&t=73140&p=374642&hil ... me#p374642

ciao,
Beppe

Thank you very much Bepe! That has been really helpful!

I'm just wondering, why would anyone want to use the "CryptoMaterialNode" then in the first place?
Its good to have options, but sometimes it makes things much more complicated for the average users (like me) that don't tend to dive too deep into the technical aspects of octane.