Tune your settings.
Not just your ears.

Retail moved the 1080p/native-res setting: in the beta it was DLSSModeMP = DLAA; on retail that option is gone and the equivalent is DLSSPerfModeMP = Native Resolution — same sharpest-image idea on a CPU-bound rig, new name. Any config still built on the beta schema carries the old line, and retail ignores it silently.

1. Pick your variant. Same hardware profile as the BO7 package, and the same measurements — those were taken in Black Ops 7 on that machine. MW4 itself has not been run with these files. 1080p is built for a CPU-bound rig (8-core + RTX 5070-class), 1440p for a GPU-bound rig (9800X3D-class + RTX 5080-class). Go by resolution first.
2. Check your CPU's core count (Task Manager → Performance → CPU → “Cores”). If it isn't 8, open every .txt file in your chosen variant folder with Notepad and set RendererWorkerCount to your cores minus 1 in all of them — table below. 8 cores? Skip this, both variants already ship with 7.
3. Open Modern Warfare 4 once, then close it completely — launching is what generates the config files.
4. Press Win + R, type %localappdata%, then go to Activision → Call of Duty → players.
5. Look at the exact file names the game generated (s.*.cod26.*). If they differ from the package — a season update can bump s.1.0 to s.1.1, the MW4 beta itself did this between its two weekends — rename the package files to match exactly. This is the #1 reason a config silently does nothing.
6. Back up your current files somewhere safe before touching anything.
7. Delete the game's existing s.*.cod26 files.
8. Paste only the files that match what your game generated. Each variant folder ships four files with identical content — .txt (single-file layout), .txt0 + .txt1 (two-slot layout), and .m (marker) — because the MW4 configs circulating right now use a single .txt, Black Ops 7 uses the two-slot layout, and which one MW4 retail actually uses can't be confirmed without the game installed. Copy whichever names match; the extras just sit there unused. Two-slot layout? Replace both .txt0 and .txt1 — replacing only one means the game can still load the other.
9. Launch the game. If it asks to restore or reset your settings, click No.
10. Let shader preloading finish before you queue a match.
11. In Settings, set your resolution and refresh rate.

1. Pick your variant. 1080p is built and measured on a CPU-bound rig (Ryzen 7 5800X + RTX 5070). 1440p is built for a GPU-bound rig (Ryzen 7 9800X3D + RTX 5080-class) — a template, not run on that hardware yet. Not sure? Go by resolution first.
2. Check your CPU's core count (Task Manager → Performance → CPU → “Cores”, not “Logical processors”). If it isn't 8, open both .txt0 and .txt1 in your chosen variant folder with Notepad and set RendererWorkerCount to your cores minus 1 in both files — table below. 8 cores? Skip this, both variants already ship with 7 in both files.
3. Open Black Ops 7 / Warzone once, then close it completely.
4. Press Win + R, type %localappdata%, then go to Activision → Call of Duty → players.
5. Back up your current 3 files — copy s.1.0.cod25.txt0, .txt1, and .m somewhere safe before touching anything.
6. Delete all 3 of your existing s.1.0.cod25 files — .txt0, .txt1, and .m. Names match the current Black Ops 7 build; if a season update renames them, check the folder for the new names, and rename the three files in the package to match them exactly before pasting. Leave any file with bt in the name alone — those are from the beta.
7. Paste all 3 files from your chosen variant folder — the same ones from step 2 if you edited them. All three: the game keeps two tracking slots plus a marker file, so replacing only one means it can still load the other and your change won't apply.
8. Launch the game. If it asks to restore or reset your settings, click No.
9. Let shader preloading finish before you queue a match.
10. In Settings, set your resolution and refresh rate.

Second-machine verification and the ConfigCloudStorageEnabled fix contributed by HarryPc, from a Black Ops 7 install on a different machine and patch level. Comparing the two is what surfaced the schema drift documented above.