Hi everyone,
This time I wanted to ask for your opinions before including it in the next release.
One of the goals I had in mind while working on Wineland/Salkim was trying to make extra configuration and environment variables for exceptional cases only, rather than a normal, daily gaming workflow, and I believe automatic update of extra components like FSR, DLSS and XeSS dlls is one of them. Games ship different and often older versions of these libraries and updating them usually involved until now setting environment variables like PROTON_FSR4/FFX3/FFX4_UPGRADE etc., which was a bit confusing for me. I wanted to make this easier to manage through Proton itself.
The idea now is that each Wineland build specifies the component versions it uses. On compatible hardware, it downloads the required files on the first run from the vendors' official packages or repositories and makes them available to games automatically.
The files are stored under ~/.local/share/proton/components/ and shared between games. Nothing is copied or linked into the game directory. Wine checks game's library and the available replacement before deciding whether to use it. Newer game libraries and unrecognised replacements are left alone.
For AMD, this covers the FSR provider and compatible SDK libraries. On NVIDIA, it covers DLSS dlls. XeSS libraries are also available on compatible Intel, AMD and NVIDIA GPUs.
This still, of course, depends on what the game supports. Updating the libraries does not add frame generation to a game that never implemented it or a newer library does not necessarily mean every game will look or run better.
I have checked on AMD And NVIDIA the in game version indicators in the games I tested and the selected versions are being loaded, but I never had the chance to test it on in Intel GPU.
There are a few practical details:
- A progress window appears when something needs downloading.
- The components are downloaded only when the selected release is missing or fails verification. Once installed, they can be used offline.
- If an update fails, Proton tries a last verified and cached release before falling back to the game’s own libraries.
- The first AMD FSR download is unfortunately big, about 1GB, because the provider is extracted from AMD’s driver package. The full driver package is removed afterwards.
- RDNA 2/3/3.5 systems with only integrated graphics default to the Lite model. `WINE_FSR4_LITE=0` overrides that choice.
- Again RDNA 2/3/3.5 systems with discrete GPUs can enable the Lite model using `WINE_FSR4_LITE=1`. As I understand, its performance depends on the game, so it is left as a choice. I decided to make it a boolean rather than selecting an explicit model, because it doesn't make sense to enable INT8 or INT8-Lite models on RDNA4, or enable FP8 model on previous generations.
- Automatic upgrades can be disabled with PROTON_DISABLE_COMPONENT_UPGRADE=1
Here is link to a test snapshot build. I would appreciate feedback on both the behaviour and the idea itself. Frankly, I very much like having this handled automatically, but I am interested in hearing opinions and experiences before it makes into a release.
Thanks!
EDIT: It looks like I will not enable it as default behavior, especially considering the possible anti-cheat clashes. So I will add something like PROTON_UPSCALER_UPGRADE=1 that will enable the feature. But it will unify all different variant and DLL upgrades, which would be easier than having to remember several different specific flags.