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-29121
Regression
No
Unable to rotate GameObject with Rect tool when Blueprint mode is activated
Reproduction steps:
1. Open the attached project “HoverRotate”
2. Open Scene “Assets/Scenes/SampleScene.unity”
3. Make sure the Rect tool is selected
4. Select the “Image” GameObject
5. In the Inspector, activate the Blueprint mode button by clicking on the square with dashed borders
6. Hover the mouse around one of the corners of the “Image” GameObject
Expected result: Cursor changes to notify the user that GameObject can be rotated and lets GameObject be rotated.
Actual result: Cursor doesn’t change and GameObject can’t be rotated
Reproducible with: 2020.3.45f1, 2021.3.20f1, 2022.2.8f1, 2023.1.0b5, 2023.2.0a4
Reproducible on: Windows 10
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
- Package signature validation unexpectedly return an invalid signature status if the validation check is done after the code signing certificate validaty range has passed
- 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
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.