-
-
Notifications
You must be signed in to change notification settings - Fork 161
Troubleshooting
DLSS Swapper searches for DLLs with specific names to detect various technologies in games. If a certain technology does not come in a DLL then we are unable to swap it. This includes FSR 1, FSR 2, and FSR 3.0.
If you are a certain technology to show up in DLSS Swapper and it doesn't you can open your game folder and can search for these specific DLLs manually. If they are found but DLSS Swapper still does not detect them please file a bug report.
If they don't exist then the game does not have the technology in a way that DLSS Swapper can use.
The current supported DLLs are:
- nvngx_dlss.dll
- nvngx_dlssg.dll
- nvngx_dlssd.dll
- amd_fidelityfx_dx12.dll
- amd_fidelityfx_vk.dll
- libxess.dll
- libxell.dll
- libxess_fg.dll
If you are expecting to see FSR 1, FSR 2 or FSR 3.0 they are not supported by DLSS Swapper. Their implementations do not use a DLL based approach. With no compatible DLLs in the game we have nothing to swap.
Several things can cause to be in a not ready to play state such as:
- Game is a preload
- Game has a pending update
- Game is currently updating
When the game is in this state you can still change DLLs, however if there is an update pending it may override your changes. It is usually best to refresh the game and wait for this banner to disappear.
TODO
The way DLSS Swapper defines a "downloaded" and an "imported" DLL could also be called "known" and "unknown".
When you import a DLL we do a few checks to make sure it is not a duplicate of an existing DLL. One of those checks is to check against the known DLLs list. If the DLL is on the known list it will show up as though it was downloaded.
A side-effect of how DLSS Swapper handles "known" and "unknown" DLLs is if you import a DLL that is currently unknown it will show up in the app as an imported DLL. If DLSS Swapper later updates and this DLL is now known, that existing record will be converted from an imported state to a downloaded state.
See imported DLL looks the same as a downloaded DLL for more information as to why we do this.
test sidebar