dxvk VS wine-staging

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​​.

Give DXVK a try https://github.com/doitsujin/dxvk/releases, use 32bit d3d9.dll

Vulkan is an alternative to DX which isn't MS-proprietary. I wouldn't be surprised if there was a Vulkan implementation for windows which uses DX under the hood, just as dxvk is a DX implementation that uses Vulkan under the hood.

I solved. I install all libraries manually. https://github.com/jp7677/dxvk-nvapi/releases/tag/v0.6 https://github.com/lutris/d3d_extras/releases/tag/v2 https://github.com/HansKristian-Work/vkd3d-proton/releases/tag/v2.9 https://github.com/doitsujin/dxvk/releases/tag/v2.2

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

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

You'll need the usual dependencies for Wine, so installing Wine or Wine-staging on your system is recommended even if only for that. Comes with support for AMD FSR through Proton's fullscreen hack - Enable with WINE_FULLSCREEN_FSR=1 env var, and tweak sharpening amount with WINE_FULLSCREEN_FSR_STRENGTH=5 (5 is default sharpening, lower numbers mean more sharpening, 0 is max sharpening) Comes with support for Nvidia DLSS for native Vulkan games (requires driver 470+), disabled by default - You can enable it with the PROTON_ENABLE_NVAPI=1 env var in your game's launch options - ValveSoftware/Proton@0503dde Comes with staging's mfplat implementation - https://github.com/wine-staging/wine-staging/commits/master Comes with the latest devel version of DXVK - https://github.com/doitsujin/dxvk/commits/master Comes with the latest devel version of HansKristian & Doitsujin's vkd3d-proton standalone - https://github.com/HansKristian-Work/vkd3d LAA is enabled by default. It fixes a huge amount of crashes on 32-bit games when using DXVK. However a small number of (older) games might run into issues with it, so you can disable LAA by using PROTON_DISABLE_LARGE_ADDRESS_AWARE=1 %command% in your game's launch options. Proton build has winetricks integration. It requires you to have the tk package (python3-tk on Debian based distros) installed and can be turned on/off in the ~/.steam/(root)/compatibilitytools.d/proton_tkg_6.16.r0.g931daeff.release/user_settings.py file.

Download the staging patches: git clone https://github.com/wine-staging/wine-staging --depth 1 (same deal as the first step: added "--depth 1" to only download the latest files from the source code)

This one could be a candidate for fixing this (but I have not tried what happens if I don't apply this to a recent wine version): https://github.com/wine-staging/wine-staging/blob/534f6ae34e89615fa424ee3e3002b1b3d419a8ba/patches/winebuild-pe_syscall_thunks/0002-winebuild-Call-__wine_syscall_dispatcher-through-the.patch

Alternatively, re-compile wine-staging and add this patch, which fixes the crash; and also this patch that fixes the locking cursor issue.

Hah, sorry, I misread your post and thought you said Roblox was crashing for you. To fix the mouse issue, like I said, you'll need to compile wine-staging from the very latest commit (otherwise it will crash), and also include the patch I mentioned.

You'll need the usual dependencies for Wine, so installing Wine or Wine-staging on your system is recommended even if only for that. Comes with support for AMD FSR through Proton's fullscreen hack - Enable with WINE_FULLSCREEN_FSR=1 env var, and tweak sharpening amount with WINE_FULLSCREEN_FSR_STRENGTH=5 (5 is default sharpening, lower numbers mean more sharpening, 0 is max sharpening) Comes with support for Nvidia DLSS (requires driver 470+), disabled by default - You can enable it with the PROTON_ENABLE_NVAPI=1 env var in your game's launch options - ValveSoftware/Proton@0503dde Comes with staging's mfplat implementation - https://github.com/wine-staging/wine-staging/commits/master Comes with the latest devel version of DXVK - https://github.com/doitsujin/dxvk/commits/master Comes with the latest devel version of HansKristian & Doitsujin's vkd3d-proton standalone - https://github.com/HansKristian-Work/vkd3d LAA is enabled by default. It fixes a huge amount of crashes on 32-bit games when using DXVK. However a small number of (older) games might run into issues with it, so you can disable LAA by using PROTON_DISABLE_LARGE_ADDRESS_AWARE=1 %command% in your game's launch options. Proton build has winetricks integration. It requires you to have the tk package (python3-tk on Debian based distros) installed and can be turned on/off in the ~/.steam/(root)/compatibilitytools.d/proton_tkg_6.14.r6.g1bc4da9d.release/user_settings.py file.

Who thought calling this "DOSBox Staging" as a good idea? Using that as the project name for a fork is (unintentionally?) confusing. Staging has a specific meaning with regard to software development, and additionally Wine Staging is a test branch for wine development. In both uses the "staging" software is implied to be part of the same project and maintainers, whereas this is a fork that's maintained by different developers with significant differences.