Multi-layer EXR renders and saves "combined" output regardless if it's checked on or off in the view layer properties. #108991

Closed
opened 2023-06-14 23:01:44 +02:00 by aulerius · 4 comments

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98

Blender Version
Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1d3

Short description of error
When ticked off, the "combined" pass is being rendered and included as a layer when outputting multi-layer EXRs. This applies both to Eevee and Cycles. Expected behavior would be to have it omitted and not processed by the renderer.

More context:
In Cycle's case this introduces a large overhead when the user is not it interested in ray-traced lighting information for example. (personally, I want to export motion vectors, which are only available in cycles)
This is true in the most simple case when "Compositing" is ticked off and there is no node tree, but also introduces further unwanted behavior in the context of compositor. I have a guess that this is related to the fact that "composite" node in the compositor, that follows the "output" settings in Scene settings, is always inherently outputted as a file, as discussed here. In the case of multi-layer EXR, I suppose this "composite" image under the hood is force fed by "combined" layer, ignoring the user's tickmark.
Additionally, if the scene output properties use multi-layer EXR and there are "file output" nodes active in the nodetree with EXR output, it can potentially overwrite files from "file output" in the same folder, despite the user potentially indenting to disable "combined" file output by disconnecting the "composite" node.

Exact steps for others to reproduce the error
In the attached blend file, just hit CTRL+F12 to render animation and inspect the resulting EXR files created in the "export" directory.
The "combined" pass is turned off.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98 **Blender Version** Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: `e1ccd9d4a1d3` **Short description of error** When ticked off, the "combined" pass is being rendered and included as a layer when outputting multi-layer EXRs. This applies both to Eevee and Cycles. Expected behavior would be to have it omitted and not processed by the renderer. **More context:** In Cycle's case this introduces a large overhead when the user is not it interested in ray-traced lighting information for example. (personally, I want to export motion vectors, which are only available in cycles) This is true in the most simple case when "Compositing" is ticked off and there is no node tree, but also introduces further unwanted behavior in the context of compositor. I have a guess that this is related to the fact that "composite" node in the compositor, that follows the "output" settings in Scene settings, is always inherently outputted as a file, as [discussed here](https://blenderartists.org/t/file-output-node-default-output/664752). In the case of multi-layer EXR, I suppose this "composite" image under the hood is force fed by "combined" layer, ignoring the user's tickmark. Additionally, if the scene output properties use multi-layer EXR and there are "file output" nodes active in the nodetree with EXR output, it can potentially overwrite files from "file output" in the same folder, despite the user potentially indenting to disable "combined" file output by disconnecting the "composite" node. **Exact steps for others to reproduce the error** In the attached blend file, just hit CTRL+F12 to render animation and inspect the resulting EXR files created in the "export" directory. The "combined" pass is turned off.
aulerius added the
Status
Needs Triage
Type
Report
Priority
Normal
labels 2023-06-14 23:01:45 +02:00
Member

Hi, thanks for the report.

When ticked off, the "combined" pass is being rendered and included as a layer when outputting multi-layer EXRs

As far as I know, "Combined" pass results are always generated irrespective of the checkbox value, see: https://projects.blender.org/blender/blender/src/branch/main/source/blender/render/intern/render_result.cc#L297

      /* A render-layer should always have a "Combined" pass. */
      render_layer_add_pass(rr, rl, 4, "Combined", view, "RGBA", false);

This is not limited to Multi-layer EXR output format. Other file formats such as PNG also generates combined pass result in render-output window.

Not a bug If I understand the report correctly.
If there is misunderstanding from my side, feel free to mention that.

Hi, thanks for the report. > When ticked off, the "combined" pass is being rendered and included as a layer when outputting multi-layer EXRs As far as I know, "Combined" pass results are always generated irrespective of the checkbox value, see: https://projects.blender.org/blender/blender/src/branch/main/source/blender/render/intern/render_result.cc#L297 ``` /* A render-layer should always have a "Combined" pass. */ render_layer_add_pass(rr, rl, 4, "Combined", view, "RGBA", false); ``` This is not limited to `Multi-layer EXR` output format. Other file formats such as PNG also generates combined pass result in render-output window. Not a bug If I understand the report correctly. If there is misunderstanding from my side, feel free to mention that.
Author

No, it seems you're right then!

I would still argue such decision is debatable, as I was not the only one finding this feature confusing or unwanted.
...I suppose from here this discussion would be more suited for RCS proposal?
From UX standpoint, maybe the checkmark for "combined" should not exist at all, If it is always rendered anyway.

No, it seems you're right then! I would still argue such decision is debatable, as I was not the only one finding this feature confusing or unwanted. ...I suppose from here this discussion would be more suited for RCS proposal? From UX standpoint, maybe the checkmark for "combined" should not exist at all, If it is always rendered anyway.
Member

Thanks.

I suppose from here this discussion would be more suited for RCS proposal?

yes

I would still argue such decision is debatable... From UX standpoint, maybe the checkmark for "combined" should not exist at all, If it is always rendered anyway.

@brecht hi, any opinion on this?

Thanks. > I suppose from here this discussion would be more suited for RCS proposal? yes > I would still argue such decision is debatable... From UX standpoint, maybe the checkmark for "combined" should not exist at all, If it is always rendered anyway. @brecht hi, any opinion on this?

Duplicate of #65456.

Duplicate of #65456.
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2023-06-16 18:11:31 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#108991
No description provided.