Search Issue Tracker
Fixed in 3.1.2
Votes
1
Found in [Package]
3.1.0
Issue ID
1344618
Regression
Yes
Enabling FXAA results in a worse effect than No Anti-Aliasing when using RenderTexture
How to reproduce:
1. Open the user's attached "anti-aliasing" project
2. Open the Scene "SampleScene"
3. In the Hierarchy select the "Camera" GameObject (child of the "Renderer" GameObject)
4. In the Inspector, "Post-process Layer" Component switch the Anti-aliasing Mode between "No-Anti-aliasing" and "FXAA"
5. In the Game view compare the image quality
Expected results: When the "FXAA" is enabled the car looks better
Actual results: When the "FXAA" is enabled the car looks worse
Reproducible with: 3.1.0 (2019.4.28f1), 3.1.1 (2019.4.28f1, 2020.3.13f1, 2021.1.13f1, 2021.2.0b1)
Not reproducible with: 3.0.3 (2018.4.36f1, 2019.4.28f1)
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
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
Resolution Note (fix version 3.1.2):
Fixed in PostProcessing 3.2.0 available in Unity 2019.4.19f1 and above