Search Issue Tracker
Duplicate
Votes
0
Found in
2018.1.0a6
2018.2.1f1
Issue ID
1066341
Regression
Yes
[Android] Some Mesh triangles are missing on Moto G 4 with OpenGLES3
Steps to reproduce:
1. Open user attached project
2. Build & Run on Android device
3. Observe the missing mesh triangles on spheres
Expected result: There should be no missing mesh triangles are missing on Moto G 4 with OpenGLES2
Reproduced in: 2018.3.0a7, 2018.2.1f1, 2018.2.0a1, 2018.1.9f1, 2018.1.0a6
Not reproduced in: 2018.1.0a5, 2017.4.8f1
Regression since: 2018.1.0a6
Tested devices:
Reproduced with:
Motorola Moto G (5) Plus (Moto G (4)), 7.0, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 405
Htc HTC One M9*, OS:7.0, CPU:arm64-v8a, GPU:Adreno (TM) 430
No repro:
Lge Nexus 5 (Nexus 5), 6.0.1, CPU: Snapdragon 800 MSM8974, GPU: Adreno (TM) 330
Sony Xperia Z3 (D6603), 6.0.1, CPU: Snapdragon 801 MSM8974AC, GPU: Adreno (TM) 330
Google Pixel (Pixel), 8.1.0, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
Xiaomi Mi 4i (Mi 4i), 5.0.2, CPU: Snapdragon 410 MSM8916, GPU: Adreno (TM) 405
iPhone 7+ iOS 11.1.1
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
- Sprite Masks affect Sprite Renderers outside their range when a Light2D is present with specific Target Sorting Layers selected
- URP Lens Flare is rendered in the wrong position when Render Graph Compatibility Mode is enabled and Render Scaling is not 0
- Editor crashes on DrvPresentBuffers when loading RenderDoc while using OpenGLES 3.0 or OpenGLES 2.0 Graphics API
- [Test Runner] Incorrect name under Window > Panel after project restart
- [iOS] Crash when using fallback fonts created at runtime
This is a duplicate of issue #1066274