Prevent FPS Abuse "Speedhack" exploit

[V3nilla]

If the player's FPS is more than 1000+, then the client's ticks will not match the server's ticks, which is why the player's speed will supposedly be higher, although his speed will be identical to normal, from the outside it looks like the player is lagging and moving fast at the same time (although it is). It works for any SI, as well as for the survivors. Most current PC's can achieve FPS higher than 1000+ in most cases (like watching at sky, floor, or in places where there is practically nothing).

[SirPlease]

I'm not particularly in favor of forcing the majority of users who use fps_max 0 to change their settings.
According to the Valve dev wiki this behavior only occurs on listen servers, but is unconfirmed.

Would it be possible for you to provide a video showcasing the issue on a dedicated server where this would actually have a meaningful impact?
It seems to me that in normal gameplay players wouldn't be able to abuse this, since they simply can't look at areas that would give them the FPS needed to give them pseudo-speedhacks.

Another thing worth mentioning is that while modern PCs could definitely reach into that FPS range when looking at an empty area, most players do not have a "modern" PC. This includes my own setup, which unfortunately means I cannot test it myself 😅

[V3nilla]

It seems to me that in normal gameplay players wouldn't be able to abuse this, since they simply can't look at areas that would give them the FPS needed to give them pseudo-speedhacks.

Players will not be able to exploit this exploit if there is an anti-cheat (like SMAC) with an Anti-Speedhack module. If there is an SMAC on the server, then the player will be teleported back a little, but then from the side of the player who is trying to fix the SMAC, the screen will be jerky (And from the side of the admin, constant spam in the chat from the anti-cheat that some player is suspected of speed hacking). But there is no SMAC in your repository from the beginning, and on many servers that were made based on your repository, this can be done. But the method of fixing this exploit using SMAC is not perfect at all, because SMAC loads the server CPU very heavily, which causes many other problems.

[SirPlease]

I understand the point about SMAC, but my question wasn't about mitigation just yet.
What I'm trying to understand is whether this is a real issue on dedicated servers.

From what I could find, this was indeed an issue in Source games.
However, in both TF2 and CS:GO it either never affected dedicated servers or was patched later on (I can't confirm if the latter happened).
If you're unable to provide a video, a simple confirmation that you've tested it on dedicated servers and are 100% certain it occurs on both listen and dedicated servers would suffice for me.

[V3nilla]

If you're unable to provide a video, a simple confirmation that you've tested it on dedicated servers and are 100% certain it occurs on both listen and dedicated servers would suffice for me.

Yeah, im unable to record this due to heavily tweaked Windows, which causes a lot of problems with recording apps. Im a 100% sure that the problem occurs on listen and dedicated servers(because i have my own 4 servers and i tested this on them).