Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0a8
Issue ID
1022997
Regression
No
[Android] [MeizuMX5] Artefacts appear on UI when switching MSAA to 4 or 8 during runtime
How to reproduce:
1. Open the attached project
2. Build and run Test scene on Meizu MX5
3. Click on Switch MSAA button 2 or 3 times
4. MSAA switches to 4x Multi Sampling or 8x Multi Sampling
Result: artefacts appear on UI
Reproducible: 2017.2.2p2, 2017.3.2f1, 2018.1.0b13, 2018.2.0a5, 2018.2.0a8
DUT(reproducible):
Meizu MX5 (5.0.1, MediaTek Helio X10, PowerVR Rogue G6200, GLES 3.1)
DUT(not reproducible):
Google Pixel 2 ( 8.1.0, Qualcomm Snapdragon 835, Adreno 540 , GLES 3.2)
Samsung Galaxy Note 8 (7.1.1, Qualcomm Snapdragon 835, Adreno 540, GLES 3.2)
Samsung Galaxy S8 (7.0, Samsung Exynos 9 Octa, Mali-G71, GLES 3.2)
Nvidia SHIELD tablet (6.0.1, nVidia Tegra K1, nvidai Tegra K1, GLES 3.2)
Samsung Galaxy Tab3 10.1 (4.4.2, Intel Atom Z2560, PowerVR SGX 544MP2, GLES 2)
Samsung S3 Mini VE (4.2.2, Marvell PXA988, Vivante GC1000, GLES 2.0)
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
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
- [Linux] "Error while reading movie" errors are thrown when opening templates
- Shader warnings are being thrown after building Mixed Reality Template
Resolution Note:
Won't fix: device specific issue. Workaround: set MSAA quality to highest expected level in project settings, then during runtime lowering MSAA level will not produce artifacts.