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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Package signature validation unexpectedly return an invalid signature status if the validation check is done after the code signing certificate validaty range has passed
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0b1
Resolution Note (fix version 2021.2):
Fixed in 2021.2.6f1