Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a2
Issue ID
1051601
Regression
No
Assertion failure when discarding changes after nesting a Prefab in Prefab Mode
If you are editing a Prefab in Prefab Mode, add another Prefab to the hierarchy and then back out and discard changes, an assertion failure will take place.
Assertion failed on expression: 'prefabInstanceFileID != 0'
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
Assertion failed on expression: 'fidA != 0'
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
1. Install Unity
2. Open the attached project
3. Find PrefabA in Assets and open in Prefab Mode
4. Make sure Autosave is OFF
5. Add PrefabB to PrefabA
6. Exit Prefab Mode and discard changes
Result:
Assertion Failures occur.
Expected Result:
No errors should appear in the Console.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment