“Valve rolled back AG2, and suddenly my 540 Hz monitor feels broken. Others can’t even tell.”

When the recent midweek patch was released, some players (like me on 540 Hz) immediately felt aiming and tracking so much smoother it was night and day, while others said “what are you talking about? Feels the same.”

Both reactions are actually true - it all comes down to refresh rate and how your hardware interacts with the system. High-refresh players with low or unstable FPS saw the benefits instantly, while most players on 144-240 Hz didn’t notice much at all.

I’ve dug deeper after the recent changes and tried to figure out this phenomenon.

Why high refresh can actually feel worse now

Right now, CS2 ties movement and input back to FPS/frame timing. That means:

• Enemy models don’t move smoothly if FPS isn’t stable.
• Your crosshair input feels inconsistent, updating frame by frame.
• Game performance isn’t really determined by average FPS - it’s the 1% lows that matter most. Even brief dips or spikes can cause your crosshair to stutter, and on high-refresh monitors, those microstutters are extremely noticeable.

On 540 Hz, the monitor shows every tiny stutter or duplicated frame. Even if your average FPS is high (e.g., 300 FPS), those 1% lows make tracking feel broken.

⚡ What is AG2 (AnimGraph 2)

AnimGraph 2 (AG2) in CS2 is the system that controls player model animations. Its goal is to make movement smooth and predictable, so:

• Player animations look natural even at high FPS
• Positions of models are more stable - fewer visual jumps or teleports
• Peekers advantage is easier to read because animations match reality more consistently

AG2 does not change the underlying physics or remove peekers advantage, but it makes the game feel more readable.

Why most people didn’t notice anything

If you’re on 144 Hz or 240 Hz:

• The screen refreshes slower → hiding tiny frame-time issues.
• Your FPS is usually closer to your refresh rate, so pacing feels fine.
• You’re not pushing the game into a state where these problems are obvious.

So for most players, the rollback patch really did feel like “nothing changed.”

Why high refresh felt so good under AG2

Before the rollback, AG2 handled input and movement differently: it decoupled them from FPS, tying everything to a stable simulation clock instead. That meant:

• Enemy movement was smooth and predictable.
• Crosshair input stayed consistent, even when FPS dipped or wobbled.

For players on 540 Hz, especially with lower or unstable FPS, the difference was immediately obvious - tracking felt fluid, and for once, the hardware advantage actually worked as intended.

Why AG2 is a bright future for CS2

One of the most frustrating issues right now is how peekers advantage interacts with high refresh monitors and FPS fluctuations.

• Old system (current FPS-tied setup): Movement is tied to FPS and frame timing. On unstable FPS, the peeker’s model updates unevenly - sometimes appearing “delayed” or “snappy” to the defender. Combined with network latency, this exaggerates peekers advantage, making it feel unfair.
• AG2 system (when active): Movement is tied to a stable simulation clock, so player motion is applied consistently, independent of FPS. Models appear smooth, timing feels accurate, and what you see better matches reality.
• Why high refresh makes the difference obvious: On 540 Hz, you see more “frames of truth.” With the old system, every stutter is visible and peekers advantage feels exaggerated. With AG2, frames line up consistently, making peeks smoother and easier to read for both players.

✅ Summary:

• Old system: peekers advantage feels worse because FPS fluctuations cause jittery models → defenders react to “laggy” peeks.
• AG2: movement is independent of FPS → smoother models, peekers advantage still exists but is less exaggerated, creating a fairer, more predictable game experience.

The paradox right now

• Higher refresh can feel smoother… but only if the game handles input properly.
• With the current FPS-tied system, the higher your Hz, the more microstutters and inconsistencies you notice - making tracking feel worse rather than better.
• That’s why some players are screaming that aiming feels awful, while most on standard setups don’t notice a thing.

What helped me until AG2 returns

After testing different setups, the only solution that truly made the game feel playable on 540 Hz was capping my FPS about 10% below my average. This reduced microstutters and made tracking feel much more consistent.

Other tweaks I experimented with:

• Lowering refresh closer to your FPS (e.g., 300 Hz instead of 540)
• Toggling VRR on or off to see which felt smoother

These adjustments aren’t perfect - nothing feels as good as AG2, but they significantly reduce the jitter that high refresh exposes.