CS2’s Telemetry HUD is the practical starting point for frame-rate and network information. The old CS:GO net_graph instructions should not be copied unchanged.
Open Settings → Game → Telemetry and choose which indicators to display. Valve documents the feature in its Source2 Telemetry HUD guide. Use an always-visible option while investigating, then return to the presentation you prefer.
| Indicator | Question it helps answer |
|---|---|
| Frame time and FPS | Is local rendering steady? |
| Ping | What round-trip network delay is observed? |
| Network delivery indicators | Are packet delivery or timing problems being reported? |
A low average ping does not rule out delivery problems, and a high FPS average can hide unstable frame times.
cl_showfps 1 can provide a simple FPS display. It should not be presented as complete CPU/GPU monitoring or as a full substitute for the network HUD. Old claims about every numbered mode need checking against the current build rather than assuming the highest number is the most useful.
Note the map, approximate time, settings and exact symptom when a problem occurs. Compare a local performance issue separately from a service outage. The tickrate explainer distinguishes tickrate, rate, FPS and ping.
Settings, Game, Telemetry.
Use the current Telemetry HUD rather than relying on old CS:GO instructions.
Yes. It is a simple FPS option.
No. FPS information alone is not a complete network diagnosis.
No. They measure client rendering and server simulation respectively.
No. Delay averages and delivery quality are different signals.
No. Frame-time variation can still cause visible stutter.
The symptom, time, map and relevant telemetry, then compare one change at a time.