Hello
I appreciatr your feedback here, but your reasoning is wrong.
TAA is always enabled when DLSS is enabled, in the Config file.
Just go back and look at the config files of F1 2022, F1 2021. These all have TAA enabled if DLSS is enabled.
Plus in the config file, if you manually set TAA to disabled, and leave DLSS to on. Then when you start the game. It will automatically set TAA to on, and disable DLSS.
I really thought you were on to something, when I first read your post.
But after firing up the game, and doing a bit of tweaking, these are my conclusions.
@rdalcroftThat may be, but this is an erroneous behaviour, and should not be happening as this would run two passes of anti-aliasing.
Notice how FSR2 and XeSS isn't using TAA.
If you manually disable TAA and enable DLSS in the config file, the game will show TAA to be enabled, but won't actually be enabled. (Just view the configuration files while running the game). As long as you don't change any anti-aliasing setting, it will be whatever you configured in the config file, and as soon as you change anything in game, it will be whatever the settings in the UI toggles.
You will also run the game with a significantly lower internal resolution when disabling TAA, and leaving DLSS on (even when using DLAA), which also seem to be an unexpected behaviour.
So even if the game says "TAA" in the settings, you would be using DLSS.
I suggest that you run DLSS with the overlay and you'll be able to see the input and output resolution and when DLSS is being used.
Anti-aliasing config in hardware_settings_config.xml:
<antialiasing taa="false" checkerboard="false" cmaa2="false" dlss="true" cas="0" fsr="0" fsr2="0" xess="false" /> <aa_quality value="0" />
What's being shown in the menu (DLSS status overlay still active in bottom left corner even though menu says TAA, which is disabled in the config):
