wine-tkg-git VS wine-staging

NTSync still seems to outperform any userspace fsync implementation https://github.com/Frogging-Family/wine-tkg-git/issues/936#i...

See: https://github.com/Frogging-Family/wine-tkg-git/issues/936

The exact version that I'm using: https://github.com/Frogging-Family/wine-tkg-git/actions/runs/4806748824

Clone the wine tkg git repo: git clone https://github.com/Frogging-Family/wine-tkg-git

Can't use native bcrypt.dll however Valve's proton uses a patched version. Wine-tkg uses Valve's version, might want to give it a try.

Now you can't just go from vanilla WINE to WINE Staging by installing stuff. You would have to patch the source code of WINE with all those patches: https://github.com/wine-staging/wine-staging/tree/master/patches and then compile it yourself.

Read this for more info: https://wiki.winehq.org/Wine-Staging

I've got the source from here and applied the patch as it says here

vkd3d-proton: - occasional upstream pending patches wine: - uses proton's bleeding edge wine base: https://github.com/ValveSoftware/wine/tree/experimental-wine-bleeding-edge-7.0-20190-20220716-pe79367-w7a9d8c-d5aa943-v5b7313 - adds wine-staging on top of it: https://github.com/wine-staging/wine-staging/tree/master/patches - adds FSR patches on top of it: https://github.com/GloriousEggroll/proton-ge-custom/blob/master/patches/proton/48-proton-fshack\_amd\_fsr.patch - adds a handful of other game fixes on top of it: https://github.com/GloriousEggroll/proton-ge-custom/blob/e01207aafe539d8d3ed49301665da717340e4c1d/patches/protonprep-valve-staging.sh#L295 - removes the proton-specific steamclient changes so that it works as a normal wine build: https://github.com/GloriousEggroll/proton-ge-custom/blob/master/patches/proton/0001-De-steamify-proton-s-WINE-so-it-can-be-used-as-a-sta.patch ffmpeg: - we enable some codecs not available in steam's ffmpeg gstreamer: - we enable some codecs not available in steam's gstreamer protonfixes: - these are python scripts that automate installing various winetricks and/or other per-game tweaks. this achieves the same thing most lutris installers perform. -------------------------

USE "HOMEBREW" https://brew.sh/ Or "MACPORTS" https://www.macports.org/ As subsystem or wrapper to help wine to be stable. I trying homebrew for a week right now with many versions of wine ( stable & bev , etc The fastest WINE wrapper updated is WINE STAGING. 🍷 https://github.com/wine-staging/wine-staging

Install Wine Staging and winetricks. Then create a new 64 bit prefix. You can run winetricks for this.

It's possible there's blockers for it not being updated, but you can also get a general idea as to how long updates on Fedora's end takes by comparing the dates on that site to the releases on Staging's GitHub.

These patches are missing: https://github.com/wine-staging/wine-staging/tree/master/patches/winepulse-PulseAudio_Support

FFXI should run fine on Steam Deck as it's reported as Gold in ProtonDB but, as I'm used to play the game on Windows, it can be fully enhanced/HD remastered with a lot of graphical and QOL community mods (Ref. here) which are all based on Windower - This is probably a core issue for the SD trying to run this third party/"dll injector". After having a chat with Windower support on Discord, I found out that the main issue is this commit in Wine. Now it would be great to know if this commit will be included in the Proton build used by the SD - Keeping it short: Proton is basically Valve's implementation of Wine. I'm definitely going to try this as soon as I have my hands on the SD as FFXI is still such a great/unique MMORPG and I would also suggest to check it out to everyone having a few friends to bring in.

Source: git mirror's contributor graphs located at wine-staging.