Search Issue Tracker
Fixed
Fixed in 2021.3.33f1, 2022.3.12f1, 2023.2.0a7
Votes
0
Found in
2021.3.16f1
2022.1.24f1
2022.2.2f1
2023.1.0a25
2023.2.0a1
2023.3.0a3
Issue ID
UUM-21958
Regression
No
Constrained fields don't work as supposed to when using numeric field special function expressions on Transform Component's Scale field on multiple GameObjects at the same time
Reproduction steps:
- Open the attached “BugTest1.zip” project
- Open the “Assets/Scenes/SampleScene.unity” Scene
- Select all of the Cube GameObjects in the Hierarchy window
- Enter “L(1,5)” into the Transform Component’s Scale’s 'X' field
- Observe the Cube GameObjects in the Game View
Expected result: All of the Cube GameObjects have their ‘X', ‘Y’ and ‘Z’ Scale values equal to one another (The GameObjects retain Cube shape)
Actual result: The 'X’ Scale value is not “1”, but 'Y' and ‘Z’ Scale values are set to “1”(Some of the Cubes turn into Cuboids)
Reproducible with: 2021.3.16f1, 2022.1.24f1, 2022.2.2f1, 2023.1.0a25
Couldn’t test with: 2020.3.44f1 (“Constrained Proportions” option is not available)
Reproducible on: Windows 10 (21H2)
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