Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.3.0f2
Issue ID
977455
Regression
No
[SpriteRenderer] Illumination does not work on Sprite Renderer on WebGL/Mobile platforms or in playmode
How to reproduce:
1. Open the user attached project, switch platform to Android(or iOS and WebGL)
2. Open "TestScene1" and observe the Sprite Renderer with "Test Material" attached (see that Illumination is not working)
3. Create a Cube or any other 3D Object and assign "TestMaterial" and "HDR1" texture and see that Illumination is working
Expected result: Both Sprite Renderer and Mesh Renderer should display same results (both should be Illuminated)
Actual result: Illumination does not work with Sprite Renderer
Reproducible with - 2017.2.2p2, 2017.3.2f1, 2018.1.0b12, 2018.2.0a6
Notes - On Standalone when entering playmode, Illumination on Sprite Renderer also stops working
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
Add comment