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 designBegin 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.
// 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. 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.
Built locally in your browser. Nothing is uploaded.
// 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
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
ratevalues. CS2’s netcode manages rates differently from CS:GO, and a copied number can reduce rather than improve stability.
Black: average / Blue: 1% 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 completeKeep 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 answersIs cl_cmdrate still a useful CS2 command?
Does an autoexec improve FPS?
What causes packet loss in CS2?
Controls & Peripherals
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.
Counter-Strike 2: CTD, DXGI_ERROR_DEVICE_HUNG & Black-Screen Launch Fixes
Stabilise Counter-Strike 2 on PC: diagnose crash-to-desktop loops, DXGI device-hung resets, black-screen starts, and anti-cheat or DLL launch blocks on Source 2.
Counter-Strike 2: Shader Stutter, Frame Pacing & Source 2 Config Tuning
A measured stutter-hunting routine for Counter-Strike 2: shader compilation warm-up, frame-pacing limits, upscaler presets, and the exact Source 2 settings file to edit.
Counter-Strike 2: Safe Mod Install, Load Order & Post-Patch Conflict Recovery
Install mods on Counter-Strike 2 without breaking the build: framework order, script conflicts after a patch, and a clean rollback path that keeps your saves intact.