Search Issue Tracker
By Design
Votes
1
Found in
2017.4
2019.3.0f5
2020.1
Issue ID
1213833
Regression
No
Rotating multiple selected Game Objects in the Editor sets their Rotation to one of the selected object's
Steps to reproduce:
1. Open the attached project (1213833.zip)
2. Ensure that "Sphere", "Cube" and "Cylinder" all have differing rotations set
3. Select the aforementioned objects
4. Attempt to change the Transform Rotation in the Inspector (either by inputting a value or using your mouse cursor to increment/decrement)
Expected result: Objects retain their original Rotation and are only rotated on the select axis
Actual result: Some (seemingly random) object is selected as a "reference" and the rest of the objects inherit its Rotation values
Reproduced in: 2017.4.36f1, 2018.4.16f1, 2019.2.18f1, 2019.3.0f5, 2020.1.0a20
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
When multi selecting, it is the expected behavior that changing values in the inspector will apply a single value to all values. To get the expected result, use the Rotation Tool in Pivot mode instead.