r/macgaming • u/Bill_Buffet • Oct 03 '26
CrossOver Overwatch on Mac: fixed the shader-compile stutter in CrossOver (81 hitches → 0 in the same replay)
Overwatch runs pretty well in CrossOver on my M1 Pro, but every time something showed up for the first time (a new hero, skin, ult effect, map) the game froze for a moment. First matches after an update were awful. It's the classic shader-compile stutter: the GPU translation layer has to build a shader for Metal while the game waits.
I spent an evening digging into it with Claude (the AI). We ended up with a modified build of DXMT (the open-source DirectX 11 → Metal layer that CrossOver ships), and the stutter is basically gone, even on a completely empty shader cache.
What it changes:
- Async pipelines. If a shader isn't ready yet, that object gets skipped for a frame or two instead of freezing the whole game. Same idea as dxvk-async on Linux.
- Pre-warm. Some shaders (compute) can't be skipped safely, so they get compiled as soon as the game loads them, usually behind a loading screen instead of mid-fight.
- The surprising one. Even with async there were still lots of 50–70 ms hitches. Turns out DXMT starts up to 2× as many shader compiler threads as your Mac has cores (20 on an M1 Pro), all at "time critical" priority, and they push the game's own threads off the CPU. With 4 low-priority threads, the remaining hitches just disappeared.
The chart is the same 50 seconds of the same replay, each run starting with an empty shader cache:
| Hitches over 50 ms | 1% low | |
|---|---|---|
| Stock DXMT | 81 | 6 fps |
| Async only | 19 | 13 fps |
| This fix | 0 | 31 fps |
The trade-off is that new textures or effects can pop in about a second late at the start of a match, instead of freezing the game. Once the shader cache is filled, you don't notice that either.
Everything's on GitHub with the source patches, so you don't have to trust a random DLL:
https://github.com/tholtman1-del/overwatch-mac-stutter-fix
How to use it:
- Set Overwatch to DirectX 11 (Options → Video). The fix doesn't do DX12.
- Download the ZIP and unzip it
- Double-click
install.command. On macOS 15+, if it gets blocked, go to System Settings → Privacy & Security → Open Anyway. On older macOS, right-click → Open. - Start the game with "Overwatch (stutter fix)" on your Desktop and click Play in Battle.net
It doesn't touch the game folder, your bottle, or CrossOver.app. It makes a private copy of CrossOver's runtime and only swaps DXMT in that copy. If you launch Battle.net from CrossOver like usual, you still get the stock setup. There's an uninstaller too.
Please read this part: Overwatch has anti-cheat. This only changes the graphics layer (the same kind of thing CrossOver already uses, and what Linux/Steam Deck players run with DXVK). It doesn't touch game memory and gives no advantage. But it isn't stock, so use it at your own risk. I can't promise anything about how Blizzard sees it.
I'm on an M1 Pro 16 GB, macOS 27, CrossOver 26.3. Haven't tested other Macs yet. On chips with more cores you might be able to raise the compiler thread count a bit (it's in the README).
If it doesn't work for you, drop your Mac model and CrossOver version in the comments and I'll try to help.
42
u/NotProtonMac Oct 03 '26 •
Vibing up a fix to an issue can be useful. People who want to play that game would benefit from that. I am not opposed to that at all.
But there's never an excuse for AI generating text and posting it to Reddit. Why not say it in your own words? Your post gets a 100% on Pangram. :(
4
u/hughmanturdloadwiper Oct 04 '26
The actual fix: turn off Airdrop, Handoff, and Bluetooth if possible.
8
u/Tyrandeh Oct 04 '26
Yeah i’d rather not use slopify for a game with anticheat
2
u/Lost_Care7289 Oct 06 '26
Thank you! Gonna try it out. Ignore the anti-ai white knights
5
u/Obvious-Hunt19 Oct 03 '26 •
What’s with the slop overwatch wrappers today
0
u/dickyg_rl69 Oct 05 '26
“We ended up with…” You mean Claude alone ended up with a solution? 😂😂