-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature request] Note the initial DLSS version for each game to allow for easy revert #247
Comments
Hey @recoi1er , thanks for filing an issue. There is a reset button to reset to what was swapped out, however we can't tell what the game currently should have. This means if the game updates we can't tell that what exists was swapped with DLSS Swapper, swapped manually, swapped from another tool, etc. This means that hitting reset would actually downgrade it to what the game comes with. The functionality is we copy the file to be ".dll.dlsss" (or something). So we only check if the file exists and if it does it means we can swap it back. If you delete that file the swap back will no longer appear. You are correct though, the UI does not show what the swap back will go to. In the newer version of DLSS Swapper (not released yet) we do track what we last saw so we can report that it has changed outside of the application. We also track the backup files so we can show what revert will change it to. |
I figure an easy way for this to be tracked is when a game is loaded into your app, whatever version of DLSS it currently has becomes its “default” and gets an asterisks next to it just for a visual on what it last had. Also one thing that would be really nice is when a game is loaded into the app, if that version of DLSS is not yet downloaded it offers a prompt to download it with a check box to always download without prompting |
If I have a game and it has DLSS 3.1 (DLSS versions are made up in these examples), I swap it to DLSS 3.2 I can make it show that it was 3.1. However if the game updates and it now has DLSS 3.3 then DLSS Swapper will still show 3.1 as the version it wants to go back to. We can watch for changes, so after the game updates to 3.3 above DLSS Swapper will just go "🤷♂️I guess we are 3.3 now" and removes any reference to 3.2 that we swapped to, or 3.1 which was the "default" from before. The downside to this is if you use another tool or swap DLSS dlls yourself in Windows Explorer then we will remove the backup that we kept incase things go badly. I guess if things go badly enough people can just verify/repair their game with their game manager, or swap a fresh DLSS dll in.
The problem with downloading at the swap screen is we'd then have to stop the user doing anything else. Allowing them to go to library page to download a different dll, or go to a different game and trigger another dll can complicate things. If they choose to swap to DLSS 3.2 which is currently not downloaded if we threw up a "downloading" screen with progress bar then we can do it. It just means they have to wait until its done (or cancel it) before they can do anything else. There is also this other issue I created which is sort of on topic. If you have four games games, two have DLSS 3.1, another has 3.2 and another has 3.3, DLSS Swapper should be able to import these 3 versions so you an use any of these three DLSS versions in any of these four games without downloading a single DLSS file. It's possible people won't have the issue of downloading a DLSS files if they happen to have a game with the latest. |
Is your feature request related to a problem? Please describe.
Would love to see a way to easily go back to the default version the app had, like a revert option or maybe just an asterisks next to the version that the game currently had as its default version
Describe the solution you'd like
If you change to a version of DLSS that doesn't but don't recall what it was before, would be nice to easily go back by being to see a visual cue (like an *) next to that version!
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: