Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2022.1.X
Planned for 2020.3.X, 2021.3.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
-
Ironbell
May 10, 2022 10:57
Issue is still present in 2022.1.15 and 2022.1.16, please adjust it accordingly.
-
pennomi
May 09, 2022 17:39
This issue is still present in 2022.1.16.
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
- [VFX/Timeline] Wrap Mode Loop is only playing VFX once
- Package Manager doesn't start on Windows 7
- Toggling "Optimize Mesh Data" in Project Settings doesn't invalidate build pipeline cache for Addressables
- [HDRP] [DXR] Shadowmatte doesn't support RT shadows
- [HDRP] TAAU@100% and TAA produces different results
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0f1