I am trying to render out a long movie queue of jobs to a multilayer EXR with a few post process materials using the movie render graph.
I am having trouble getting the multilayer exr naming for the post process materials to be correct. I would like them to always be “WorldNormal” or just the name I input into the post process material name. For some reason it seems to be putting additional prefix or suffix into the layer name. I often get camera name included in the layer name. I have tried editing the PPM File name format. I am using nuke 15 to read in the multilayer EXR and view each later.
PPM File Name Format: {renderer_sub_name}.{frame_number}
Can you just put the exact name you want in the Name field of the PPM Index in the Deferred Renderer node? Like, if I put “Test” in there the layer name when I read it in nuke or rv is just “Test”. Are you rendering all cameras? If you just try and name it in a Default Graph are you able to name it the way you want? Maybe there is something in the graph that is triggering MRG to try and tag is with a decripter so that it does not overwrite another layer.
I am not using the “render all cameras option”. I have a sequence with multiple camera cuts and I have just made another sequence with a single camera to test with both. I am using the default graph to test with. The only changes I have made were outputting multiplayer EXR in global, removing jpeg output, enabling the default post process materials depth and motion, and putting different options into the PPM File Name Format.
in the PPM File Name Format I have just tried putting:
{render_pass}
{renderer_sub_name}
keeping this empty
just putting the text “test”
These always seems to output the camera name if there are multiple camera cuts and if there is only 1 camera it will use the suffix “_extra” at the end of the pass name.
Results I am getting are
depth_extra - with no camera cuts
depth_cameraName - if there are multiple camera cuts.
The “extra” seems to be added in Nuke. Its not in the raw exr pass. For the camera name this look like a bug. I’ll JIRA it as its likely an easy fix. Do you all build your own engine? If so I can make a note to send you the git link to incorporate the fix.
Interesting that _extra gets incorporated from nuke.
We typically use the offline installer provided by epic. We have built the engine from source when recommended if it solves issues we are running into.
Ok I just requested the JIRA be made public. Its assigned but waiting to be started due to other priorities. When it gets fixed I’ll reply back here with a Git link so you can incorporate the change. It is still unclear if it will make the next hotfix. If it does I’ll reply back here as well.