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
Comments (1)
-
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a8