Compositor Active During Incomplete Render in Viewports #116554

Closed
opened 2023-12-26 14:43:17 +01:00 by philovivero · 1 comment

System Information
Operating system: macOS-13.6.1-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M2 Ultra 1.2

Blender Version
Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: 9be62e85b727
Worked: I'm not sure this ever "worked" differently than it does now, but as it is implemented, it's a major performance hit.

Short description of error
In viewport, while rendering is still incomplete, compositor is applied at every iteration of the render.

Exact steps for others to reproduce the error

  1. In 3D viewport, go to rendered mode
  2. Click the render settings button in upper right of 3D viewport
  3. Choose compositor "always"
  4. Move around your scene, see how compositor applies before render is complete

I'll include a .blend that demonstrates the problem and a short video as well. In the video you can see how when I'm moving around the 3D viewport, the compositor is applying from the very first iteration of Cycles. Same thing happens in Eevee, though I do not demonstrate that here. Then, at the end of the video, I do an actual render, where you can see the scene goes through its iterations until done, then and only then is the compositor node tree applied.

This is not bad in the included scene, but in any complex scene, having the compositor during every iteration of the render slows it down dramatically.

I could see someone wanting the compositor before render is complete, but can we at least have the option to follow the same workflow as actual render, such that compositor is only applied after render is complete?

**System Information** Operating system: macOS-13.6.1-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M2 Ultra 1.2 **Blender Version** Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: `9be62e85b727` Worked: I'm not sure this ever "worked" differently than it does now, but as it is implemented, it's a major performance hit. **Short description of error** In viewport, while rendering is still incomplete, compositor is applied at every iteration of the render. **Exact steps for others to reproduce the error** 1. In 3D viewport, go to rendered mode 2. Click the render settings button in upper right of 3D viewport 3. Choose compositor "always" 4. Move around your scene, see how compositor applies before render is complete I'll include a .blend that demonstrates the problem and a short video as well. In the video you can see how when I'm moving around the 3D viewport, the compositor is applying from the very first iteration of Cycles. Same thing happens in Eevee, though I do not demonstrate that here. Then, at the end of the video, I do an actual render, where you can see the scene goes through its iterations until done, then and only then is the compositor node tree applied. This is not bad in the included scene, but in any complex scene, having the compositor during every iteration of the render slows it down dramatically. I could see someone wanting the compositor before render is complete, but can we at least have the option to follow the same workflow as actual render, such that compositor is only applied after render is complete?
philovivero added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-12-26 14:43:18 +01:00
Member

Hi, thanks for the report. Compositing results after complete render in viewport will make real-time compositor less useful (have to wait minute or two or even more to get compositing results. Then there won't be difference in realtime renders and final render).
The issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Hi, thanks for the report. Compositing results after complete render in viewport will make real-time compositor less useful (have to wait minute or two or even more to get compositing results. Then there won't be difference in realtime renders and final render). The issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2023-12-27 06:03:51 +01: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
2 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#116554
No description provided.