Which renderer to use
Highball can run each game through three different Direct3D translation layers. This is what the database knows for this title — empty rows are open questions, not failures.
| Renderer | Verdict | Evidence |
|---|---|---|
| DXVKDirect3D 9-11 over Vulkan | Untested | no report yet — send one |
| DXMTDirect3D 11 over Metal | Reported | 1 report |
| D3DMetalApple's Game Porting Toolkit | Untested | no report yet — send one |
No dated Highball run yet. When one lands it records the renderer, the engine build and the macOS version it was seen on — which is what stops a verdict quietly rotting. Send one.
Notes
DirectX 11 build on DXMT is the reported way to play. Reported on an M4 Max: the CD Projekt RED launcher (REDlauncher.exe) that Steam starts first fails with "Failed to create OpenGL context for QSurfaceFormat", a Qt rendering problem in the launcher rather than the game. Workaround the reporter used, start bin/x64/witcher3.exe (the DirectX 11 build) directly, with Steam running, and the game launches on DXMT. Steam's own --launcher-skip option skips the launcher too but starts the DirectX 12 build, which needs D3DMetal, not measured here. In game the reporter sees the mouse pointer offset from where clicks and aim land, not yet resolved; running windowed at the display's own resolution is the usual remedy for that class of problem and is not verified for this game. No measurement by the maintainer yet. A second report, on an M1, rates it 4 after 23 minutes on DXMT and names no problem.
Known issues
The CD Projekt RED launcher fails before the game with "Failed to create OpenGL context for QSurfaceFormat" (reported on an M4 Max, DXMT)
What helps start bin/x64/witcher3.exe (the DirectX 11 build) directly with Steam running, for example by dropping it onto Highball, which runs it in the environment; --launcher-skip as a Steam launch option also skips it but picks the DirectX 12 build
Why reported, the launcher is a Qt app drawing through OpenGL and that path is not available under this Wine
Mouse pointer drawn away from where clicks and aim land in game (reported)
What helps none verified, try windowed mode at the display's own resolution
Why not measured
Provenance
community consensus (AppleGamingWiki / r-macgaming / MacPlay), unverified by Highball Report with details from WaterWANG-1014 (highball-db#38, 2026-09-14), Apple M4 Max, macOS 15.7.7, Highball 0.9.11, engine x64-sikarugir10.0_6-r2, DXMT, rated 3 of 5 (playable with workarounds). Not verified by the maintainer. v1kk5 (highball-db#382, 2026-10-07): rated 4 after 23 minutes, Apple M1, macOS 27.0, Highball 0.10.10, engine x64-sikarugir10.0_6-r21, DXMT, with .NET 4.8, XACT, Controllers through SDL and core fonts installed.
Before installing anything, it is worth checking whether the game already ships a native Mac build.
Common questions
Does The Witcher 3: Wild Hunt work on Mac?
The Witcher 3: Wild Hunt has no native Mac build, but it is reported to run on Apple Silicon through Highball, a free open-source compatibility layer. This comes from community reports rather than a Highball test run, so treat it as a reasonable expectation rather than a guarantee.
Which renderer should I use for The Witcher 3: Wild Hunt?
DXMT. Highball can translate Direct3D through DXVK, DXMT or Apple's D3DMetal, and the right choice varies by game. The database records DXMT for The Witcher 3: Wild Hunt. Highball uses it automatically when the game has a row; to set it by hand, open Settings, then Environments.
Contribute a result
This page is generated from an open database. If you have run The Witcher 3: Wild Hunt on Apple Silicon, working or not, a report takes a minute and fills in the empty rows above. Send a report, or read how the data is put together.