Search Issue Tracker

Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.

Postponed

Votes

48

Found in

2019.3.0a1

2019.3.0b5

2020.1.0a1

Issue ID

1189089

Regression

Yes

Parent and child nested Scriptable Object Assets switch places when parent Scriptable Object Asset is renamed

Project Browser

-

How to reproduce:
1. Download and open the attached project "1189089.zip"
2. Create a parent Scriptable Object Asset (Right-click -> Create -> MyObjects -> ParentObject)
3. Add a child Scriptable Object Asset (MyMenu -> AddChildObject)
4. Rename the NewParentObject Asset

Expected result: NewParentObject Asset is renamed
Actual result: NewParentObject Asset switches places with the NewChildObject Asset and the NewChildObject Asset is renamed

Reproducible with: 2019.3.0a1, 2019.3.0b6, 2020.1.0a8
Not reproducible with: 2017.4.32f1, 2018.4.11f1, 2019.2.8f1

  1. Response avatar

    Resolution Note:

    Requires a system rewrite of how we handle main object name. This is considered a feature. Once it is complete, most bugs in regards to asset names should be fixed. This issue is tracked internally.

Comments (9)

  1. 690dd33162f4b442491b979ebed4d53e?d=mm

    Lukas-Wendt

    May 25, 2020 10:29

    Something interesting to note - the file id of the main asset is always (as far as I have seen) 11400000. In the meta file there is a field called mainObjectFileID - which is always 0. Setting this to 11400000 after the swap has occurred reverts the issue. It is really interesting that the main object is easily identifiable in the asset file but still gets lost.

  2. 76b1f86726c7970d7466648c8ae02076?d=mm

    ayellowpaper

    May 18, 2020 10:49

    "This is considered a feature". Yeah that's definitely not a bug from a users perspective. Just as you would expect renaming a file works.

  3. Ad582f21c8594ee6751607a007c27cc8?d=mm

    unity_8PWF9mB-QFO06A

    Apr 08, 2020 13:48

    you can just reset name override from code

  4. A6dca519389585504071fc701b44fc92?d=mm

    Ran-Crump

    Apr 06, 2020 16:46

    Sounds like a great idea Evgeny

  5. 4710745378bd5a7c3aec154a408ef3c4?d=mm

    Zeejfps

    Apr 05, 2020 18:57

    alphabetically AFTER one of the SubAssets*

    Since I can't edit my comment for some reason.

  6. 4710745378bd5a7c3aec154a408ef3c4?d=mm

    Zeejfps

    Apr 05, 2020 18:56

    To me it seems like the issue has something to do with how the assets are ordered based on the asset names. This bug only happens if the MainAsset is renamed to something that comes alphabetically before one of the SubAssets. Moreover, this only seems to happen only on the second time the MainAsset is renamed. (In my testing)

  7. 5fc54bf2aad489eb27b97933f9a33178?d=mm

    EvgenyVasilyev

    Apr 05, 2020 18:53

    While we are at it, can we add a way to rename SubAssets?

  8. 4710745378bd5a7c3aec154a408ef3c4?d=mm

    Zeejfps

    Apr 05, 2020 18:51

    Has my vote!

  9. E5ee54c16c35811b3bd5dd7bfe870392?d=mm

    mateuszjaworski

    Feb 07, 2020 16:11

    Remember to switch asset pipeline from version 1 to version 2, because version 1 seems to work properly.

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.