Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice

Grid Pro - Bug Report : 2D Collider missing update call?

Discussion in 'World Building' started by Jiraiyah, Jun 20, 2018.

  1. Jiraiyah


    Mar 4, 2013
    I think I found a bug, take a look :

    I'm working on a 2D game, and all the sprites are children of an empty game object for better management, now, I add different types of colliders to these children, problem is, when i move the parent around using the snap to grid feature, the collider won't snap in place properly unless i open the parent in hierarchy, find the child and click on it, that is when the collider snaps in place, how to solve this problem? it's becoming tedious. unless i add the collider to the parent (something that i'm trying to avoid doing it) i don't see any other option right now.

    this pictures may help :
    1- while moving the parent -->
    2- release the mouse, the collider is wrong ! -->
    3- do any extra thing, like take a screen shot, or minimize and restore unity window, the collider is readjusted and right, same happens if you open the hierarchy and click on the child --->

    even if i use ctrl+d for a duplication when the collider is wrong, the previous one gets fixed but move the new one, same issue is there unless somehow you do one of those conditions above.

    Remember most of the time, unless you refresh the collider, if you start the game play, the collider's position will be wrong and this alone caused 2 hours from me when i was starting to work with a new character movement asset and thought the problem was related to settings !!!!

    I asked @yahodahan in pm, and he directed me toward the forum with this answer :
    Hi! Could you post this in the Forum so Karl (tech dev) can join and help? Thanks! Sounds like the collider is somehow not getting an update notification?