Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.2.0a12
Issue ID
1147073
Regression
No
[XR][Android] Using deferred rendering path results into black screen with single-pass
How to reproduce:
1. Open attached project
2. Build to Android
Result - Observe black screen or one eye rendered only.
Notes:
1. Seems to happen only with Single-Pass
2. Oculus+Deferred seems worst, Daydream+Cardboard only exhibits problems on S9 and Note9(Mali). See below device list for more details
Reproducible with - 2019.3.0a1, 2019.2.0a12, 2019.1.0f2
DUT:
Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72 (Black screen on all SDK's)
Samsung Galaxy S10+ (SM-G975U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Samsung Galaxy S8 (SM-G950F), Android 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
Samsung Galaxy Note8 (SM-N950U), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
Samsung Galaxy Note9 (SM-N960F), Android 8.1.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72 (Black screen on all SDK's)
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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Resolution Note:
Unity's support for Cardboard, Daydream, and GearVR has been deprecated in our 2019.3 release and will be removed in a future release. As such, we're deprioritizing our support for those XR platforms, and won't be actively fixing issues related to the platform.
This issue is being marked as Won't Fix. If that resolution isn't appropriate, please reopen the issue and let us know the issue's impact for you.