This release may have bugs! Please report any you find, especially ones related to enabling/disabling HDR that didn't exist in the previous version.

Now you can go into your games and turn that HDR on with no launch options (other than PROTON_ENABLE_WAYLAND=1)

TBH this was never the goal of this project, but it was certainly an interesting experience to get here.

You MUST use the Nvidia 595 driver (or higher) when using this proton from now on.

New Stuff:

• proton: Remove PROTON_ENABLE_HDR=1
  • dxvk: Add the opposite of the above: DXVK_NO_HDR=1. DXVK_HDR=1 should still work if you need it.
• winewayland: Enable server-side decorations by default (and fix some issues with it)
  • Most of the compositor bugs from the previous release still apply; tiling has been fixed on KWin though. Disable with WAYLANDDRV_SSD=0
• winewayland: Fix min/max size hints with fractional scaling (fixes winecfg under hyprland)
• winewayland: Fix some fullscreen->windowed transitions moving back to fullscreen.
• winewayland: Rework changing fullscreen output logic.
• Import upstream proton changes
• Update protonfixes

Known issues:

• HDR may not be detected with some displays
• FSR 4.1.0, FSR 4.0.3, FSR 4.0.2, FSR 4.0.1 have all been delisted by AMD on their symbol server, so downloads of those versions don't work at the moment.

Winewayland driver requirements:

Compositor behavior varies a lot; from my testing, KWin is the best in terms of features and compatibility. (Although it also has its own shortcomings, such as lack of commit-timing)
Nvidia 595+
Mesa 25.2+
Known issues with Nvidia:

• potentially increased input lag (compared to a pure x11 session, not xwayland)
  • We now have measurements: https://davidjusto.com/articles/m2p-latency/
  • Only XWayland is affected on Nvidia according to this person's numbers. edit: after an informal discussion with another person they said their measurements agree
  • According to older testing by a KWin developer (https://zamundaaa.github.io/wayland/2021/12/14/about-gaming-on-wayland.html) AMD GPU doesn't have any input lag difference (which makes sense since I don't really see why XWayland should affect latency in any way)
• 570 driver (and potentially lower) just freeze
  • Yes, it actually took Nvidia until May 2025 to get their driver working properly with wayland applications O_o

Notes:

Please report issues in the issues section of this GitHub repository (Make sure it is specific to these builds and is not present on upstream Proton). I am open to issues related to winewayland as I'm the one working on it. However, if it is related to winewayland ensure that you test on winex11 first to make sure it is NOT an issue there. Ensure you put the same information that you would put in a normal Proton compatibility report (e.g logs, OS information). With winewayland issues, please mention your compositor and its version.

Please Read:

Read the docs to see all (new) environment variable options with this build: https://github.com/Etaash-mathamsetty/Proton/blob/em-10/docs/EM-ADDITIONS.md

Detailed summary of changes to winewayland: https://github.com/Etaash-mathamsetty/Proton/blob/em-10/docs/CHANGES.md

Well, you don't have to read the second one if you don't want to :)