Grand Theft Auto V Enhanced on Mac

Which renderer to use

Highball can run each game through four different Direct3D translation layers. This is what the database knows for this title — empty rows are open questions, not failures.

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

Starts under vkd3d, refuses under D3DMetal, and neither finishes. The game needs Highball's Wine 11 engine (CrossOver 26.3 base) and two graphics modes in one process tree: the Rockstar Games Launcher signs in under DXMT, the game is DirectX 12 only. Under D3DMetal it quits at once with ERR_GFX_D3D_NOD3D12, and what causes that is NOT yet known: the game creates a D3D12 device, makes 137 capability queries that all succeed, creates a DXGI factory and enumerates an adapter, and then refuses. Under vkd3d it reaches the story-mode loading screen at 53-62 fps and then loses the GPU device because MoltenVK cannot translate some of its shaders to Metal. Turn BattlEye off in the launcher first (Settings > My installed games), its driver cannot load under Wine. GTA Online is out of reach regardless. If sign-in is refused with #1.000.7, set the Mac's clock (see the rockstar recipe).

Known issues

• ERR_GFX_D3D_NOD3D12 within seconds of starting, under the D3DMetal graphics mode

  What helps none known. Not an app-level problem.

  Why cause not established on Apple M1 Pro hardware, and a long list of candidates has been excluded by measurement on 2026-09-08 (macOS 26.6.2, engine x64-crossover26.3-r4, D3DMetal 3.0 and Apple's D3DMetal 4.0b2 from Game Porting Toolkit 4). Excluded: the DirectX 12 Agility SDK loader (the game declares SDK 611 and never calls D3D12GetInterface; supplying it changed nothing); device creation (succeeds at 12_0 on the real adapter); capability values (137 CheckFeatureSupport calls all return S_OK, and forcing every one of them to report supported changes nothing); the advertised feature level (D3DMetal claims 12_2 and even accepts device creation there, but making it report and behave exactly like vkd3d, 12_0 with E_INVALIDARG above, changes nothing); ray tracing (D3DM_SUPPORT_DXR=1 raises the tier to 1.1, no change); the GPU identity presented (vendor, device and description overridden, no change); DXGI (factory, adapter enumeration, GetDesc3, outputs, tearing, video memory budget and swapchain creation in seven configurations all succeed, identically to vkd3d); Highball's own timestamp shim (removing it entirely changes nothing); and Metal 4 mode. The game creates a device, reads capabilities, creates no resource, raises no exception, and quits. Field reports are consistent with a hardware floor: it is reported working on M4 Pro and M5 Pro and never on M1 or M2, and it uses hardware ray tracing, which Apple GPUs only have from M3 onward (this Mac reports GPU family Apple 7). That is a correlation, not a proof, and it does not explain why the same Mac starts the game under vkd3d.

• Under vkd3d it loads to a black screen with only the progress bar, then exits on its own near the end of the load

  What helps none at the app level. The tessellation half needs SPIRV-Cross to implement Component decoration for tessellation, which upstream has declined as too complicated. Turning the game's Tessellation setting to 0 reduces the failures and removes the device loss, but the run still does not complete.

  Why MoltenVK cannot translate two classes of the game's shaders to Metal, and one of them is a deliberate upstream limitation rather than a bug. Measured 2026-09-08 on an M1 Pro, macOS 26.6.2, engine x64-crossover26.3-r4 with MoltenVK 1.4.1: 42 graphics pipelines fail with 'Component decoration is not supported in tessellation shaders' (84 occurrences, control and evaluation stages), and 27 compute pipelines fail with MSL compile errors on vkd3d's bindless descriptor arrays ('reinterpret_cast casts away qualifiers', 'indirection requires pointer operand'). The tessellation one is an explicit SPIRV_CROSS_THROW in SPIRV-Cross's spirv_msl.cpp, with the comment 'Technically tessellation as well, but it is too complicated to support', still present on main, so a newer MoltenVK does not fix it. Setting the game's Tessellation option to 0 cuts the graphics failures from 42 to 13 and avoids the device loss, but does not eliminate them: the game still builds tessellation pipelines for some passes. Stock MoltenVK cannot be substituted to test newer translation code, because the engine needs an x86_64 build carrying the MVK_SHADOW_IMPORT patch that lets it work behind Wine's winevulkan; upstream fat builds report no Vulkan 1.3 device and nothing starts.

Provenance

tested locally on Apple Silicon (M1 Pro, macOS 26.6.2, engine x64-crossover26.3-r4) on 2026-09-08: it launches and loads under vkd3d and the GPU device is then lost, twice, at default and at minimum settings

Before installing anything, it is worth checking whether the game already ships a native Mac build.

Common questions

Does Grand Theft Auto V Enhanced work on Mac?

Grand Theft Auto V Enhanced 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 Grand Theft Auto V Enhanced?

vkd3d-proton. Highball can translate Direct3D through DXVK, DXMT, Apple's D3DMetal or vkd3d-proton, and the right choice varies by game. The database records vkd3d-proton for Grand Theft Auto V Enhanced. 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 Grand Theft Auto V Enhanced 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.

Download Highball