This is my build of Proton with the most recent releases of vanilla WINE. It has FFmpeg enabled for FAudio by default, and all of Proton's patches ported over to be applied to WINE, as well as Wine-staging and VKD3D.
- FFXIV Launcher
- FFXV Steam
- Mech Warrior online
- Assetto Corsa HUD
- Sword Art Online gnutls
- ORIGIN downloads fix
- Monster Hunter World
- Mortal Kombat 11
- GTA V Keyboard input fix
- Steep fix
- AC Odyssey black bars fix
- Various WINE hotfixes for WINE functionality that fix regressions per version
- Various Proton hotfixes for Proton functionality that fix regressions per version
- Screen fixes for Nier: Automata, Sekiro, Dark Souls
- Path of Exile vulkan renderer fixed
- Mount and Blade Warband
- Divinity Original Sin 2
- Persona 4
- Sea of Thieves
- World of Warcraft DX12 compatibility
- Diablo 1 Menu fix
- COD: Blackops II launch fix (requires running from steam in wine --"winesteam", does not work in proton)
- All of Valve's WINE Proton patches
- Wine-staging patches
- Vulkan child window patch
- Protonfixes integration (has various scripts to run winetricks on games that need them)
- FAudio with FFmpeg enabled (fixes audio/voices in multiple games)
- Various WINE hotfixes for WINE functionality that fix regressions per version
- Various Proton hotfixes for Proton functionality that fix regressions per version
- DXVK is compiled with async for faster shader compiling. See environment variables section for more information pm usage.
- Spyro Reignited Trilogy
- Mortal Kombat 11
- Injustice 2
- Power Rangers: Battle for the Grid
- Darksiders: Warmastered Edition
- Borderlands 3
- Resident Evil 2 Remastered
- Resident Evil 3 Remastered
- Resident Evil 7
- PC Building Simulator
- Dangonronpa V3
- Super Lucky's Tale
- Remnant: From the Ashes
- BlazBlue Centralfiction
- Bloodstained: Ritual of the Night
- Crazy Machines 3
- Warframe does not need
WINEDLLOVERRIDES="xaudio2_7=n,b"— FAudio replaces xaudio2. Using this override WILL lead to game crashes - Warframe is problematic with VSync. Turn it off or on in game, do not set to
Auto - Warframe needs a set a frame limit in game. Unlimited framerate can cause slowdowns
- Warframe on Nvidia: you may need to disable GPU Particles in game otherwise the game can freeze randomly. On AMD they work fine
- Borderlands 3 Marcus game intro audio does not work correctly, can skip it. Rest of the game is playable and videos work
- Injustice 2 and MK11 are missing cutscene audio
Full patches can be viewed in protonprep.sh.
This section is for those that use the native version of Steam.
- Download a release from the Releases page.
- Create a
~/.steam/root/compatibilitytools.ddirectory if it does not exist. - Extract the release tarball into
~/.steam/root/compatibilitytools.d/. - Restart Steam.
- Enable proton-ge-custom.
This section is for those that use the Flatpak'd version of Steam.
- Download a release from the Releases page.
- Create a
~/.var/app/com.valvesoftware.Steam/data/Steam/compatibilitytools.d/directory if it does not exist. - Extract the release tarball into
~/.var/app/com.valvesoftware.Steam/data/Steam/compatibilitytools.d/. - Restart Steam.
- Enable proton-ge-custom.
- Install VirtualBox and its kernel modules. Make sure they are enabled at boot.
- Install Vagrant.
- Clone this repo by executing:
git clone --recurse-submodules http://github.com/gloriouseggroll/proton-ge-custom
-
Drop any custom patches into patches/, then open patches/protonprep.sh and add a patch line for them under #WINE CUSTOM PATCHES in the same way the others are done.
-
Apply all of the patches in patches/ by running:
./patches/protonprep-nofshack.sh &> patchlog.txt
in the main proton-ge-custom directory. Open patchlog.txt and search for "fail" to make sure no patch failures occured. An easy way to do this is like so:
grep -i fail patchlog.txt grep -i error patchlog.txt
- Open proton-ge-custom a terminal and type the following:
vagrant up (On the first run choose yes, it will ask you to run vagrant up again)
vagrant up (this will take a while on the first run, as it prepares everything)
build_name=some_custom_build_name make redist | tee buildlog.txt (this will start the build and log everything to buildlog.txt so that you can review the log if something fails)
vagrant halt (this will shut down the build afterwards)
For future builds you only need to run:
build_name=some_custom_build_name make redist
vagrant halt
Builds will be placed in proton-ge-custom/vagrant_share/ as both the full folder and a .tar.gz of the folder.
- Right click any game in Steam and click
Properties. - At the bottom of the
Generaltab, CheckForce the use of a specific Steam Play compatibility tool, then select the desired Proton version. - Launch the game.
vagrant syncs the Proton directory to any files in the cloned repo. So, if you want to make changes, close the VM with vagrant halt, make your changes, then launch vagrant again with vagrant up
Environment variable options:
| Compat config string | Environment Variable | Description |
|---|---|---|
| PROTON_LOG | Convenience method for dumping a useful debug log to $HOME/steam-$APPID.log. For more thorough logging, use user_settings.py. |
|
| PROTON_DUMP_DEBUG_COMMANDS | When running a game, Proton will write some useful debug scripts for that game into $PROTON_DEBUG_DIR/proton_$USER/. |
|
| PROTON_DEBUG_DIR | Root directory for the Proton debug scripts, /tmp by default. |
|
| wined3d | PROTON_USE_WINED3D | Use OpenGL-based wined3d instead of Vulkan-based DXVK for d3d11 and d3d10. This used to be called PROTON_USE_WINED3D11, which is now an alias for this same option. |
| vkd3d | PROTON_USE_VKD3D | Use vkd3d for DX12 games. NOTE: This will disable DXVK since it relies on dxgi.dll |
| noesync | PROTON_NO_ESYNC | Do not use eventfd-based in-process synchronization primitives. |
| nofsync | PROTON_NO_FSYNC | Do not use futex-based in-process synchronization primitives. (Automatically disabled on systems with no FUTEX_WAIT_MULTIPLE support.) |
| forcelgadd | PROTON_FORCE_LARGE_ADDRESS_AWARE | Force Wine to enable the LARGE_ADDRESS_AWARE flag for all executables. |
| noforcelgadd | Disable forcelgadd. If both this and forcelgadd are set, enabled wins. |
|
| oldglstr | PROTON_OLD_GL_STRING | Set some driver overrides to limit the length of the GL extension string, for old games that crash on very long extension strings. |
| vkd3dfl12 | Force the Direct3D 12 feature level to 12, regardless of driver support. | |
| WINE_FULLSCREEN_INTEGER_SCALING | Enable integer scaling mode, to give sharp pixels when upscaling. | |
| cmdlineappend: | Append the string after the colon as an argument to the game command. May be specified more than once. Escape commas and backslashes with a backslash. | |
| seccomp | PROTON_USE_SECCOMP | Enable seccomp-bpf filter to emulate native syscalls, required for some DRM protections to work. |
| async | DXVK_ASYNC | Allows Async to be used with DXVK. This can help with stutter in some games, however it is recommended not to be used with games that have sensitive anti-cheats. Use at your own risk. |
| nowritewatch | PROTON_NO_WRITE_WATCH | Disable support for memory write watches in ntdll. This is a very dangerous hack and should only be applied if you have verified that the game can operate without write watches. This improves performance for some very specific games (e.g. CoreRT-based games). |
As many of you may or may not already know, there is a Credits section in the README for this Git repository. My proton-ge project contains some of my personal tweaks to Proton, but a large amount of the patches, rebases and fixes come from numerous people's projects. While I tend to get credited for my builds, a lot of the work that goes into it are from other people as well. I'd like to take some time to point a few of these people out of recognition. In future builds, I plan to make clearer and more informative Git commits, as well as attempt to give these people further crediting, as my README may not be sufficient in doing so.
I and many others owe TKG. In regards to both WINE and Proton. He has dedicated a lot of time (2+ years at least) to rebasing WINE and Proton patches, as well as making his own contributions. Before he came along, I did some rebasing work, and mainly only released things for Arch. These days he almost always beats me to rebasing, and it saves myself and others a lot of work.
Regularly his rebases can be found in my patches list:
proton-fsync_staging.patchproton-fsync-spincounts.patchproton-FS_bypass_compositor.patchvalve_proton_fullscreen_hack-staging.patchproton-rawinput.patchproton-steamclient_swap.patchproton-protonify_staging_rpc.patchproton-protonify_staging.patchproton-steam-bits.patchproton-sdl_joy.patchproton-sdl_joy_2.patchproton-gamepad-additions.patchproton-vk-bits-4.5.patchproton-winevulkan.patch
Within these patches are Proton rebases. Many of them I've done on my own before he did them, however as he regularly rebases, many of my older patches have been replaced with his rebase patches. He deserves a huge amount of recognition for this.
Derek was responsible for the original rawinput patches, as well as several various game fixes in the past, just to name a few: MK11, FFXV, MHW, Steep, AC Odyssey FS fix. He has also done a massive amount of work on media foundation/mfplat, which should be hopefully working very soon.
Joshua is the creator of D9VK and also a huge contributor of DXVK. He is also known for his recent DOOM Eternal WINE fixes and also many of the Vulkan tweaks and fixes used, such as FS hack interger scaling.
Philip is the creator of DXVK and a heavy contributor of VKD3D. He also put up a lot of my bug reporting for Warfram years ago, when DXVK started.
Hans-Kristian is a heavy contributor of VKD3D and he also created a lot of WINE patches that allowed WoW to work.
Ethan is the creator of FAudio, and he also listened to my Warframe bug reports years ago.
Chris is the creator of the original Protonfixes project. The portions of Protonfixes I've imported are what allow customizations to be made to prefixes for various Proton games. without Proton fixes many games would still be broken and/or require manual prefix modification. Huge thanks to Chris.
Amine is the current maintainer of dxvk-async. This is a feature that was originally removed from dxvk as it happened around the same time a few overwatch bans happened. It was thought, but never confirmed whether or not this feature caused the bans, so the feature was removed as a safety precaution. It is still safe to use in many single player games, and games that do not have competitive anti-cheats. It has also been confirmed to work safely in Warframe and Path of Exile.
I also of course need to thank my fellow wine-staging maintainers: Alistair Leslie-Highes, Zebediah Figura and Paul Gofman
They have contributed MANY patches to staging, far beyond what I have done, as well as kept up with regular rebasing. A lot of times when bug reports come to me, if it has to do with staging I end up testing and relaying information to these guys in order to get issues resolved.
Additionally, a thank you is owed to Andrew Aeikum (aeikum), and kisak (kisak-valve) for regularly keeping me in the loop with Proton and fsync patches, as well as accepting PRs I've made to fix Proton build system issues, or listening to bug reports on early Proton patches before they reach Proton release.
And finally - To all of my patrons that have supported me, thank you so much. It's because of you that I've been able to keep this project going, getting bug fixes reported, getting Proton/WINE issues fixed, getting various hardware and/or game fixes handled, and so on. Thanks to you, I have been able to use the spare budget in order to both help support the other people that make my project possible, as well as get things necessary for testing such as new game releases or specific hardware that hits odd issues. It's had a huge effect not just for this project, but a large trickle down effect.
My wine-staging co-maintainers are often able to ask me for testing games, or testing on different hardware if they don't have access to it. This also trickles into both Proton bug reporting AND Lutris bug reporting, as I'm able to provide bug testing and feedback and custom builds and upgrades to them as well. I'm also able to test driver related issues for things such as mesa and getting things reported + patched. This in turn leads to early patches for Mesa, the kernel, VKD3D, and other packages on my copr repos as well. The trickle down effect is just one gigantic awesome rabbit hole for getting things fixed. Thank you once again.
For anyone else interested, my Patreon can be found here: