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.
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
- Editor crashes when loading RenderDoc with Graphics API set to OpenGLES2 or OpenGLES3
- [Windows] Development Build with no scenes shows a purple screen when using OpenGLES3 graphics API
- Shader variants take too much memory at runtime
- [HDRP][VFX] Output mesh with default shader is incorrectly sorted before the HDRP fog
- Error "'GamepadSpeakerOutputType' does not exist in the namespace 'UnityEngine'" occurs in the Console when building a project
mayasarii876
Mar 09, 2022 02:58
http://103.56.148.201/
http://103.56.148.201/newmpo
http://103.56.148.201/mpo17
http://103.56.148.201/mpomm
http://103.56.148.201/mpotower
http://103.56.148.201/parisklub
http://103.56.148.201/juraganslot
http://103.56.148.201/mpo500
http://103.56.148.201/mpokick
http://103.56.148.201/mpoyes
http://103.56.148.201/xyzklub
http://103.56.148.201/betmpo
http://103.56.148.201/ogslot88
http://103.56.148.201/hoki777
http://103.56.148.201/mpojuta
http://103.56.148.201/299slot
http://103.56.148.201/mpo188
http://103.56.148.201/mpogacor
http://103.56.148.201/mpo300
http://103.56.148.201/rgo365
http://103.56.148.201/kingdom288
http://103.56.148.201/wigompo
http://103.56.148.201/mpo8899
http://103.56.148.201/mpopelangi
http://103.56.148.201/mpo555
http://103.56.148.201/dutampo
http://103.56.148.201/klik368
http://103.56.148.201/388hero
http://103.56.148.201/19dewa
http://103.56.148.201/mpoxl
http://103.56.148.201/mpoas
http://103.56.148.201/mposun
http://103.56.148.201/qqslot
http://103.56.148.201/mposport
http://103.56.148.201/dewa234
http://103.56.148.201/mesinmpo
shubhamswaraj2021
Aug 19, 2020 13:09
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
BrucePhillips
Jul 11, 2020 12:51
Tried this and it worked. Thanks for sharing. <a href="https://www.beststampedconcrete.com/naples.html">fort myers stamped concrete"</a>
concretecolumbia
Dec 16, 2019 17:20
Why doesn't it work in my end?
https://www.charlottejunkremovalservice.com/
maxgray1
Oct 01, 2019 12:15
Your actual writings capabilities are good. You've got to publish even more.
https://pokecoinsblaster.club
https://simsimoleons.club
https://battlecatsxp.xyz
https://shadow2gems.club
https://bowlingkingcash.xyz
jmitcheson
Jul 12, 2017 03:33
In which release is this issue fixed? It is appearing on the "Known issues" list for 2017.2
tnqiang
Feb 23, 2017 11:54
Occurs in Unity 5.5.0p3.
And the cpu consume is always high.
Mikael-H
Dec 16, 2016 14:29
Seeing this in 5.4.1f as well
Rickywild
Apr 12, 2016 12:24
I'm getting spikes that drop CPU below 30FPS Unity 5.3.4f1 (64 - bit) In profiler found under Camera.Render->Culling->SceneCulling.
Also off subject slightly, Canvas.Buildbatch for the UI develops these game stopping spikes.
I've only just noticed these today as i've been waiting for Unity 5.3.5 to be released;I've been told this version will fix the Physics spikes that lag the hell out of my game.
There sure are a lot of bugs
Rycons
Feb 11, 2016 18:12
This issue still persists on Unity version 5.3.2p3.
Culling is frequently spiking above 90ms which is constantly stalling our game.