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 perfect on DXVK on an M5 Pro over 29 minutes. The frame rate drops for a moment on some maps and the first time some effects play, then recovers. Nothing was measured here.
Known issues
Short frame rate drops on some maps and the first time some effects play (reported on an M5 Pro, DXVK)
What helps none needed, it recovers by itself
Why likely shaders being compiled the first time they are needed. Not measured
Provenance
Reported by Swiss-Mac-User (highball-db#658, 2026-10-24), Apple M5 Pro, macOS 27.2, Highball 0.10.22, engine x64-sikarugir10.0_6-r29, DXVK, sync off, rated 5 of 5 after 29 minutes. Not verified by the maintainer.
Before installing anything, it is worth checking whether the game already ships a native Mac build.
Common questions
Does Half-Life 2: Deathmatch work on Mac?
Half-Life 2: Deathmatch 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 Half-Life 2: Deathmatch 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.