Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.2.0f2
Issue ID
1063828
Regression
No
[Android] Tessellation not visible or has artifacts on devices with Adreno 5xx/630 with MSAA enabled
Reproduction steps:
1) Download and open attached project
2) Go to Project Settings > Quality
3) Enable Anti Aliasing (set it to 2x, 4x or 8x - all of these modes reproduce the issue)
4) Build and run on an Android device
-- Notice that sphere is not rendered or, as in some cases, game crashes
Expected result: Expecting to see a red sphere rendered
Reproduced with:
Unity 2018.3.0a11, 2018.2.7f1, 2018.1.9f2, 2017.4.10f1, 2017.2.3p4
Devices under testing:
Reproduced on:
VLNQA00153, Google Pixel XL (Pixel XL), 8.0.0, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530 - (renders black screen)
VLNQA00090, Samsung Galaxy S8 (SM-G950U), 7.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540 - (renders black screen)
VLNQA00173, Xiaomi Redmi 6Pro (Redmi 6 Pro), 8.1.0, CPU: Snapdragon 625 (MSM8953), GPU: Adreno (TM) 506 - (sphere is not rendered)
VLNQA00091, Google Pixel 2 XL (Pixel 2 XL), 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540 - (sphere is not rendered)
Unable to reproduce on:
VLNQA00144, Samsung Galaxy S9 (SM-G960U1), 8.0.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00107, Huawei Nexus 6P (Nexus 6P), 8.0.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
VLNQA00134, Samsung Galaxy S8 (SM-G950F), 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00025, Xiaomi Mi 5s (MI 5s), 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00135, Lge LG G5 (LG-H850), 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
iPhone 7 Plus A10 A1784 iOS 11.1 - renders sphere in a magenta
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
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- Dynamic text is rendered in the background when it is inside the <font> tag
Resolution Note (2019.3.X):
Won't fix: Drivers issue, drivers have a fix on latest devices. Workaround on some devices: render the tessellated geometry first.