Search Issue Tracker
Fixed in 5.0.1
Votes
1
Found in
5.0.0f3
Issue ID
675563
Regression
No
[PhysX]Huge physics spikes in Profiler on some Android devices
Profiler shows Physics spikes on some Android devices every several seconds
Comments (32)
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
- Terrain heightmap loses precision on Android and iOS when the heightmap texture is blitted to a RenderTexture using the default Blit shader
- Tiny unscaledDeltaTimes (~1e-5 s) happen randomly in the iOS/Android Player
- UI Builder's Canvas stays blue when a Visual Element within its bounds was selected before enabling and disabling the Preview and Canvas Background is enabled
- “The main object name " should match the asset filename" warning is shown in the Inspector when creating a new Color Library
- "Assertion failed on expression: 'fidA != fidB'" error is thrown when using specific Prefabs on HDRP and URP
Miscellaneous
Jan 20, 2021 06:42
Happens in Unity 2019 (year 2021)
jeffreyf
Sep 16, 2016 13:12
Happens in Editor for 5.3.p2. Should we submit a new bug to try and get this re-opened?
Nehrk
Jul 28, 2016 15:49
Unity 5.3.5f1
11 colliders, 1 Rigidbody. 78 ms. Empty Scene. Fixed?))
UmairEm
Jul 27, 2016 14:58
Still facing this issue in v. 5.3.3 f1
sunxdc15
Jul 21, 2016 08:05
not fixed!! still happens in 5.3.4p4 on Android devices
BAnyBudde
Jun 13, 2016 14:08
Is someone from Unity going to reply to this issue, I have this issue in 5.3.4f1 and it's KILLING my framerate!
lfzuo
Apr 26, 2016 06:02
I fix my problem.There is a thread running without Thread.Sleep.You can check your code，
May be helpful
Rickywild
Mar 21, 2016 16:00
I've put a post up about this here http://answers.unity3d.com/questions/1157658/huge-physics-spikes-in-empty-scene-and-populated-s.html
I can't continue with development until this is fixed. It happens with an empty scene, i really hope this is addressed soon :(
TimNick151297
Mar 12, 2016 16:24
Seems that some postprocessing effects cause this issue - no clue, why. Disabling volumetric lighting solved this issue for me.
TimNick151297
Mar 12, 2016 16:16
I'm still experiencing this issue in 5.3.0f4, too.