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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment