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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment