Search Issue Tracker
By Design
Votes
0
Found in
5.6.1p2
Issue ID
918122
Regression
Yes
Alpha value is not clamped to zero when setting shader's alpha blending value to negative
To reproduce:
1. Open user's project, in Project window click Unlit_NegativeAlpha material
2. In Inspector window, right-click material, select Edit Shader
3. In opened shader's file go to line 39 and make sure alpha value is negative, feel free to change it up to different negative values
Expected: shader's alpha value is clamped at 0 - no matter the negative value, material should remain invisible
Actual: shader's alpha value is not restricted to any negative float, material becomes black, has interesting shading effects
Reproduced in: 5.6.1p2, 5.6.1p3, 2017.1.0b9, 2017.2.0a3
Not reproduced in: 5.4.5p3, 5.5.4f1
Regression starts in: 5.6.0a1
Note: check picture attached for comparison of correct and incorrect shading
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- OnPointerExit and OnPointerEnter is mistakenly called when an overlapping child Image is destroyed
- Dynamic text is rendered in the background when it is inside the <font> tag
Add comment