Search Issue Tracker
Fixed
Votes
0
Found in
4.3.0a2
Issue ID
554998
Regression
Yes
Occlusion Culling appears to be slower than not culling
Steps to reproduce :
- import the project attached
- open the scene
- press play and look at CPU Usage in the profiler
- select the Antigua Stadium and clear the Occlusion data
- press play again and notice the profiler
*Note :
Regression from 4.2RC4, before clearing the data the CPU usage was lower that it is in 4.3.
Comments (5)
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
- “Frame Debugger On” text color not maintained across different Editor Themes in toolbar
- Rendering artefacts appear in the Game view window when maximizing/minimizing Inspector window and Frame Debugger is Enabled
- [MacOS] AdvancedDropdown in the Profiler is not scrollable even when not all options in the list are visible
- Memory leak when a lot of Particle Systems instantiated while Profiler is open
- "ArgumentOutOfRangeException" error is thrown when trying to delete letters from an RTL TextField when using the Advanced Text Generator
danisb
Jul 03, 2015 08:20
We're having CPU spikes in all platforms (PC/PS4/XB1). 5.0.1 and 5.0.3
phasiclabs
Jun 24, 2015 12:15
We are also seeing Camera.Render->Culling->SceneCulling->WaitingForJob stalling once every couple of seconds using 5.0.1 (the stalls are for 10-16 seconds).
cadellinman
May 28, 2015 16:19
Still not fixed. There is a thread about the issue here- http://forum.unity3d.com/threads/occlusion-culling-cpu-spike-in-profiler.314978/
simmania
Mar 11, 2015 12:23
This is not fixed in Unity5.0.0f4
Furthermore: enabling occlusion culling introduces heavy spikes in the rendering performance.
More specifically the function from profiler:
Camera.Render->Culling->SceneCulling->WaitingForJob stalls the CPU on these spikes massively.