Menu
 

CS2 Animgraph 2 Beta Server Admin Guide (April 2026) - Counter Strike 2 Wiki

CS2 Animgraph 2 — Community Server Admin Guide

Valve dropped the Animgraph 2 beta in early April 2026 and pushed major updates through April 24. It's a from-scratch rewrite of CS2's animation system — a node-based graph that replaces the old state-machine. For community server admins, the relevant facts are: it's beta-branch only, it requires both client and server on the same branch, and the network/CPU savings are real (7–12% FPS, 33% packet-size reduction on senders). This guide covers the install, the configuration changes, and what's known to break.

Branch status (late April 2026): Animgraph 2 is on the animgraph2 beta branch only. The main branch still ships the old animation system. Players and servers must be on the same branch — a main-branch client cannot join an animgraph2 server and vice versa.

What Animgraph 2 Actually Is

Animgraph 2 is the node-based animation pipeline Valve built for Source 2 to replace the legacy Source-1-derived state machine. In CS2 specifically, it changes:

  • Aim-punch handling — full camera motion from external aim-punch sources is now applied based on network state, while bullet-trajectory effects still apply server-side immediately. Translation: visual feedback is smoother but hitreg is unchanged
  • Third-person mirror accuracy — third-person animations now perfectly match what the local player sees in first-person. This kills several "ghost peek" exploits where the model lagged what the gun was actually doing
  • Knife/grenade/weapon-swap animations — fully reworked, no more in-air crouch transition pop
  • Reload animations — XM1014 shells, dual berettas, and several others were fixed in the April 24 update

Installing the Animgraph 2 Dedicated Server

1. Switch the dedicated server to the beta branch

# Linux
./steamcmd.sh +login anonymous \
  +app_update 730 -beta animgraph2 validate \
  +quit

# Windows (steamcmd.exe)
steamcmd +login anonymous ^
  +app_update 730 -beta animgraph2 validate ^
  +quit

App ID 730 is the same; the -beta animgraph2 flag selects the branch. The download is a delta on top of your existing CS2 install, so it's small (~200 MB) if you're already on main.

2. Tell players to opt in

Players must opt their Steam client into the animgraph2 beta branch:

  1. Steam library → right-click Counter-Strike 2 → Properties → Betas
  2. Beta participation → select animgraph2
  3. Wait for the patch to download (~3–5 GB)

3. Server config — what changes

The Animgraph 2 build does not introduce new server.cfg or gamemodes_server.txt keys. Your existing config carries over. Sub-tick networking parameters are unchanged. The notable behavior differences:

  • Reduced bandwidth per player: sender packets ~33% smaller, receiver packets ~9% smaller. You can support more players on the same upload pipe
  • CPU usage drops 7–12% on the dedicated server process under load — measure before you raise maxplayers
  • Demo recording compatibility: demos recorded on animgraph2 cannot be replayed on main-branch clients; keep this in mind for tournament archives

Performance Numbers — Verified

MetricAnimgraph 1 (main)Animgraph 2 (beta)Change
Avg FPS (CPU-bound)baseline+7–12%Improvement
Sender packet sizebaseline−33.69%Improvement
Receiver packet sizebaseline−9.25%Improvement
Server CPU per slotbaseline~−10%Improvement
RAM per slotbaseline≈ sameNo change

These are community-measured numbers from the first three weeks of the beta. They'll shift as Valve continues to push updates — expect Valve to roll Animgraph 2 to main once the data justifies it.

What Breaks on the Beta Branch

  • Most plugins. SourceMod, Metamod, and any binary plugin compiled against the main-branch headers may crash. Test on a staging server before your community migration. Most active plugin authors are publishing animgraph2 builds — check your stack one by one
  • Custom workshop maps generally work, but maps with custom entities tied to animation events may show visual glitches
  • Animation-script plugins (taunts, skins with custom anims) often need updates — Source 2 anim scripts work, anything Source-1-derived breaks
  • Demo replay across branches is not supported (mentioned above)

Should Your Community Server Switch?

ScenarioRecommendation
Casual community / DM serverYes — performance gains are real, your players will appreciate the smoother animations
Competitive scrim serverWait — until the matchmaking pool is on animgraph2, training on it shifts your muscle memory in ways that may hurt on main
Heavily-modded RP serverWait — verify every plugin and custom anim before flipping
Tournament archive serverStay on main — demo compatibility is critical
Public surf / KZ / 1v1 serverYes — the third-person animation fixes alone are worth the switch for these mode types

Rollback Path

If something breaks and you need to revert to main:

./steamcmd.sh +login anonymous \
  +app_update 730 -beta NONE validate \
  +quit

-beta NONE takes you back to the live branch. Your cfg/, custom maps, and demos are preserved across branch switches; only the engine and DLLs change.

Connection Test for the Public Animgraph 2 Server

If you want to verify your client is on the right branch before standing up your own server, the original community animgraph2 deathmatch server is at:

connect 149.28.53.70:27015

You'll get an immediate "wrong build" error if you're on the main branch.

Supercraft's CS2 server hosting supports both main and animgraph2 branches via a one-click branch toggle in the panel. Your config and maps follow you across the switch — no SteamCMD involvement required.

Related Guides

Top