Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.2.0b10
2019.2.8f1
2019.3
2020.1
Issue ID
1188928
Regression
Yes
[SRP] Objects lit by multiple Spot lights sometimes have their _unityLightIndices[0] set to all zeroes
How to reproduce:
1. Open the attached "LightIndicesBug.zip" project
2. Open scene "SampleScene"
3. Open Window > Analysis > Frame Debugger and click "Enable" in the opened window
4. In the Frame Debugger, select "Draw Mesh Cube (2)"
5. Inspect the "unity_LightIndices0[2]" shader property
Expected results: The unity_LightIndices matrix contains three different indices
Actual results: The unity_LightIndices matrix is set to all zeroes
Reproducible with: 2019.2.0b10, 2019.3.0b7, 2020.1.0a7
Not reproducible with: 2019.2.0b9
Note:
If the unity_LightIndices matrix is correct, try moving any of the cubes until you see some flicker in the scene and then use the Frame Debugger to confirm the issue
-
fherbst
Oct 22, 2019 12:57
When will this be backported? 2019.3 is unusable with URP due to this bug!
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a8