Search Issue Tracker

Fixed in Unity 5.3.7

Votes

84

Found in

5.3.3p1

Issue ID

775290

Regression

Yes

[ScriptableObject] Name of child scriptable objects changes spontaneously

Scripting

-

-

Priority: 2Necessary for shipping a final release

-

Severity: 2Core functionality majorly impacted

Steps to reproduce:

1. Open attached project
2. Delete "Repro Asset" scriptable object found in Assets folder
3. In top menu, click "Repro > Setup Repro Asset"
4. Once asset is created, expand it and notice that it has 3 children. Two named "Child Node" and one is named "Repro Asset"
5. On keyboard, click ctrl+s to save scene and once Save Scene window appears press cancel
6. Expand "Repro Asset" again ant notice that this time only one ScriptableObject is named "Child Node" and other two are named "Repro Asset"

Note: All children created in Step 4 should be named Child Node. Looks like one of them gets renamed instantly.

Regression introduced in: 5.3.3p1 (looks like 770926 introduced it)
Reproduced with: 5.4.0b8

Workaround: Name your main/containing asset's file something
alphabetically before all child assets

Comments (8)

  1. 3826b4d42892778f649fa8c0ce0e42b4?d=mm

    JuliusJ

    Aug 29, 2016 09:06

    Should be fixed in 5.4.0p4 when it comes out

  2. 4ff331252f29470ced7466bb5577f74b?d=mm

    numberkruncher

    Aug 28, 2016 03:11

    I am still seeing this problem in 5.4.0p3.

  3. 4ff331252f29470ced7466bb5577f74b?d=mm

    numberkruncher

    Aug 20, 2016 22:52

    Yup still seeing the problem in Unity 5.4.0p2.

  4. 4ff331252f29470ced7466bb5577f74b?d=mm

    numberkruncher

    Jul 30, 2016 22:48

    This page claims "Status: Fixed in Unity 5.3.7" yet the problem persists in Unity 5.4.0f3...

  5. Bd29741151c2e18acf6ecead5c91e4c7?d=mm

    artanist

    Jul 07, 2016 18:53

    It say that it's fix in 5.3.7, does that mean we have to wait until that version for the fix ? The latest for now is 5.3.5f1

  6. D0dcb575bfa60a6c679fa4fdc03635ff?d=mm

    mpulkkinen

    May 27, 2016 05:51

    Seriously, still no progress? Still occurs in 5.3.5f1, and yes, still makes project / data management nightmare. We've spend extra time to make editor scripts to counter this issue ( in data management wise )

  7. 3306e107e5abd0e992b219eab1199a56?d=mm

    zadr

    Apr 11, 2016 06:49

    Still occurs in 5.3.4p2 and 5.4.0b13.

  8. 25ff6c80bc334e4fb622e31d80eb558f?d=mm

    CrabSchell

    Mar 24, 2016 17:24

    We are seeing this in 5.3.4f1 as well.

All about bugs

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