Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.1.X, 2019.2.X
Votes
0
Found in
2018.3.12f1
2019.1.0a10
2019.2.0a1
Issue ID
1147902
Regression
Yes
Prefabs lose references to unnamed meshes after upgrading the project to 2019.1.0a10 and above
How to reproduce:
1. Open the attached project ("bugreport.zip")
2. Open the repro scene ("SampleScene")
3. Notice the building in the scene view
4. Select the "testbug" object in the Inspector (it is a child of the Main Camera)
5. Note that its children objects reference meshes with no name
6. Close the project and upgrade it to 2019.1.0a10 or above
7. Inspect the scene view and the "testbug" object
Expected results: Building can be seen in the scene, "testbug" still has references to the meshes
Actual results: "testbug" object and its prefab loses references to the unnamed meshes
Reproducible with: 2019.1.0a10, 2019.1.0f2, 2019.2.0a13
Not reproducible with 2017.4.26f1, 2018.3.14f1, 2019.1.0a9
Notes:
1. Upgrading the project from 2017.4 to 2018.3 does not reproduce the issue
Comments (1)
-
dcfstudios
Oct 25, 2019 16:08
Issue still occured when trying to upgrade a project from Unity 2018.3.5f1 (64-bit) to Unity 2019.2.10f1 (64-bit).
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2019.3):
Fixed in 2019.1.9f1, 2019.2.0b7, 2019.3.0a7