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 | 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 the default engine and DXMT: it starts smooth, then the picture and the sound lag. The game starts through Ubisoft Connect. No frame rate or settings were given and nothing was measured here.
Known issues
Frame and sound lag after a smooth start (reported on an M1 Pro, macOS 27.0.1, DXMT, engine r28)
What helps none known
Why not measured. Both lagging together usually means the CPU is the limit
Provenance
Reported by DipeshMajithia (highball#438, 2026-10-22), Apple M1 Pro, macOS 27.0.1, Highball 0.10.22, engine x64-sikarugir10.0_6-r28, DXMT environment, msync: playable, not smooth. Not verified by the maintainer.
Before installing anything, it is worth checking whether the game already ships a native Mac build.
Common questions
Does Far Cry 3 work on Mac?
Far Cry 3 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 Far Cry 3 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.