EXR render passes from Unity into After Effects? Tweet

[alecmaassen]

Hi,

So I'm coming from the Cinema 4D plugin and helping a colleague on a project where we are rendering EXR sequences out of Unity for a small animation. We've figured out how to render the 'raw' beauty pass, but I cannot figure out how to include all my render passes in the EXR.

Normally my workflow is rendering out tonemapped EXR's out of C4D and then bringing into After Effects and use the Extractor tool to extract the Beauty pass, z depth, diffuse, etc. However I cannot figure out how to do this in AE when the EXR comes from Unity? All I get is the beauty pass, even if the render passes are checked and the EXR is set to tonemapped?

[alecmaassen]

bump

[likeshesaid]

Hi Alec!

This is Nicole (Ruggiero lol -- small world). I haven't done this in Unity but have you tried to set your kernels from pathtracing/direct lighting/etc to infochannels -- then choose zdepth under type (or whatever other info channel you need)? It should directly just render those infochannels instead of the beauty pass I believe if it functions similarly to c4d.

[alecmaassen]

haha HEY!!! So I get what your saying, and we've been able to render discrete depth passes out of Unity just fine as PNGs, which will work for our project. But we are curious about the EXR file type in general because that's what I have always used in C4D. I've followed the same steps and settings from C4D, which should work, but I think Unity might actually have a bug for its EXR exporter. ((

[Xhed]

Render passes export in EXR indeed looks to be broken. Thanks for the report, we will look into it.

[jalley]

Hi there,

Has been this bug in EXR export been fixed in current release? We are actually planning to export different EXR passes for doing composition afterwards.
Any particular advice on that when working with the Unity plugin?

Thanks,
jalley

[cDB3NU9z]

Render passes work well for me when exporting to EXR 32-bpc untonemapped. (That's all I have tested.)

[ChrisHekman]

Thanks cDB

I can confirm, this issue should be fixed in the current build.