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
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
- Root motion is not reapplied when transitioning from an animation without root motion to an animation with root motion
Resolution Note (fix version 2020.1):
Fixed in 2020.1.17f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.14f1