Unsquared roughness of some shaders #50355
Labels
No Label
Meta
Good First Issue
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 & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information 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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-manual#50355
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
After several discussions with concerned individuals and confirmation from Brecht on the Cycles mailing list, it appears that the roughness on the refractive, glass and glossy shaders are unsquared, the opposite of expected behavior for roughness on such shaders. This cannot be changed for backwards compatibility, but the manual states nothing about this and there's been much speculation and confusion about the issue, a lot of people thinking it was an issue with color management when in fact, it is not. So I suggest that it be specified in the paragraphs pertaining to the roughness of those shaders that the values are unsquared, and that for expected result, if using anything else than an image on which the values have already been squared, the input should be passed through a math node to square it.
The mailing list discussion is attached as a text file if you need more details.
cycles-roughness.txt
Changed status to: 'Open'
Added subscriber: @Eranekao
This issue was referenced by 3267
Changed status from 'Open' to: 'Resolved'