Search Issue Tracker
Won't Fix
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
- The text below Orientation Gizmo does not change when the Scene viewing direction changes
- CPU is overused and the usage cannot be limited for Runtime when the Editor is not rendering anything
- Recorder Texture Sampling does not record Canvas images correctly when the Camera projection is Orthographic
- [HDRP] HDAdditionalLightData.RequestSubShadowMapRendering on directional lights breaks cascade shadows rendering
- Memory leaks when Instantiating Objects with SerializeReference
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.