Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.21f1
2022.2.12f1
2023.1.0b9
2023.2.0a7
Issue ID
UUM-30938
Regression
Yes
Camera gets forcefully redirected after continuous movement
Reproduction steps:
1. Open the attached “The Game 2.zip“ project
2. Open the “SampleScene” scene
3. Enter Play mode and move mouse cursor around for 20-40 seconds
4. Observe the Game window
Expected result: Camera rotates with mouse cursor without any problems
Actual result: Camera gets forcefully redirected
Reproducible with: 2021.3.7f1, 2021.3.21f1, 2022.2.12f1, 2023.1.0b9, 2023.2.0a7
Not reproducible with: 2020.3.46f1, 2021.3.6f1
Reproduced on: macOS Monterey 12.6 (Intel), Windows 11 (by the reporter)
Note: Not reproducible in Build
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
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Resolution Note:
This seems to be a user script error. We've seen no other similar reports of camera issues and moving the camera is a common operation. The user clamps rotations, uses incremental rotations and mixes rotations on two different objects in the hierarchy. It seems likely something goes wrong with their camera logic. This may be numerical instability, gimbal lock or a variety of other script errors that are not Unity-bugs.
Resolution Note (2023.2.X):
This seems to be a user script error. We've seen no other similar reports of camera issues and moving the camera is a common operation. The user clamps rotations, uses incremental rotations and mixes rotations on two different objects in the hierarchy. It seems likely something goes wrong with their camera logic. This may be numerical instability, gimbal lock or a variety of other script errors that are not Unity-bugs.