Releases: BananaWorks07/Proton
Release list
Proton-EM 10.0-37 HDR
This is this project's first anniversary (or roughly around that time). Originally called Proton-FSR4, it aimed to bring FSR4 to Linux in a user-accessible way by extending some of my prior reverse engineering of the AMD D3D12 extensions library.
That project gave me an idea: what if I try to make my own Proton builds, but I also develop other parts of the Wine that powers them? Today, we stand on a mountain of work, from my ntoskrnl work to make some AntiCheatExpert games work under Linux, the DLL that loads FSR4 into your games, to my winewayland work, to porting NTSync to Proton. This project is the most impactful one I've ever built, to the point where if you don't use my work from its source, you are familiar with it (see: Proton-GE, Proton-CachyOS, and DW-Proton).
However, to me its impact is more defined by what I learned and the problem-solving skills that I developed. The challenges the Wayland driver presented me were among the most difficult problems I have ever encountered, and solving them for the first time brings a sense of satisfaction that I cannot describe.
Thank you all for your support; this project wouldn't exist without it.
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. For visibility reasons, these versions are no longer marked as pre-release. (These versions also work for people without HDR monitors, if that wasn't clear before)
Now you can go into your games and turn that HDR on with no launch options (other than PROTON_ENABLE_WAYLAND=1)
If you are on Nvidia:
You MUST use the Nvidia 595 driver (or higher) when using this proton from now on.
New Stuff (from last HDRTEST):
- winewayland: Respect size hints when moving from maximized and tiled window states to normal state.
- winewayland: Implement window focus loss, minimization, and even un-minimization.
- This may have bugs, so please report them :)
- winewayland: Check for set_minimized support and disable focus loss implementation when this feature is not present.
- win32u: Implement VkSurface caching to avoid flickering in Doom Eternal and some other broken games.
- winewayland: Cache previously released vulkan client surface. This avoids flickering in the other case where broken vulkan apps create a new surface and swapchain on each swapchain recreation but also don't leak the old surface. Examples of this are Wolfenstein: Youngblood. (an improvement over Doom Eternal, I guess)
- Import upstream proton changes
- Update protonfixes
Known issues:
- If HDR is not detected: go to your HDR calibration and change the paper white luminance to be something less than the max luminance
- As of writing: Nvidia 595 drivers don't sanitize the HDR metadata passed through the
VK_EXT_hdr_metadataextension, so games like Death Stranding 2 crash with HDR enabled on Nvidia. This can be worked around in DXVK & also DXVK-NVAPI, but Nvidia should just follow Mesa's precedent and sanitize wrong values.- Amend (5/1/26): You should see something like
[destroyed object]: error 5: min_lum can't be higher or equal to max_lumin the logs if this happens. Please tell Nvidia to fix it; it's like maybe 2 lines of code they need to change.
- Amend (5/1/26): You should see something like
- Nvidia Reflex doesn't work on native Wayland applications; this is a known Nvidia driver bug.
- 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 :)
Proton-EM 10.0-36 HDR TEST
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. For visibility reasons, these versions are no longer marked as pre-release. (These versions also work for people without HDR monitors, if that wasn't clear before)
Now you can go into your games and turn that HDR on with no launch options (other than PROTON_ENABLE_WAYLAND=1)
If you are on Nvidia:
You MUST use the Nvidia 595 driver (or higher) when using this proton from now on.
New Stuff (changes from last HDRTEST):
- winewayland: Check if ST2084/extended sRGB color spaces are supported by the compositor before advertising HDR
- This will likely cause HDR to not be supported under GNOME, which is correct behavior.
- winewayland: Reduce stack usage of NtUserMapVirtualKeyEx.
- winewayland: Refactor wayland output handling.
- Specifically, the changes introduced by me
- Import upstream proton changes
- I've heard yall need a vkd3d-proton update to play Crimson Desert
- proton: Add a workaround for #89
- Update protonfixes
Known issues:
- If HDR is not detected: go to your HDR calibration and change the paper white luminance to be something less than the max luminance
- 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 :)
Proton-EM 10.0-35 HDR TEST
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=1should still work if you need it.
- dxvk: Add the opposite of the above:
- 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
- Most of the compositor bugs from the previous release still apply; tiling has been fixed on KWin though. Disable with
- 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:
- If HDR is not detected: go to your HDR calibration and change the paper white luminance to be something less than the max luminance
- 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 :)
Proton-EM 10.0-34
Proton-EM enters the new year! (Sorry for taking so long)
Most likely this will be the (second) last release before Proton 11 rebase.
There will be another HDR testing version (soon) that won't need any environment variables to activate HDR in games (other than PROTON_ENABLE_WAYLAND) of course.
New Stuff:
- proton: Drop automatic HDR WSI for Nvidia. (Nvidia 595 released!)
- winewayland: Import upstream window layering
- winewayland: Fix Vk->char conversion truncating to 1 byte
- winewayland: Fix right shift virtual key
- winewayland: Fix freezing issues when querying the window icon.
- winewayland: Add a hack to fix modifier key release with alt and meta keys
- winewayland: Send both normal and raw relative mouse inputs to win32u
- winewayland: Fix instances where wglSwapBuffers would freeze with windows that haven't turned visible yet.
- winewayland: Implement server-side decorations
- These should be mostly stable; the only issue I have seen is windows getting stuck in split-screen mode, for example. You can just resize the window instead of trying to move it out of the tiled modes.
- Unfortunately, the feature cannot be enabled by default due to compositor bugs. Popup menus are cut off on KWin. The test application I was using (winecfg) managed to completely break Hyprland, so I couldn't do any testing there. On Cosmic, the menus are cut off with CSD and SSD both 😆
- If you want to use it, set
WAYLANDDRV_SSD=1
- winewayland: Fix crashes with rectangular window icons (https://gitlab.winehq.org/wine/wine/-/merge_requests/10002)
- winewayland: Enable IME support and import fix for the key repeat issue (https://gitlab.winehq.org/wine/wine/-/merge_requests/10007)
- ntdll: Import Genshin Impact freezing on exit fix: (https://gitlab.winehq.org/wine/wine/-/merge_requests/9890)
- ntdll: An attempt to fix https://bugs.winehq.org/show_bug.cgi?id=59333
- Import upstream proton changes
- FSR4 Redstone is now fully supported. Denoiser (Doesn't work on RDNA3 yet), Upscaling, MLFG, NRC :D
Winewayland driver requirements:
Compositor behavior varies a lot; from my testing, KWin is the best in terms of features and compatibility.
Nvidia 580+
Mesa 25+ (only because DXVK requires this)
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
Winewayland HDR recommended configuration:
DE: Plasma 6.6+, works most of the time: Plasma 6.5, Gnome 48+
Drivers: Mesa 25.2 or greater, Nvidia 595+
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 :)
Proton-EM 10.0-33
Small maintenance release as the stuff I want to work on next is rather tricky :)
Funny joke old me; this is probably the largest release in a while. Hopefully no more major issues with the keyboard code. :)
New stuff:
- winewayland: Implement support for numlock, capslock modifiers
- winewayland: Implement support for extended virtual key codes
- winewayland: Fix Vk->char conversion when dead keys are present
- winewayland: Pause pointer position updates when a warp is pending
- Fixes mouse cursor escaping in CoD Black Ops 1, S&Box if the mouse is moved quickly
- win32u: implement cross thread keyboard layout query
- proton: Add a way to disable wine wayland workarounds
- Set
WINE_WAYLAND_HACKS=0, may fix critical section timeouts in EA App for instance when launching through link2ea protocol
- Set
- winewayland: Detect HDR support and report it through DisplayConfigGetDeviceInfo
- Preparation for eventually getting rid of
PROTON_ENABLE_HDR. However, the NVIDIA driver exists and is preventing me from releasing a Proton version with this feature... Surely the 600 driver series will finally support HDR... - Based on an upstream wine patch (https://gitlab.winehq.org/wine/wine/-/merge_requests/9556)
- Preparation for eventually getting rid of
- winewayland: Rework fractional scale redraw
- winewayland: Create fractional scale/content type objects during role assignment
- atidxx: Fix the vtable layout to add missing virtual destructor
- amdxc: Implement support for FSR4 MLFG upgrade
- proton: implement support for
UMU_USE_STEAM=1 - proton: handle FSR4 upgrade through protonfixes
- proton: Automatically set
ENABLE_HDR_WSI=1if the NVIDIA driver is detected andPROTON_ENABLE_HDR=1is set. - Import upstream splay tree implementation
- Import upstream proton changes
Winewayland driver requirements:
Nvidia 575+ (580+ recommended due to fifo-v1 protocol)
Known issues with Nvidia:
- Potentially increased input lag (compared to a pure x11 session, not xwayland)
- 570 driver (and potentially lower) just freeze
Any recent version of Mesa should be ok
Winewayland HDR recommended configuration:
DE: Plasma 6.5, Gnome 48+, Hyprland 0.49+
Drivers: Mesa 25.1 or greater
Nvidia Driver still requires the HDR WSI layer (novideo moment)
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.
I will try my best to respond to issues, but of course I may not respond if I'm busy
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
Proton-EM 10.0-32
New stuff:
- winewayland: Fix virtual key mappings
- ntdll: Ignore
DOTNET_ROOT,DOTNET_BUNDLE_EXTRACT_BASE_DIRenvs- Fedora still hasn't fixed their dotnet packages...
- Import upstream wine Zw exports
- Fixes Zenless Zone Zero CPU performance
- Import upstream wine syscall numbering.
- Import more upstream unix env fixes
- Import upstream proton changes
Winewayland driver requirements:
Nvidia 575+ (580 recommended due to fifo-v1 protocol)
Known issues with Nvidia:
- Potentially increased input lag (compared to a pure x11 session, not xwayland)
- 570 driver (and potentially lower) just freeze
Any recent version of Mesa should be ok
Winewayland HDR recommended configuration:
DE: Plasma 6.5, Gnome 48, Hyprland 0.49
Drivers: Mesa 25.1 or greater
Nvidia Driver still requires the HDR WSI layer (novideo moment)
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.
I will try my best to respond to issues, but of course I may not respond if I'm busy
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
Proton-EM 10.0-31
New stuff:
- winewayland: Fix DPI scaling support
- Setting 192 DPI (or whatever you want) in winecfg is now supported on winewayland
- winewayland: Fix xkb locale files
- winewayland: Implement support for
wp-pointer-warp-v1- This protocol helps to guarantee pointer warps will be honored
- winewayland: Implement support for
ext-data-control-v1.- KWin 6.5 drops support for the wlr version, which this protocol seems to supersede anyway
- winewayland: Drop cursor shape workaround for KWin 6.4 and lower.
- The lowest supported KWin version is now 6.5.2
- winepulse/mmdevapi: Fix some issues with containerid implementation
- Superseded by upstream proton code, contributed that fix into the upstream version.
- Add sched quantum hack to ntsync (works around Ubisoft Connect updater not working)
- Import upstream ntsync fixes
- Import upstream unix env fixes
- Import upstream proton changes
edit: Reuploaded 10.0-31 with fixed locale files
Winewayland driver requirements:
Nvidia 575+ (580 recommended due to fifo-v1 protocol)
Known issues with Nvidia:
- Potentially increased input lag (compared to a pure x11 session, not xwayland)
- 570 driver (and potentially lower) just freeze
Any recent version of Mesa should be ok
Winewayland HDR recommended configuration:
DE: Plasma 6.5, Gnome 48, Hyprland 0.49
Drivers: Mesa 25.1 or greater
Nvidia Driver still requires the HDR WSI layer (novideo moment)
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.
I will try my best to respond to issues, but of course I may not respond if I'm busy
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
Proton-EM 10.0-30
New stuff:
The long awaited keyboard update!
- winewayland: Implement dead keys (Thanks Rémi Bernon for the original code)
- Only one dead key is supported right now; typing in a letter that requires two dead keys in succession is not supported yet
- For example you cannot type
ä́yet
- winewayland: Fix French AZERTY keyboard layout
- winewayland: Fix Dvorak keyboard layouts
- winewayland: Fix ntdll loader section timeouts
- Import upstream changes
Winewayland driver requirements:
Nvidia 575+ (580 recommended due to fifo-v1 protocol)
Known issues with Nvidia:
- Potentially increased input lag (compared to a pure x11 session, not xwayland)
- 570 driver (and potentially lower) just freeze
Any recent version of Mesa should be ok
Winewayland HDR recommended configuration:
DE: Plasma 6.4, Gnome 48, Hyprland 0.49
Drivers: Mesa 25.1 or greater
Nvidia Driver still requires the HDR WSI layer (novideo moment)
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.
I will try my best to respond to issues, but of course I may not respond if I'm busy
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
Proton-EM 10.0-2F
New stuff:
Small maintenance release since it's been a while.
- Add support for the FSR4 watermark. Enable with
FSR4_WATERMARK=1 - Tweaked winewayland move hack
- Minor bug fixes & fetch upstream changes
Release was updated to remove duplicate wine-mono.
Winewayland driver requirements:
Nvidia 575+ (580 recommended due to fifo-v1 protocol)
Known issues with Nvidia:
- Potentially increased input lag (compared to a pure x11 session, not xwayland)
- 570 driver (and potentially lower) just freeze
Any recent version of Mesa should be ok
Winewayland HDR recommended configuration:
DE: Plasma 6.4, Gnome 48, Hyprland 0.49
Drivers: Mesa 25.1 or greater
Nvidia Driver still requires the HDR WSI layer (novideo moment)
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.
I will try my best to respond to issues, but of course I may not respond if I'm busy
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
Proton-EM 10.0-2E
New stuff:
- winewayland: Add workaround for KWin cursor-shape-v1 (version 2) non-conformance
- winewayland: Add
--in-process-gpufor idtech launcher - Minor bug fixes & fetch upstream changes
Winewayland driver requirements:
Nvidia 575+ (580 recommended due to fifo-v1 protocol)
Known issues with Nvidia:
- Potentially increased input lag (compared to a pure x11 session, not xwayland)
- 570 driver (and potentially lower) just freeze
Any recent version of Mesa should be ok
Winewayland HDR recommended configuration:
DE: Plasma 6.4, Gnome 48, Hyprland 0.49
Drivers: Mesa 25.1 or greater
Nvidia Driver still requires the HDR WSI layer (novideo moment)
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.
I will try my best to respond to issues, but of course I may not respond if I'm busy
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