Controls & Peripherals / Counter-Strike 2 / Source 2

CS2 Subtick, Autoexec, and Packet Loss: A Field Fix

A current-source method for stabilising Counter-Strike 2 frame time and diagnosing packet loss without relying on outdated CS:GO netcode placebo.

Official Steam Store header artwork for Counter-Strike 2.

CS2 inherited a vocabulary from CS:GO and a new engine underneath it. That is a bad combination for copy-pasted advice. The game now uses subtick input and a redesigned network path; an autoexec full of 2019 rate commands is not a performance fix. It is archaeology.

This file treats CS2 as a modern Source 2 shooter. We focus on two separate problems — frame-time stability and packet loss — because they require different evidence and different fixes.

The only autoexec you need to start

Minimal by design

Begin with a short, reversible config and add one line at a time:

  • Set a frame cap just below your refresh rate. Unstable uncapped frames are not competitive.
  • Use one documented network diagnostic, not a stack of rate guesses.
  • Keep the crosshair and viewmodel settings you actually use; they do not affect performance.
  • Record your average FPS and 1% low before changing anything.

Step one: establish the frame path

On a high-refresh monitor, CS2 benefits more from a consistent frame time than from a wildly uncapped average. Set the resolution you can actually hold, then use a cap around 3–5 FPS below the refresh rate to leave room for engine spikes. If your system cannot sustain 240, cap at 144; a stable 144 is better than a stuttering 220.

The autoexec below is deliberately short. It does not use obsolete CS:GO interpolation variables.

<Steam>\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg\autoexec.cfg
// GamePathHub CS2 baseline
fps_max 240
fps_max_ui 120
engine_no_focus_sleep 0
cl_showfps 1
cq_netgraph 1
// Remove cl_showfps after verification if you prefer a clean HUD.
CS2 does not automatically execute this file. Add +exec autoexec.cfg to Steam launch options, or exec it from the developer console after the file exists.

Step two: verify that it loaded

Open the console and type exec autoexec.cfg, or add +exec autoexec.cfg to the launch options. If the console reports an unknown command, the file has a typo or the setting no longer exists in this build.

Config builder / Counter-Strike 2 Source 2

Built locally in your browser. Nothing is uploaded.

Game config directory
// GamePathHub baseline // Counter-Strike 2
// Source 2 autoexec — keep it short and measurable.
fps_max 240
fps_max_ui 120
engine_no_focus_sleep 0
// Optional: lock the refresh path when the monitor supports it.
// fps_max 240
Built for a 8 GB GPU class at a 240 FPS ceiling. Launch once with -console to confirm cvars loaded.

Step three: prove the network problem

Packet loss is not a config bug you can solve with a clever cvar. Verify it with cq_netgraph 1 and the in-game connection quality readout. Then test the path physically:

  • Connect Ethernet directly to the router. If the loss disappears, the Wi-Fi link was the problem.
  • Stop downloads and cloud sync on the network. CS2 cannot send state reliably through a saturated upstream.
  • Disable VPN and third-party “game accelerator” software.
  • Check whether loss affects only CS2. A general upstream fault will show up in another game or a call.
  • Do not set random rate values. CS2’s netcode manages rates differently from CS:GO, and a copied number can reduce rather than improve stability.
CS2 / 1080p competitive frame-time check
Scale 0–390 FPS
Black: average / Blue: 1% low
Uncapped average 382 FPS / 221 low
Cap 240 239 FPS / 232 low
Cap 144 143 FPS / 140 low
Cap 240 + Discord overlay 238 FPS / 190 low

Bench route: offline workshop map with smoke and molotov stress. i9-13900K, RTX 4080 SUPER, 32 GB DDR5. Native 1080p, high preset, no upscaler.

The uncapped average is the trap: it produces a bigger number while the frame-time consistency gets worse. The cap line is the practical result. The overlay row is a reminder that even a “light” overlay can cost 40 FPS at the 1% low in a smoke-heavy scene.

Mouse path and peripheral checks

CS2 is sensitive to USB polling and Windows pointer settings. If aim feels inconsistent but frame times look stable:

  • Disable pointer acceleration in Windows and confirm the game’s raw input setting.
  • Use a wired connection or a wireless receiver that is not behind a USB hub.
  • Reduce polling rate from 8 kHz to 2 kHz if your CPU is already loaded. The marginal latency gain may not be worth the CPU overhead.
  • Remove mouse companion software from startup while testing, then re-enable one profile at a time.

CS2 stutter and packet-loss split

0 / 7 complete

Keep your launch options short

Use +exec autoexec.cfg only after the file exists and the commands are valid. -novid, -high, and -console are the only other flags worth trialling. Avoid undocumented memory flags and “unlock FPS” packs. CS2’s frame pacing is not improved by disabling security or driver features.

If packet loss is confirmed and persists over wired Ethernet on multiple games, involve your ISP and capture evidence. No autoexec will fix a line problem, and pretending otherwise wastes your evening.

Did this fix work on Patch Update 1.40.8.3 — subtick network fixes?

One click. No account. Your vote is stored in this browser and de-duplicated per file.

Verified against Update 1.40.8.3 — subtick network fixes. Votes are local-only telemetry.

Counter-Strike 2: bench questions

3 answers
Is cl_cmdrate still a useful CS2 command?
No. Treat CS2's network stack as its own system. Modern configs should avoid copied CS:GO rate and cmdrate stacks. Use a minimal autoexec with documented settings and verify with net graph.
Does an autoexec improve FPS?
Only if it changes a setting that actually affects your system, such as a frame cap or a UI element. Most CS2 performance comes from resolution, GPU state, and a stable refresh path, not a long list of console commands.
What causes packet loss in CS2?
Common causes are Wi-Fi interference, a saturated upstream, a bad router QoS rule, a VPN, or a driver power-saving mode. Start with a wired connection and test packet loss both ways before touching game config.
Filed under

Controls & Peripherals

Patch tested: Update 1.40.8.3 — subtick network fixes

This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.

Continue the file stack Game hub ↗
Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.