Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.4.X
Votes
3
Found in
5.5.4p3
Issue ID
949576
Regression
No
[Android] Objects with Mobile Vertex Lit shader ignore Point light and Spot light when built on a device with Adreno 418 GPU
To reproduce:
1. Download and run attached "test_vertex_lighting.zip" project.
2. Open it on a device with Adreno 418 GPU.
Expected result: Objects receive lighting from light source.
Actual result: Objects aren't receiving any lighting from light source.
Reproduced with: 2017.3.0b1, 2017.2.0f1, 2017.1.1p3, 5.6.3p3, 5.5.4p5, 5.4.5p3, 5.3.8p2.
Devices under test:
Reproduced with:
Lge LG H815 (G4), OS:6.0, CPU:arm64-v8a, GPU:Adreno (TM) 418,
Build:lge/p1_global_com/p1:6.0/MRA58K/1620215065b6f:user/release-keys
Not reproduced with:
Samsung SM G925F (Galaxy S6 Edge), OS:7.0, CPU:arm64-v8a, GPU:Mali-T760,
Build:samsung/zeroltexx/zerolte:7.0/NRD90M/G925FXXU5EQFC:user/release-keys
Xiaomi Mi 4i*, OS:5.0.2, CPU:arm64-v8a, GPU:Adreno (TM) 405,
Build:Xiaomi/ferrari/ferrari:5.0.2/LRX22G/V8.1.5.0.LXIMIDI:user/release-keys
Notes: Issue is specific to devices with Adreno 418 GPU. Directional light works as expected.
Verified with: 2018.1.0a6
Comments (1)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
dputros
Oct 03, 2017 05:57
What is the workaround for this?