homebrew-wine VS dxvk

You will need to install homebrew. ARM users will also need Rosetta (I think), but homebrew should be the native version. Next we need wine that can run 32 bit binaries: brew install --cask --no-quarantine gcenx/wine/wine-crossover.

The standard Wine package also stopped working with the Catalina update. To get around this, we'll use a specific version of Wine, developed by Gcenx, made for MacOS 10.15+. To install it, you first need to install Homebrew. To do this, open the application Terminal (the easiest way to do this is hit Cmd + Space, then type "Terminal", then hit return), type in the following command, and hit return:

For Wine version that works for me is Wine-Crossover version provided here https://github.com/Gcenx/wine-on-mac#macos-catalina-and-later.

Crossover from Codeweavers (which is a version of WINE) runs 32-bit applications on post-Mojave MacOS with a 32->64-bit conversion layer and one of the free/open-source versions of WINE based on the code donated by Codeweavers (located here: https://github.com/Gcenx/homebrew-wine) does the same thing.

Currently using: ==> wine-crossover: 22.0.1 https://github.com/Gcenx/homebrew-wine/

Try `gcenx` distribution of wine with crossover patches (https://github.com/Gcenx/homebrew-wine).

Ah, sorry, I assumed from you mentioning installing Wine that you had Homebrew already. Yeah, you need to install Homebrew, there's a command to copy on its website. Once that's done, you need to run the command on the page I linked above to install the fixed version of Wine. After that completes, you should be able to just run the exe (it may prompt you for permission to access a folder or two first), or if not it'll probably ask you to pick which app to use if you try (in which case you can just select Wine Crossover from the list it presents).

Someone is trying to game on them, or at least run DirectX apps in Linux, based on this PR: https://github.com/doitsujin/dxvk/pull/3795

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

Kid named DXVK :

DXVK versions after 2.0 require Vulkan 1.3 support, which may not be available on your GPU. Try using an older build, such as this one.

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

What to download:https://github.com/doitsujin/dxvk/releases/tag/v2.3