Search Issue Tracker
Fixed in 2017.2.0f3
Votes
33
Found in
5.2.1p1
Issue ID
743462
Regression
No
[Occlusion culling] Performance spike in Culling when Camera is not rendering every frame
Reproduction steps:
1. Download and open the repro project form the attached link
2. Open and play the "CorridorDemo" scene (Assets\Scenes)
3. Check in the profiler, that ever 2 seconds, when FakeCamera calls to Render function, it shows a performance spike on Culling call
Note:
- When on "FakeCamera" Culling Mask is set only to "water" layer there aren't any spikes. Spikes are about from 5 ms to 18 ms.
- This culling spike problem relates to realtime reflection probes as well. Performance spikes are higher about 10 ms when realtime reflection probe (set to render all elements) is rendered faster than every 0.5 s.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Source Generation with GeneratePropertyBag fails when using reserved keywords as variable names with @ prefix
- Prismatic ArticulationBody moves in opposite direction when using targetVelocity
- Shader Graph skybox material is rendered inccorrectly in builds when "Allow Material Override" or "Cast Shadows" are enabled and the "Deferred" Rendering Path is used
- Object motion is affected by incorrectly added rotation motion when importing animations
- Base class's Context Menu method is called when calling it in the Editor from the child class and the child class overrides this method
Add comment