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 | 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
Doesn't start yet in one report on an M1 Mac mini: the game ends itself right after starting, before it opens a window, on the Wine 10 and Wine 11 engines. The Steam release carries Denuvo Anti-Tamper (store page).
Known issues
Exits right after starting, before any window (M1, Wine 10 engines and Wine 11 r28, r30 and r31)
What helps none known. Untested: turning the Steam overlay off for the game
Why not diagnosed. Right after the game's sweep of system, process and thread information queries, many of which Wine doesn't answer, exception c0000409, the code a Windows program uses to stop itself at once, is raised from inside Steam's overlay DLL gameoverlayrenderer64.dll (offset 0xdea75 in every log), before any graphics device exists, so the graphics mode isn't involved (the reporter's +loaddll traces, highball-db#1058)
Epic Online Services fails to install on the Wine 10 engines (SetNamedSecurityInfo error 120, MSI error 1603)
What helps the Wine 11 engines install it
Why error 120 means the call isn't implemented, a Windows security call Wine 10 lacks for what the installer asks (the reporter's reading)
Provenance
Reported by DanielAdomian (highball-db#1058, 2026-11-07), Apple M1 Mac mini with 16 GB, the Wine 10 engines and the Wine 11 (CrossOver 26.3) engines, exits at start. Not verified by the maintainer. DanielAdomian again on highball-db#1058 (2026-11-08), +loaddll logs on the Wine 11 engines r30 and r28 (D3DMetal, the Games environment): r31 fails the same way, and Highball shows the game as running for a few seconds. Before the end SWGR-Win64-Shipping.exe queries nearly every system, process and thread information class in a shuffled order, many of which Wine doesn't answer, which looks like a fingerprinting pass. The c0000409 address lies inside Steam's overlay DLL, gameoverlayrenderer64.dll, at offset 0xdea75 in both logs, and the first log's address ends the same way. An earlier reply said it sat in one of Wine's DLLs, which was wrong.
Before installing anything, it is worth checking whether the game already ships a native Mac build.
Common questions
Does STAR WARS: Galactic Racer work on Mac?
STAR WARS: Galactic Racer 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 STAR WARS: Galactic Racer 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.