Cycles lamp "strength" ignores scene's "unit scale", producing inconsistent renders in scenes with consistent scaling #53517

Closed
opened 2017-12-08 22:17:50 +01:00 by Chase Moskal · 12 comments

System Information
Windows 7, GTX 580

Blender Version
Broken: 2.79 5bd8ac9
Worked: ---

Short description of error
Lamp emission 'strength' values are not correctly factoring the scene's Unit Scale, leading to inconsistent renders for scenes of the same dimensions (by the blender ruler).

In a blender scene configured for Centimeters unit scale, an area lamp of size 1 meter, requires 1 000 000 (one million) emission strength in order to reasonably light a 6m scene. A strength value of 10 is expected instead.

Mesh emitters are not affected by this bug — in the same "Centimeters" scene described above, a mesh emitter of the same 1 meter size needs only 10 emission strength.

If the scene is remastered to use Meters unit scale (such that the blender ruler still makes the same measurements) — the mesh emitter still works consistently with 10 strength, and the lamp then agrees is also happy with 10 strength — this illustrates the inconsistency between mesh-emitters and lamps with respect to unit scale.

Exact steps for others to reproduce the error

**System Information** Windows 7, GTX 580 **Blender Version** Broken: 2.79 5bd8ac9 Worked: --- **Short description of error** Lamp emission 'strength' values are not correctly factoring the scene's Unit Scale, leading to inconsistent renders for scenes of the same dimensions (by the blender ruler). In a blender scene configured for `Centimeters` unit scale, an area lamp of size `1 meter`, requires `1 000 000` (one million) emission strength in order to reasonably light a 6m scene. A strength value of `10` is expected instead. Mesh emitters are not affected by this bug — in the same "Centimeters" scene described above, a mesh emitter of the same `1 meter` size needs only `10` emission strength. If the scene is remastered to use `Meters` unit scale (such that the blender ruler still makes the same measurements) — the mesh emitter still works consistently with 10 strength, and the lamp then agrees is also happy with 10 strength — this illustrates the inconsistency between mesh-emitters and lamps with respect to unit scale. **Exact steps for others to reproduce the error** - [stage-crazy-lamps-2.blend ](https://drive.google.com/open?id=1l_gT-6_DrfSYaHDPYFvzTlxh5SJqlLo0) - the above scene demonstrates strength one-million is required when using centimeters scale - also see the [stack overflow post ](https://blender.stackexchange.com/questions/96115/why-do-my-lamps-require-an-insane-strength-value-of-1-million) which spurred the discovery of this bug
Author

Added subscriber: @chase-moskal

Added subscriber: @chase-moskal

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2017-12-24 16:06:06 +01:00

Lamps are in Watts, the size of the lamp intentionally does not affect the intensity, only the softness of the shadows. Mesh lights are in Watts/m^2 and are affected by the mesh scale.

In the future we may add some options to controls this behavior, but it's not a bug.

Lamps are in Watts, the size of the lamp intentionally does not affect the intensity, only the softness of the shadows. Mesh lights are in Watts/m^2 and are affected by the mesh scale. In the future we may add some options to controls this behavior, but it's not a bug.

Added subscriber: @bliblubli

Added subscriber: @bliblubli

@brecht adding this information in the tooltip or as a unit like for the distance values would clarify such discrepancies.

@brecht adding this information in the tooltip or as a unit like for the distance values would clarify such discrepancies.

Added subscriber: @novelistparty

Added subscriber: @novelistparty

@brecht When I change my units to cm, the light from a point lamp becomes dim in the render. Why is that?

@brecht When I change my units to cm, the light from a point lamp becomes dim in the render. Why is that?

Changing unit settings in the render does affect the render, unless perhaps you are using an addon or importer that takes them into account. It only affects the display and editing of values in the UI.

Changing unit settings in the render does affect the render, unless perhaps you are using an addon or importer that takes them into account. It only affects the display and editing of values in the UI.

@brecht After I change units, I expect that I could re-add the default scene objects and that the render would be the same as the unchanged default scene. That isn't what happens. The most noticeable difference is that the Point Lamp strength has to be increased a lot; I would expect it's strength to be scaled to match it's larger size.

Things (I've found) that don't automatically scale to match the default blender-units scene when I set units to Centimeters:

  • a Point Lamp's strength
  • the View Clip distance. Before the unit change, it is 0.1 to 1000 (blender units). After the unit change it becomes 1mm to 10m. That doesn't match 1 blender unit = 1 meter.

If I'm not understanding something about why these things behave this way, could you point me at some documentation or blog posts about how this works in Blender. I can't find anything definitive about this and it seems really common to immediately change a project to Centimeters. I'm hoping for a more self-consistent experience with Blender. Thanks!

@brecht After I change units, I expect that I could re-add the default scene objects and that the render would be the same as the unchanged default scene. That isn't what happens. The most noticeable difference is that the Point Lamp strength has to be increased a lot; I would expect it's strength to be scaled to match it's larger size. Things (I've found) that don't automatically scale to match the default blender-units scene when I set units to Centimeters: - a Point Lamp's strength - the View Clip distance. Before the unit change, it is 0.1 to 1000 (blender units). After the unit change it becomes 1mm to 10m. That doesn't match 1 blender unit = 1 meter. If I'm not understanding something about why these things behave this way, could you point me at some documentation or blog posts about how this works in Blender. I can't find anything definitive about this and it seems really common to immediately change a project to Centimeters. I'm hoping for a more self-consistent experience with Blender. Thanks!
vurolele commented 2020-05-23 15:19:05 +02:00 (Migrated from localhost:3001)

Added subscriber: @vurolele

Added subscriber: @vurolele
vurolele commented 2020-05-23 15:19:05 +02:00 (Migrated from localhost:3001)

This comment was removed by @vurolele

*This comment was removed by @vurolele*
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
5 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#53517
No description provided.