Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0f1
Issue ID
926104
Regression
Yes
Translating multiple UI elements at once does not apply the same translation to all elements
To reproduce:
1. Open attached Unity project "UITranslateMultiBug.zip"
2. Open "scene01" scene
3. In the hierarchy, expand HUDCanvas and select "item1" and "item2" at once (or any other 2 or more "item" objects)
4. Move select objects by the y axis
Expected result: all of the objects selected should translate the same (see attached gif "Expected.gif)
Actual result: Selected objects translate at different speeds (see attached gif "Actual.gif")
Regression first introduced in: 2017.1.0f1
Reproduced on: 2017.1.0f1, 2017.1.0f2, 2017.2.0b1
Not reproduced on: 5.6.2f1, 2017.1.0b10,
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
- 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
This is a duplicate of issue #925765