Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.2.X
Votes
130
Found in
2019.1
2019.1.3f1
2019.2.0a1
2019.3.0a1
Issue ID
1155879
Regression
No
[SRP] unity_LightIndices[1] are identical to every object and are set per frame
How to reproduce:
1. Open the attached "case_1155879-LightIndices" project
2. Move around the Scene and inspect how the spheres are lit
Expected results: The lighting should not change
Actual results: The lighting changes and flickers
Reproducible with:
2019.1.6f1 (with SRP 5.16.1)
2019.2.0b6, 2019.3.0a6 (with SRP 6.7.1)
Note: By using the Frame Debugger you can notice that every rendered object has identical unity_LightIndices[1]. This data is set every frame instead of every draw and can change based on the Camera's position.
Comments (2)
-
Jasper-Flick
Nov 22, 2019 21:27
The indices still fail when the SRP Batcher isn't active, when more than one material is used. It fails in so many ways that I don't know where to begin. Do some tests!
-
Jasper-Flick
Jun 19, 2019 09:31
Although this issue is listed under Scriptable Render Pipeline Lightweight, it affects all SRPs. It's not a bug in the LWRP package, but in Unity 2019.
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 2019.3):
Fixed in: 2019.2.0b10, 2019.3.0a10