Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0f2
Issue ID
1038898
Regression
No
[Android][Meizu Pro 7 Plus] Rotating GO with lambert material makes it flicker artifacts
Steps to reproduce:
1. Open user attached project
2. Deploy to device
3. Inspect visual artifacts
Reproduced on: 2018.1.0f2, 2018.2.0f2, 2018.3.0a6
Reproduced on: GLES2 and GLES3
DUT:
Reproduced with:
VLNQA00155, Meizu PRO 7 Plus (PRO 7 Plus), Android 7.0, CPU: MediaTek Helio X30 MT6799, GPU: PowerVR Rogue Marlowe
Not reproduced with:
VLNQA00004, Meizu - (MX5), Android 5.0.1, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
VLNQA00076, Amazon Fire HD 8 (2015) (KFMEWI), Android 5.1.1, CPU: MediaTek MT8135, 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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2019.3.X):
Won't fix: caused by z-fighting between forward base and forward additive shader passes (caused by GPU optimizations calculating different depth value in each pass).