Search Issue Tracker
By Design
Votes
12
Found in
2019.4
2020.3
2021.2.12f1
2021.3
2022.1
2022.2
Issue ID
1406765
Regression
No
CPU spikes by 3-10% at "Physics.Processing" when using Physics.RebuildBroadphaseRegions
Reproduction steps:
1. Open the attached "PhysicsPerformanceRepro.zip" project
2. Open the "OutdoorsScene" Scene
3. Enter the Play mode
4. Open and observe the Profiler window
Expected result: There are no CPU spikes at "Physics.Processing"
Actual result: CPU spikes by 3-10% at "Physics.Processing"
Reproducible with: 2019.4.37f1, 2020.3.33f1, 2021.3.1f1, 2022.1.0b14, 2022.2.0a10
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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Resolution Note:
The spikes appear under Physics.Processing only due to the fact that, by design, if Physics is not done simulating yet and we're just waiting for it to be done, we allow for other jobs to jump in and do their work. It doesn't have to be physics related at all. This helps process things quicker, but of course generally we still show this section as "Physics.Processing" in the profiler, since we are waiting for it to be done.