DirectX games on a Mac: DXMT, D3DMetal and DXVK explained

Why Macs need a translator

A Windows game asks Direct3D (the graphics part of DirectX) to draw each frame. macOS has no Direct3D. Its modern graphics API is Metal; OpenGL is deprecated and stuck at version 4.1, and there's no native Vulkan. So Wine-based apps swap Windows' Direct3D DLLs for a translator that turns each Direct3D call into Metal work.

That translator decides more about whether a game runs, and how fast, than anything else in the stack. Wine handles the rest of Windows; Rosetta 2 handles the Intel CPU code. See the full guide to Windows games on a Mac for how the pieces fit.

The layers, side by side

Wine-based apps bundle different mixes. CrossOver 26 ships D3DMetal 3.0 and DXMT; Sikarugir defaults to DXMT with D3DMetal and DXVK as toggles; Grapple ships both and picks between them for you (Automatic uses D3DMetal). Parallels is different: it runs real Windows and supports up to DirectX 11.1 through its own virtual GPU.

DXMT

DXMT is an open-source, Metal-based translation layer for Direct3D 10 and 11, built specifically for Wine on macOS. Because it targets Metal directly, there's no Vulkan middle step. It's the default DirectX 10/11 path in Sikarugir, is included in Grapple as the fallback when D3DMetal isn't installed, and CrossOver includes it as well. It doesn't handle DirectX 12 or DirectX 9.

D3DMetal

D3DMetal is Apple's own Direct3D-to-Metal layer, part of the Game Porting Toolkit. It's the main route to DirectX 12 games on a Mac, and it covers DirectX 9 to 11 too. It is closed source: CrossOver and Grapple include it, and other tools let you point them at a copy you installed yourself.

DXVK + MoltenVK

DXVK translates Direct3D 8–11 to Vulkan and is the workhorse behind Proton on Linux and the Steam Deck. On a Mac, Vulkan itself has to be translated to Metal by MoltenVK. That double hop, and Vulkan features MoltenVK can't provide, mean Mac builds of DXVK lag behind the Linux ones. It remains a useful fallback, especially for DirectX 9 games.

WineD3D

Wine's built-in translator turns Direct3D into OpenGL. On macOS that means Apple's old OpenGL 4.1, so it's slow for modern games, but it's the most compatible option for very old titles (DirectX 7–9) and anything the other layers break.

Which one should I use?

• DirectX 9 and older: start with WineD3D or DXVK.
• DirectX 10 and 11: start with DXMT; if the game crashes or renders wrong, try D3DMetal.
• DirectX 12: D3DMetal is the realistic option. If it fails, cloud gaming is the fallback.
• Not sure which DirectX a game uses? The PC system requirements on its store page usually say, and community reports on AppleGamingWiki often name the layer that works.

Whatever the layer, the first minutes of a new game often stutter while shaders are translated and cached. Judge performance after that settles. Games with anti-cheat are a separate problem no graphics layer can fix — see anti-cheat games on a Mac.

FAQ