Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2017.3
2018.4
2019.4
2020.3
2021.1
2021.2
Issue ID
1310218
Regression
No
CullPerObjectLights have ms increase every frame when Light Probe property is set to Blend Probes
How to reproduce:
1. Open the attached "CullPerObjectLights.zip" project
2. Open the "SampleScene" Scene
3. Enter Play Mode
4. Open the Profiler (Window -> Analysis -> Profiler)
5. Enter "CullPerObjectLights" in the search bar
6. Press and drag on any Frame in the Profiler window
7. Observe the ms in the Overview
Expected result: CullPerObjectLights has 0ms
Actual result: CullPerObjectLights has 0.2ms
Reproducible with: 2018.4.33f1, 2019.4.23f1, 2020.3.2f1, 2021.1.1f1, 2021.2.0a11
Notes:
- The issue is reproducible with both Forward and Deferred Rendering Path
- When Rendering Path is set to Legacy Vertex Lit the ms is 0.4
- The issue is not reproducible if Mesh Renderer's Light Probe property is set to Off
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
- Set as first/last sibling is not working when using Menu Bar
- [Hololens 2] GameObjects with an ARAnchor attached are deleted when disabled
- AvatarBuilder.BuildHumanAvatar() is unable to find Transform when entering Play Mode
- Trying to read mesh produces "Reading UV coordinates of mesh "" failed. Only float32 format is supported." error
- Reload Script Assemblies never load when entering debug mode
Resolution Note (fix version 2021.2):
Performance improvement when mesh render does not have the light probes property set to none and no light probes are in the scene.