wine-staging VS Proton

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.

The "Metaverse" is a complete joke, and among gamers, Valve has a way better reputation than Meta. Why would they want to dilute that brand?

They already have their own platform (Steam), OS (SteamOS), VR headset (Index), their own Windows translation layer (Proton, https://github.com/ValveSoftware/Proton), their own partnership with cloud gaming (Steam Cloud Play using GeForce Now , https://partner.steamgames.com/doc/features/cloudgaming), etc.

IMO: As someone with thousands of games on Steam, there's no way in hell I'd want that linked to Facebook. I think they eventually removed the requirement to have a FB account to use a Quest, but they still require a Meta account. Yuck.

This reeks of Facebook recognizing the Metaverse as the failure that it was and opening it up because it's no longer relevant...

Or Valve's Proton[0], a tool for playing Windows games on Linux.

https://github.com/ValveSoftware/Proton

Did you mount it with the correct flags?

there is a hack to try and use your existing windows game install from an NTFS drive, but i don't recommend it as steam will try to save file names that are not allowed on NTFS...plus ext4 is faster.

From a quick search, here's what I found. It looks like you're encountering some common issues that can occur with games running on Linux through Proton, especially with the recent updates to games like Satisfactory that might affect compatibility. The log entries you're seeing related to D3DCompile2 failing to compile shader and the issues with Ternary operator and LinearToSrgbBranching not being defined, suggest that there's a problem with shader compilation. This can often be related to the version of Proton or the graphics drivers you are using. Some users have reported that the game does launch with the -vulkan option but with graphical glitches and lower performance, which indicates that the Vulkan renderer is working but possibly not optimally on your setup. From the discussions in the community, users have suggested ensuring that the latest drivers for your graphics card are installed and, if using an Intel GPU, that the Mesa drivers are up to date since Intel XeSS references were found in the logs. If you're using NVIDIA graphics, make sure you have the latest drivers and possibly set the PROTON_ENABLE_NVAPI=1 %command% to enable DLSS if you're under Vulkan. If you're using an Optimus laptop with both Intel and NVIDIA GPUs, make sure your Optimus setup is correctly configured. Some users have found success by specifying DXVK_FILTER_DEVICE_NAMES=GeForce to force the game to use the NVIDIA GPU. It's also worth noting that if you're encountering issues with DirectX 11, you might want to try forcing the game to use DirectX 10 if possible or look into DXVK configurations that could resolve compatibility issues. Lastly, if none of these solutions work, you could try running a trace with apitrace to gather more detailed logs that might point to the specific issue. If you're still stuck, it would be a good idea to report the issue to the Proton GitHub page or seek further assistance in the game's community forums where others might have encountered and solved similar issues. For more information and to find others who might have resolved similar issues, check out the community discussions on GitHub​​, Steam Community​​, and the DXVK GitHub page​​.