Etaash-mathamsetty/Proton EM-10.0-27

Proton-EM 10.0-27

on GitHub

New stuff:

• Enabled NTSync by default
  • Use PROTON_NO_NTSYNC=1 to switch back to Fsync
  • It has better compatibility than both Fsync and Esync, so it is worth the potentially slightly reduced performance.
  • Also, make sure your scheduler doesn't do any goofy stuff with futex objects such as prioritizing processes that hold futex objects, since NTSync obviously doesn't hold any futexes...
• Implement org.kde.StatusNotifierItem system tray support (original MR: https://gitlab.winehq.org/wine/wine/-/merge_requests/2808)
  • Context menus are placed incorrectly, but unfortunately it's impossible to fix even for x11
  • xembed (the original system tray solution) doesn't really work that well either, so I'll just leave it like this for now until I find a way to enable/disable it without causing weird bugs
• Fix PROTON_FSR4_UPGRADE=1 env
• Add support for \\KnownDlls\\ntdll.dll section
  • If you know, you know...
    • (If you know how to debug the rest lmk)
• Import upstream proton changes
  • Fixes DLSS frame generation with Doom The Dark Ages

News:
If everything goes well, Anti-Lag 2 will be supported out of the box on D3D12 applications in Proton Experimental (bleeding-edge) in the coming week. 🎉

Winewayland driver requirements:
Nvidia 575+
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). Unlike Proton-GE 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