Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2019.1.0a7
2019.1.0a10
Issue ID
1105065
Regression
Yes
Lights not rendered correctly on Samsung S6 Edge device on Vulkan
Steps to reproduce:
1. Open attached project
2. Open "Lights" scene and build for android
3. Observe lights behaving incorrectly, almost not lighting up the surface, having weird cutouts
Expected: The plane should be covered in a brightly lit rainbow of colors
Actual: It's not. Something in the lights or shaders went wrong
Repro on 2019.1.0a10, 2019.1.0a8, 2019.1.0a7
No repro on 2018.3.0b12, 2019.1.0a6
Devices Under Test:
Repro:
VLNQA00093, Samsung Galaxy S6 edge (SM-G925F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
No Repro:
VLNQA00003, Razer Razer Phone (Phone), Android 7.1.1, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00136, Samsung Galaxy S9+ (SM-G965F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00005, Samsung Galaxy S7 (SM-G930V), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00125, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00138, Huawei P20 Pro (CLT-L29), Android 8.1.0, CPU: HiSilicon Kirin 970, GPU: Mali-G72
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment