Skip to content

VR: Rephrase DLSS-FG warning message#406

Open
gwizdek wants to merge 1 commit intopraydog:masterfrom
gwizdek:rephrase-dlss-fg-warning
Open

VR: Rephrase DLSS-FG warning message#406
gwizdek wants to merge 1 commit intopraydog:masterfrom
gwizdek:rephrase-dlss-fg-warning

Conversation

@gwizdek
Copy link

@gwizdek gwizdek commented Jan 29, 2026

Every other day we are asked about the DLSS-FG warning. This will save us a lot of headaches.

@DarkSigmaDevelopment
Copy link

DarkSigmaDevelopment commented Jan 29, 2026

It might also be helpful to change it to a yellow or orange color instead of red.
Most complaints in the Discord call it an error. Even though the text clearly says Warning.

Furthermore, people do not know the distinction between DLSS for Frame Generation and DLSS for Upscaling.
So perhaps that should be incorporated. If it can be done without bloating the message.

@lobotomy-x
Copy link

I don't think rephrasing the message will address the root issue. In truth there's no real point to having any message in the GUI if our only goal is to prevent FG. I wrote a lua script that automatically finds and disables any of the 3 variants of FG if VR is enabled and active and adds a panel for changing super resolution settings, e.g. you can set the DLSS presets normally reserved for Nvidia profile inspector.

This could be added to the backend directly but there's no real benefit other than increasing reach since it just has to run once on start. I will post it in discord later. It can be installed as a global script. I don't mind if it gets remade into C++ and PRd or even if we had some default scripts that ship with the official release like reframework has that's the sort of thing we could include.

Of course this doesn't help at all with the potential issues from using the streamline swapchain that require disabling HAGS and/or deleting the plugin. But neither does the in-game warning since an out of game action is required so we kind of just have to tell people what to do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants