Search Issue Tracker
Fixed in 5.3.5
Votes
0
Found in
5.3.2p1
Issue ID
769275
Regression
No
[Android] Normals not oriented properly on Adreno 2xx models
To reproduce:
1) Open attached project
2) Open Scenes/Main scene
3) Make sure the camera is set to position X: 2.940638 Y: 25.82 Z: 14.9368 and rotation: X: 35 Y: 225 Z: 0
4) Play on editor to see how it is expected to look
5) Build and run on device
6) Notice how distorted the objects look (and in some Unity versions even flicker constantly)
DUT(reproduced):
HTC Sensation XE (Android 4.0.3) (Adreno 220)
LG Optimus L7 (Android 4.0.3) (Adreno 200)
Samsung Galaxy M Style (Android 2.3.6) (Adreno 200)
DUT(not reproduced):
Samsung Galaxy S5 Neo (Android 5.1.1) (ARM Mali-T720)
Google Nexus S (Android 2.3.3) (PowerVR SGX 540)
Samsung Galaxy Note 10.1 (Android 4.1.2) (ARM Mali-400)
Google Nexus 5 (Android 6.0.1) (Adreno 330)
LG Optimus 4X HD (LG X3) (Android 4.0.3) (Nvidia Tegra 3)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- GBuffer/Render Deferred Lighting and Render Pass related Errors constantly thrown after switching a Build Profile
- Player settings icons are not retrieved when using "PlayerSettings.GetIcons" method
- Bunch of "TargetParameterCountException" errors thrown in the Editor Console when opening the "Adaptive Probe Volumes" tab in the "Lighting" window
- Non-removable serialized data for a renderer feature still appears even when the renderer feature is deleted
- URP Cascaded Shadows do not have a falloff in Player when the Player is built not in Development Mode
Add comment