Search Issue Tracker
Duplicate
Votes
1
Found in
2019.1.0a1
2019.1.0b8
2019.2.0a1
Issue ID
1141428
Regression
Yes
Missing mesh reference when importing a unitypackage in 2019.1
Steps to reproduce:
1. Open the project from owncloud provided in edits
2. Open the "cockpit" Scene
3. In Hierarchy window, select any of the "Missing.." game objects
4. Observe the Inspector window of selected object
Result: Missing mesh references (object picker is either empty or stating "missing")
Reproducible with: 2019.1.0f2, 2019.2.0a11
Note: Open "Repro2019.1.0f2" Project to see the difference (all the Package errors have been solved). "pedestal:1_low 1" is in the Scene but mesh is missing.
Comments (2)
-
ClearRoseOfWar
Jul 30, 2020 16:08
If the same thing has happened, then this is still happening in unity 2019.4.5f1
Gunna try and upgrade to a new version I guess... (Again :p ) -
creat327
Sep 27, 2019 17:46
still failing
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
This is a duplicate of issue #1146750