Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
18
Found in
3.5.0f1
2018.4
2019.3
2020.1
2020.2
Issue ID
442732
Regression
No
SerializeField list objects are not initialized with class/struct default values when adding objects in the Inspector window
How to reproduce:
1. Open the attached 'project-442732.zip' project
2. In the Hierarchy window select 'Test'
3. In the Inspector window set the 'Test Data' array size to 1
Expected result: new TestData object is initialized with its default values (someFloat = 30f, someBool = true, someInt = 10)
Actual result: new TestData object is initialized with default variable type values (someFloat = 0f, someBool = false, someInt = 0)
Reproducible with: 2018.4.23f1, 2019.3.15f1, 2020.1.0b10, 2020.2.0a12
-
Kogamma
Feb 21, 2023 09:57
Yeah, this is really strange behaviour, would be very good to fix this
-
AtsusaKai
Apr 21, 2022 13:33
10+ years have passed... Any chance this issue gets resolved?
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
When the first element is added to an array via SerializedProperty it is allocated by zeroing the memory rather than calling the constructor. And when adding additional elements it copies the previous element. We will consider changing that behavior as part of future quality improvement work in the area of SerializedObject/SerializedProperty but also wary of any possible performance and backward compatibility impact for changing this behaviour.