Hello, I’m trying to render a shot that needs to be split in multiple passes simultaneously (due to the randomness of the content) using the Movie Render Graph, but I also need to have Object IDS (cryptomatte) at the same time in the very same render. I’m trying to use the Object IDs node set to full (Unreal 5.5.1) with a deferred render pass node and I expect the same result as when I render with the movie render queue and add Object IDs, but Nuke doesn’t recognize the cryptomatte. When I use MRGraph, I get ObjectID00, ObjectID01 and when I use the MRQueue, I get ActorHitProxyMask00, ActorHitProxyMask01 which are recognized as a layer by the cryptomatte node and allow the selection.
Did anyone ever get the crypto to work with the movie render graph in 5.5?
Thanks in advance!
PS: we really cannot split this in multiple renders. No caching possible.
I’m running into the same problem in 5.5.4. I have the graph set up to use Path tracing, and it’s outputting ObjectID00, ObjectID01, ObjectID02. Not being recognized by Nuke.
Hi @comlys, I am having a same issue on 5.5.4
There are layers called objectID1, 2..
but Nuke does not recognise them as cryptomatte.
If I use normal MRQ setting “object ID” it works.
If I put viewmetadata node in nuke to the rendered exr from rendergraph, I see no information regarding cryptomatte is outputted. Whereas old MRQ render has tons of information such as actor name, material name etc…
(I loved your Render Graph youtube tutorial by the way!)
The issue is as @Kosuke_Iwasaki and others above describe. The object Id passes do output in the multilayer exr, it’s just when trying to use them in the cryptomatte it seems like no information is attached to the object id layer.
Hi @comlys@Nando-Cordeiro
I tested in 2 different machines and one spits out and one did not.
And noticed the one it did not spit the cryptomatte had an older Nvidia driver.
Updated to the latest version and still had a bit of hiccup but after restarting it, the crypto came out fine.
I’ve narrowed it down a tiny bit on my end. I rendered a sequence with Movie Render Queue with deferred rendering and Object IDs, and that works as expected.
I rendered a deferred render with Movie Render Graph and Object IDs, and that also worked as expected.
When I switched to Path Tracer in Movie Render Graph, and it did write Object ID layers to the EXR, however they are not recognized in Nuke anymore. Viewing those individual layers in Nuke does show that they contain data, but the cryptomatte node will not recognize them.
I’ve attached two EXRs, one with deferred rendering, one with path tracing.