Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
1
Found in
2020.3.40f1
2021.3.11f1
2022.1.20f1
2022.2.0b11
2023.1.0a14
Issue ID
UUM-19013
Regression
No
Camera jitters when changing Field of View at large coordinates
Reproduction steps:
- Open the attached project (“CameraAnimationBug“)
- Select Scene “Assets/CameraJitter/CammeraJitterBug“
- Enter Play Mode
Expected results: Field of View changes smoothly
Actual results: Camera jitters while Field of View changes
Reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.20f1, 2022.2.0b11, 2023.1.0a14
Reproduced on: Windows 11
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This seems a natural artefact from the use of floating point number by real-time rendering. It is an inherit limitation we can't really do much about.
In the sample the issue is amplified even more than with regular rendering by having a camera with a very narrow field of view 1 degree while fields of view of around 90 are more common. This leads to even worse precision artefacts.
To put this in perspective this is like using a camera with a 1.2 meter (1200mm) focal length while a normal lens is around 50mm.
These settings lead to an almost parallel camera. It's better to jus use an orthographic camera for these sort of effects.
Resolution Note (2023.1.X):
This seems a natural artefact from the use of floating point number by real-time rendering. It is an inherit limitation we can't really do much about.
In the sample the issue is amplified even more than with regular rendering by having a camera with a very narrow field of view 1 degree while fields of view of around 90 are more common. This leads to even worse precision artefacts.
To put this in perspective this is like using a camera with a 1.2 meter (1200mm) focal length while a normal lens is around 50mm.
These settings lead to an almost parallel camera. It's better to jus use an orthographic camera for these sort of effects.