Page 1 of 1
Cryptomattes change when Renderque is interrupted
Posted: Sun Nov 06, 2022 1:44 pm
by 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)
Re: Cryptomattes change when Renderque is interrupted
Posted: Sun Nov 06, 2022 7:41 pm
by 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.
Re: Cryptomattes change when Renderque is interrupted
Posted: Mon Nov 07, 2022 10:30 am
by 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.
Re: Cryptomattes change when Renderque is interrupted
Posted: Tue Nov 08, 2022 8:50 am
by 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
Re: Cryptomattes change when Renderque is interrupted
Posted: Tue Nov 08, 2022 10:23 am
by KeeWe
Maybe a hint inside the menu would be nice. Or get rid of the none named passes altogether.
Re: Cryptomattes change when Renderque is interrupted
Posted: Wed Nov 09, 2022 12:05 pm
by henningricke
bepeg4d wrote: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.