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
- [tvOS] Project crashes on startup on Apple TV simulator (both X86_64 and ARM64 architectures)
- Context menus open on a different monitor when there are three monitors used
- Crash on Umbra::QueryExt::queryStaticShadowCasters when opening a specific project
- Crash on GfxDeviceD3D12Base::DrawBuffersCommon when opening a specific project
- Shader variants are recompiled while Building when the Platform is switched and changed back after the first Build
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.