Bevel Shader node Samples value has too low hardcoded limit #80012

Closed
opened 2020-08-22 13:31:16 +02:00 by Ludvik Koutny · 10 comments
Contributor

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.77

Blender Version
Broken: version: 2.83.5, branch: master (modified), commit date: 2020-08-19 06:07, hash: c2b144df39
Worked: (newest version of Blender that worked as expected)

Short description of error
Bevel shader value has hardcoded limit for the max amount of samples at a very low value of 16. This causes issues when using Bevel shader as a mask for wear and tear procedural materials (by calculating distance between original and beveled normals). Trying to clean the noise using Cycles' AA sampling is then much less efficient and more performance wasting than simply increasing the Bevel samples value to sufficient levels.
image.png

Exact steps for others to reproduce the error

  1. In a new .blend file, create a new material and add Bevel shader node
  2. Try to set samples value above 16

Result: The samples value can not be raised above 16.

Expected: The samples value can be raised above 16 so that sufficient sampling can be achieved when using Bevel node output as a maks for procedural materials.

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.77 **Blender Version** Broken: version: 2.83.5, branch: master (modified), commit date: 2020-08-19 06:07, hash: `c2b144df39` Worked: (newest version of Blender that worked as expected) **Short description of error** Bevel shader value has hardcoded limit for the max amount of samples at a very low value of 16. This causes issues when using Bevel shader as a mask for wear and tear procedural materials (by calculating distance between original and beveled normals). Trying to clean the noise using Cycles' AA sampling is then much less efficient and more performance wasting than simply increasing the Bevel samples value to sufficient levels. ![image.png](https://archive.blender.org/developer/F8803150/image.png) **Exact steps for others to reproduce the error** 1. In a new .blend file, create a new material and add Bevel shader node 2. Try to set samples value above 16 Result: The samples value can not be raised above 16. Expected: The samples value can be raised above 16 so that sufficient sampling can be achieved when using Bevel node output as a maks for procedural materials.
Author
Contributor

Added subscriber: @Rawalanche

Added subscriber: @Rawalanche

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Thaks for the report.
Can you provide a simple file showing the problem?

Thaks for the report. Can you provide a simple file showing the problem?
Author
Contributor

In #80012#1001771, @mano-wii wrote:
Thaks for the report.
Can you provide a simple file showing the problem?

Yes, I can, but this request makes no sense to me as this is not scene specific.

BevelSamples.zip

> In #80012#1001771, @mano-wii wrote: > Thaks for the report. > Can you provide a simple file showing the problem? Yes, I can, but this request makes no sense to me as this is not scene specific. [BevelSamples.zip](https://archive.blender.org/developer/F8808412/BevelSamples.zip)

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Germano Cavalcante self-assigned this 2020-08-24 17:44:22 +02:00

Now I was able to understand the problem better.

As far as I can see this is not a bug, but a request for changed or improved behavior.
There is a reason why this value is limited (See the manual )
Therefore, although procedural, the use of high values indicates misuse as it leaves the materials complex and the rendering time longer.

For user feedback and feature requests other channels are used: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
We cannot accept feature requestes in this bug tracker. (Here explains the reasons:: https://wiki.blender.org/wiki/Reference/Not_a_bug)

Now I was able to understand the problem better. As far as I can see this is not a bug, but a request for changed or improved behavior. There is a reason why this value is limited (See the [manual ](https://docs.blender.org/manual/en/dev/render/shader_nodes/input/bevel.html#properties)) Therefore, although procedural, the use of high values indicates misuse as it leaves the materials complex and the rendering time longer. For user feedback and feature requests other channels are used: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests We cannot accept feature requestes in this bug tracker. (Here explains the reasons:: https://wiki.blender.org/wiki/Reference/Not_a_bug)
Author
Contributor

In #80012#1001865, @mano-wii wrote:
Now I was able to understand the problem better.

As far as I can see this is not a bug, but a request for changed or improved behavior.
There is a reason why this value is limited (See the manual )
Therefore, although procedural, the use of high values indicates misuse as it leaves the materials complex and the rendering time longer.

For user feedback and feature requests other channels are used: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
We cannot accept feature requestes in this bug tracker. (Here explains the reasons:: https://wiki.blender.org/wiki/Reference/Not_a_bug)

This makes absolutely no sense whatsoever, because following this logic, Ambient Occlusion shader should also have samples limit hardcoded at this extremely low value. Should I report a new bug that AO shader samples can be increased above 16?

Actually, as a result of this issue, the rendertimes are longer because trying to clean up this kind of sampling with AA samples is incredibly inefficient. (Brute forcing lack of secondary rays with excessive amount of primary ones)

> In #80012#1001865, @mano-wii wrote: > Now I was able to understand the problem better. > > As far as I can see this is not a bug, but a request for changed or improved behavior. > There is a reason why this value is limited (See the [manual ](https://docs.blender.org/manual/en/dev/render/shader_nodes/input/bevel.html#properties)) > Therefore, although procedural, the use of high values indicates misuse as it leaves the materials complex and the rendering time longer. > > For user feedback and feature requests other channels are used: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests > We cannot accept feature requestes in this bug tracker. (Here explains the reasons:: https://wiki.blender.org/wiki/Reference/Not_a_bug) This makes absolutely no sense whatsoever, because following this logic, Ambient Occlusion shader should also have samples limit hardcoded at this extremely low value. Should I report a new bug that AO shader samples can be increased above 16? Actually, as a result of this issue, the rendertimes **are** longer because trying to clean up this kind of sampling with AA samples is incredibly inefficient. (Brute forcing lack of secondary rays with excessive amount of primary ones)

This issue was referenced by a9ae45597c

This issue was referenced by a9ae45597c334334a715e72de953b0f28fc34a07

This issue was referenced by 5f86a10477

This issue was referenced by 5f86a104775be51e216c40efe1bd69c3e35f49e7
Member

Changed status from 'Archived' to: 'Resolved'

Changed status from 'Archived' to: 'Resolved'
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 & 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
Asset System
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline & 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
4 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#80012
No description provided.