Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.5f1
Issue ID
1056443
Regression
No
[Android] Uniform array dynamic indexing not working in vertex shader on Adreno 3XX/405
Steps to reproduce:
1. Open user attached project
2. Build and deploy to device
3. Inspect game objects
Expected behaviour: All GO's are green
Actual behaviour: Different GO's are different color
Reproduced on: 2017.4.6f1, 2018.1.7f1, 2018.2.0f1, 2018.3.0a4
Reproduced on: GLES2 and GLES3
Reproduced with:
VLNQA00039, Htc One mini 2 (HTC One mini 2), Android 4.4.2, CPU: Snapdragon 400 MSM8226, GPU: Adreno (TM) 305
VLNQA00108, Lge LG Leon 4G LTE (LG-H340n), Android 5.0.1, CPU: Snapdragon 410 MSM8916, GPU: Adreno (TM) 306
VLNQA00034, Lge Nexus 4 (Nexus 4), Android 5.1.1, CPU: Snapdragon S4 Pro APQ8064, GPU: Adreno (TM) 320
VLNQA00058, Sony Xperia Z (C6603), Android 4.4.4, CPU: Snapdragon S4 Plus MSM8960, GPU: Adreno (TM) 320
VLNQA00032, Motorola Moto X (2nd Gen) (XT1092), Android 5.1, CPU: Snapdragon 801 MSM8974AC, GPU: Adreno (TM) 330
VLNQA00054, Xiaomi MI 4LTE (MI 4LTE), Android 6.0.1, CPU: Snapdragon 801 MSM8974AC, GPU: Adreno (TM) 330
VLNQA00104, Lge Nexus 5 (Nexus 5), Android 6.0.1, CPU: Snapdragon 800 MSM8974, GPU: Adreno (TM) 330
VLNQA00023, Xiaomi Mi 4i (Mi 4i), Android 5.0.2, CPU: Snapdragon 410 MSM8916, GPU: Adreno (TM) 405
Not reproduced with:
VLNQA00107, Huawei Nexus 6P (Nexus 6P), Android 7.1.2, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
VLNQA00022, Xiaomi Redmi Note 3 (Redmi Note 3), Android 5.1.1, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00153, Google Pixel XL (Pixel XL), Android 8.0.0, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
VLNQA00126, Samsung Galaxy S5 mini (SM-G800F), Android 6.0.1, CPU: Exynos 3 Quad 3470, GPU: Mali-400 MP
VLNQA00110, Samsung Galaxy Note2 (GT-N7100), Android 4.4.2, CPU: Exynos 4 Quad 4412, GPU: Mali-400 MP
VLNQA00121, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00012, Samsung Galaxy S6 (SM-G920F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00021, Samsung Galaxy S7 (SM-G930F), Android 7.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
VLNQA00096, Samsung Galaxy S8 (SM-G950F), Android 8.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00152, Huawei P9 (EVA-L19), Android 7.0, CPU: HiSilicon Kirin 955, GPU: Mali-T880
iPod Touch 6th gen, iOS 10.2.1
iPhone 7 Plus iOS 11.1.1
iPhone 6S Plus iOS 10.3.2
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2018.3.X):
Won't fix: GPU drivers issue. Most reliable workaround is to use unsigned integer variables for array indexing.