Search Issue Tracker
Fixed
Fixed in 2022.3.24f1, 2023.2.18f1, 6000.0.0b14
Votes
0
Found in
2022.3.21f1
2023.2.14f1
2023.3.0b10
6000.0.37f1
Issue ID
UUM-66550
Regression
Yes
ManagedReference fields with a custom PropertyDrawer aren't refreshed properly when changing properties
How to reproduce:
1. Open the attached “BugDrawerTests.zip” project
2. In the Project window, select “TestObject”
3. In the Inspector window, open the Context Menu using three dots and select “Use Int”
4. Open the Context Menu using three dots and select “Use Float”
5. Observe the result
Expected result: “PolymorphicData” appears as a foldout with a float field inside called "Value"
Actual result: “PolymorphicData” doesn’t change
Reproducible with: 2022.2.0b10, 2022.2.21f1, 2022.3.21f1, 2023.2.14f1, 2023.3.0b10
Not reproducible with: 2021.3.36f1, 2022.2.0b9
Reproduced on: macOS 14.3.1 (Intel)
Not reproducible on: No other environment tested
Notes:
- if nothing changes in the Inspector window, then setting the Editor window’s layout to “Default” should help
- for the first nonaffected editor version in the 1st step, use the "BugDrawerTests2022.zip" project and the names of fields can be not the same
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
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Resolution Note (fix version 6000.0.0b14):
Fixed in: 6000.0.0b14