Start with the recommendations below. Change one setting at a time and compare an offline/practice run before a match. These are performance-first starting points, not a measured best preset for every PC. Keep your own resolution, sensitivity, key binds, controller dead zones and field of view.
Supported graphics files (create them by saving settings in the game first):
<Steam>/userdata/<your numeric account>/730/local/cfg/cs2_video.txt. Exit Steam before capture/apply. Only the registered Steam installation and its default userdata path are accepted.Call of Duty/players/options.*.cst or s.1.0.*.txt, .txt0, .txt1. Pick the file modified by the current Warzone build, not another Call of Duty title. Other versions/locations use the in-game checklist only.%LOCALAPPDATA%/EA SPORTS FC 27/fcsetup.ini or Documents → EA SPORTS FC 27/fcsetup.ini. Only an existing recognized local file is supported. If your build uses another format or only cloud storage, use the checklist in game; Apply will stop rather than guess.| Setting | Starting point |
|---|---|
| Display | Fullscreen, highest monitor refresh; keep preferred resolution/aspect ratio |
| V-Sync | Off for the latency-first, tearing-allowed option |
| Frame cap | Start uncapped with Reflex; compare a sustainable in-game cap if frame times or thermals are inconsistent |
| NVIDIA Reflex | Enabled recommended for FPS/latency balance; compare Enabled + Boost if prioritizing latency over heat/power and possible FPS loss |
| AMD | Enable in-game Anti-Lag 2 on supported GPU/driver; no old Anti-Lag+ injection |
| Quality | Start Low; anti-aliasing None or lowest; effects/shaders/particles Low |
| Visibility | Preserve player visibility/contrast; compare dynamic shadows All for tactical information against its GPU cost |
| Upscaling | Native first; lower resolution/upscale only if GPU limited and the image remains clear |
Valve recommends maximum refresh and supports a separate smoothness option: G-Sync/FreeSync where available; with NVIDIA G-Sync use V-Sync and Reflex together. This avoids tearing, while latency-first uncapped play with V-Sync off can be faster. Keep these as separate comparisons. Do not stack arbitrary -high, -threads, tickrate, timer or registry packs. Valve now restricts changing fps_max while connected to a server; set the cap in the main menu.
| Setting | Starting point |
|---|---|
| Display | Fullscreen Exclusive if available, highest monitor refresh |
| Gameplay V-Sync | Off for latency-first play |
| NVIDIA Reflex | On; compare On + Boost, especially if CPU limited; heat and power can rise |
| AMD | In-game Anti-Lag 2 only if the current game and GPU expose it; otherwise compare supported driver Anti-Lag using the existing AMD controls |
| Quality | Low preset; reduce shadows, volumetrics, particles, reflections and ray tracing where offered |
| Textures | Low/Normal within available VRAM; watch streaming stalls rather than maximizing an arbitrary VRAM percentage |
| Blur / depth of field / film grain | Off or 0 where offered for a clearer image |
| Frame generation / driver Smooth Motion / AFMF | Off for this competitive profile; generated display frames do not increase input sampling |
| Render resolution / upscaling | Native 100% first; if GPU limited compare DLSS/FSR Quality, then Balanced/Performance if needed for your target FPS |
| On-Demand High-Quality Streaming | Minimal where offered, to reduce streaming bandwidth |
| Frame cap | Uncapped first with Reflex; compare a sustainable cap using the game's limiter if frame times fluctuate |
Let shaders finish before testing. Activision recommends current Windows updates and its supported driver versions; do not blindly downgrade to one permanent driver. Menus and configuration names change between Call of Duty releases. A profile for cod.exe is useful only when your current Warzone actually runs that executable. Other executable names must be selected in NVIDIA App manually.
| Setting | Starting point |
|---|---|
| Graphics preset | Performance (official FC 27 preset), then lower individual costly options if needed |
| Enhanced Ultra Visuals | Off |
| Display | Highest monitor refresh; Fullscreen if offered, keep preferred resolution |
| V-Sync | Compare Off for latency-first play; if tearing is distracting compare VRR within its supported range |
| Frame rate | A target your PC can sustain during gameplay; compare uncapped versus a stable cap, rather than chasing average FPS with large spikes |
| Hair / crowd / grass / cloth / shadows | Low/Off where available; use the in-game VRAM indicator |
| Motion blur / frame generation | Off where offered |
| NVIDIA / AMD | Supported per-game driver settings; no FC 27 Reflex support is assumed |
Test offline Kick Off first. If that is smooth but online matches feel delayed, compare EA Connection Quality (ping, jitter and loss); registry or graphics changes cannot remove server/distance delay. EA specifically notes that high average FPS can coexist with poor responsiveness, and recommends lowering an unsustainable target, reducing graphics, closing heavy background apps and checking dual-channel RAM. FC 27 recommends an SSD.
The three Apply NVIDIA profile buttons explicitly target cs2.exe, cod.exe or FC27.exe using the same documented NVAPI controls as the existing Fortnite/VALORANT profiles: prefer maximum performance, V-Sync Off, highest refresh preference, driver FPS limiter Off. Original overrides are saved in the existing GPU recovery journal. Restore GPU profiles covers all five games. These buttons do not enable Reflex or frame generation. V-Sync Off is the latency-first choice; choose the smoothness/VRR alternative in the driver/game yourself.
Existing AMD controls remain supported driver controls with global scope; per-game overrides can take precedence. Prefer the in-game Anti-Lag 2 integration where available. The app never injects into games or modifies anti-cheat, game binaries, drivers or game memory.
Use the same scene, resolution, cap, driver and game version for each comparison. Warm up and let shader compilation finish. Record average FPS, 1% lows, frame-time spikes and, when exposed, PC latency. Repeat multiple runs. A configuration match is not an input-to-display measurement. No zero-delay, maximum-FPS, fixed process-count or future-update guarantee is possible.
Quality choices such as Low, blur Off and frame-generation Off are LeCoreOS performance/clarity recommendations informed by these sources, not an official universal game preset. No public stable writer schema for every game build was found; local replay uses only your existing game-written values.