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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 3.1.2):
Fixed in PostProcessing 3.2.0 available in Unity 2019.4.19f1 and above