Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a14
Issue ID
1116224
Regression
No
[XR][Android][Cardboard] Shadows are culled too soon on Huawei Mate 20 Pro
How to reproduce:
1. Open attached project
2. Build to device
3. Move the camera so that the shadow of the cube would be barely visible (video attached)
Expected result - A part of shadow is still visible
Actual result - Shadow is culled too soon
Reproducible with - 2019.1.0a14, 2018.3.1f1, 2018.3.0b1
DUT:
Reproducible with:
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
Not reproducible:
VLNQA00230, Oneplus OnePlus6T (ONEPLUS A6013), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00166, Huawei P20 (EML-L29), Android 8.1.0, CPU: HiSilicon Kirin 970, GPU: Mali-G72
VLNQA00164, Samsung Galaxy S8 (SM-G950F), Android 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
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
- Main Camera rendering is being overwritten by a UI Camera when using multiple cameras with URP and the second camera's background type is set to "Uninitialized"
- VisualTreeAsset has significantly increased memory allocation size at runtime when the project is built with IL2CPP scripting backend
- NullReferenceException is logged when cancelling Shader Graph recovery of an already deleted Shader Graph
- White Edges appear during Camera movement in runtime when using FSR2 with Motion Vectors and Exposure enabled
- Lens Flare renders without occlusion when the light source is obstructed by solid objects when running on Android using OpenGL
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.