Pretty shure thats not the fault of AMD but the fault of “anti cheat” Software makers…
Anticheat needs to be sort of zealous to even matter. If you’re gearing yourself towards gaming and then messing specifically with the engine in a multiplayer game, in ways that are notorious for being used for cheating… then it’s kind of on you.
Don’t get me wrong, some anticheat is quite invasive, but still. Necessary evil, fixture of the gaming ecosystem - AMD should’ve known better.
The anti cheat is doing its job: making sure that nothing sketchy is hooking into the game code or dependent libraries.
It’s AMD that should have realised this would be a problem. They know how games are made. They know this stuff exists. They of all people should have seen this coming a country mile away.
I guess? I mean the job of an anti cheat is to make sure that external applications aren’t injecting or hooking core game DLLs to ensure integrity.
But if you make a device for gamers… You should know this is the industry standard for competitive gaming for over 20 years.
Most anti cheats cause problems with everything, the system is 20 years old as you said, it needs to be reworked. Like some users get banned just for playing on Linux…
Anti-cheat on the client should be an anti-pattern. Devs continue to make the mistake of imagining you can control the code running on someone else’s device and waste their efforts there instead of working more on the server (preventative) or analysis (punitive) side.
VAC is way better than no-VAC. cs wouldn’t even be playable if it was full of cheaters like the old days. I still hate it but glad it’s there.
