Friday, October 13th 2023
Enabling AMD Anti-Lag+ in Counter Strike 2 Will Get You Banned
With the release of AMD Software Adrenalin drivers version 23.10.1 WHQL, AMD has added Anti-Lag+ support for Counter Strike 2, but it appears that this will only result in a VAC (Valve Anti-Cheat) ban. Apparently, the Anti-Lag+ feature is implemented by detouring engine dll functions, and any tampering with CS code will result in a VAC ban.
Valve was keen to note that once AMD ships an update, it will work on identifying affected users and reversing the ban. Luckily, the Anti-Lag+ technology only works on Radeon RX 7000 series RDNA 3 graphics cards, so it could be a limited number of Counter Strike 2 players. The issue comes as a surprise considering that Anti-Lag+ has already been implemented in various games, including competitive ones like Apex Legends, PUBG: Battlegrounds, Fortnite, and others, and only has issues with Counter Strike 2 and its VAC system. Hopefully, AMD will fix the issue pretty soon and we will keep an eye out for an update.
Source:
Counter Strike 2 Twitter
Valve was keen to note that once AMD ships an update, it will work on identifying affected users and reversing the ban. Luckily, the Anti-Lag+ technology only works on Radeon RX 7000 series RDNA 3 graphics cards, so it could be a limited number of Counter Strike 2 players. The issue comes as a surprise considering that Anti-Lag+ has already been implemented in various games, including competitive ones like Apex Legends, PUBG: Battlegrounds, Fortnite, and others, and only has issues with Counter Strike 2 and its VAC system. Hopefully, AMD will fix the issue pretty soon and we will keep an eye out for an update.
102 Comments on Enabling AMD Anti-Lag+ in Counter Strike 2 Will Get You Banned
Not just EAC, but also Vanguard. It can feel like most others are hacking, if you have packet loss.
Fun fact: I can enjoy Halo CE online multiplayer on a server with 280 ms ping with no packet loss and it plays so much better than low ping with packet loss!
The issue is with anti-lag+
Sorry, my display language is in Hungarian, but it is good for the point:
This is the default setting, so practically everybody is safe
While I am still puzzled how AMD's CPU department is 1337 and their GPU department is tumbling from one pile of poop into the next, let's not fall into the AMD bashing. There where tons of other innocent players banned from games in the past for running other software (f.e. RGB software). The lazy anti cheat providers who straight out "pro-active" ban players are as well to blame here.
However, considering that nV Reflex is already integrated into the game, AMD obviously "had no time" for reaching out Valve to implement own advertised features. As they are to preoccupied with MI/AI/enterprise stuff for serious gentlemen with serious funds. Why would they worry about all these "menchildren" peasants and their silly games. Thus, why bother with testing the consumer drivers then?
On the other hand, CS2 was in development not so long time ago. AMD obsiously had time to introduce their SDK to Valve, while both CS2 and Anti-Lag+ were in beta.
I mean if you want to make that argument then AMD needed to program this differently.
Personally I once got a VAC ban because the ping was too slow, yeah you read that right. Considering I left CS:GO because aimbots were rampant, I'm kinda surprised they are starting to get serious about fighting cheaters again.
In some games, said bans will display alongside VAC bans on a Steam profile, but the profile will remain in good standing with VAC, and game bans apply on a per-title basis.
couldn't malware that's intercepting, inspecting, and altering TCP/IP packets
or
bad hardware that's 'inconsistently' dropping packets
also 'trigger' an actual VAC Ban?
I'm asking/mentioning as I recall devices for the Xbox 360 that did similar, and were a PITA for msft to detect and ban.
IIRC, the eventually-found un-bannable 'trick' was using a physical switch on one of the Ethernet conductors/pairs, to simulate (on-demand) an 'ISP/Network problem' while not-entirely disconnecting the 'hacker/exploiter'.
If done quick-enough, an exploiter could 'freeze' everyone else in the game (they hosted),
frag them, then re-enable proper LAN/WAN function.
I wonder if VAC has a detection mechanism for this kind of dumb hardware-level TCP/IP exploit?
Most games use server authoritative methods.
Sounds like a lawsuit.
All sounds like a good way for Valve to make a buck.