Search Issue Tracker
Fixed in 5.3.0
Votes
90
Found in
5.0.1f1
Issue ID
686526
Regression
Yes
[Shaders] Missing fallback from Directional to NonDirectional mode with shaders that do not support it (GLES2.0/SM2.0/DX11level9
WORKAROUND: Use non-directional mode
To reproduce:
1. Open attached project
2. Build and run to iOS (same on Android based on forum thread)
3. Notice there is no lighting (screen attached)
Gles2 is forced in settings. Works fine on gles3
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
sisermann
Apr 08, 2015 20:17
GearVR is depending on this, ES 3.0 is not working properly with GearVR. So all folks will have to go back down to ES 2.0.
The Oculus VR JAM 2015 is happening soon ... So it would be cool if the entrants would either be working on ES 3.0 or ES 2.0 with lightmaps or better both.
sisermann
Apr 08, 2015 20:17
GearVR is depending on this, ES 3.0 is not working properly with GearVR. So all folks will have to go back down to ES 2.0.
The Oculus VR JAM 2015 is happening soon ... So it would be cool if the entrants would either be working on ES 3.0 or ES 2.0 with lightmaps or better both.
Tommie060708091011
Apr 04, 2015 15:07
This is a major issue I would say.
The average devices in households still only support gles2 I think.
How can we raise awareness for this?