===============================================================
  VanySound Gaming Mode
  BLACK OPS 7 / WARZONE CONFIG  -  two variants, pick one

  vanysound.com  ·  x.com/VanySound
  Settings only. No audio processing. Free to share.
===============================================================

  1080p\   for 1080p monitors on a mid-range CPU
  1440p\   for 1440p monitors on a fast modern CPU

Each folder has THREE files. You need all three. See step 4.


---------------------------------------------------------------
WHICH ONE
---------------------------------------------------------------

Pick by RESOLUTION first, then sanity-check the CPU.

1080p  - built and measured on: Ryzen 7 5800X (8c/16t),
         RTX 5070 12GB, 32GB RAM, 1080p 240Hz, SSD.
         On this class of rig the CPU is the limit, not the GPU.
         That single fact drives the whole setup.

1440p  - built for: a fast 8-core like a Ryzen 7 9800X3D,
         a 5070 Ti / 5080 class GPU with 16GB, 1440p 240Hz.
         Here the GPU is the limit instead.

Not sure? Go by resolution. It matters more than the CPU.

Note on those hardware specs: they're stated here, in writing, so
you know where the tuning came from. They are NOT written into the
config files. The Monitor / GPU / driver / detected-hardware fields
in both variants are generic placeholders, and the game overwrites
them with your own on first launch. Nothing in the files identifies
a machine - see the last section.


---------------------------------------------------------------
INSTALL
---------------------------------------------------------------

1. Open the game once, then close it completely.

2. Press Windows + R, type:   %localappdata%
   Then go to:  Activision  >  Call of Duty  >  players

3. Delete all 3 of your s.1.0.cod25 files:
      s.1.0.cod25.txt0
      s.1.0.cod25.txt1
      s.1.0.cod25.m

4. Paste all 3 files from your chosen folder.

   *** WHY 3: the game keeps TWO config slots, .txt0 and .txt1,
   plus a 2-byte .m marker. Replace only one slot and the game can
   load the other, so nothing changes. That's why a lot of
   downloaded configs "do nothing".

   Checked on a real install: a beta pair was byte-for-byte
   identical and the retail pair differed by exactly one line.
   They track each other, but they are separate slots. ***

5. Check RendererWorkerCount matches your CPU (next section).
   If you change it, change it in BOTH .txt files.

6. Launch the game. If it asks whether to restore or reset your
   settings -> click NO.

7. Let shader preloading finish before you queue a match.

8. Settings > set YOUR resolution and YOUR refresh rate.


---------------------------------------------------------------
RendererWorkerCount - CHECK THIS ONE
---------------------------------------------------------------

Both variants ship with:

    RendererWorkerCount@0;51989;59387 = 7

Correct for ANY 8-core CPU - which covers both a 5800X and a
9800X3D. Same core count, same value. 8 cores? You're done.

Otherwise set it to your PHYSICAL core count minus 1:

    4 cores   ->  3
    6 cores   ->  5
    8 cores   ->  7     <- what both files ship with
    12 cores  ->  8
    16 cores  ->  8     (it does not scale past 8)

    Intel 12th gen or newer (hybrid CPUs):
    use your P-CORE count minus 1. IGNORE the E-cores.
       i9-14900K (8P + 16E)  ->  7
       i5-14600K (6P + 8E)   ->  5

Task Manager > Performance > CPU, read "Cores",
NOT "Logical processors".

WHY NOT LEAVE IT ALONE:
Because the game's auto-detect overshoots your physical core count.
Measured, not copied off a guide: on a Ryzen 7 5800X - 8 physical
cores - the game had written 9. Nine workers on an eight-core CPU.
Identical value in both the beta and the retail config, so that's
consistent engine behaviour, not a fluke.

Other reported auto picks: Ryzen 5 3600 (6c) -> 4. i5-14600K
(6P + 8E) -> 14, because it counts the E-cores.

Setting this by hand is a REDUCTION from what the game gave you.


---------------------------------------------------------------
THE 3 SETTINGS THAT DIFFER BETWEEN THE VARIANTS
---------------------------------------------------------------

1) DLSSModeMP        1080p = DLAA      1440p = DLSS

   The big one. At 1080p on a 5070-class card the GPU sits idle
   while the CPU caps your framerate. Upscaling from 720p buys you
   NOTHING and costs you a blurry image you have to find enemies
   in. So: DLAA - native 1080p with DLSS anti-aliasing. Sharpest
   possible image, free on a CPU-bound rig.

   At 1440p the GPU IS the limit, so DLSS Quality earns real frames.

   Most "max FPS" configs ship DLSS Maximum Performance at 1080p.
   That renders the game at 540p. Don't.

2) VRS               1080p = false     1440p = true

   Variable Rate Shading cuts GPU shading work. CPU-bound, it buys
   zero frames and only costs image quality. GPU-bound, it pays
   for itself.

3) WorldStreamingQuality   1080p = Low    1440p = High

   Streaming costs CPU. A 5800X can't spare it; a 9800X3D can, and
   High means less texture pop-in.


---------------------------------------------------------------
TUNING
---------------------------------------------------------------

8 GB VRAM:
  TextureQuality = 1  or  2     (ships at 0 = highest)
  VideoMemoryScaleMP = 0.700000 (ships at 0.80)
  Lower TextureQuality number = HIGHER resolution textures.
  Textures cost VRAM, not FPS. Running them low genuinely makes
  enemies harder to separate from the background, for nothing.

Short of frames at 1440p:
  DLSSPerfModeMP = Balanced     (ships at Maximum Quality)

1080p but on a FAST cpu (9800X3D class):
  You may be GPU-bound. Flip the 1080p variant to VRS = true and
  DLSSModeMP = DLSS.

1440p on a SLOWER cpu (5800X class):
  Use the 1440p variant but set VRS = false and
  WorldStreamingQuality = Low.

Micro-stutter that won't go away:
  Try  GPUUploadHeaps = false  instead of true.
  This controls Resizable BAR. Both files ship "true" because that
  is what the game itself picks on ReBAR-capable hardware (verified
  on a real RTX 5070 install), but plenty of people report "false"
  is what finally killed their stutter. Evidence is genuinely split.
  First thing to A/B test.

360Hz+ panel, or you want no cap:
  MaxFpsInGame = 297   (ships at 237 for 240Hz panels, max is 300)
  Or CapFps = false to remove the cap.

You want the announcer quieter:
  VoiceVolume = 0.000000
  It ships at 1.0 because "enemy UAV above" is information. Music,
  War Tracks, Licensed Music and Cinematic volume are all already
  at 0 - that's noise competing with footsteps.

Want more enemy shadow tells:
  ShadowQuality = High
  Costs frames, but shadows around corners give players away.
  Ships at Low, which keeps shadows present but cheap. Very_Low -
  what most configs use - throws that tell away entirely.

Not NVIDIA:
  AMD:    AmdAntilag2 = true
          AATechniquePreferredMP = FSR AA
          AMDFidelityFX = FSR 3
  Intel:  AATechniquePreferredMP = XeSS


---------------------------------------------------------------
NOTES, HONESTLY
---------------------------------------------------------------

- Every value is INSIDE its documented in-game range. No executable
  edits, no memory edits.

- STLodSkip is 0 in both. Raising it deletes foliage and gives you
  vision through bushes. That's a cheat, not a tweak.

- GraphicsQuality is left at "Balanced" on purpose. It's the preset
  label, not a setting. Changing it can make the game re-apply the
  whole preset over the individual values.

- StaticSunshadowClipmapResolution is left at 512, the value the
  game itself wrote. I don't know what 0 does in this engine and
  I'm not going to guess on your machine.

- Reflex is "Enabled", not "Enabled + boost". Boost raises clocks
  regardless of load - nothing for you when you're CPU-bound, and
  worse on power-limited rigs.

- The 1440p variant's driver fields and the two "Detected" hardware
  fields are blank/zero. I don't own a 9800X3D, so I'm not inventing
  measurements for one. The game fills those in on first launch.

- If you ever share YOUR OWN config, blank these three lines first:
      SoundOutputDevice / SoundInputDevice / VoiceOutputDevice
  They hold Windows audio endpoint IDs that look like
      {0.0.0.00000000}.{BC46A4FD-F2D8-...}
  Correction worth making: an endpoint ID is NOT necessarily unique
  to your machine - I've since seen the identical output-device ID
  on two completely unrelated PCs. But it does broadcast which sound
  device you run, so blank it anyway. Already empty in these files.

  While you're at it, also blank: Monitor, GPUName, LastUsedGPU,
  DisplayDriverVersion, GPUDriverVersion, DetectedFrequencyGHz and
  DetectedMemoryAmountMB. Those four together - monitor model, GPU,
  CPU power score and exact RAM reading - do identify a specific
  machine. Most published configs leak all of them.

- Seasonal updates can overwrite your config. Re-check after patches.
  People will tell you to set the files read-only to stop that.
  Don't: the game then can't save ANY setting you change in the
  menus, and you'll be convinced the config is broken.

===============================================================
