Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2018.4
2018.4.27f1
2020.2
Issue ID
1282836
Regression
No
The first Object selected dictates what Flags will be set when editing multi-selected objects with EnumFlagsField mixed values
How to reproduce:
1. Open the attached project("EnumFlagsFieldBugReport.zip")
2. Select "ExampleObject1" in the Hierarchy
3. Click on the dropdown of "Int Flags Field" in the Inspector window
4. Set the value to "None"
5. Select "ExampleObject2" in the Hierarchy
6. Click on the dropdown of "Int Flags Field" in the Inspector window
7. Set the value to "Flag 1"
8. Select "ExampleObject1" and "ExampleObject2" in the Hierarchy
9. Click on the dropdown of "Int Flags Field" in the Inspector window
10. Set the value to "None"
Expected results: Both "ExampleObject1" and "ExampleObject2" "Int Flags Field" values are set to "None"
Actual results: "ExampleObject1" and "ExampleObject2" "Int Flags Field" values do not change
Reproducible with: 2018.4.28f1, 2019.4.12f1, 2020.1.9f1, 2020.2.0b7
Note: reproduces only when you select a value that the first Object("ExampleObject1") already has marked as Flag
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note (fix version 2021.1):
Fixed in: Unity 2021.1.0a9 and newer