Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.4
2018.4.27f1
2019.4
2020.1
2020.2
Issue ID
1284638
Regression
No
[Android] Eyelid is displayed incorrectly when skinMeshRenderer.SetBlendShapeWeight is used on Andreno 506 and 510 GPU's
How to reproduce:
1. Open the user's attached project "TestShader.zip"
2. Load the Scene "test1"
3. Build and Run the project to an Android device
4. On the device move both of the UI sliders completely to the right
Expected result: Both eyelids get properly closed
Actual result: Left eyelid clips over and exceeds its length, right eyelid is completely open
Reproducible with: 2018.4.30f1, 2019.4.17f1, 2020.1.17f1, 2020.2.0a20
Not reproducible with: 2020.2.0a21, 2020.2.0f1, 2021.1.0a9
Reproducible on:
VLNQA00022, Xiaomi Redmi Note 3, Android 6.0.1, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00052, Xiaomi MI MAX, Android 7.0, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
Reproduces according to the user on:
OPPO R9s, Android: 6.0, CPU: Octa-core 2.0 GHz Cortex-A53, GPU: Adreno 506
Vivo X7, Android: 6.0, CPU: Octa-core (4x1.8 GHz Cortex-A-72 & 4x1.4 GHz Cortex A-53), GPU: Adreno 510
OPPO R9sk, Android: 7.1.1, CPU: Octa-core 2.0 GHz Cortex-A53, GPU: Adreno 506
Not reproducible on:
VLNQA00288, Samsung Galaxy J7, Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830
VLNQA00332, Samsung Galaxy XCover4, Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
N/A, Nokia 7 Plus, Android 10, CPU: Snapdragon 660, GPU: Adreno (TM) 512
N/A, Google Pixel XL, Android 9, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
N/A, Meizu MX5, Android 5.0.1, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
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 (fix version 2020.2):
Does not reproduce anymore in 2020.2.0a21 and above