Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2019.1.0a14
Issue ID
1115810
Regression
Yes
Nested Prefabs - MissingReferenceException when discarding changes to a prefab with a CapsuleCollider attached
If you are editing a prefab with a capsule collider attached and then discard the changes you made by leaving isolation mode, the following exception will occur:
MissingReferenceException: The object of type 'CapsuleCollider' has been destroyed but you are still trying to access it.
Your script should either check if it is null or you should not destroy the object.
As a knockon, the next time you select the prefab or any instance of it in the hierarchy, several more exceptions will occur.
1. Install Unity
2. Open the attached project
3. Find GameObjectWithCapsuleCollider.prefab in the assets folder
4. Open the prefab in isolation mode
5. Make sure that autosave is turned OFF
6. Move the transform
7. Exit isolation mode and discard all changes
Expected Result:
The changes are discarded and no exceptions occur.
Actual Result:
A MissingReferenceException occcurs.
Tested on Windows.
Occurs on 2019.2.0a1, 2019.1.0a14
Does not occur on 2018.3.0f2, 2019.1.0a13
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 2019.2):
Exception should no longer appear.