Search Issue Tracker

Not Reproducible



Found in


Issue ID




Colliders are not updating to match attached gameObject location



Colliders are not updating to match attached gameObject location. After their object is stored and returned from a pool (reparenting, deactivating and re-activating the gameObject in the process) they become stuck at the location they were at when first activated. The collider gizmo does not reflect this.

To reproduce:

1. Download attached project "WoP" and open in Unity
2. Open "bug_example" scene and enter Play mode
Note: Enable gizmos in the game view for better visual cues to raycasting
3. Using a gamepad navigate the player character to the weapon on the ground and pick it up using the 'B' button (XBOX controller)
4. Use the 'X' button (XBOX controller) to fire the weapon at the enemy, killing them and causing them to return to the pool.

- The enemies spawn one at a time from a pool of 10 total.
- After the 10th enemy has been dispatched they will start recycling. At this point observe that both the aim assist feature and the collision of projectiles confirm the enemy's collider remains at their initial spawn point as they move about.
- By selecting the enemy in the hierarchy and disabling/enabling their sphere collider, observe that it moves to the latest position of the game object but does not update.
- Workaround: By adjusting any property of the sphere collider, observe that the collider now begins to follow the game object as would normally be expected
- This issue appears on Unity Editor and Standalone Build

Reproduced on Unity 2017.2.0f3 and 2017.2.0p1
Not reproduced on Unity 2018.1.0a2
Could not check for regression on Unity 2017.1 and 2017.3 because XBOX Controller does not work for some reason

Comments (43)

  1. Twice-Circled

    Aug 16, 2022 14:07

    Anyone still seeing this issue, you might need to: project settings -> physics -> auto sync transforms -> tick.

    Otherwise your collider positions might not be updating to reflect the position of their transform. For me this was the issue because I was not using the physics engine for anything but raycasts. Therefore the collider positions were not being updated as part of the general physics update. Hope this helps. :)

  2. joniwalkerkiy

    Apr 15, 2021 08:05

  3. Develax

    Jan 01, 2021 15:23

    The same issue in v. 2020.2.0f1

  4. shubhamswaraj2021

    Aug 18, 2020 16:20

    good one <a href="">lyricsauto</a>

  5. sharkwithlasers

    Apr 14, 2020 06:57

    Getting a similar issue on 2019.3.6f1.

    Colliders seem to be lagging behind the actual transform position when I move the gameobject.

  6. 4tzer

    Mar 05, 2020 08:41

    2019.2.9f1: This issue was driving me nuts. Updating the centre of the Collider resolved it. Odd to read that it's not reproducable.

  7. ImpossibleRobert

    Jan 17, 2020 12:48

    I suspect I am stumbling into the same issue right now with 2019.3.f5. It seems somehow like the colliders are not updated at the same time as the game object is resized but slightly later. I am not at the bottom of the issue though yet.

  8. Gandarufu

    Dec 08, 2019 13:35

    Still having the same issue in 2019.3 and yet his issue is closed and marked as resolved? For some reason colliders don't update when you move the gameobject, but stay in their original spot.

  9. danUnity

    Dec 01, 2019 01:43

    I still have the issue where if I scale a game object with a collider on it. The collider stays at the same size. I'm using unity 2019.2.0f1. Not sure why we can't vote for it even if it's not reproducible. If we still have the issue, we should still be able to vote...

  10. stewe02

    Nov 15, 2019 16:55

    I'm having the same problem on unity 2019.2.6f1
    What should I do ?

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.