- Proton (SLR and Native)
- Updated to the most recent Proton Experimental release
10.0-20260312. - Enabled
wine-nvmlby default for Nvidia GPUs at the request of its developer in order to get wider testing for it.wine-nvmlallows applications running under Wine to call some NVML functions as if the native Windows driver was installed into the prefix with the purposes of monitoring GPU temperature, utilization, etc. It gives the benefits of GPU utilization reporting without going through the manual installation process. It can still be disabled withPROTON_NVIDIA_NVML=0if needed. ntsynchas been enabled by default. It can still be disabled when required withPROTON_USE_NTSYNC=0.gplasynchas been removed from our alternative DXVK, and with itPROTON_DXVK_GPLASYNC.PROTON_DXVK_LOWLATENCYremains, and it is the only option now.- Imported
winewayland.drvupdates from Proton-EM (up to Proton-EM 10.0-34). - IME is NOT disabled by default on
winewayland.drvany more, repeat keys should work now regardless. - Added a temporary alternative
vkd3d-protonusing thedescriptor-heap-testbranch. Can be enabled withPROTON_VKD3D_HEAP=1. Needs at least the595.45.04Nvidia beta driver. Be aware that this can introduce issues like black screens, broken shadows or similar. Do NOT report them to the upstreamvkd3d-protonproject - Updated D7VK to v1.5
- Updated protonfixes to Open-Wine-Components/umu-protonfixes@c5da693
- Fixed the FSR4 downloader to fallback to a previous version if the required DLL could not be found. Recently AMD removed all the
amdxcffx64.dllversions other than4.0.0, so now bothPROTON_FSR4_UPGRADEandPROTON_FSR4_RDNA3_UPGRADEwill download that version. The downloader will try to find and download newer versions if they become available again.
- Updated to the most recent Proton Experimental release
- Proton (SLR specific)
- None
- Proton (Native specific)
- None
- Wine (Standalone)
- None
Note
We have been building arm64 packages of Proton-CachyOS for the past few versions. They are now part of the release but they are untested and possibly
broken. To use this build you will need to get and build a development version of umu-launcher from https://github.com/Open-Wine-Components/umu-launcher.
From the CLI interface it should work normally by pointing PROTONPATH to this proton build. If you want to enter the steamrt4 container to inspect it
without running proton, you can do so by running PROTONPATH=umu-steamrt4-arm64 umu-run xterm.
I also provide unpatched builds of Proton Experimental with support for umu-launcher in my personal repository
https://github.com/loathingKernel/Proton/releases which can be used for testing arm64
We are looking for testers, if you are interested, feel free to contact me (@loathingKernel) in the CachyOS Discord server.
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. The x86_64_v2
and x86_64_v3 should be absolutely identical between them and with x86_64 across the board, and x86_64_v4 can be worse in some cases.
Feel free to experiment and see which fits better for your system, of course.
Warning
This release includes a x86_64_v4 package. This package is largely untested and experimental.
It may exhibit issues or completely refuse to work. Use at your own discretion and report issues here only.
Note
For Wayland specific flags and options, please refer to: https://github.com/Etaash-mathamsetty/Proton/blob/em-10/docs/EM-ADDITIONS.md
Note
For FSR4 related documentation, please refer to: https://github.com/Etaash-mathamsetty/Proton/blob/em-10/docs/FSR4.md
Note
For DXVK-Sarek specific options to tune its behavior refer to: https://github.com/pythonlover02/DXVK-Sarek?tab=readme-ov-file#shader-compilation
Note
For the low-latency related 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-10.0-20260312