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
- All newly created color markers of Gradient Editor get removed at once when trying to remove one of them
- Nested Canvases with the same Order in Layer ignore Z position for render order when sharing parent Canvas
- ShaderGraph Material subasset loses texture reference when reimporting all assets while using a scripted importer
- Values changed on a prefab are not retained when entering Play Mode
- Shadow Caster 2D shadows partially disappear in specific spots when used with Composite Collider 2D in the Game view
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.