Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.45f1
2021.3.18f1
2022.2.7f1
2023.1.0b3
2023.2.0a2
Issue ID
UUM-28031
Regression
No
Problem when using EditorGUILayout.EnumFlagsField with a non-ordered Flags Enum
Reproduction steps:
1. Open the “EditorHandleGizmoTest“ Project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Select the “GameObject” GameObject in the Hierarchy Window
4. Select the “Error Enum (Script)” Component in the Inspector Window
5. Under “This no work” Property check various properties and observe the field
Expected result: The Property field displays the checked properties
Actual result: The Property field displays incorrect properties
Reproducible with: 2020.3.45f1, 2021.3.18f1, 2022.2.7f1, 2023.1.0b3, 2023.2.0a2
Reproduced on: Intel MacOS 13.1
Note: The same situation can also be seen on other drop-down properties on the “GameObject” GameObject
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:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas. As such, we have decided not to invest time and resources into addressing it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2023.2.X):
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas. As such, we have decided not to invest time and resources into addressing it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.