Noise texture behavior and documentation are inconsistent. #104755

New Issue

John-Doe-19 · 2024-03-28T17:54:51+01:00

John-Doe-19 commented

2024-03-28 17:54:51 +01:00

Page Information
File: manual/render/shader_nodes/textures/noise.rst
Blender Version: 4.0 - 4.2
Documentation Language: en
Permanent Link

Short description of error
"When Normalize disabled, output values are in the range -1.0 to 1.0." This isn't consistent with the behavior I've observed; What seams to happen is, each level of detail is constrained between -1.0 and 1.0, then the levels are added to get the final output. There is a chance this isn't intended behavior. But given that if the output was between -1.0 and 1.0 it would still be normalized, so I think it's an issue with the documentation.

**Page Information** File: `manual/render/shader_nodes/textures/noise.rst` Blender Version: `4.0 - 4.2` Documentation Language: `en` [Permanent Link](https://docs.blender.org/manual/en/4.1/render/shader_nodes/textures/noise.html#properties) **Short description of error** "When Normalize disabled, output values are in the range -1.0 to 1.0." This isn't consistent with the behavior I've observed; What seams to happen is, each level of detail is constrained between -1.0 and 1.0, then the levels are added to get the final output. There is a chance this isn't intended behavior. But given that if the output was between -1.0 and 1.0 it would still be normalized, so I think it's an issue with the documentation.

John-Doe-19 added the

labels 2024-03-28 17:54:51 +01:00

Matthew Hinson referenced this issue from a commit

2024-05-31 17:08:10 +02:00

Nodes: Correct value range for non-normalized Noise

Matthew Hinson closed this issue

2024-05-31 17:08:11 +02:00

Blender Bot added

and removed

labels 2024-05-31 17:08:12 +02:00

Matthew Hinson commented

2024-05-31 17:08:35 +02:00

I checked the source code of this node and you're right: each noise layer gets added to the previous one, so the higher the Detail, the larger the value range. Fixed the documentation.

Sign in to join this conversation.