Search Issue Tracker
Fixed
Fixed in 2023.1.X, 2023.1.0a6
Won't Fix in 2021.1.X
Votes
0
Found in
2021.1.4f1
2023.1.0a8
Issue ID
UUM-7711
Regression
No
[URP] RenderingData.lightData.visibleLights[] is not sorted when its count is lower than cullingParameters.maximumVisibleLights
How to reproduce:
1. Open the user's attached "VisibleLightsCountBug_URP_2021.2.zip" project
2. Open the "SampleScene" Scene
3. Move the Scene view camera a bit
4. Observe the Console log
Expected result: "PointSorted = True" is printed in the Console log
Actual result: "PointSorted = False" is printed in the Console log (Point Lights are not sorted by distance)
Reproducible with: 7.5.3 (2019.4.24f1) 10.5.0 (2020.3.7f1), 11.0.0 (2021.1.4f1), 12.0.0 (2021.2.0a15)
Note:
- The issue is not reproducible with Spot Lights
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 2023.1):
A correction was added to the documentation - to explain the behaviour that is seen in the project.
No behaviour was changed in this case.
See updated docs for ScriptableCullingParameters > maximumVisibleLights -
https://docs.unity3d.com/2023.1/Documentation/ScriptReference/Rendering.ScriptableCullingParameters-maximumVisibleLights.html
Resolution Note (2021.1.X):
Docs updated in 2023.1 - see resolution notes for more about the clarified behaviour.