Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2019.4.10f1
Issue ID
1281637
Regression
No
Performance degrades when Unity can't resolve which Light Probe to use for a specifically placed object in Scene
How to reproduce:
1. Open the user's attached project "LightProbePerformanceDrain.zip"
2. In the Project tab, open Assets/Scenes/LVL_Desert.unity
3. Open the Profiler (Window > Analysis > Profiler) and make sure that Target Player is set to Playmode
4. Enter Play mode and wait for approx. 2 seconds from when the Profiler starts recording
5. Exit Play mode
6. Click on one of the peaks in CPU Usage in Profiler and make sure that display is set to Hierarchy
7. In the display pane, search for "ExtractRenderNodeQueue" (or find it manually by going to PlayerLoop > Camera.Render > CullResults.CreateSharedRendererScene > WaitForJobGroupID > ExtractRenderNodeQueue)
Expected results: Total amount of time spent on ExtractRenderNodeQueue is less than 1%
Actual results: Total amount of time spent on ExtractRenderNodeQueue is 25-60% (see "profiler.png")
Reproducible with: 2019.4.13f1
Not reproducible with: 2020.1.10f1, 2020.2.0b8, 2021.1.0a2
Could not test with: 2018.4.28f1 due to errors
Notes:
* The issue seems to be caused by one specifically placed Long Ramp and can be fixed by disabling it (Statics > Ramps > levelprefab_general_stunt_ramp_long_BUGGED_PROBE_BEHAVIOR in Hierarchy tab)
* The issue seems to reproduce on Xbox and Windows Standalone builds, as well as in the Editor
* According to the user, the performance drain is caused by objects for which Unity cannot resolve a Light Probe to use
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
- [VisionOS][iOS] Second camera functionality is broken on XR scene
- Crash on GfxDeviceD3D12Base::DrawBuffersCommon when changing a specific prefab
- Crash on GfxDeviceD3D12Base::UpdateComputeResources when in the Play mode
- Crash on SerializedProperty_CUSTOM_SetStringValueInternal when setting SerializedProperty string value
- "Shader error: 'LoadDOTSInstancedData_half4'" error is thrown when using a Shader with halfs instead of floats for a material with GPU Resident Drawer enabled
Resolution Note (2020.1.X):
The issue could be worked around by adding more light probes around the prefab that's located far from the original probeset and rebaking GI. Moreover, this issue is fixed in the later Unity versions (2020.1 and newer).