Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.45f1
2021.3.20f1
2022.2.8f1
2023.1.0b5
2023.2.0a4
Issue ID
UUM-30239
Regression
No
Rect Transform is rotated very fast when using Rotate tool in Blueprint mode
Reproduction steps:
1. Open the attached project “FastRotate”
2. Select the Rotate tool by clicking on the button in Scene view or press the assigned key (by default: e)
3. In the Scene view via the Toggle Tool Handle Rotation dropdown menu change from Global to Local
4. Select the GameObject “Image”
5. In the Inspector activate Blueprint mode by selecting the square with dashed borders
6. In the Scene view rotate the GameObject by clicking and dragging the axes of the wireframe sphere Gizmo that appears around it
Expected result: GameObject is rotated at a normal speed
Actual result: GameObject is rotated over 100 times faster than it is supposed to be
Reproducible with: 2020.3.45f1, 2021.3.20f1, 2022.2.8f1, 2023.1.0b5, 2023.2.0a4
Reproducible on: Windows 10
Note: When Ctrl is held down, it activates snapping to the rotation, but whenever the mouse is moved a little bit so it would not change the snap position, it still rotates the GameObject.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
After investigation, we have deemed this a low priority issue that won’t be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so.
If you feel this is a wrong assessment, please reach out again, providing more details about the impact of that issue.
Resolution Note (2023.2.X):
After investigation, we have deemed this a low priority issue that won’t be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so.
If you feel this is a wrong assessment, please reach out again, providing more details about the impact of that issue.