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 | Reported | 2 reports |
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 over an 84-minute session on an M5 Pro, 60 to 120 fps on medium to high settings with the game's own frame generation turned on. The game is DirectX 12 only, so the mode was almost certainly D3DMetal, but the reporter did not state it. No measurement here yet. Two warning dialogs appear at launch and can be dismissed with OK, one about the graphics driver being below requirements and one claiming no graphics card is installed; both come from the game reading a driver version D3DMetal does not report. The reporter also had to switch the game to windowed mode, fullscreen did not work. A second reporter on an M4 Pro (engine r17, Highball 0.10.2) rates it 3, playable with workarounds, after a 17-minute first look and again after 57 minutes, the workarounds not yet named either time. A later report on a base M5 (macOS 27, D3DMetal on the default engine line) rates it 4, playable with minor issues, without naming them.
Known issues
Two warnings at launch, 'driver below the current game requirements' and 'no installed graphics card has been detected' (reported on an M5 Pro)
What helps click OK on both, the game runs
Why the game reads a driver version and adapter identity that D3DMetal does not report the way a Windows driver does
Fullscreen does not work, the game had to be switched to windowed (reported on an M5 Pro)
What helps use windowed or borderless in the game's display settings
Why not measured; matches the fullscreen mode-switch limitation on macOS (highball#72)
Provenance
Reported by moffatluke (highball-db#99, 2026-09-17), Apple M5 Pro, macOS 27, Highball 0.9.19, engine x64-sikarugir10.0_6-r3, rated 5 of 5 after 84 minutes. Graphics mode not stated. Not verified by the maintainer. BabySatan5282 (highball-db#278, 2026-10-02), Apple M4 Pro, macOS 26.7.1, Highball 0.10.2, engine x64-sikarugir10.0_6-r17, DXMT as the environment's mode (the game is DirectX 12 only, so its own mode was most likely D3DMetal), rated 3 of 5, playable with workarounds, after 17 minutes, with a fuller review promised. The same reporter's second report (highball-db#306, 2026-10-04), same Mac, macOS and engine, rates it 3 of 5 again after 57 minutes, the workarounds still not named. sahilas (highball-db#604, 2026-10-21), Apple M5, macOS 27, Highball 0.10.21, engine x64-sikarugir10.0_6-r29 as reported, D3DMetal, rated 4 of 5 with nothing named as off and no session length. Abhronil-Dutta (highball-db#722, 2026-10-27), Apple M5, macOS 27.0.1, Highball 0.10.22, engine x64-sikarugir10.0_6-r28, D3DMetal for the game (the environment's mode is DXMT, which has no Direct3D 12), msync, rated 4 of 5 after 59 minutes: minor lag, otherwise played fine.
Before installing anything, it is worth checking whether the game already ships a native Mac build.
Common questions
Does Marvel's Spider-Man Remastered work on Mac?
Marvel's Spider-Man Remastered 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 Marvel's Spider-Man Remastered 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.