macos Playing Call of Duty 4 with CoD4x on Apple Silicon (Porting Kit)

[iboomboom]

Call of Duty 4 + CoD4x on Apple Silicon using Porting Kit

I spent a good 3 days sorting this out for the most optimal combination. There are a few different ways you can play this aging game on Apple Silicon. It becomes challenging given that Apple has discontinued 32-bit app support. What I have here is a fully tested setup for playing Call of Duty 4 - Modern Warfare with the CoD4x client on Apple Silicon with up to 125+ FPS. This works for both CD/retail owners and Steam owners. The base-game install differs slightly between the two, but everything from the CoD4x client onward is identical. I used AI to create the steps following my experiments and then I revised the notes.

Tested on: M2 Pro/M5 Max, macOS (Tahoe), Porting Kit +  WineskinCX64 23.7.1 (revision 4, D3DMetal-v2.1).

 

---

TL;DR : why this is finicky and what to do

Three separate problems get tangled together:

1. Graphics engine. COD4 MW is a 32-bit Direct3D 9 game. The engine you pick has to accelerate D3D9 specifically. D3DMetal does. DXMT and DXVK/d9vk do not.
2. Steam has to be running for servers that have Steam auth enabled, applies to CD version of the game too. Steam's webhelper crashes with HW acceleration D3DMetal on Apple Silicon when run with Win 10 compatibility, set it to Windows 7 in Wine Config Utility under Applications tab. 
3. Performance is CPU-bound. A 2007 game can't tax an M-series GPU. The limiter is the translation layer on the CPU, and Steam sitting on the performance cores steals your frames. This can be addressed by demoting Steam to the efficiency cores.
    

---

Part 1 — Build a CLEAN wrapper 

1. In Porting Kit, select the stock Call of Duty 4 port, then Install with extra options.
2. For the engine, choose the CX64Bit D3DMetal option (it will show as WineskinCX 23.7.1 D3DMetal-v2.1, see picture below).
3. Set the wrapper's Windows version to Windows 10 at creation. This is the version the game will run under, and it's fine for the game.
4. Select Mac Driver and Steam in dependencies

---

Part 2 — Install the base game & Steam

CD / retail owners:

• Install from the disc by mounting an ISO, then right click on Setup.exe and choose Open With Porting Kit.

OR

•  Copy your existing game files into the wrapper's drive_c/Program Files (x86)/Activision/Call of Duty 4 - Modern Warfare/).
• Apply the official 1.7 patch if your copy isn't already at that level.

Steam owners:

• Since we selected a D3DMetal engine Steam will not automatically install due to inherent incompatibility. Download Steam for Windows from their website. Then right click on the exe in your macOS Finder window and select Open With "Porting Kit". This will install Steam, and try to run it and most likely will result in a crash, look at Step 3 for more details. 
• Install COD4 MW through Steam into this wrapper once you've followed the procedure in Step 3.

 

---

Part 3 — Install Steam into the SAME wrapper

Steam must live in the same wrapper/prefix as iw3mp.exe. A separate Steam bottle will not authenticate the game.

3a. Set the Windows version BEFORE first login 

Use a per-application override so you can make Steam happy without disturbing the game:

1. Open winecfg → Applications tab → Add application → select steam.exe.
2. With steam.exe selected, set its Windows version to Windows 7.

3b. Add the CEF launch flags (this stops the webhelper crash)

The webhelper crash on Apple Silicon is a known 64-bit CEF bug under Wine. Steam's own "disable hardware acceleration" toggle does not fix it. Forcing the 32-bit webhelper does. Set Steam's launch arguments to:

-cef-force-32bit -no-cef-sandbox -cef-single-process -cef-in-process-gpu -cef-disable-d3d11 -cef-disable-breakpad -nofriendsui -nofasthtml

(In Porting Kit/CrossOver, set these as the arguments on the Steam launcher)

3c. Quiet Steam down

In Steam settings, once logged in:

• Interface / Downloads: turn off "allow downloads during gameplay" and automatic game updates.
• Cloud: disable Steam Cloud.
• In Game: disable the Steam Overlay (it hooks the game's frame-present call and adds per-frame overhead under D3DMetal — a classic stutter source).
• Low Performance Mode: enable it. With the 32-bit webhelper forced, leaving web-view GPU acceleration on plus Low Performance Mode was stable in testing and reduced overhead. If you still get instability, try turning web-view GPU acceleration off — it's the one knob to flip if the webhelper is still unhappy.

---

Part 4 — The performance unlock: demote Steam to the efficiency cores

This is what takes you from a jittery 40–120 to a solid 125+FPS.

Why: the game is CPU/translation-bound, so any process competing for CPU steals frames directly — that's why FPS dips even when you're staring at a wall (the wall is trivial for the GPU; the dip is Steam spiking on the CPU). macOS doesn't let you hard-pin processes to cores, but it does place work on P-cores vs E-cores by QoS class. Demote Steam's webhelper to background QoS and the scheduler parks it on the E-cores, freeing the P-cores for the game.

The tool is taskpolicy. Do it after Steam is up and logged in. The script below watches for the webhelper processes and demotes them automatically (they spawn several and can respawn, so a one-shot command misses some).

Important: it targets only steamwebhelper. It does not touch steam.exe, iw3mp.exe, or the shared wineserver — throttling the wineserver would slow the game too, since they share it.

The watcher script

Save as cod4-steam-qos.sh:

#!/bin/bash
#
# cod4-steam-qos.sh
# Keeps Steam's webhelper processes demoted to background QoS so the
# macOS scheduler parks them on the efficiency (E) cores, leaving the
# performance (P) cores free for the game (iw3mp.exe under D3DMetal).
#
# Only targets processes whose command line contains "steamwebhelper".
# Does NOT touch steam.exe, iw3mp.exe, or the shared wineserver.
#
# Usage:
#   1. Launch Steam (through your Wine wrapper) and let it log in.
#   2. In Terminal:   sudo bash cod4-steam-qos.sh
#   3. Leave it running while you play. Ctrl-C to stop.

set -u

PATTERN="steamwebhelper"   # matched against the FULL command line
INTERVAL=5                 # seconds between re-scans

if [ "$(id -u)" -ne 0 ]; then
  echo "Please run with sudo:  sudo $0" >&2
  exit 1
fi

seen=" "
count=0

cleanup() {
  echo
  echo "[cod4-qos] stopped. Demoted processes stay on the E-cores until Steam restarts."
  exit 0
}
trap cleanup INT TERM

echo "[cod4-qos] watching for '$PATTERN' every ${INTERVAL}s (Ctrl-C to stop)…"

while true; do
  # -i = case-insensitive, -f = match the full argument list.
  # Wine names each process after its loader, so the real .exe name only
  # appears in the arguments — -f is what makes this match at all.
  for pid in $(pgrep -if "$PATTERN"); do
    taskpolicy -b -p "$pid" 2>/dev/null   # idempotent; safe to re-apply
    case "$seen" in
      *" $pid "*) : ;;
      *) seen="$seen$pid "
         count=$((count + 1))
         echo "[cod4-qos] demoted PID $pid  (total this session: $count)" ;;
    esac
  done
  sleep "$INTERVAL"
done

Run it (in the normal macOS Terminal:

sudo bash cod4-steam-qos.sh

Confirm it's working in Activity Monitor → Window → CPU History — you'll see Steam's load move onto the E-cores. PIDs reset each session, so run the script each time you play (or adapt it into a launch agent if you want it permanent).

Runs under sudo so taskpolicy never stops to ask for a password mid-loop.

---

Part 5 — In-game settings

• Resolution: native/fit-to-screen is fine — you're not GPU-bound, so resolution barely moves the needle. If you're on a Retina wrapper, check the Retina Mode toggle; with it on, your chosen resolution may actually render at 2× (4× the pixels) under the hood. This will be in Properties for the port, keep it unchecked. 

• Framerate cap: CoD4 is idTech3, so com_maxfps is tied to jump physics. The canonical competitive values are 125 and 250. Open console (~) and set:

  /com_maxfps 125
  /cg_drawfps 1
  

  A cap you can hold steadily feels far better than a higher one that swings, because input and jump physics are framerate-linked. If you can't sustain 125 with Steam running, lock to a value you can.

---

Part 6 — Play session order of operations

1. Launch Steam through the wrapper (Win7 per-app override + CEF flags). Let it log in. Minimize it.
2. Run the QoS script: sudo bash cod4-steam-qos.sh.
3. Launch the game. You can launch through Steam, or launch iw3mp.exe directly with Steam idling in the background — the auth server only needs Steam alive, not the launcher path.
4. Connect to your Steam-auth CoD4x server.

Do not close Steam. The server re-validates continuously via Steamworks; kill Steam and you get dropped. Minimized + demoted is the sweet spot: present enough to auth, quiet enough to stay off your frame budget.

---

Troubleshooting

• FPS is low / stuck at the non-accelerated level. Confirm the QoS demotion actually ran (CPU History window). 
• FPS swings wildly while staring at a wall. That's Steam spiking on the P-cores. Run the QoS script; disable the overlay and background downloads.
• Steam crashes on launch. Make sure the CEF flags are actually applied, set steam.exe to Win7 per-app, and verify you didn't change the Windows version after installing Steam.
• Steam worked, then broke after "Updating Steam". A version/OS change re-bootstrapped it. Relaunch with flags; if needed, rebuild the Steam side and don't touch the OS version afterward.
• Graphics look wrong / glitchy. You almost certainly have leftover DXVK/d9vk overrides from a different engine, create a new wrapper. 
• Can't join auth servers. Steam must be running, logged in, and in the same wrapper as the game.
• Installing COD4: /connect 74.91.116.93:28960, it will auto install COD4x client for you upon connect. Trust the process.

---

Why not DXMT, DXVK, or a Parallels VM?

• DXMT translates D3D10/11 only — it does nothing for a D3D9 game, so CoD4 falls back to the slow path.
• DXVK/d9vk on Mac is D3D9 → Vulkan → MoltenVK → Metal (extra layers), and its D3D9 component is deprecated. Slower than D3DMetal here, and it fights D3DMetal for the D3D9 path.
• Parallels + Linux guest — no true GPU acceleration and you'd stack even more translation. Skip.
• Parallels + Windows 11 ARM guest — actually viable (real Windows, real Steam, x86 emulation via Prism, Parallels' virtual GPU) and avoids the whole Wine/webhelper mess, but the virtual GPU caps framerate well below native D3DMetal. Good fallback if you don't want to tune; not the high-FPS path.

---

Credits

• CoD4x team — client and docs (github.com/callofduty4x/cod4x-docs)
• NovaVeterans — Mac/CrossOver CoD4x walkthrough
• CodeWeavers community — the -cef-force-32bit webhelper fix
• Everyone in the macgaming / CoD4x community who documented pieces of this

If this helped, drop your chip model + FPS results below so we can build a compatibility list. Please tag whomever does mac gaming.

cc: @deadman @El_Terrible @YACCster 

 

 

Edited July 3 by iboomboom
removed extra images

[Qualicum]

way easier on linux lmao

[iboomboom]

Linux has a native version, macs are well just difficult. 

[YACCster]

20 hours ago, iboomboom said:

 

---

Why not DXMT, DXVK, or a Parallels VM?

 

• Parallels + Windows 11 ARM guest — actually viable (real Windows, real Steam, x86 emulation via Prism, Parallels' virtual GPU) and avoids the whole Wine/webhelper mess, but the virtual GPU caps framerate well below native D3DMetal. Good fallback if you don't want to tune; not the high-FPS path.

 

cc: @deadman @El_Terrible @YACCster 

 

 

This is interesting but I don't seem to have a problem with Parallels generating very acceptable frame rates as you can see from my screenshots and the installation of COD4 and 4x is dead simple there on my Windows 11 ARM, just like it would be on standard PC.

[iboomboom]

Yaccster, are you playing on a Mac Studio? 

[YACCster]

1 hour ago, iboomboom said:

Yaccster, are you playing on a Mac Studio? 

No just a little MBP 16” m3 max 128GB/8TB

[iboomboom]

For double translation, x86 to ARM to host that's very respectable FPS with all the settings. Comparatively speaking my M5 MAX gave me around 250+ FPS but ocasionally not sustained. If you are getting sustained rates then perhaps Parallels is doing a better job.

[El_Terrible]

Boom, this is an excellent set of instructions. Thanks for putting the effort in. I will try it out and report back.

[YACCster]

Tried Crossover 25 and 26 and it worked (https://www.codeweavers.com/crossover), again dead simple install downloaded my COD4 from Steam in the bottle and  attached to our server and it installed COD4x for me, just a couple of clicks and it was off and running.  The performance was massively sub-par (60fps max)  relative to my Parallels setup however.  I haven't taken much time to see if I could refine it to do better though.

[iboomboom]

30 minutes ago, YACCster said:

Tried Crossover 25 and 26 and it worked (https://www.codeweavers.com/crossover), again dead simple install downloaded my COD4 from Steam in the bottle and  attached to our server and it installed COD4x for me, just a couple of clicks and it was off and running.  The performance was massively sub-par (60fps max)  relative to my Parallels setup however.  I haven't taken much time to see if I could refine it to do better though.

Yeah, Porting Kit was also straight forward at first but my fps was bad. It's because by default it doesn't send data to the GPU instead uses the CPU fallback.  If you see FPS in the 100s then it's using the Metal API. 

[iboomboom]

@Poppyseed please try this. 

[El_Terrible]

Well, I am out. The performance (Intel Mac) is terrible. No pun intended. The amount of effort I've put into getting this to run over the last few weeks is astonishing. I am sorry I couldn't get it working. It's been a fun ride with everyone, and I am going to miss the game and XI, but I can't play this version.

[iboomboom]

I am sorry to hear that El Terriblay... we put a lot of consideration when undertaking this effort. The benefits simply outweigh the cons. I play on an Apple silicon and it's very respectable. Apple is going to discontinue 32-bit app support in the next macos release, so you will eventually not be able to play the game on a Mac. 

Are you 100% sure the gpu translation is working? My FPS was 10-15 when it was purely CPU fallback. I don't have an Intel Mac otherwise I would've investigated. 
 

@azzkikr has an Intel Mac. Maybe he can try it out too. 
For shits ands giggles can you try parallels? They've a trial version. If you just hate windows try Linux on parallels. 

[iboomboom]

@El_Terrible

Somebody who loves this game even more than us, took it upon themselves to create a native 64bit version of the game. I have not tested it but this apparently works on x86_64 macs too. Try it?

https://github.com/SwagSoftware/KisakCOD 

[El_Terrible]

I'll try these options, Boom.

KIsak does not run natively on Macs, so it's going to need CrossOver or Porting Kit to work. I was excited there for a few minutes.

I've been playing on a 2012 Mac Pro, so the system never gets updated. I would upgrade to Apple Silicon, but that's not in the cards right now. I've considered a cheap mini PC, but not with prices where they are right now.

I don't hate Windows. I just prefer Macs. I'll try Parallels Windows and Linux.

 

Edited July 14 by El_Terrible
clarification

[iboomboom]

@El_Terrible don't give up there's hope and it's worth it.

 

[El_Terrible]

I am able to get it running in CrossOver with 40-50 fps. A few people said I am glitching on their end.  I know it would run in BootCamp, but this is the Mac I work with, so it isn’t practical to restart every time I want to play.

I am going to see what I can do to boost performance. 

[iboomboom]

2 hours ago, El_Terrible said:

I am able to get it running in CrossOver with 40-50 fps. A few people said I am glitching on their end.  I know it would run in BootCamp, but this is the Mac I work with, so it isn’t practical to restart every time I want to play.

I am going to see what I can do to boost performance. 

Very nice. Since you have intel CPU, you probably have the integrated GPU. What's your resolution? Drop the in-game resolution to lower number to see if it works. Also, adjust your /rate to 15000 and then reconnect. Set the graphics to the lowest and disable anti-aliasing. Only enable shadows.

[YACCster]

On 7/13/2026 at 6:06 PM, iboomboom said:

I Apple is going to discontinue 32-bit app support in the next macos release, so you will eventually not be able to play the game on a Mac. 

Um, Apple discontinued 32-bit support in macOS Catalina 10.15(released in October 2019).

[El_Terrible]

1 hour ago, YACCster said:

Um, Apple discontinued 32-bit support in macOS Catalina 10.15(released in October 2019).

This is why I've been running the old machine with the old OS - just to play COD.

[iboomboom]

2 hours ago, YACCster said:

Um, Apple discontinued 32-bit support in macOS Catalina 10.15(released in October 2019).

You are right.  I should've been clearer.  Porting Kit gives a warning that you are running software that will not be supported in the next version of macOS. 

In contrast, I created a DOS game in 2002 and it still runs on Windows 11 today. 

[YACCster]

28 minutes ago, iboomboom said:

You are right.  I should've been clearer.  Porting Kit gives a warning that you are running software that will not be supported in the next version of macOS. 

In contrast, I created a DOS game in 2002 and it still runs on Windows 11 today. 

Yeah, it's Rosetta2 that actually still is supposed to be available but only for games after next year, so we will see..

[iboomboom]

13 hours ago, El_Terrible said:

This is why I've been running the old machine with the old OS - just to play COD.

I just bought a 16" 2019 mbp core i9 32gb ram 1tb storage off of backmarket.com for $440 including tax. I intend to give it to my son after I install windows on it. 

he keeps breaking my old gaming desktop with 1070ti  

FYI.