Search Issue Tracker
By Design
Votes
0
Found in [Package]
7.3.1
Issue ID
1234765
Regression
No
[Shader Graph][URP]Texture starts changing to color pink when opacity raises above 1
Steps to reproduce:
1. Open the attached project "Case_1234765"
2. Navigate to Shader->Subgraphs and open the shader graph contained in the folder
3. In the "Blend" node start increasing Opacity(1) above 1 and notice how Texture transforms to the color pink
Expected results: Texture does not changes to color pink when opacity is above 1
Actual results: Texture changes to color pink when opacity is above 1
Reproducible with: 2019.3.12f1(7.3.1), 2020.1.0b8(8.0.1), 2020.2.0a9(8.0.1)
Note: Was unable to test with 2018.4 due to shader graph braking. Video is attached below
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
That's simply how the math works out when the Blend node has an opacity over 1 for that texture call. It's by design -- the user should clamp the input in their graph to desired ranges for their specific use-case.