Search Issue Tracker
Fixed
Fixed in 6000.0.49f1, 6000.1.3f1, 6000.2.0b1
Votes
14
Found in
6000.0.26f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-87199
Regression
No
Physics SyncColliders 3x-7x performance regression from 2022LTS to U6
Steps to reproduce:
1. Open attached project in Unity 2022 LTS
2. Open scene Colliders_MoverInHierarchyComplex.unity
3. Enter playmode and capture CPU performance using profiler
4. Make a copy of the project and open it in Unity 6, then repeat the steps above
5. Compare results
6. Repeat exercise but this time building both versions for a less powerful platform
Although this is a regression on all platforms, the numbers add up very quickly on lower powered device such handheld consoles and low/mid spec mobile devices.
Actual results:
Syncing Physics colliders is about 3-7 times slower in Unity 6 compared to an identical scene in Unity 2022 LTS.
The variance in regression comes from scene configuration and complexity, but certain complex hierarchy configurations that were already a bit slow in 2022 LTS are now significantly slower in Unity 6.
Expected results:
Cost of syncing transforms in Unity 6 is on par with or lower than cost of syncing transforms in Unity 2022 LTS.
Reproducible with versions:
6000.0.26f1
Not reproducible with versions:
2022.3.20f1
Tested on (OS):
Windows
macOS
Android
Notes:
For a point of reference, testing the included repro on a low-powered Android device it spends about 3 ms / frame syncing transforms in Unity 2022 LTS and 15 ms / frame in Unity 6 - so 5x as long in U6.
Comments (2)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
christopherphelps1024
Jul 26, 2025 12:56
Yes! Lost 10fps in my project going from 2022 to 6
stonstad
Apr 11, 2025 18:54
Can confirm the same behavior in our project. We're seeing a drop from 60 FPS to 20 FPS due to Physics.SyncTransforms behavior. We can compare the projects size by size and see that it is due to physics perf.