I have found another issue with Octane and Render View Layers. This time using the compositor with FileIO nodes.
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!
Problem exporting View Layers with FileIO nodes
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)