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 | Reported | named in upstream release notes |
| D3DMetalApple's Game Porting Toolkit | Untested | no report yet — send one |
Last confirmed 2026-09-30. That run predates per-report engine and macOS logging, so those are not recorded for it. A newer report would carry both.
Notes
login background video fixed. The dead left click reported on an M5 (highball#144) came after opening the terms links, a switch to the browser and back, and is the focus fault fixed in engine r15 (highball#182). Measured here 2026-09-19 on an M1 Pro, macOS 27.0, engine r5, Highball 0.9.32: the title screen and the in-game menu react to a left click on DXMT and on DXVK alike (tap to start proceeds to the data download), so the dead left click reported on an M5 is not a macOS 27 or a graphics-mode matter on this hardware. Measured on an M4 with macOS 27.0 on 2026-09-30, DXMT: after a Dock restore, Cmd+Tab or a click on another app the game took no input on engine r13 and takes it on r15. Checked here on 2026-10-05 on an M4 with engine r21, DXMT: the title screen (v1.35.2) comes up at 110 s; not played past it.
Known issues
The game stops taking left clicks after switching to another app and back, for example after opening the terms links in the browser (reported on an M5, macOS 27.0, DXMT), while clicks keep working in the Steam window
What helps Fixed in engine r15, which environments on the default engine pick up by themselves once Steam is closed. On an older engine, restart the game.
Why Wine 10's Mac driver sent the game a made-up click in its title bar whenever macOS gave it focus back, and Unity ignores the focus gain that follows such a click, so it keeps drawing but drops every click and key (Wine bug 48121, highball#182). Measured on an M4 with macOS 27.0: after a Dock restore, Cmd+Tab and a click on another app the game took no input on engine r13 and takes it on r15
Provenance
DXMT changelog v0.73 (github.com/3Shain/dxmt/releases)
Before installing anything, it is worth checking whether the game already ships a native Mac build.
Common questions
Does Umamusume: Pretty Derby work on Mac?
Umamusume: Pretty Derby has no native Mac build, but it is reported to run on Apple Silicon through Highball, a free open-source compatibility layer. It is named as working or fixed in upstream release notes. Highball has not run it, so treat this as a strong report rather than a verified result.
Which renderer should I use for Umamusume: Pretty Derby?
DXMT. Highball can translate Direct3D through DXVK, DXMT or Apple's D3DMetal, and the right choice varies by game. The database records DXMT for Umamusume: Pretty Derby. 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 Umamusume: Pretty Derby 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.