Search Issue Tracker
By Design
By Design in 6000.1.X
Votes
0
Found in
2021.3.45f1
2022.3.51f1
6000.0.25f1
6000.1.0a2
Issue ID
UUM-85945
Regression
No
Rotating GameObjects is not possible when transform.up is assigned through script
How to reproduce:
1. Open the attached “IN-87058” project
2. Open the “SampleScene”
3. Enter Play mode
4. In the Hierarchy, select the “Test” GameObject
5. In the Inspector, try changing the values of the Transform’s y-rotation field
6. Observe the result
7. Exit Play mode
8. Open the “Test.cs” script attached to the “Test” GameObject
9. Uncomment line 16, save the changes, and close the code editor
10. Repeat steps 3 to 6
Expected result: It is possible to rotate the GameObject both before, and after uncommenting the code in step 9
Actual result: It is not possible to rotate the GameObject after uncommenting the code in step 9
Reproducible in: 2021.3.45f1, 2022.3.51f1, 6000.0.25f1, 6000.1.0a2
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: Also affects transform.forward and transform.right
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
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- 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
Resolution Note:
This is by design because Transform and custom user's script confict in setting the rotation. Transform tries to set one rotation from input control and user's script is overriding that change by reseting to default up vector (Rotation and up vector are derrived from the same data). This resetting is reflecting in the UI of transform as well showing that no matter the input, rotation is kept the same.
Resolution Note (6000.1.X):
This is by design because Transform and custom user's script confict in setting the rotation. Transform tries to set one rotation from input control and user's script is overriding that change by reseting to default up vector (Rotation and up vector are derrived from the same data). This resetting is reflecting in the UI of transform as well showing that no matter the input, rotation is kept the same.