Search Issue Tracker
By Design
Votes
0
Found in
6000.0.50f1
6000.1.5f1
6000.2.0b3
Issue ID
UUM-107999
Regression
No
Temporal Anti-aliasing causes jittering/shaking when using a Camera overlay in the Scene View
How to reproduce:
1. Open the project “IN-102544_JitterTAA”
2. Move the Game View Tab to another screen
3. Click on the Game View or move the mouse on the little Camera in the Scene View
4. Observe the Game View
Expected result: No jitter/shake is present
Actual result: The GameObjects jitter/shake
Reproducible with: 2023.3.0b10, 6000.0.50f1, 6000.1.5f1, 6000.2.0b3
Could not test with: 2022.3.62f1 (URP 14 does not support Temporal Anti-aliasing)
Reproducible on: Windows 11, MacOS (M1)
Not reproducible on: No other environments tested
Notes:
- Recommended to move the Game View to a screen with Higher resolution than the screen with the Editor/Scene open
- The Main Camera → Rendering → Anti-aliasing is set to Temporal Anti-aliasing enabled
- The PC_RPAsset → Quality → Upscaling Filter is set to Spatial-Temporal Post-Processing
- TAA is officially supported from the 15.2+ URP versions What's new in URP 15 (Unity 2023.1)
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.