When to enable OverrideAutoExposure?

[TheSpider12]

As the title said. I'm not sure what this setting does. The note is: "May help with issues where DLSS2 games would fail to activate auto-exposure with DLSS3.1". How to know if the DLSS2 games in question fail to activate auto-exposure?

[emoose]

That was a request from a user, afaik certain DLSS2 games had an option to enable auto-exposure, but when using 3.1.1+ nvngx_dlss.dll the option would have no effect, guess they changed the flag value to enable it or something, that setting just forces the DLSS3.1.1 flag for it which apparently helped.

How to know if the DLSS2 games in question fail to activate auto-exposure?

Easiest way is probably to use DLSS2 DLL, enable OverrideDlssHud setting, and see what it says in bottom left corner, if that says "Auto-exposure: ON" then the game is activating DLSS2's AutoExposure, and it's probably worth setting OverrideAutoExposure to true to make sure DLSS3.1.1 also uses it.

Even if game doesn't use AutoExposure itself it could be worth trying with it enabled though, game might have been released before AE was added, seems it can help with ghosting in some games at least: https://www.youtube.com/watch?v=bY3DUJ-NYJ4

[TheSpider12]

Easiest way is probably to use DLSS2 DLL, enable OverrideDlssHud setting, and see what it says in bottom left corner, if that says "Auto-exposure: ON" then the game is activating DLSS2's AutoExposure, and it's probably worth setting OverrideAutoExposure to true to make sure DLSS3.1.1 also uses it.

Even if game doesn't use AutoExposure itself it could be worth trying with it enabled though, game might have been released before AE was added, seems it can help with ghosting in some games at least: https://www.youtube.com/watch?v=bY3DUJ-NYJ4

I tried this with Shadow of tomb raider's dlss2 dll and OverrideDlssHud enabled but I saw nothing at the bottom left corner. Only when I replaced the dlss2 dll file with dlss 3.1.1 dev dll file or dlss 3.1.1 latest released dll file then I saw it said AUTOEXPOSURE: OFF

However, if I don't enable autoexposure in that game then there's severe ghosting.

[emoose]

I replaced the dlss2 dll file with dlss 3.1.1 dev dll file or dlss 3.1.1 latest released dll file then I saw it said AUTOEXPOSURE: OFF

It could be saying that because game is still using the DLSS2 auto-exposure flag with the DLSS3.1 dll you swapped to, so DLSS3.1 wouldn't realize game is trying to set AE.

OverrideDlssHud should work on most DLSS2 non-dev DLLs too, but maybe the one included in SOTTR is too old for the method it uses to work... will try looking into that soon.

For now you could try seeing if the reg file method lets it show up with the original DLSS DLL it came with: https://github.com/emoose/DLSSTweaks/blob/master/external/ngx_driver_onscreenindicator_all.reg (click the download icon next to "Raw" text, then double-click file it downloads and press Yes to merge it)

You can remove that reg edit afterwards with this reg file: https://github.com/emoose/DLSSTweaks/blob/master/external/ngx_driver_onscreenindicator_off.reg

[TheSpider12]

I replaced the dlss2 dll file with dlss 3.1.1 dev dll file or dlss 3.1.1 latest released dll file then I saw it said AUTOEXPOSURE: OFF

It could be saying that because game is still using the DLSS2 auto-exposure flag with the DLSS3.1 dll you swapped to, so DLSS3.1 wouldn't realize game is trying to set AE.

OverrideDlssHud should work on most DLSS2 non-dev DLLs too, but maybe the one included in SOTTR is too old for the method it uses to work... will try looking into that soon.

For now you could try seeing if the reg file method lets it show up with the original DLSS DLL it came with: https://github.com/emoose/DLSSTweaks/blob/master/external/ngx_driver_onscreenindicator_all.reg (click the download icon next to "Raw" text, then double-click file it downloads and press Yes to merge it)

You can remove that reg edit afterwards with this reg file: https://github.com/emoose/DLSSTweaks/blob/master/external/ngx_driver_onscreenindicator_off.reg

With autoexposure not enabled the game suffers from severe ghosting. I guess autoexposure should be set to on.

Is there a downsides of always setting autoexposure (or overrideappid, also) to on in the ini file for the sake of convenience?

[Austinzveare]

I replaced the dlss2 dll file with dlss 3.1.1 dev dll file or dlss 3.1.1 latest released dll file then I saw it said AUTOEXPOSURE: OFF

It could be saying that because game is still using the DLSS2 auto-exposure flag with the DLSS3.1 dll you swapped to, so DLSS3.1 wouldn't realize game is trying to set AE. OverrideDlssHud should work on most DLSS2 non-dev DLLs too, but maybe the one included in SOTTR is too old for the method it uses to work... will try looking into that soon. For now you could try seeing if the reg file method lets it show up with the original DLSS DLL it came with: https://github.com/emoose/DLSSTweaks/blob/master/external/ngx_driver_onscreenindicator_all.reg (click the download icon next to "Raw" text, then double-click file it downloads and press Yes to merge it) You can remove that reg edit afterwards with this reg file: https://github.com/emoose/DLSSTweaks/blob/master/external/ngx_driver_onscreenindicator_off.reg

With autoexposure not enabled the game suffers from severe ghosting. I guess autoexposure should be set to on.

Is there a downsides of always setting autoexposure (or overrideappid, also) to on in the ini file for the sake of convenience?

I'd be curious about this too, as I've been forcing AE & overrideappid for every game.