Search Issue Tracker

Fixed in 2017.2



Found in


Issue ID




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

Comments (32)

  1. D40ed9727d7be0dbf1b368d8092082a3?d=mm


    Jul 13, 2020 17:20

    kedi ve köpek mamaları kedi kumu çeşitleri

  2. 1ea7cd21d79153fa4f1d055ba65bed0b?d=mm


    Jun 20, 2017 10:22

    FWIW: Rolls out with 5.5.4p2 scheduled for mid July. Unless high demand, there won't be a back-port to earlier versions. Anthony.

  3. 1ea7cd21d79153fa4f1d055ba65bed0b?d=mm


    Jun 18, 2017 11:27

    FWIW: The fix will be out with 5.6.2 Patch 1

  4. D6b1ae8f30ed04820fd57c5a009e2e93?d=mm


    Jun 17, 2017 06:26


    Awesome, that's fantastic to hear :)

  5. 1ea7cd21d79153fa4f1d055ba65bed0b?d=mm


    Jun 16, 2017 20:34

    @UNCADE - there will be a 5.6 back-port, as well as a likely 5.5 fix later on. I can't share the dates as of yet though. Encourage you to watch this thread, there will be an announcement as soon as I confirm the version/date. Thanks.

  6. D6b1ae8f30ed04820fd57c5a009e2e93?d=mm


    Jun 14, 2017 21:41


    Is there going to be no fix for 5.6?
    If so that is extremely disappointing, as this has been an issue for the entirety of Unity 5.

  7. 1ea7cd21d79153fa4f1d055ba65bed0b?d=mm


    Jun 14, 2017 09:28

    Back-port will be available as part of 2017.1 beta 10.

  8. 1ea7cd21d79153fa4f1d055ba65bed0b?d=mm


    Jun 07, 2017 10:09

    The fix will be shipped in 2017.2 alpha 3. Back-ports are pending.

  9. Ba1fb4d7a2ec50878bb72b06244bc8e1?d=mm


    May 20, 2017 12:57

    Which release will this fix be available in? Will it be ported back to 5.6?

  10. 8a752c2b1280270698f0bf6779e69b8d?d=mm


    May 08, 2017 12:58

    (Well at least I think I fixed it, I need Anthony to try the fix and confirm :) Fingers crossed)

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.