Changing the WINE base moving forward
Added 2022-02-27 02:54:20 +0000 UTCHi Guys,
As many of you know I started this project almost immediately after proton was released -- almost 4 years ago now. When the project began, wine-staging was still bringing in a large amount of fixes for games that proton did not have, however the tides have changed quite a bit since then.
These days, there are a -massive- amount of changes to proton's base code, and most games run on proton just fine. In fact many run on proton first before fixes for those games are then ported to WINE or staging.
With the addition of both EAC and BattleEye support, my biggest concern here is keeping compatibility with those. Not to mention fullscreen hack and mfplat/media foundation, the addition of gamescope, the LFH and QPC, and fsync performance patches from proton, and now also compatibility with the Steam Deck hardware.
Additionally, as you guys know with each WINE version, comes both fixes and regressions. I would like to start keeping those regressions to a minimum. So the idea I have moving forward is to use Valve's WINE build as a base, and forego using staging, then just pull patches needed from staging or upstream as they are discovered to be needed for various games/applications.
We would still retain our protonfixes and mfplat patches and additional game patches. We would also still retain the latest versions of dxvk + vkd3d and any patches needed for them. Also it would be much easier to take Valve's WINE and just remove the steam-specific patches for wine-ge than vice-versa at this point considering the massive amount of patches. In addition to this, it makes more sense in terms of working with Valve to get fixes upstreamed, as our code base would be directly based on theirs and therefore easier to backport.
Thank you all for your amazing support, I really appreciate everyone. I felt the need to post my thoughts here in case anyone is partial to wine-staging and/or sticking to the most recent wine release every time they come out.
TLDR: I'm (most likely) dropping staging and using Valve's WINE for Proton-GE's base, and will pull patches from staging as they become needed.
Comments
I'm definitely partial to staging -- I'm part of the staging team. The problem is at this point it's more efficient to use proton's wine base and just add patches from staging than the other way around. It used to not be that way but 4 years worth of patching will do that >.<
Glorious Eggroll
2022-02-27 15:57:23 +0000 UTCI'm definitely partial to wine-staging, but to be pragmatic I say you should go with whichever path is most efficient and reliable for your workflow. Work smarter, not harder. The staging guys do amazing work, as do you. You have my gratitude and support regardless. Cheers!
dpanter
2022-02-27 10:41:47 +0000 UTC
