Search Issue Tracker
Fixed in 2020.1.X
Votes
3
Found in
2020.1.0a2
2020.1.0a17
Issue ID
1211768
Regression
No
Serialized ScriptableObject template class field appear as a non-ScriptableObject field in the Inspector
Steps to reproduce:
1. Open the attached project (case_1211768.zip)
2. Add "GenericSerialization" script to any game object in the Hierarchy
Expected result: "Scriptable Object Wrapper" is rendered the same as "Concrete Wrapper" (ScriptableObject field)
Actual result: "Scriptable Object Wrapper" is rendered the same as "Wrapper" (Able to expand & assign Value field)
Reproduced in: 2020.1.0.a2, 2020.1.0a20
Cannot test with: 2017.4.36f1, 2018.4.16f1, 2019.2.19f1, 2019.3.0f5, 2020.1.0a1 (Template class serialization unsupported)
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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a22
Fields of types that are MonoBehaviour/ScriptableObject subclasses will now correctly serialise by reference, instead of serialising the referenced MB/SO as a nested object.