Highball
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 | Reported | 1 report |
| DXMTDirect3D 11 over Metal | Untested | no report yet — send one |
| 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
Reported playable on an M1 Pro with DXVK, around 60 fps in the areas tested by the Metal HUD at 1800x1169, with sound, controller, saves and resolution changes working and occasional flickering and stuttering. In windowed mode the game sometimes stays on a black screen until its window is dragged by the title bar or minimized and restored, after which the intro videos play, on both the default engine r28 and the Wine 11 engine r27. Fullscreen starts without that, and Emulate display mode changes fixed a wrongly scaled or offset fullscreen picture. A controller has to be connected before the game starts. Nothing was measured here.
Known issues
In windowed mode the game sometimes stays on a black screen with no response to keyboard or mouse (reported on an M1 Pro, macOS 26.7, DXVK, engine r28 and the Wine 11 engine r27)
What helps drag the game window by its title bar, or minimize and restore it, and the intro videos start. Starting in fullscreen avoids it
Why not measured. The reporter suspects window state changes or event handling
The fullscreen picture is wrongly scaled or positioned (reported on an M1 Pro, macOS 26.7, DXVK, engine r28)
What helps turn on Emulate display mode changes in Highball, by the report
Why not measured
A controller connected after the game has started is not picked up (reported on an M1 Pro, macOS 26.7, DXVK, engine r28)
What helps connect the controller before starting the game
Why not measured
Occasional flickering and stuttering (reported on an M1 Pro, macOS 26.7, DXVK, engine r28)
What helps none known
Why not measured
Provenance
Reported by flacknabe-cpu (highball-db#609, 2026-10-21), Apple M1 Pro with 16 GB, macOS 26.7, Highball 0.10.22, engine x64-sikarugir10.0_6-r28, DXVK environment, msync, Metal HUD on, frame cap 60, rated 4 of 5 after 2 minutes, with a longer write-up in a comment that also tried the Wine 11 engine x64-crossover26.3-r27. Not verified by the maintainer.
Before installing anything, it is worth checking whether the game already ships a native Mac build.
Common questions
Does Darksiders II Deathinitive Edition work on Mac?
Darksiders II Deathinitive Edition 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.
Contribute a result
This page is generated from an open database. If you have run Darksiders II Deathinitive Edition 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.