While upstream wine does support OS X 10.8 and later the provided packages target macOS High Sierra and later.

While I've provided DXVK-async packages there are not recommended, upstream DXVK had removed this feature after reports of possible bans related to anti-cheat systems. DXVK-macOSĭXVK-macOS provides custom DXVK packages with macOS in mind, those packages don't require a modified version of MoltenVK. CodeWeavers patched MoltenVK to fake unsupported extensions along with a custom version of DXVK that was modified specifically for macOS. Upstream DXVK won't work on macOS as additional modifications are required.ĬrossOver-20 and later include DXVK support, this provides 64Bit DirectX 10 and DirectX 11 support.

MoltenVK supports Vulkan 1.1 core features so that's enought to to run some 64Bit (Apples Metal API is 64Bit) DirectX 10 & DirectX 11 games. This usually happens when the game uses DirectX10 or above, the version of OpenGL included on macOS hasn't been updated in years so it's missing some needed extensions. Now you will also have access to winetricks command within Terminal Why doesn't my game work on mac but Winehq says it does? Here is an example of using both commands to create a 32Bit only WINEPREFIX The default architecture of a WINEPREFIX will be 64Bit meaning 32Bit and 64Bit applications & games are supported but that's not always ideal for several reasons.Ī new WINEPREFIX can be created and also setting WINEARCH You can override this by using the WINEPREFIX command The default WINEPREFIX will be ~/.wine so anything you install will be placed into the hidden ~/.wine folder. The above is the Winehq way to install wine on mac but that makes it cumbersome to use considering you must launch the Wine Stable, Wine Devel or Wine Staging app each time to get access to wine within Terminal Wine basics If your intention is to have a more stable environment use wine-stableĬurrenty macOS packages are not uploaded to Winehq, those can be downloaded from here Grab a wine package usually using the latest wine-devel is recommended, but most agree it's best to use the latest wine-staging due to additional patches. How to manually install wine on mac using Winehq releases The -no-quarantine command is required as homebrew by default adds the quarantine flag to downloaded casks, this causes Gatekeeper to treat the bundle as damaged. Only a single wine package can be installed using brew

The above command will install the most recent wine-staging pkg available on winehq but it will also add wine for use in Terminal meaning you no longer need to launch the installed Wine Staging app each time you want to access wine. Brew install -cask -no-quarantine wine-staging

Wine 10.15