Emission performance bug (cycles render) #108558

Closed
opened 2023-06-02 22:17:52 +02:00 by TRIGON · 2 comments

System Information
Operating system: Win 11 Pro ( 10.0.22000 )
Graphics card: 3090

Blender Version
Broken:
3.5.1 steam version ( e1ccd9d4a1 ),
blender-3.5.0-stable+v35.1be25cfff18b-windows.amd64-release
blender-3.6.0-beta+v36.3788f70647a6-windows.amd64-release

Worked:
blender-3.3.6-stable+v33.948f8298b982-windows.amd64-release

When using the Emission node on a hi-poly object and the value of Emission Strength is greater than 0.5, then the render time increases dramatically (updating lights)
The bug is more noticeable when moving an object in mode Display Render preview.
The more polygons on the object, the more the bug manifests itself (100,000+)
If the Strength value is less than or equal to 0.5, the bug does not appear

Reproducing the error:
Option 1:
-Run emission_bug.blend
-Activate the Display Render preview mode
-In the Shader Editor, select one of the four material outputs
-Move the object plane in a circle
-We make sure that when the value of emission strength is higher than 0.5, the rendering time becomes much higher

Option 2:
-In the new scene create an object for 100 000+ polygons
-Assign a node material to the object
-Connect the Emission node to the material output
-Change the Strength value to 0.5 or less
-Activate the Display Render preview mode
-Move the object in a circle
-Make Strength higher than 0.5
-Move the object in a circle
-We make sure that when the value of emission strength is higher than 0.5, the rendering time becomes much higher

p.s: in Blender 3.6.0 the rendering speed is generally increased, but the bug still persists.
the bug was checked on 3 different systems, the behavior is the same everywhere

**System Information** Operating system: Win 11 Pro ( 10.0.22000 ) Graphics card: 3090 **Blender Version** Broken: 3.5.1 steam version ( e1ccd9d4a1d3 ), blender-3.5.0-stable+v35.1be25cfff18b-windows.amd64-release blender-3.6.0-beta+v36.3788f70647a6-windows.amd64-release Worked: blender-3.3.6-stable+v33.948f8298b982-windows.amd64-release **When using the Emission node on a hi-poly object and the value of Emission Strength is greater than 0.5, then the render time increases dramatically (updating lights) The bug is more noticeable when moving an object in mode Display Render preview. The more polygons on the object, the more the bug manifests itself (100,000+) If the Strength value is less than or equal to 0.5, the bug does not appear** **Reproducing the error:** **Option 1:** -Run **emission_bug.blend** -Activate the **Display Render preview** mode -In the **Shader Editor**, select one of the four **material outputs** -Move the object plane in a circle -We make sure that when the value of **emission strength** is higher than **0.5**, the rendering time becomes much higher **Option 2:** -In the new scene create an object for 100 000+ polygons -Assign a node material to the object -Connect the **Emission** node to the **material output** -Change the **Strength** value to **0.5** or less -Activate the **Display Render preview** mode -Move the object in a circle -Make **Strength** higher than **0.5** -Move the object in a circle -We make sure that when the value of **emission strength** is higher than **0.5**, the rendering time becomes much higher p.s: in Blender 3.6.0 the rendering speed is generally increased, but the bug still persists. the bug was checked on 3 different systems, the behavior is the same everywhere
TRIGON added the
Severity
Normal
Type
Report
Status
Needs Triage
labels 2023-06-02 22:17:53 +02:00

This is mostly expected due to the use of the Light Tree feature : Render properties -> Sampling -> Lights -> Light Tree
https://docs.blender.org/manual/en/dev/render/cycles/render_settings/sampling.html#lights

Using the Light Tree often produces less noise during render but is more expensive to calculate for many emissive triangles.

Yes, performance was improved for 3.6 (the work to address #105550 for example). Future changes may improve this further but Light Tree calculations will always be more expensive than without.

@weizhen There's somewhat interesting behavior here with Emission strength of .4999 vs .5001. Do you think that merits any followup for this particular scene?

This is mostly expected due to the use of the Light Tree feature : `Render properties` -> `Sampling` -> `Lights` -> `Light Tree` https://docs.blender.org/manual/en/dev/render/cycles/render_settings/sampling.html#lights Using the Light Tree often produces less noise during render but is more expensive to calculate for many emissive triangles. Yes, performance was improved for 3.6 (the work to address #105550 for example). Future changes may improve this further but Light Tree calculations will always be more expensive than without. @weizhen There's somewhat interesting behavior here with Emission strength of .4999 vs .5001. Do you think that merits any followup for this particular scene?

We have a heuristic where beyond a certain threshold it guesses the emission importance sampling is useful, this is just crossing that threshold. That is the expected behavior.

Emission sampling can be manually turned off in the material properties.

We have a heuristic where beyond a certain threshold it guesses the emission importance sampling is useful, this is just crossing that threshold. That is the expected behavior. Emission sampling can be manually turned off in the material properties.
Blender Bot added
Status
Archived
and removed
Status
Needs Info from Developers
labels 2023-06-02 22:47:58 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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#108558
No description provided.