Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.3.0a3
2020.1
2020.1.0a12
Issue ID
1198740
Regression
Yes
Various Inconsistencies when creating a prefab out of a corrupted GameObject
How to reproduce:
1. Open QA-Supplied project (link in Edit)
2. Open Scene in Assets -> 00_Scenes->outdated->PrefabBug
3. In the Hierarchy window, select level (disconnected and wrong hierarchy)->PolyP and drag it into the Project window to create a Prefab
4. Ctrl + z to undo
Expected: Hierarchy text is blue (since it is a prefab now), Inspector doesn't show a "disconnected" warning, opening it from Hierarchy opens the prefab.
Actual: Hierarchy text is grey, Inspector shows a yellow "disconnected" text, opening it from Hierarchy opens a different prefab
Reproduced in: 2019.3.0a3, 2019.3.0b11, 2020.1.0a13
Not reproduced in: 2017.4 (old Prefab system) 2018.4.13f1, 2019.2.13f1, 2019.3.0a1, 2019.3.0a2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Add comment