Search Unity

Why 2dCollider editor will be auto eset after any operation ?

Discussion in '2D' started by Bagazi, Jul 28, 2019.

  1. Bagazi

    Bagazi

    Joined:
    Apr 18, 2018
    Posts:
    144
    upload_2019-7-28_20-41-54.png
    I use the box collider to edit the colliding area ,when I change any position of those four reference points,the "status" of the editor will set back .. upload_2019-7-28_20-44-50.png
    So I have to click the "Edit Collider" button again to continue the colliding-area edition.
     
  2. Bagazi

    Bagazi

    Joined:
    Apr 18, 2018
    Posts:
    144
    I was doing it on Prefab... But it is OK within hireachy gameObject...
     
  3. MelvMay

    MelvMay

    Unity Technologies

    Joined:
    May 24, 2013
    Posts:
    1,964
    Yes, behaviour was introduced when the new prefab system came in. Internally the prefab edit stuff was causing an inspector reload when you edited a property which triggered the exit of the collider editing. It has been fixed in later Unity versions (I'd need to check which) but I'm not sure of the backport fix status.

    If you take a copy of your project and try in 2019.3 as I believe it works there.

    I can chase to see what's happening with backports there.
     
    Last edited: Jul 28, 2019
  4. Bagazi

    Bagazi

    Joined:
    Apr 18, 2018
    Posts:
    144
    Oh,I see.Thanks:)