- Proton (SLR and Native)
- Updated to Proton Experimental
11.0-20260701b - Added
winepipewire.drvdriver for Wine to directly use Pipewire instead of usingwinepulse.drvand going through pipewire-pulse. Thanks to @M0n7y5.- The driver is enabled by default. To disable it and use
winepulse.drvsetPROTON_USE_PIPEWIRE=0. - You can also use
WINE_AUDIO_DRIVERto set the list of drivers for wine to choose from. The default list ispipewire,pulse,alsa. For exampleWINE_AUDIO_DRIVER=pulsewill usewinepulse.drvexclusively. - When reporting issues with
winepipewire.drvremember to usePROTON_LOG=warn+pipewire,warn+mmdevapi %command%for create meaningful logs. - You can make sure the game uses
winepipewire.drveither throughpw-topor by looking at the audio device names in the game itself which should include(Pipewire)in their name.
- The driver is enabled by default. To disable it and use
- Imported
amdxc64changes from Proton-EM to enable FSR44.1.1on all supported hardware. Thanks to @Etaash-mathamsetty. - Due to the updates regarding FSR4 and the update to version
4.1.1ofamdxcffx64.dllthe following things have been adjusted accordingly.- The
amdxcffx64.dlldriver dll is copied automatically, there is no need to usePROTON_FSR4_UPGRADEany more, although the environment variable remains to request a specific version of the dll ( restricted to4.0.0and4.1.1only right now ). - It's worth noting here that when using the OptiScaler integration,
PROTON_FSR4_UPGRADEwill accept more versions than just4.0.0and4.1.1and it will control the version of the respective FidelityFX SDK dlls. - It is not possible anymore to manually provide different
amdxcffx64.dlldll versions through the protonfixes cache. It was ugly and confusing anyways. I am glad it's gone. - Since the dll is always present the following shorter environment variables will also work.
Variable Description FSR4_UPGRADEUpgrade FSR3/4 to newer FSR4 (FP8 or I8) using AMD's FSR 4.1.1 amdxcffx64.dll taken from Proton Experimental. This option is not needed on RDNA2-4 discrete GPUs. MLFG_UPGRADEEnables FSR4 MLFG upgrade to use redstone frame generation. Can be used in tandom with FSR4-I8 on RDNA3 using DXIL_SPIRV_CONFIG=wmma_rdna3_workaround. - Removed
PROTON_FSR4_RDNA3_UPGRADEas settingDXIL_SPIRV_CONFIG=wmma_rdna3_workaroundis not required any more in most cases, with the exception of enabling MLFG on RDNA3 (see table above). - Removed
PROTON_FSR3_UPGRADE, it has been renamed toPROTON_FFX3_UPGRADE. You do not need to ever use this under normal circumstances. - To make it a bit confusing again, the versions controlled through
PROTON_FFX4_UPGRADEcan also be controlled throughPROTON_FSR4_UPGRADEwhen OptiScaler is enabled, to remain somewhat compatible with existing configurations. - I am still considering how to make all this a bit more streamlined and consistent, so expect changes in this area in the future.
- The
- Added the DualSense 5 patches that were skipped previously due to the rebase to Proton 11.0. Thanks to @xzn.
- Added some stubs to
dnsapiwhich should allow iRacing to run. The anti-cheat blocks the game from fully working. Thanks to @DanFraserUK. MRs: CachyOS/wine-cachyos#18 https://gitlab.winehq.org/wine/wine/-/merge_requests/11208 - Fixed Surviving Mars crashing after loading into the start menu along with some other audio-related issues. Thanks to @NelloKudo. Issue: #233 #236
- Fixed compile-time configuration for GStreamer, specifically enabled
glib-checksagain, as disabling them caused some issues with media playback since Wine depends on the APIs they provide for fault checking. Thansk to @NelloKudo. - Updated
d7vkto versionv1.12. - Improved the Vulkan version detection and the underlying API to also check for driver versions and extensions in the future. Thanks to @CommandMC.
- Added
PROTON_ADD_CONFIGenvironment variable to supply configuration through compatibility configs instead of environment variables. It accepts a comma-separated list of compat configs. If you are wondering what these are, they are the first column in the tables of environment variables in the documentation. - Enabled the
compileritem inDXVK_HUDby default. Since there are too many invalid reports due to shader compilation from new users, this should provide a visual feedback aid of what is going on.
- Updated to Proton Experimental
- Proton (SLR specific)
- None
- Proton (Native specific)
- None
- Wine (Standalone)
- None
Important
I know that we have a lot of different packages that might cause confusion. My suggestion is to be conservative and use x86_64.
Feel free to experiment and see which fits better for your system, of course.
Note
- For Wayland specific flags and options, please refer to: https://github.com/Etaash-mathamsetty/Proton/blob/em-10/docs/EM-ADDITIONS.md
- For FSR4 related documentation, please refer to: https://github.com/Etaash-mathamsetty/Proton/blob/em-10/docs/FSR4.md
- For
dxvk-sarekspecific options to tune its behavior refer to: https://github.com/pythonlover02/DXVK-Sarek?tab=readme-ov-file#shader-compilation - For
dxvk-low-latencyrelated options to tune its behavior refer to: https://github.com/netborg-afps/dxvk-low-latency?tab=readme-ov-file#dxvk-low-latency
Base: https://github.com/ValveSoftware/Proton/tree/experimental-11.0-20260701b