Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2018.1
Issue ID
1253433
Regression
No
[SerializeReference] Non-Serialized fields loose their default initializers value when after entering PlayMode
1) Add Script InitBug.cs to a project
2) In the project view, create a new "Initialized Fields Bug" asset.
3) Select the asset and click the cog icon to show the assets context menu, select "Check Values".
4) The console should say that both fields are NOT null.
5) Enter play mode.
6) Select the asset and click the cog icon to show the assets context menu, select "Check Values".
7) The SerializeReference field is now null. This should never happen.
If a value is changed in a script during play mode, all the non-serialized fields will lose their values.
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note (fix version 2020.1):
Fixed in 2020.1.17f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.14f1