Cryptomatte ID's inconsistent when a render is reset.

[cannon126]

I love the level of control cryptomattes give me, however; whenever I reset a render (crash, stop to make changes, restart on a different day), the ID's change; so my cryptomatte also does between framesets.

When I'm compositing I can't use a single cryptomatte throughout a sequence because of all the changes, it drives me nuts, especially on a 1000 frame+ sequence where I had to start and stop the render multiple times.

Anyone else have this problem and/or solutions?

[Raoul]

I did run into this problem in the past.
It is due to the type of Cryptomatte youre outputting.
try choosing CryptoMaterialNodeName... ( not CryptoMaterialNode).. that way the color should be linked to the material Name.. ---do note though: if you have materials with the same name they will have the same color matte.

Would be good to have this kind of information in the Manual ( if its not there already)

well thats what solved it for me, hope it helps.
R

[turtles123]

i did some testing and as long as i dont touch the object manager the cryptomatte cryptoinstance is consistent from render to render. i think the color is assigned based on the id number in the object manager.

[bepeg4d]

Raoul is right!
Please have a look at here:
viewtopic.php?f=24&t=73140&p=374642&hil ... te#p374642

ciao Beppe

[cannon126]

Thanks for the help guys.

I can't, for the life of me, figure out how to properly use the "CryptoObjectNodeName". Does anyone know how to set this parameter to objects in c4d, or what is it referring to?

I've tried changing the layer id's on octane object tags, the names of the tags themselves, the bake id...just can't figure it out. I get single same color cryptomattes for objects with tags on them no matter what I try.

Any help is appreciated!

[aoktar]

You don't need to set something in C4d side, just use CryptoObjectNodeName pass as said. And avoid to use unnecessary passes for performance