Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
0
Found in
2020.3.40f1
2021.1.28f1
Issue ID
UUM-21003
Regression
No
Arrays textures get damaged when using "Alpha Is Transparency"
How to reproduce:
1. Open the user’s attached project “rugby-unity.zip”
2. In Project Search type “Player” and open the “Player 185” Prefab asset
3. Observe the player’s arm
Expected result: array texture on arm has no distortions
Actual result: array texture on arm has distortions
Reproducible with: 2020.3.40f1, 2021.1.28f1
Not reproducible with: 2021.2.0f1, 2021.3.4f1, 2022.1.20f1
Couldn’t test with: 2021.2.0a1 - 2021.2.0a19, 2022.2.0b10, 2023.1.0a14 (hangs while opening the project)
Reproducible on: Windows 10 Pro
Workaround:
1. In the Hierarchy expand “Player 185” GameObject and “Player_185” prefab and in the root select “Player_185”
2. In the Inspector expand “Shader Graphs_Unufied Player Shader” Material
3. Click on the Texture in “Nationality”
4. Open pinned texture “African_Array”
5. In the Inspector disable “Alpha Is Transparency” and press Apply
6. Observe the “Player_185” in the Scene view
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
- The Scene view flickers when moving around if there are visible Hair Shaders
- The gradient ShaderGraph is inverted when using the Perceptual blend mode
- Particle System allocates large amounts of memory when it is very far away from the origin of the Scene
- [Build Profile] [VisionOS/iOS/tvOS] - Build Player Library button is getting displayed depending on the selected build target
- EnsureRunningOnMainThread error in TessellationJob.ApplyInset
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2020.3.X):
This was fixed in later versions by the introduction of a new "Alpha Is Transparency" algorithm, which cannot be easily backported as we are aware that users are relying on the 2020.3 algorithm functioning exactly the way that it currently does. Fixing this properly in 2020.3 while keeping the same algorithm + landing that bugfix before 2020.3 reaches end-of-life seems quite unlikely: resolving as "Won't Fix".