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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
atmosgames
Dec 10, 2016 18:35
Good gracious. This needs to be fixed. Anyone had any luck?
Here is a video of it happening. I've raised over 100K on Kickstarter, and my 5 year project will likely ship with this game breaking bug.
https://www.youtube.com/watch?v=pvUmqOzztoY
Peris
Dec 09, 2016 09:50
Definitely still happening in 5.5, just encountered it on my project.
Peris
Dec 02, 2016 01:57
Has anyone been able to confirm yet if this is fixed with the new PhysX update in 5.5?
Peris
Sep 22, 2016 06:33
Agree that this needs to be higher severity, I know of several games suffering from this issue. Making your own character controller isn't really a nice workaround, considering how many projects use it. It's a crippling, game breaking feature for so many games.
DavidByers
Sep 19, 2016 16:13
I'll second ALAN-LAWRANCE's comment. There is no workaround as far as I can tell. If so I'd love to hear it. This is a pretty major bug imo, not being able to trust colliders is a huge deal.
alan-lawrance
Sep 12, 2016 19:31
This issue is categorized as Severity 3 meaning "workaround is possible". What is the work-around, to use rigid bodies instead of a CC? Should be higher Severity and Priority IMO.
DavidByers
Sep 02, 2016 04:15
Here's a video of the issue happening in my game if at all useful.
https://www.youtube.com/watch?v=-DzomnEMW3Y
Unfortunately this is a gamebreaking bug for me.
Doomgriever
Aug 31, 2016 20:05
Can confirm, have had this problem with CC on all my projects for over a year now. Even shipped a game with this bug (sadly) http://store.steampowered.com/app/431840/
And I refuse to ship another game with this bug again. As my character for my games does not need physics I see no reason to write my own rigid body controller, the Character Controller works perfectly for my games, except for this very annoying bug!
Peris
Aug 12, 2016 05:12
I recorded a video of it happening in my game.
In this case, one of the wall tiles lost it's collision with the player. The collision still works with everything else, including other character controllers. As you can see in the video, I can run straight through one of the wall tiles:
http://www.brameulaers.net/debugvid/colliderbug_broken.mp4
The other wall tiles still have collision. Since they are all instances of the same prefab, there's no reason one of them shouldn't be working. It's definitely an engine side bug.
After refreshing the scene, the collider works fine, as you can see in this video:
http://www.brameulaers.net/debugvid/colliderbug_normal.mp4
It's completely random and impossible to reproduce for me. It only started happening in unity 5, I've been working on this project since unity 3 and never had any problem before!
DavidByers
Jul 11, 2016 16:14
I just wanted to chime in that I'm running into the same issue. Unity will randomly ignore collisions with a character controller and mesh collider, it feels like it happens every 1000 colliders or so. Collisions will not work at all with a collider that is gliched. I'm running 5.3.5f1 on Windows 10.