This is my build of Proton which the most recent release of vanilla wine, has ffmpeg enabled for faudio by default, and all of Proton's patches ported over to be applied to vanilla wine.
All patches:
-Warframe launcher loop patch
-DXVK Async patch applied and enabled specifically for warframe
-Mech Warrior online patch
-Resident Evil 4 patch
-World of Final Fantasy patch
-Skyrim SE/Fallout 4 script extender patch
-kde plasma systemtray fix patch
-FAudio with FFMpeg enabled (fixes audio/voices in multiple games)
-All of Valve's wine proton patches. Yes. All of them. I got quite a few of them from TKG, and parsed the remaining patches myself from their git commits.
Building Proton in a nutshell:
- Install virtualbox and its kernel modules, make sure they are enabled at boot
- Install vagrant
- Clone this repo:
git --recurse-submodules clone http://github.com/gloriouseggroll/proton-ge-custom - Initiate the submodules in the cloned repo:
cd proton-ge-custom
git submodule update --init
-
Drop any custom patches into game-patches-testing/, then open game-patches-testing/proton-prep.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 /game patches/testing by running:
./game-patches-testing/proton-prep.sh &> patchlog.txt
in the main proton-ge-custom directory. Open patchlog.txt and search "fail" to make sure no patch failures occured.
- in a terminal and type:
vagrant up (this will take a while on the first run, as it prepares everything)
vagrant ssh (this will ssh you into the vagrant VM
To leave the VM at any time just type exit
NOTE ON MODIFICATIONS:
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
- Edit the build name and build proton
cd ~/build
nano Makefile
Change the BUILD_NAME to whatever you want, then save & exit
- Build proton
cd ~/build
make all dist
- Rename the dist folder to your BUILD_NAME, then tar it for easier distribution:
mv dist Proton-Custom-Name
tar -cvzf Proton-Custom-Name.tar.gz Proton-Custom-Name/
- Move it to the /vagrant folder. This folder is accessible on your main system in the vagrant_share folder inside the cloned repository folder:
mv Proton-Custom-Name.tar.gz /vagrant/
- Shut down the VM:
exit
vagrant halt
- Now open vagrant_share inside the cloned repo folder on your main system. Extract the tarball into
~/.steam/root/compatibilitytools.d/, and restart steam. You will have to create the compatibilitytools.d folder.