Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a2
Issue ID
1051652
Regression
No
Re-creating a prefab of variant instance with missing base prefab throws cyclic prefab exception
User accidentally deleted a base prefab, trying to re-create prefab using its variant, prompts "Cyclic Prefab nesting not supported".
Steps to Reproduce:
1. Create a game object in the hierarchy.
2. Drag the game object to Project window to create a Prefab.
3. Create its Prefab Variant. ( Right Click on Prefab >> Create >> Prefab Variant)
4. Delete Base Prefab.
5. Drag Prefab Variant to Hierarchy, repeat step 2 to re-create the lost prefab.
6. Select "Original Prefab" on Create Prefab window(Pops up on dragging Prefab Variant Instance to Project Window)
See attached video to reproduce the issue. (RecreateLostPrefab.mov)
Observe: "Cyclic Prefab nesting not supported" window pops up.
Expected Result: New Prefab should be created.
Reproducible On: Version: 2018.3.0a2 (e9113db2e9bf)
Branch: prefabs/improved
Note:
- Appears on both OSX and Windows
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment