Summary
The Object ID Node in movie render graph creates bugged Cryptomattes with certain node setups. The cryptomatte correctly exports, but the metadata doesn’t embed into the EXR causing it to be inaccessible in the compositing software. It seems the defaultlayer output when using EXR multilayer doesn’t treat object ID correctly.
Please select what you are reporting on:
Creative
What Type of Bug are you experiencing?
UI/Tools
Steps to Reproduce
Create a multilayer EXR movie render graph.
In your first output, render a scene with differed render, normals, depth and vector post process materials. Add an Object ID node directly after the differed render. Make it the first render layer and hook into output node.
This will create the bugged EXR files.
To fix, I need to split into a second output. The first output just has the differed renderer and layer node, the second output includes the object ID node. The first output will fail to encode cryptomatte, the second output will encode cryptomatte properly.
Expected Result
Cryptomatte should work regardless of which output it goes to.
Observed Result
Cryptomatte fails on first output layer, works on second.
Platform(s)
Windows 10
Upload an image
Additional Notes
The attached image is the only variant I could find that works. The problem is that it will always render two EXRs. But I only want to have to render one EXR with Normals, Depth, Vectors, and Cryptomatte layers.