Search Issue Tracker
Fixed
Votes
0
Found in
2018.4
2019.4
2019.4.16f1
Issue ID
1298626
Regression
No
[Android] Shader is not rendered on Adreno 610 and Adreno 612 devices
Steps:
1. Open user's attached project ("StreetDrag_2.zip")
2. Player Settings > Publishing Settings > Custome Keystroke - disable
3. Build and Run on Adreno 610 or Adreno 612 device
Expected behavior: shader is rendered - vehicle and other internal parts of the room are visible.
Actual behavior: shader is not rendered - the room looks dark.
Reproduced with: 2018.4.33f1, 2019.4.23f1, 2020.1.0a16.
Not reproduced with: 2020.1.0a17, 2020.3.2f1, 2021.1.1f1, 2021.2.0a10.
The issue has been fixed in: 2020.1.0a17.
Reproduced with:
VLNQA00334, Xiaomi Mi A3 (Mi A3), Android 10, CPU: Snapdragon 665 SM6125, GPU: Adreno (TM) 610
Not reproduced with:
VLNQA00042, Lge LG G3 (LG-D855), Android 5.0, CPU: Snapdragon 801 MSM8974AC, GPU: Adreno (TM) 330
VLNQA00096, Samsung Galaxy S8 (SM-G950F), Android 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00229, Oneplus OnePlus6T (ONEPLUS A6013), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
The issue has been fixed in: 2020.1.0a17.