Search Issue Tracker
Fixed
Votes
0
Found in
2019.4.1f1
2019.4.7f1
Issue ID
1269987
Regression
Yes
[Android]A fractured or black screen is rendered on Android devices When using Vulkan Graphics API
Steps to reproduce:
1. Open user's attached project "Dark3D.zip"
2. Build it on Android
3. Notice the screen is black or very fragmented view is rendered
Expected results: The Scene is rendered
Actual results: A black screen or fragmented view is rendered
Reproducible with: 2019.4.7f1, 2019.4.8f1
Unable to reproduce in: 2019.4.6f1
VLNQA00220, Samsung Galaxy Note9 (SM-N960F), Android 8.1.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00123, Google Pixel 2 XL (Pixel 2 XL), Android R, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00024, Xiaomi Mi 5 (MI 5), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
Fixed in: 2020.1.0a1
Note:
-Andreno GPU renders a fractured screen, Mali GPU renders a black screen
-The issue only reproduces with Vulkan
- Screenshots of fragmented view are attached
Comments (2)
-
CineTek
Aug 17, 2020 13:25
When is this going to be implemented in 2019.4 LTS? We are unable to continue suporting Android at all without this being fixed!
-
orsoleads
Aug 15, 2020 12:53
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
- Tooltip messages should be presented in human language not in code strings
- [Linux] Editor doesn’t auto reload when an Asset is imported or a Script is changed
- MouseDownEvent is triggered when changing from Scene view to Game view
- "GlobalObjectIdentifierToObjectSlow" returns Null when retrieving "GlobalObjectId" from GameObject inside a Prefab
- Shader is invisible in the Build when using BiRP on Meta Quest 2
Resolution Note:
Fixed in: 2020.1, 2020.2