CS2 - Hilo oficial

9.2ms is the frame time. If every frame is exactly the same, it will be 1000 / the FPS. However the FPS show the average FPS over the last second or so, while the frame time number will display the worst frame, and when a spike happens, it will hold that spike for a bit. So both numbers are measuring your "frame rate" but the number on the left is much, much more useful as a measurement of the quality of your experience.

We included the FPS readout because that is what players are used to, and decades of expectations cannot be changed overnight. But really, it is a pretty poor metric for understanding performance for two reasons. First, very small changes can seem like huge changes. The difference between 2ms and 2.5 ms is pretty small! But it's 100FPS! And 100fps is also the same as the difference between 5 and 10ms. So talking about a gain or loss of a certain number of fps is just really not very meaningful. Talking about a ms frame time change, or a percentage change, is much more helpful for understanding. The second reason is that the average case performance is much less important compared to the worst case (or 1% frame rate). If you get a big spike, that spike is the only thing that matters. The ms readout on the left shows the worst frame over the past second, and holds spikes on the screen longer.

The other two numbers are the packet misdelivery rate, in the upstream and downstream directions. When those numbers are nonzero, it means there is some sort of network problem. That is the tl;dr version. If you want to know a bit more detail: You can mostly think of "misdelivery" as packet loss, but this also includes packets delivered out of order. But not all out of order delivery is included. In some cases, if the packets are delivered in rapid enough succession, we can automatically correct it at the packet level. Those packets dont count as misdelivered. If they arrive out of order and further apart, we dont correct it at the packet level and it will count as "misdelivered", but we can still often correct at the fragment reassembly level, so unfortunately this can be a pessimistic indicator for some network connections. There is some room for improvement here, to provide an indicator that more closely measures problems that are really causing to gameplay problems, but in general if this number is high (1% is pretty high), there is probably something going on with your network connection.

Neither number has anything to do with choke.

There is also another number that can show up occasionally. If you see "slow server frame" it is referring to a problem on the game server.