Forum Discussion
During my experimentation with DLSS I noticed that if you manually disable TAA in hardware_settings_config.xml while using DLSS, you will get a lower internal resolution, and not the quality level that defined with the key "aa_quality" in the config.
Because if you do this, it automatically Turns TAA to on, and Disables DLSS, when you start up the game.
Shame, as I thought this would be the answer.
- 2 years ago@rdalcroft For me, at this point in time, the best way forward is turning off any AA in the settings config file, and forcing FXAA through Nvidia control panel. Has some jaggies, but at least less ghosting and blur, to the point where it has become a lot more clear.
- 2 years ago
@rdalcroft wrote:Because if you do this, it automatically Turns TAA to on, and Disables DLSS, when you start up the game.
Shame, as I thought this would be the answer.
This is not true and you need to stop claiming this as you doesn't seem to have actually checked this at all.
Notice how DLSS is still active (overlay in the bottom left corner, but settings page still says TAA?
The content of the anti-aliasing configuration are the following:
<antialiasing taa="false" checkerboard="false" cmaa2="false" dlss="true" cas="0" fsr="0" fsr2="0" xess="false" /> <aa_quality value="0" />
Every time you make a change to the settings, the settings are immediately written to the file, so you can easily see what is enabled and disabled.
So if you make a change in the UI, it will change in the config.
Regarding the status of TAA it is just visually indicated in the settings page, but not actually active.
Codemasters are most likely just falling back and displaying the first entry in the array of options when the settings in the config file does not match any of the predefined presets and thus, it's just visual in the menu and nothing else.
About F1® 23
Recent Discussions
- 14 days ago
- 21 days ago
- 21 days ago
- 21 days ago
- 27 days ago