Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.1.0b9
Issue ID
1005571
Regression
No
[GI] Global Illumination processes are taxing the CPU in empty scenes while using the editor
Steps to reproduce
1. Create a new project, and remove everything from the scene (or alternatively, download the attached project).
2. Disable both realtime and baked GI options in the Lighting window.
3. Make sure that the Profiler window is open.
4. Press Play in the editor.
5. Notice the CPU utilization in the Global Illumination section in Profiler.
Expected behavior
With all the lightmapper options disabled, CPU should not be utilized by GI related tasks.
Actual behavior
CPU utilization by GI-related tasks sometimes reaches 1ms.
Notes
• Tested in Unity 2017.3.0p3, 5.6.5.p1, 2017.2.0f3, 2018.1.0b9.
• Clearing baked data, GI cache (both within Unity and manually), and removing the lightmap folder does not fix the issue.
• Restarting the editor does not help.
• The issue affects both Scene and Game modes.
• The issue is not present in standalone builds.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment