Default Clamp value #62691

Closed
opened 2019-03-17 21:05:09 +01:00 by Marco · 13 comments
Member

System Information
Operating system: Ubuntu 18.04 64bit
Graphics card: AMD RX 580 (8GB)

Blender Version
Broken: 2.80.49, cc5bdf0293, 2019-03-16

Short description of error
screenshot.png
This is not a bug, I would like to have the Clamp Indirect value in Cycles to be 0 instead of 10.
In 2.8 the default value is 10, while in 2.7 it was 0.
Please can you make it 0 as i was getting 2 different results with the same project file (one saved in 2.7 and the other in 2.8) and i was't finding the issue.

**System Information** Operating system: Ubuntu 18.04 64bit Graphics card: AMD RX 580 (8GB) **Blender Version** Broken: 2.80.49, cc5bdf029324, 2019-03-16 **Short description of error** ![screenshot.png](https://archive.blender.org/developer/F6840174/screenshot.png) This is not a bug, I would like to have the Clamp Indirect value in Cycles to be 0 instead of 10. In 2.8 the default value is 10, while in 2.7 it was 0. Please can you make it 0 as i was getting 2 different results with the same project file (one saved in 2.7 and the other in 2.8) and i was't finding the issue.
Author
Member

Added subscriber: @nacioss

Added subscriber: @nacioss

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
William Reynish self-assigned this 2019-03-17 21:12:26 +01:00

As you say yourself, this is not a bug, but different defaults.

Opening old files with certain clamp values should not, and does not change or override the clamp value. I just tested this, and it does not happen. If you experience this, it is a bug, but in your report it is not quite clear if you are having that particular issue or not.

As you say yourself, this is not a bug, but different defaults. Opening old files with certain clamp values should not, and does not change or override the clamp value. I just tested this, and it does not happen. If you experience this, it is a bug, but in your report it is not quite clear if you are having that particular issue or not.
Author
Member

Nono, the clamp value remained 0 from Blender 2.7.
screen.jpg
So, i have an addon that generates skies, since i was getting, as you can see, darker results in Blender 2.8, then i wanted to find out why:
So the left window shows the generated sky in a new 2.8 project, the right window shows Blender 2.79 with the same values in the addon.
Then i started searching what was wrong, until i found that the clamp value of Blender 2.8 was 10 instead of 0.
I really think you should set it 0 as default for new users not getting into trouble like me.

Nono, the clamp value remained 0 from Blender 2.7. ![screen.jpg](https://archive.blender.org/developer/F6840240/screen.jpg) So, i have an addon that generates skies, since i was getting, as you can see, darker results in Blender 2.8, then i wanted to find out why: So the left window shows the generated sky in a new 2.8 project, the right window shows Blender 2.79 with the same values in the addon. Then i started searching what was wrong, until i found that the clamp value of Blender 2.8 was 10 instead of 0. I really think you should set it 0 as default for new users not getting into trouble like me.

Added subscriber: @brecht

Added subscriber: @brecht

@brecht: Thoughts on default clamp values?

@brecht: Thoughts on default clamp values?

It was an intentional change, I don't think it's better overall to go back to 0.

D2769: Cycles: change defaults for filter glossy, clamp and branched path AA.

It was an intentional change, I don't think it's better overall to go back to 0. [D2769: Cycles: change defaults for filter glossy, clamp and branched path AA.](https://archive.blender.org/developer/D2769)

Also, exposure -6.781 is a really extreme value, would not recommend to use that in practice.

Also, exposure -6.781 is a really extreme value, would not recommend to use that in practice.
Author
Member

Brecht, you wrote it, "in production files the clamp is enabled".
Most work i do is not for a short film, i do still images and having Clamp 0 is necessary. By the way, you said you set it to 10 because of noise, well i don't think it is the case since there is the Denoisier. And anyway having it set to 0 as default could prevent people with no experience to see weird results.

Brecht, you wrote it, "in production files the clamp is enabled". Most work i do is not for a short film, i do still images and having Clamp 0 is necessary. By the way, you said you set it to 10 because of noise, well i don't think it is the case since there is the Denoisier. And anyway having it set to 0 as default could prevent people with no experience to see weird results.
Author
Member

I have exposure -6.781 there because i'm dealing with real world Sun and Sky values such as 700 of strength for Sun and 60 for Sky. Since the measurement unit of the strength value is W/m2

I have exposure -6.781 there because i'm dealing with real world Sun and Sky values such as 700 of strength for Sun and 60 for Sky. Since the measurement unit of the strength value is W/m2

Also for still images do people overwhelmingly use clamping, and it's standard in other renderers to enable it by default.

Clamp still helps significantly even when using denoising.

If you're going to adjust exposure then you should simply adjust clamp accordingly too.

Also for still images do people overwhelmingly use clamping, and it's standard in other renderers to enable it by default. Clamp still helps significantly even when using denoising. If you're going to adjust exposure then you should simply adjust clamp accordingly too.
Author
Member

Then what about the caustics enabled by default?
caustics.png
Don't tell me they are enabled in the production files.
And i still don't agree to keep Clamp = 10

Then what about the caustics enabled by default? ![caustics.png](https://archive.blender.org/developer/F6846638/caustics.png) Don't tell me they are enabled in the production files. And i still don't agree to keep Clamp = 10
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#62691
No description provided.