Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
1
Found in
2021.2
Issue ID
1383439
Regression
Yes
[SERIALISATION] Going into play mode does not deserialize the object properly
When going into play mode, a Prefab with the attached MonoBehaviour with an override on the string value for the objectValue will not deserialize the object properly.
1. Open provided project
2. Open SampleScene
3. Select TestPrefab in hierachy
4. Change string fields, Enter playmode
Expected Result: no error
Actual Result: Error printed in console: A field decorated with [SerializeReference] references an unknown managed type!
Notes: If the error does not occur, try changing the string once more and entering play mode again. Mostly required in 2022.1.
Changing the options of Domain reload and reload scene on enter Playmode does not affect the results (Preferences/Editor)
Comments (1)
-
Catsoft-Works
Dec 20, 2021 16:35
This has only been partially fixed. Now when instantiating a prefab variant with an overriden field that is marked as [SerializeReference] will not use the overriden value, but the last selected one from a component of the same type.
This is most likely a caching issue where the last value used is used.
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 2022.1):
Fixed in 2022.1.0b1
Resolution Note (fix version 2021.2):
Fixed in 2021.2.6f1