Search Issue Tracker
Fixed
Votes
0
Found in
5.5.0p3
Issue ID
868935
Regression
Yes
Newly declared arrays become null when attached to gameObject script is edited
To reproduce:
1.Download and open attached project
2.Attach Behav script to Main Camera object
3.Open Behav script and uncomment declaration of b array(5th line)
4.Save changes and check values of b array in the inspector
Expected result: Size of b array being 5 and all elements of the array are visible in the inspector. Elements being fully accessible.
Actual result: Size of b array is 0. There aren't any visible array elements. These elements are not accessible trough the editor.
Reproduced with: 5.5.0f3, 5.5.0p3, 5.6.0b3
Not reproduced with: 5.4.3p3, 5.3.7p2, 5.2.5f1
Workaround: attach script to the object when both arrays are uncommented.
Note: b array values are null, even though b array is declared in script with 5 elements.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Foldout arrow indent is misaligned in the Inspector when used in Custom Type
- [Android] The Player screen turns black when playing a video under certain conditions
- Search window icons at the bottom are cut off when Search window is resized vertically
- "Try something else?" text label is cut off when searching for a long text in the Search window
- Rendering Debugger window sections do not have a minimum width set when resizing with the slider in the middle of the window
Add comment