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
- 2D Renderer Breaks When Animating Material Property with MaterialPropertyBlock
- PlayModeStateChange.ExitingPlayMode is not logged when Play Mode is exited due to recompilation
- Crash on `anonymous namespace'::PrepareTreesAndWriteWindParamsJobData::Execute when entering Play Mode on a specific project
- Errors "InvalidOperationException: Trying to use a texture (_InternalGradingLut)..." and “Render Graph Execution error” shown and Scene turns black when 16 or more Render Objects are used
- GameObjects in the Game View are rendered differently than in the Scene View when the Rendering Path is set to "Deferred" and Screen Space Shadows Renderer Feature is added
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.