UPDATED: The critical bug has been “fixed”.

If you activate the AMD graphics function, you could be banned from Counter-Strike 2, which launched on September 27.

First published October 14.

Updated, October 17, 11:23 p.m.:

With GPU driver 23.10.2, AMD has deactivated the “Anti-Lag+” function that blocks CS2 triggers and can cause players in other games to be kicked from online play because the function modifies the game code.

Also new to the driver is support for Assassin’s Creed Mirage, The Lords of the Fallen, and Forza Motorsport.

This is what AMD said about the update:

“AMD has received reports of some games triggering anti-cheat for players when AMD Anti-Lag+ is enabled. To address this issue, we have released AMD software: Adrenalin Edition 23.10.2 driver that disables Anti-Lag+ in all supported games – “We recommend that players use the new driver. AMD is actively working with game developers to find a solution to reactivate Anti-Lag+ and help bring back players affected by the anti-cheat ban. We will provide more information as it becomes available.”

Correct this also:

• A crash occurred while playing Starfield on Radeon RX 7000 series
• Driver crashes while playing Counter Strike 2 with MSAA or FSR enabled on some AMD graphics products such as Radeon RX 7900 XTX.
• More stable performance in Counter Strike 2.
• EA SPORTS FC 24 cannot open on some AMD graphics products, such as the Radeon RX 7800 XT.
• System freezes or faces black screen when playing video files on Radeon RX 6000
• The screen may freeze randomly after changing the encoding format while streaming certain games using AMD Link.
• Crash in Call of Duty: Modern Warfare II when Radeon Anti-Lag is enabled.

Known issues:

• Audio may sometimes become out of sync with video when recording from AMD Software: Adrenalin Edition with AV1 codec.
• Image disturbances can be observed in Forza Motorsport when ray tracing is enabled.
• Flickering can be observed briefly in Total War: Pharaoh’s menus after changing graphics settings.

Valve warns – waiting for AMD

In fact, it is Valve itself that is reporting the bug in X, so there is no doubt that one should not do the following: Do not enable Anti-Lag/+ with AMD hardware. “Any tampering with the CS code will result in a VAC ban.” So it’s not like that maybe It happens, but guarantee if you connect to play with the function activated.

So what exactly is AMD’s technology that’s screwing it up? AMD launched Anti-Lag+ technology in September. The function activates “frame alignment” ie Game code “For better synchronization of image updates to reduce lag and improve the gaming experience.”

When will this be fixed? It’s not a good thing to say because Valve is waiting for new drivers from AMD before they can “identify affected users and then remove the ban.”