Search Issue Tracker
Fixed
Fixed in 2020.3.42f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b10, 2023.1.0a11
Unknown (hidden) 2021.1.X
Votes
0
Found in
2021.1.0a1
2021.3.1f1
2022.1.0b16
2022.2.0a11
2023.1.0a6
Issue ID
UUM-2364
Regression
Yes
Color artifacts in imported textures when Alpha Source is set to Input Texture Alpha
Reproduction steps:
1. Open the attached 'texture test 2021' project
2. Open the 'SampleScene'
3. Observe the 'Quad' GameObject
Expected result: The 'Quad' GameObject is completely black with a white stripe at the bottom
Actual result: The top half of the 'Quad' GameObject is white
Reproducible with: 2021.1.0a1, 2021.3.1f1, 2022.1.0b16, 2022.2.0a11
Not reproducible with: 2019.4.38f1, 2020.2.0b5, 2020.3.34f1
{+}*Important*{+}: The "actual result" mentioned above is expected and by design due to a previous optimisation. What the fix focuses on instead, is clarify that the user should not rely on the colour data of texels where Alpha == 0 when Alpha Is Transparency is enabled. (this applies to 2020.3 as well, before the optimisation change was made)
As such, when verifying, you should check that the tooltip for "Alpha is Transparency" & API docs have been updated as seen in the PR, instead of checking the repro project scenario.
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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2021.1.X):
Version is no longer supported.