Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3.0a4
Issue ID
1159644
Regression
No
[Vulkan] Adreno 630/640 generates corrupted mipmaps when height of the texture is power of 2 + 1
To reproduce:
1. Download and open 1159644_smallerRepro.zip project
2. Build and run project on an Android device with Adreno 630
Expected result: Plane is rendered like in the editor
Actual result: Plane texture is corrupted
Note: Reproduces when texture height is a number power of 2 1, for example 513, 1025 etc. so if texture size is 513x513 - it reproduces. If 513x512 - doesnt. If the height is any other number - it does not reproduce neither.
Reproduced with: 2019.1.6f1, 2019.2.0b5, 2019.3.0a5
Devices under testing:
Reproduced with:
VLNQA00219, SAMSUNG SM-N960U, Snapdragon 845 SDM845, Adreno (TM) 630, 8.1.0
VLNQA00150, SAMSUNG SM-G960U, Snapdragon 845 SDM845, Adreno (TM) 630, 8.0.0
VLNQA00263, GOOGLE Pixel 3, Snapdragon 845, Adreno (TM) 630, 9.0.0
VLNQA00276, ASUS_Z01QD, Snapdragon 845, Adreno (TM) 630, 8.1.0
VLNQA00142, SAMSUNG SM-G965U1, Snapdragon 845, Adreno (TM) 630, 8.0.0
Not reproduced with:
VLNQA00153, GOOGLE, Pixel XL, Snapdragon 821, Adreno (TM) 530, 9.0.0
VLNQA00149, SAMSUNG SM-G960F, Exynos 9 Series 9810, Mali-G72, 9.0.0
VLNQA00006, SAMSUNG SM-G930F, Exynos 8 Octa (8890), Mali-T880, 8.0.0
VLNQA00027, XIAOMI MI MAX, Snapdragon 650, Adreno (TM) 510, 7.0.0
VLNQA00267, Samsung Galaxy S10, Exynos 9 Series 9820, Mali-G76, 9
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
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Resolution Note (2019.3.X):
This issue is caused by Adreno 630 and 640 drivers. When texture has size of 513x513 generated mipmaps are corrupted so objects with lower level of detail are using corrupted mipmaps hence the originally described artifacts appear.