Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.40f1
2021.3.11f1
2022.1.19f1
2022.2.0b10
2023.1.0a13
Issue ID
UUM-16532
Regression
No
Various light-related events incur a CPU cost in scenes with baked lights
Steps to reproduce
- Download the attached project (BakedLightsCPUSpike-URP.zip)
- Open the EmptyScene
- Open the Profiler window, and in the search box, type in "light"
- Enter Play mode
- Press T on the keyboard to load a scene additively
- Scrub through the graph until you find the the events matching the "light" search query
Expected behavior
- Light-related events should not incur a CPU cost when there are no realtime lights in the scene
Actual behavior
- Various events incur multiple milliseconds worth of CPU time even when there are no realtime lights present (check the attached screenshot)
Notes
- Reproduces in: 2020.3.40f1, 2021.3.11f1, 2022.1.13f1, 2022.2.0b8, 2023.1.0a11
- Tested on macOS
- Only reproduces upon the loading the scene initially; does not reproduce upon loading and unloading that same scene after it had been initialized
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
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
Resolution Note:
We are working on Forward+ and RenderGraph that is rewriting parts of these functions. The current runtime cost of these functions is in the order of 0.0x ms which is not enough user pain to justify we improve the old code path.
Resolution Note (2023.1.X):
We are working on Forward+ and RenderGraph that is rewriting parts of these functions. The current runtime cost of these functions is in the order of 0.0x ms which is not enough user pain to justify we improve the old code path.