Counter-Strike 2 gives you a frame counter that looks great and a game that sometimes does not feel great. You can sit on a high average in a quiet round and still feel the crosshair drag, or watch the frame time spike the moment a smoke blooms or a molotov lands. The average is the number people post. It is also the one that explains the least.

What decides whether a flick lands is the delay from your hand to the screen and how deep your worst frames dip. This guide goes through the whole chain for CS2 on Source 2: the video settings worth changing, the launch options that still do something, what VAC cares about, Windows, your GPU driver and your connection. There is a 60-second fix first if you are about to queue.

The 60-second fix before you queue

• Turn on NVIDIA Reflex in Video, Advanced Video. It keeps the render queue short, which is the biggest latency win in the menu.
• Close the browser and anything streaming. A video tab with hardware acceleration keeps the GPU busy and the CPU waking up.
• Use a high performance power plan. On Balanced the CPU parks cores between rounds, then pays to wake them when the round starts.
• Check that your mouse polls at 1000Hz and your monitor runs at its real refresh rate in Windows display settings. Both are often wrong for months.

Why CS2 can feel worse than the number says

1% lows, not the average

CS2 frame rates are spiky by nature. Smokes, molotovs and a full site of players all cost frames at the same moment, and that moment is the gunfight. A steady line feels better than a higher average with deep drops, so the number to improve is the 1% low.

Sub-tick changes what you notice

Source 2 replaced the old tick timing with sub-tick: the server knows the exact moment you clicked between ticks. That rewards a consistent input chain. If your frame times jump around, the game still registers your click at the right time, but what you saw when you clicked was late, so it feels like the game is lying to you.

The first rounds after an update

After a game or driver update CS2 compiles shaders as it meets new effects. The first few rounds on a map can hitch even on a fast PC. That is expected and goes away, and it is a bad moment to judge a settings change.

In-game settings that actually matter

CS2 is mostly limited by the CPU on mid and high end PCs, so dropping every graphics option to the minimum often changes less than people expect. These are the settings with a real effect.

Setting	Recommended	Why
NVIDIA Reflex Low Latency	Enabled (or Enabled + Boost)	Keeps the render queue short. Boost also holds GPU clocks up.
Wait for Vertical Sync	Disabled	VSync adds at least a frame of delay.
Boost Player Contrast	Enabled	Players stand out from the background. It costs very little.
Multisampling Anti-Aliasing	2x or 4x MSAA, or None on weak GPUs	CS2 looks rough without it, and at 1080p the cost is moderate.
Shader and Particle Detail	Low	Cheaper smokes and effects in the moments that matter.
FidelityFX Super Resolution	Disabled	Upscaling softens the image at range. Use it only if the GPU really cannot keep up.

Leave texture detail where your graphics card's memory allows. It costs memory, not frame time, until the memory runs out.

VAC, and what is safe to change

CS2 is protected by Valve Anti-Cheat. VAC looks for software that reads or changes the game's memory, injects code into the game or otherwise interferes with it. Changing Windows power settings, driver options, the network adapter or scheduled tasks is ordinary system configuration and a different category of thing.

Nobody can honestly promise that a tool is invisible to an anti-cheat, so we do not. What we can say is what RIP Tweaks does: it changes Windows and driver settings, and it does not read CS2's memory, inject anything into it or modify its files. The longer answer is in is RIP Tweaks safe and will it get you banned.

Launch options that still matter

Most launch option lists online were written for CS:GO. Source 2 dropped or changed many of those flags, and a few of them make things worse. The safe approach is to leave the box empty and add one option only when you know what it does.

• A frame cap. With Reflex on, an uncapped frame rate is fine. If your GPU runs hot or loud, a cap a little above your refresh rate (the fps_max console setting) keeps it steady.
• Skip thread and priority flags. Old lists add options that force thread counts or process priority. The game and Windows handle the first. The second is better done per game, and only for CS2, which is what the launch panel below does.

Windows is the real bottleneck

CS2 leans on a few fast CPU cores, so anything else that wakes up on those cores turns into a dropped frame in the middle of a duel.

• Power plan and core parking. On a balanced plan the CPU drops its clocks and parks cores whenever it thinks it is idle, and waking them costs time at exactly the wrong moment.
• Background apps. Launchers, overlays, RGB tools and updaters each wake up on their own schedule. One is nothing. Twenty of them are a stutter every few seconds.
• Timer and scheduling. A coarse system timer makes the game wait longer for its turn, which shows up as uneven frame pacing rather than lower average FPS.
• Storage. A nearly full drive slows every asset load, and that is felt as a hitch the first time something new appears.

All of it can be done by hand if you know which services are safe to touch and how to undo them. We wrote that route up in fixing micro stutters on Windows 11.

What RIP Tweaks does for Counter-Strike 2

RIP Tweaks finds Counter-Strike 2 on its own when it is installed through Steam. If it is missing from the Games page, use Add Game and point it at cs2.exe. Clicking the game opens a launch panel with two modes.

• Balanced (free) quiets background apps and applies GPU Priority, I/O Priority and Purge RAM Cache before the game starts. It touches nothing risky.
• Performance (Premium) adds Disable Segment Heap and Unbind CPU 0, which keeps the game off the processor core Windows uses most, and can close Explorer for the session. Your taskbar comes back when you stop.

Those settings are tied to cs2.exe only, not to your whole PC, and you can untick any of them before you launch. With an NVIDIA card you can also apply a driver profile built for Counter-Strike 2 from the same panel. The system wide tweaks for power, timers, network and input apply to every game, with a restore point created first.

What it does not do: it does not change Counter-Strike 2's own settings, read the game's memory or touch its files. The in-game section above is still yours to set, and the Games page guide explains the rest.

GPU control panel

NVIDIA: set Power Management Mode to Prefer Maximum Performance for Counter-Strike 2 and leave Vertical Sync off. Low Latency Mode does not matter while Reflex is on in game, because Reflex takes over the render queue.

AMD: turn on Anti-Lag in the Adrenalin profile for the game, and leave Radeon Chill and Wait for Vertical Refresh off.

Then update the driver, and do it cleanly. A driver installed on top of years of older ones carries their leftovers with it, and a fresh driver also means Counter-Strike 2 rebuilds its shader cache, so expect the first match after an update to stutter once.

Ping, packet loss and sub-tick

With sub-tick, a clean connection matters more than a low one. A steady 40ms beats a 20ms line that jumps, because every jump moves where the server thinks you were. Packet loss and jitter cost more duels than raw ping does.

• Use a cable. It beats every software network change put together.
• Turn off power saving on the network adapter, which can put the card to sleep between packets.
• Stop downloads, cloud sync and console updates on the same network while you play.
• Pick the closest region in matchmaking settings, and check the scoreboard for loss rather than ping alone.

The rest is covered in how to lower ping in games, including the changes that do not help.

Seeing whether any of it worked

Steam has a frame counter built in (Steam settings, In Game, In-game FPS counter), and the NVIDIA app or AMD Adrenalin overlay adds frame times on top. Watch your 1% lows across a few matches before and after a change, not your average, and change one thing at a time.

For a proper recording, free tools such as PresentMon or CapFrameX log every frame and calculate the 1% and 0.1% lows for you. If a change did not move the lows, it did not help, however much the average went up.

The checklist

• Reflex enabled, VSync off, Boost Player Contrast on
• Shader and particle detail low, MSAA to taste, FSR off
• Launch options empty unless you know exactly what each one does
• Monitor at its real refresh rate, mouse at 1000Hz
• High performance power plan, background apps closed
• Driver clean installed, Prefer Maximum Performance for CS2
• Wired connection, adapter power saving off, nothing downloading
• 1% lows measured before and after, one change at a time

Frequently asked questions

Will optimizing my PC get me VAC banned?

Changing Windows and driver settings is normal system configuration, not what VAC looks for. VAC looks for software that touches the game's memory or process, and RIP Tweaks does not. Be wary of anyone who promises a tool is invisible to anti-cheat.

Why does CS2 stutter when a smoke goes off?

Smokes and fire are expensive effects that land on the CPU and GPU at the same moment. Lower shader and particle detail, make sure nothing else is using the CPU, and watch whether the 1% lows improve.

Should I lower my resolution for more FPS?

Only if your graphics card is the limit. Most players are CPU bound in CS2, so a lower resolution mostly costs clarity. Many players use a stretched resolution for feel, which is a preference rather than a performance fix.

Do CS:GO launch options still work in CS2?

Many do not, and some cause problems. Leave the field empty and add options one at a time, measuring each.