Releases: GloriousEggroll/proton-ge-custom
Proton-4.10-GE-1
Changes:
-updated to wine 4.10 with improved clock_monotonic patches
-imported changes from proton 4.2.4 through 4.2.7
-backported gamepad changes from 4.10+ and proton 4.2 to 4.10
-integrated d9vk
-added nod3d9 option to proton to allow disabling of d3d9 override for d9vk
-dxvk updated to 1.2.2 with async patch enabled for PoE and Warframe
-faudio updated to 19.06.07 - fixes performance regressions in several games
-re-added missing registry entries for LAA on bayonetta, and ags for wolfenstein 2
Instructions:
Open ~/.steam/root/
Create compatibilitytools.d folder
Extract archive to ~/.steam/root/compatibilitytools.d/.
Close and re-open steam
Right click the game and click Properties
At the bottom of the General tab, Check "Force the use of a specific Steam Play compatibility tool
Then select Proton-4.10-GE-1 from the drop down and click CLOSE.
Known Issues:
--For warframe you still need a controller plugged in, or xboxdrv installed and enabled and detected by steam.
For instructions on setting up xboxdrv, see:
Step 7 here:
https://gitlab.com/GloriousEggroll/warframe-linux/wikis/Ubuntu-Install-Instructions
Or Step 6. here:
https://gitlab.com/GloriousEggroll/warframe-linux/wikis/Arch-Install-Instructions
Proton-4.6-GE-2
Proton-4.6-GE-2
Changes:
-fixed issue with incomplete proton winevulkan patch set
-warframe f6 screenshot button fixed
-wine-staging keyboard input language translation patches added
-cleaned up several duplicate proton patches
-imported changes from proton 4.2.3b
-imported proton 4.2.3b wine mono patches
-imported proton 4.2.3b winecodecs patches
-dxvk updated to 1.0.3 with async patch
-faudio updated to latest git
Instructions:
Open ~/.steam/root/
Create compatibilitytools.d folder
Extract archive to ~/.steam/root/compatibilitytools.d/.
Close and re-open steam
Right click the game and click Properties
At the bottom of the General tab, Check "Force the use of a specific Steam Play compatibility tool
Then select Proton-4.6-GE-2 from the drop down and click CLOSE.
Known Issues:
--For warframe you still need a controller plugged in, or xboxdrv installed and enabled and detected by steam.
For instructions on setting up xboxdrv, see:
Step 7 here:
https://gitlab.com/GloriousEggroll/warframe-linux/wikis/Ubuntu-Install-Instructions
Or Step 6. here:
https://gitlab.com/GloriousEggroll/warframe-linux/wikis/Arch-Install-Instructions
Proton-4.6-GE-1
Proton-4.6-GE-1
Changes:
-DXVK updated to latest git
-FAudio updated to latest git
-Wine 4.6 Now has fixed Warframe Launcher finally
Instructions:
- Open ~/.steam/root/
- Create compatibilitytools.d folder
- Extract archive to ~/.steam/root/compatibilitytools.d/.
- Close and re-open steam
- Right click the game and click Properties
- At the bottom of the General tab, Check "Force the use of a specific Steam Play compatibility tool
- Then select Proton-4.6-GE-1 from the drop down and click CLOSE.
Known Issues:
--For warframe you still need a controller plugged in, or xboxdrv installed and enabled and detected by steam.
For instructions on setting up xboxdrv, see:
Step 7 here:
https://gitlab.com/GloriousEggroll/warframe-linux/wikis/Ubuntu-Install-Instructions
Or Step 6. here:
https://gitlab.com/GloriousEggroll/warframe-linux/wikis/Arch-Install-Instructions
Proton-4.5-GE-Beta-4
Proton-4.5-GE-Beta-4
Changes:
-DXVK updated to latest git
-FAudio updated to latest git
-Proton vulkan patches added.
-Proton pulseaudio patches added.
Instructions:
Extract it to ~/.steam/root/compatibilitytools.d/. You may need to create the compatibilitytools.d folder inside the main steam folder. Then set warframe to force use Proton-4.5-GE-Beta-4
Known Issues:
--For warframe you still need a controller plugged in, or xboxdrv installed and enabled and detected by steam
Proton-GE-4.5-Beta-3
Proton-4.5-GE-Beta-3
Changes:
-DXVK updated to latest git
-FAudio updated to latest git
-Proton 4.2-2 changes merged.
-NVAPI disabled for Warframe in dxvk
-Grim Dawn anti-flicker patch re-enabled and fixed so it doesn't crash at CRATE logo on AMD
Instructions:
Extract it to ~/.steam/root/compatibilitytools.d/. You may need to create the compatibilitytools.d folder inside the main steam folder. Then set warframe to force use Proton-4.5-GE-Beta-3
Known Issues:
--For warframe you still need a controller plugged in, or xboxdrv installed and enabled and detected by steam
Proton-GE-4.5-Beta-2
Proton-4.5-GE-Beta-2
Changes:
-DXVK updated to latest git
-FAudio updated to latest git
-Bayonetta grey film cutscenes fixed
Instructions:
Extract it to ~/.steam/root/compatibilitytools.d/. You may need to create the compatibilitytools.d folder inside the main steam folder. Then set warframe to force use Proton-4.5-GE-Beta-2
Known Issues:
--For warframe you still need a controller plugged in, or xboxdrv installed and enabled and detected by steam
Proton-GE-4.5-Beta-1
Proton-4.5-GE-Beta-1
Changes:
I spent most of the weekend parsing out 90% of the commits from valve's proton in order to make patches that work for this. Major changes include:
-Large Address Awareness patch for Bayonetta/Vanquish
-Fullscreen Hack (not implemented for vulkan yet)
-esync patches updated for 4.5
-kde plasma system tray patch
-proton SDL joystick patch
-uplay steam installpath patch (uplay should work now)
-unity engine games mouse drift patch
-amd ags patches
-fullscreen hack GDI patches
-proton windowscodec patches
-proton wined3d+d3d11 patches
-grim dawn and dark souls anti-flicker patch for dxvk + auto enabled for those games
-Path of Exile added to auto-enabled async list for dxvk
-Warframe Launcher loop patch
-Warframe async auto-enabled
-DXVK updated to 1.0.1
Instructions:
Extract it to ~/.steam/root/compatibilitytools.d/. You may need to create the compatibilitytools.d folder inside the main steam folder. Then set warframe to force use Proton-4.5-GE-Beta-1
Known Issues:
--For warframe you still need a controller plugged in, or xboxdrv installed and enabled and detected by steam
--Grey film cutscenes in bayonetta - wine changed some things in d3d from 4.2 to 4.5 so I still have to slog through and see what commit broke them