Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.3.X, 2022.1.X
Votes
13
Found in
2020.2.0a14
2021.1
2021.2
2022.1
2022.2
2022.2.0a8
Issue ID
1409773
Regression
Yes
First array element expansion is broken for arrays that use Custom Property Drawers
How to reproduce:
1. Open the attached project
2. Open the "SampleScene" and select "Input array" in the Hierarchy
3. Try to add bindings to the very first element of the array via the plus sign button
4. Observe that the array doesn't expand correctly
Alternatively:
3. Select the "Custom" object and change the first element's field to "A" in the dropdown menu
4. Observe that the expansion is broken for the first array element only (might be broken for other too if checked on an older, non-fixed version)
Expected result: Arrays with custom property drawers always expand correctly
Actual result: The first first element of an array doesn't expand correctly if it uses custom property drawers
Reproduced in: 2022.2.0a8, 2022.1.0b12, 2021.2.16f1, 2021.1.28f1, 2020.3.31f1
Not reproducible with: 2020.2.0a13
-
AndrewSpalato
Jun 12, 2022 04:30
Definitely an issue that needs to be fixed in 2021.3 LTS.
-
TheFrozenFires
Jun 11, 2022 12:33
This should be a top priority fix, quite disappointed it isn't fixed in 2021.3.4 as this breaks a lot of peoples workflows
-
Syganek
Jun 10, 2022 04:57
Issue is present in 2021.3.4f1
-
thundershower
Jun 08, 2022 03:07
Still present in 2021.3.4f1
-
CGDever
Jun 06, 2022 21:21
The bug still exist in unity 2021.3.4f1
-
JoarProf
Jun 06, 2022 13:04
Yes please, fix it in LTS as soon as possible.
-
korbul
Jun 06, 2022 12:00
Please fix in LTS
-
CU_Marko
Jun 03, 2022 13:34
This really needs to be fixed for LTS versions ASAP, because it makes editing list of nested serialized objects almost impossible (have to create temporary dummy element just to have it as a first element while editing the real first element).
-
seriphis
Jun 03, 2022 13:30
Still present in 2021.3.4f1
-
DevDunk
Jun 03, 2022 12:43
Please fix in LTS
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
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a13
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0f1
Resolution Note (fix version 2021.3):
Fixed in: 2021.3.5f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.37f1