Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.51f1
2022.3.61f1
6000.0.45f1
6000.1.0b13
6000.2.0a8
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-100897
Regression
No
[ShaderGraph] Gradient Noise node output range doesn't match docs
The Gradient Noise node doesn't output values in the [0;1]range like mentioned in the doc.
It seems more to be going from about -0.015 to a bit above 1.025 .
See the following image that shows the out of range values :
!image-2025-03-21-09-50-04-480.png|width=1097,height=991!
Two possible outcomes to fix this :
1. Find the flaw in the noise function to have the output in the desired range
2. Remove the range mention in the doc. Or mention the real approximate range so users can remap or clamp it in their graphs.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
While we acknowledge this presents a challenge, due to the established user interface and functionality, we are unable to modify the core behavior in a way that would significantly disrupt existing workflows. However, for users who necessitate a different noise reduction approach, we provide the option to create custom nodes with tailored algorithms to address their specific needs.