Search Issue Tracker
Fixed in 2017.2.X
Votes
93
Found in
5.3.3p3
Issue ID
809914
Regression
No
CharacterController might start to ignore collisions after a scene was reloaded more than 85 times
Steps to reproduce:
1. Open attached project
2. Open "Test" scene
3. Run the scene
4. Notice how "Instance {number}" fails to collide with "Character(Clone)" (gif attached)
Note: a lot of instances are created and if all succeed scene is loaded once again until a failure.
Does not reproduce on OSX.
Does not reproduce on Windows when number of attempts is less ~85.
Does reproduce on Windows when number of attempts is above ~85.
Reproduced with: 5.2.4f1, 5.3.3p3, 5.3.5p5, 5.4.0b24, 5.5.0f3
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
PierreTerdiman
May 08, 2017 12:56
I was made aware of this problem today, and fixed it. It is an issue in the Unity integration code, which will hopefully get fixed soon :)
banyango
Apr 26, 2017 19:47
I upgraded to 5.5 from 5.4.3p4 and I'm getting this randomly now.
change
Apr 13, 2017 09:37
Meet the same problem in Unity 5.5.0p4, 5.6.0f3
Please fixed it，thanks
ivjohn
Mar 29, 2017 18:12
Please could you post a link to the test project that reproduces this bug. Unfortunately it seems that the issue's attachments are not downloadable by the public.
brean
Jan 24, 2017 16:28
Noticed the same issue on some occasions in Unity 5.5.0f3 during the Global Game Jam 2017 while developing a Shooter-like game.
atmosgames
Jan 19, 2017 18:05
Finally heard back from Unity on this issue (replicated in Unity 5.5):
I was successful in reproducing your bug and got some details about it from the developers.
This is an issue that people tend to run into when using the Character Controller that ships with Unity. Unfortunately, this character controller was written by the folks over at PhysX as an example, and only became a feature addition because it was so widely used. It uses very patchy code that is hard to debug.
Fortunately, in light of all the complaints received about the CC, we have decided to expose a PhysX method that will go leaps and bounds in aiding users to write their own character controller. It’s the Physics.ComputePenetration method and it will be available from Unity 5.6 going forward. If you’d like to check it out, 5.6 is in Beta right now.
atmosgames
Jan 09, 2017 22:27
Happening in Unity 5.5:
https://www.youtube.com/watch?v=o80an6j6d04
atmosgames
Jan 05, 2017 22:37
Still no answer? Anyone reproducing in Unity 5.5?
Peris
Dec 22, 2016 06:39
Happens on mesh colliders too, just confirmed.
Peris
Dec 18, 2016 01:40
Has anyone been able to confirm if this only happens on box colliders? If true I might change my world geo to mesh for a temporary fix, but I want to know before I do all the work :)