Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.67f1
6000.3.8f1
6000.4.0b8
6000.5.0a6
Issue ID
UUM-134668
Regression
No
A frame spike occurs when Physics Simulation Mode is switched from Script to FixedUpdate
How to reproduce:
1. Open the attached project "IN-133997"
2. Open the “Assets/PxTest/PxTest” Scene
3. Open the Profiler window
4. Enter Play Mode
5. Observe the Profiler
Actual result: A large frame spike of over 9000ms occurs shortly after entering Play Mode
Expected result: No large frame spikes appear after entering Play Mode
Reproducible with: 6000.0.67f1, 6000.3.1f1 (f56f53296c2c), 6000.3.8f1, 6000.4.0b8, 6000.5.0a6
Not reproducible with: 6000.3.0f1 (d1870ce95baf)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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
- GameObjects made using "GameObject.CreatePrimitive" appear pink in the Player when the default material is used
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
Resolution Note:
Hello!
The issue described in this case is occurring as a result of a previous bugfix. During the 6.X cycle Unity's SaP (Sweep and Prune) option in the Project Settings -> Physics -> Settings tab would internally be treated as ABP (Automatic box pruning). ABP performance is far higher for insertions/removals/changes within a physics scene's broad phase. The bug fix I'm referring to simply ensured SaP actual evaluated to eSAP in the PhysX integration code.
Thank you for reaching out and submitting this case!
Cheers,
AlexRvn
Resolution Note (6000.5.X):
Hello!
The issue described in this case is occurring as a result of a previous bugfix. During the 6.X cycle Unity's SaP (Sweep and Prune) option in the Project Settings -> Physics -> Settings tab would internally be treated as ABP (Automatic box pruning). ABP performance is far higher for insertions/removals/changes within a physics scene's broad phase. The bug fix I'm referring to simply ensured SaP actual evaluated to eSAP in the PhysX integration code.
Thank you for reaching out and submitting this case!
Cheers,
AlexRvn