Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2023.1.0a17
Issue ID
UUM-20788
Regression
Yes
Temporal Anti-aliasing is still visible in Game view when turning Anti-aliasing off
How to reproduce:
1. Open the attached project “TAASponza.zip“
2. Open Scene “Sponza“ (Assets/SponzaHDRP/Scenes)
3. Drag and drop the “SponzaLightingDay” Scene into the Hierarchy
4. Select the “Camera_1“ GameObject in the Hierarchy (child of the “Cameras” GameObject)
5. Focus on the Game view window
6. In the Camera Component of the “Camera_1“ GameObject go to “Rendering“ and change “Post Anti-aliasing” from “Temporal Anti-aliasing“ to “No Anti-aliasing“
Expected result: Anti-aliasing turns off
Actual result: Anti-aliasing effects remain
Reproducible with: 2023.1.0a8, 2023.1.0a17
Not reproducible with: 2022.2.0b14, 2023.1.0a6
Can’t test with: 2020.3.41f1, 2021.3.13f1, 2022.1.22f1 (“DivideByZeroException: Attempted to divide by zero.” errors in the Console)
Reproduced on: macOS (12.5)
Note:
- For the issue to be easier to see, in the Game view, change the scale from “1x“ to “10x“
- Issue also effects other TAA options (e. g. when “Sharpening Mode” is set to “Low quality“)
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
- Shader Graph Preferences are not indexed for Search and cannot be found when searching for them in the Preferences Search field
- Excessive bloom intensity when using narrow aspect ratios
- Text cursor remains visible when hovering over Command Line Arguments scrollbar in Unity Hub
- UI Builder’s "Background" icons for Repeat Y/X, Position X/Y and Slice Type are low quality and blurry in the Inspector window
- “X” button in Editor version search filter is difficult to see when Unity Hub theme is set to Dark
Resolution Note:
We didn't manage to repro the bug (neither developers or QA). Please try more recent alphas and if you still manage to repro open a bug
Resolution Note (2023.1.X):
We didn't manage to repro the bug (neither developers or QA). Please try more recent alphas and if you still manage to repro open a bug