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
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
- Animation window scrollbar keeps resetting when the scrollbar width is changed after adding an event
- LocalizationSettings.InitializationOperation hangs when re-entering Play Mode with Domain Reload disabled
Add comment