Search Unity

  1. Unity 2019.1 is now released.
    Dismiss Notice
  2. We've opened up a space to discuss, share feedback, and showcase everything related to the Unity Shader Graph! Come show us what you've made.
    Dismiss Notice

(Case 1122109) SceneAsset references go missing

Discussion in '2019.1 Beta' started by Peter77, Jan 29, 2019.

  1. Peter77

    Peter77

    Joined:
    Jun 12, 2013
    Posts:
    3,344
    Opening a 2018.3 project in 2019.1.0b1, causes all UnityEditor.SceneAsset references to go missing. I submitted the example project with 2018.3 on purpose, to allow you to see that it works in Unity prior 2019.1.0b1.

    screenshot.png

    Reproduce
    1. Open attached user project in Unity 2018.3
    2. Select "Assets/TestAsset.asset"
    3. Notice in the Inspector, that "Element 0" points to "Scene"
    4. Open attached user project in Unity 2019.1.0b1
    5. Select "Assets/TestAsset.asset"
    Actual
    "Element 0" shows "Missing (SceneAsset)".

    Expected
    References should stay intact when upgrading the project.

    Note
    The scene .meta file guid didn't change and is still in the project though.
     
    jashan and LeonhardP like this.
  2. Peter77

    Peter77

    Joined:
    Jun 12, 2013
    Posts:
    3,344
  3. Peter77

    Peter77

    Joined:
    Jun 12, 2013
    Posts:
    3,344
    My report is now marked as duplicate in the public issue tracker, without a note what the original report is. Do you mind posting the issue tracker link to the other report, so I can continue track on the issue status.

    PS: An option to Watch a public issue tracker item, and to get email notifications if the status changed, would be very very useful.
     
  4. jashan

    jashan

    Joined:
    Mar 9, 2007
    Posts:
    3,053
    I ran into the same issue, and the problem seems to be that they have changed the fileID for scene objects (the code below is from a ScriptableObject I use for defining what goes into our builds, "scenes" is of type List<SceneAsset>):

    Unity 2018.3:
    Code (CSharp):
    1. scenes:
    2.   - {fileID: 102900000, guid: 98c38a1701503df4e87e97bbc0b9d1c1, type: 3}
    Unity 2019.1:
    Code (CSharp):
    1. scenes:
    2.   - {fileID: 3671201678493226958, guid: 98c38a1701503df4e87e97bbc0b9d1c1, type: 3}
     
    Peter77 likes this.
  5. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    1,337
    The original case contains sensitive information and can unfortunately not be published to the issue tracker.
    The bug is fixed in 2019.2.0a5 and the fix should also get backported to 2019.1 in the near future.
     
    Peter77 likes this.
  6. jashan

    jashan

    Joined:
    Mar 9, 2007
    Posts:
    3,053
    Great! Would you then recommend to wait with moving a 2018.3-project to 2019.1/2019.2, or will you make sure to have proper "migrations" for all cases: Project upgrading from 2018.3 as well as project being upgraded with that bug, and project being upgraded with that bug, but fixed manually by changing the IDs in the asset files?
     
  7. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    1,337
    Lost references in upgraded projects won't be recovered by the fix. If you want to avoid fixing them manually, you should wait until the upgrade process is fixed.

    The fix will be in b4.
     
    jashan and Peter77 like this.
  8. Peter77

    Peter77

    Joined:
    Jun 12, 2013
    Posts:
    3,344
    Nice! Thanks for keeping us in the loop.
     
    jashan likes this.
  9. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    1,337
    Happy to help :).
     
    jashan and Peter77 like this.
  10. Peter77

    Peter77

    Joined:
    Jun 12, 2013
    Posts:
    3,344
    I can confirm that it works in Unity 2019.1.0b4 again.
     
    LeonhardP and jashan like this.