Sign up with Google
Fulcrum29
Honorary Master
I just find it strange. A couple of days ago Gabe Follower also posted this,
whatever VAC is looking for seems a bit over aggressive. VAC praises itself for not being a kernel-level anti-cheat, but it is sure diving deep into your system processes and resource usage. In software modification, a false positive is treated as a positive by anti-cheat systems unless marked to be ignored.
In my instance of being kicked by the server, it was random, something from Valve must have been actively running and scanning in the background. Just maybe, it was due to the ping spikes. I won't know, only Valve has that telemetry.
I also received a wide VAC-secure server time-out, so I couldn't rejoin or join any VAC-secured server.
For now, since I have never previously experienced this I will assume that Valve hasn't optimised their latest version of VACnet. I didn't receive a VAC ban, just a VAC timeout. Maybe they are in the process of collecting data for further optimisation, and whitelisting.
In the past, it was possible for cheaters to basically run panic attacks against other clients who had joined the server. Essentially manipulating the packets received by the server, by inducing it from a rogue client. This was remedied a long time ago, since cheaters used to crash the server after a comp to prevent the creation of a demo, hence no Overwatch, hence nothing for the algorithm.
I have even played CoD for a while. No issues.
