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
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
- Incorrect ScrollToItem behavior when called on a deattached ListView
- Zooming in/out in Scene View window on the display the zoom takes place in does not work
- Changing Game View resolution when there are 2 Game View Windows on 2 different displays makes the view stretched
- Maximising Game view window on one display makes black bars appear on another display
- Creating a 3D Object when using 2 monitors and 2 Game View Windows on different monitors the created 3D Object only appears on one of them
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.