The relevance of FPS for srcds

[BehaartesEtwas]

Monk, don't mix up the engines. The internal heartbeat of srcds is not fixed to 20.

@molli: fps_max must be an integer afaik. But fps_max is a limit, not the target value. if you keep in mind that the engine sleeps always an integer number of 1ms between the frames (at least it tries to do so... the result also depends on the kernel etc.), you should use a slightly higher fps_max value to obtain 66 2/3 fps, e.g. fps_max 70 (fps values between 66 and 70 are not possible to reach with an integer number of milliseconds!). Usually the FPS will slightly lower than 66 2/3 automatically, as frame processing also costs time, so the actual time between two frames is 15ms + the calculation time.

Problems occur, if the calculation time or some wakeup latency gets too big, in that case you can also reach values between 66 and 70 or so. To avoid those effects I use a ld_preload-lib to make the timing as close as possible to 15ms resp. 66 2/3 fps.