Both are correct, cl_showfps shows integer values only and does some smoothing, net_graph shows decimal values. The change was to allow up to 100.9 FPS in the case of 100 fps_max, and due to sampling this can jump to 101 occasionally. So, by design, side effect of small amounts of jitter due to OS sleep time intervals.
But what we get it's stable 101 fps with max_fps 100, stable 101, not stable 100.9. It's constanlty "due to sampling this can jump to 101 occasionally. "
Rarely seems to fluctuate betwen 101 and 100.9.
value_max meaning that we get below or equal thaht value, not around that, and not value+1, and not up to 0.9.
Because of fps depended physics we need to use fps_max 99 to achive that feel of the game that give us developer cap and fps max 101, if i use fps_max 99.1 it results in stable 100.1 fps, and this give me completely different feel of the game, due of physics.
I think f4k3 is right, topic should be reopen
Indeed, i have fps_max 101 and sometimes i see in net_graph 3 like 101.9 and even 102.x.
Since the fps is no longer limited by a cvar (like developer) now it's just ruined, because some servers automatically force my fps_max on 101 and it's a different movement...
Nothing extracted yet.
Last update changelog says:
"Fixed fps_max to actually run at that framerate, not 1 less"
With fps_max 100, cl_showfps now correctly shows 100 FPS.
net_graph shows 101 FPS though, so I guess that's wrong.