Search Issue Tracker
Fixed
Fixed in 2021.3.36f1, 2022.3.21f1, 2023.2.13f1, 2023.3.0b10
Votes
0
Found in
2021.3.34f1
2022.3.17f1
2023.2.6f1
2023.3.0b3
Issue ID
UUM-61080
Regression
No
Fields can still be edited even though multi-editing is not supported when multiple Game Objects are selected
How to reproduce:
1. Open the “MultiEdit“ project
2. Open the “SampleScene”
3. In the Scene view window select the “GameObject”
4. Then select both “GameObject” and “GameObject (1)” by dragging a box on the diamond-shaped icons
5. In the Inspector window observe the “Test Script” Component’s “Value” field
Expected result: The “Value” field is not shown or cannot be edited
Actual result: The “Value” field is shown and is editable
Reproduced with: 2021.3.34f1, 2022.3.17f1, 2023.2.6f1, 2023.3.0b3
Reproduced on: macOS 14.1.1 (Intel) (by reporter), Windows 11
Not reproduced on: No other environment tested
Note: The “Multi-object editing not supported.” message is shown in the Inspector for both the actual and the expected results
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment