Search Issue Tracker
Fixed in 2022.3.20f1
Fixed in 2022.3.X, 2023.2.X, 2023.3.X, 2023.3.0b10
Votes
0
Found in
2023.1.0a12
2023.2.0a1
2023.3.0a3
Issue ID
UUM-5919
Regression
Yes
CustomPropertyDrawer array elements disappear when changing type
1. Open the user's attached project "1409773_ArrayInspectorTest(3).zip"
2. Select the "Custom" GameObject in the Hierarchy window
3. Change the element's type (eg. A to C) under the "New Behaviour Script" component in the Inspector window
Expected result: The element remains visible
Actual result: The element disappears
Reproducible with: 2022.2.0a13, 2022.2.0a17
No repro: 2019.4.40f1, 2020.3.36f1, 2021.3.4f1, 2022.1.5f1, 2022.2.0a12
Reproducible on: macOS 12.0.1 (Intel)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2023.3):
This issue is resolved in 2023.3.0b10 and later.
Resolution Note (fix version 2023.2):
Issue is resolved in editor version 2023.2.10f1 and later
Resolution Note (fix version 2022.3):
Issue is resolved in editor version 2022.3.20f1 and later.