Add DLSS info to overlay parameters

[Hlsgs]

I know this is long shot, but any and all of the following would be very useful if they are somehow accessible:

• DLSS preset(most important)
• DLSS quality
• rendering resolution

Thank you!

[DevTechProfile]

Rendering resolution is already supported. What do you mean by "DLSS Quality"? Just to be clear, you want an overlay entry showing the current DLSS preset?

[Hlsgs]

Rendering resolution is already supported. What do you mean by "DLSS Quality"? Just to be clear, you want an overlay entry showing the current DLSS preset?

Yes, as in preset K, preset L etc. This is the most importrant one.

By DLSS quality I meant "quality", "performance" etc. but, come to think of it, this is kind of reduntant, so nevermind.

By rendering resolution I mean the actual rendering resolution of the frames that are getting then upscaled by DLSS to the resolution of the monitor (not sure if that's what's already implemented and can't test now).
This is all info that can be seen by enablind the DLSS dev overlay via a registry option, but that needs the game to restart whenever you enable/disable it. Here is what that looks like:

EDIT: Looking at the picture I shared, another piece of very useful info would be the DLSS version(v310.2.1 in that case). This is to ascertain whether nvidia container service succesfully downloaded and upgraded to the latest version of the library.

[Hlsgs]

@DevTechProfile Please excuse the ping, but I'm very curious if you've looked into whether this info is even possible to access.

[DevTechProfile]

Currently looking into this.

[DevTechProfile]

Thanks for the suggestion. We evaluated this against the current CapFrameX OSD hook architecture.

For the initial implementation, we will focus on the low-risk Frame Generation features that can reuse the state already tracked by the active CapFrameX in-game OSD hook. In particular, the FG status can be exposed without adding further NGX/Streamline hooks or changing the existing Present routing.

Full DLSS detection (preset, quality mode, and internal rendering resolution) will follow once the OSD hook itself has reached a sufficient level of stability. Providing the same information while RTSS is used requires a separate in-process observer; that observer is planned for v2.0.0.

We will keep this issue open to track the remaining DLSS detection work.

[Hlsgs]

(preset, quality mode, and internal rendering resolution)

Don't know if you meant that list to be exhaustive, but, if you did and if it's possible, please add DLSS version to it.

[DevTechProfile]

Version will be part of it. Just forgot to add it.

[DevTechProfile]

FG detection works. Needs more testing though...

[Hlsgs]

I unfortunately can't test as I don't own an FG capable GPU, so I'll be waiting patiently for the main DLSS stuff.

[evilbananas]

Great Work. This information is very useful for helping you determine if you are actually using new presets/models that NVIDIA is releasing.

The DLSS updates NVIDIA is releasing that I think would be useful to know on the OSD: DLL version, SR Preset, RR Preset and FG Preset.

Some of this you can already get from the NVIDIA overlay