Search Issue Tracker

Fixed in 2020.1

Fixed in 2018.4, 2019.2, 2019.3

Votes

9

Found in

2018.3.0b1

2019.1.0a1

2019.1.4f1

2019.2.0a1

2019.3.0a1

Issue ID

1162736

Regression

No

Re-serialization make changes to Nested Prefabs

Asset Import Pipeline

-

Steps to reproduce:
1. Download 1162736_repro.zip project
2. Open project with deleted Library
3. In toolbar select Repro -> Resterilize. Will resterilize all prefabs, forcing them to be resaved.
4. Check changes in TortoiseHG
5. Notice that some of the prefabs were change
5. Close and reopen the project
6. Resterilize once more
7. Check changes in TortoiseHG
8. Notice that second reserialization revert change prefabs
9. Re-serializing third time won't make any changes until the Library folder is removed.

Expected results: Serialization should not modify prefabs
Actual results: Serialisation modifies prefabs

Reproduced with: 2019.3.0a7, 2019.2.0b7, 2019.1.8f1, 2018.4.3f1

Note:
With the original project re-serialization, constantly modifies some of the prefabs, there is no need to delete the Library folder or reopen the project.

Comments (5)

  1. 67a125e53965d6dd83277c0ed48d2a37?d=mm

    OndrejP

    Oct 21, 2019 14:50

    Same here, exactly same behavior, ordering of modifications changes. (Unity 2019.2.9f1)

    It's big issue for us, because we use nested prefabs heavily and this change triggers reimport of all dependent prefabs, which can take minutes. Worse this happens when prefab is clicked in project, because it opens it in inspector and then it saves it right away.

    Naive approach to fixing this seems like sorting modifications by property path.

  2. 0f7b8a2bd0db84843bd88537f552867e?d=mm

    TunnelVisionGames

    Oct 15, 2019 11:57

    Happens in 2019.2.1f1 and is very annoying, because saving can now take multiple minutes, so we have to be very aware of when we press Ctrl+S.

  3. C364bb5dceae6db8cb22d210a1f6f78b?d=mm

    mcarriere

    Oct 08, 2019 15:07

    We're seeing this in 2019.2.0f1 as well.

  4. 94afef2c90b7926ea3e18b41b93114f6?d=mm

    ISanchezV

    Sep 13, 2019 13:00

    I have experienced this issue on every LTS release so far (currently 2018.4.8f1)

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.