Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2021.1.X
Votes
2
Found in
2019.3
2019.3.7f1
2020.2
Issue ID
1232538
Regression
No
[SerializeReference] CustomPropertyDrawer doesn't get correct value when multiple elements use the same attribute in collection
How to reproduce:
1. Open user's attached project
2. Open "SampleScene" Scene
3. Select "GameObject" in Hierarchy
4. In the Inspector expand "Foos"
5. In the Inspector expand "SpecificElementA", "SpecificElementB", "WorkaroundElementC"
Expected result: Under the "SpecificElementB" the 3rd field should say "FooBarred: Unfortunately Yes"
Actual result: Under the "SpecificElementB" the 3rd field says the same as "SpecificElementA" 3rd field which is "FooBarred: Yes"
Reproducible with: 2019.3.0f1, 2019.3.9f1, 2020.1.0b5, 2020.2.0a7
Could not test with: 2017.4.39f1, 2018.4.21f1, 2019.3.0a1 because [SerializeReference] was introduced in 2019.3.0a2, 2019.3.0b12 because the elements get the attribute name (member) instead of attribute
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
- The Editor does not recognize button release when first releasing the "LShift" button and then "Numpad2"
- Reflection Probe doesn't load until it's selected in the Hierarchy window when the project has been opened
- "ArgumentNullException" error in the Console when selecting certain ScriptableObjects and entering Play Mode
- Configurable joints become bouncier when setting "Bounciness" below 1
- Prefabs get corrupted when editing Particle System curves
Resolution Note (fix version 2020.2):
Fixed in 2021.2.0a4
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b7
Resolution Note (fix version 2020.2):
Fixed in 2020.2.6f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.22f1