Octane will correctly render an animation containing view layers when output is set via FileIO nodes in compositor only for the first frame. The first frame correctly places each render view on its own layer in a multi EXR file. However, all subsequent frames of the animation place both render views onto the same layer and duplicate that combined output for each view.
This does not happen when using the same set up for Eevee or Cycles. With those renderers, each view layer is maintained on a separate layer in the EXR file throughout the entire animation.
See attached sample files.
It is possible I may not be setting up the nodes correctly – though as I sated it does work in Eevee and Cycles.
I have come to rely on file output in compositor as it is currently the only way to truly control what layers are populated into our multi EXR files. Using the defaults (either Blender or Octane output) always places Combined, Depth, and sometimes other unwanted layer passes into our files. This significantly increases the size of our .exr files and makes using them in our compositing application slower and more difficult. The problem is compounded when using Render View Layers as those unnecessary passes are duplicated, causing files that are now twice as large!
ViewLayers-FileIO-Compositor-Issue.zip- (24.28 MiB) Downloaded 109 times
