New stuff:
- Automatically download amdxcffx64 when FSR4 is enabled. This works around violating the EULA of the AMD driver if we were to ship this DLL directly.
- Switch to
PROTON_FSR4_UPGRADE=1to enable this behavior - The first launch with this option enabled downloads the DLL which takes time. The game will start once the download is complete. At this point, the games will be able to use FSR4 provided you have the correct drivers and env. Downloading step only occurs when you download a new build of Proton-EM as the DLL is stored alongside the other libraries contained within Proton-EM
- The proton log file will tell you if the download succeeded or failed, and the DLL can be manually downloaded if necessary. Please consult the documentation for steps of how to do the manual download.
- Enables FSR4 to work out of the box without having to move DLLs around once vkd3d-proton and RADV support VK_EXT_shader_float8.
- Switch to
- Implement EDID emulation for luminance data for winewayland
- Import initial implementations of atiadlxx and atidxx. Enables use of the native AMD AGS library for when AGS is statically linked in games. Some older Unreal Engine titles may do this. More work needs to be done to fix bugs and inaccuracies in the implementation (and implement support for HDR).
- Documentation on how to enable this feature will not be made available until the code is in a better state
Winewayland driver requirements:
Nvidia 575+
Any recent version of Mesa should be ok
Recommended patches for mesa: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/34918
These patches fix annoying games that (almost) violate the vulkan spec like the IdTech engine.
Winewayland HDR recommended configuration:
DE: Plasma 6.4 or Gnome 48
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