[ad_1]
Further report from VideoCardz.com has uncovered more issues stemming from AMD’s Anti-Lag technology and the way its implemented. Yesterday, Valve made an announcement and confirmed that AMD Anti-Lag+ is causing players to get flagged for violation of Valve’s Anti-Cheat which results in a ban. VAC bans are usually permanent but Valve has stated they are awaiting AMD’s update to reverse false bans.
AMD has responded by pulling the latest driver update which enables Anti-Lag+ on supported games.
The issue revolves around the way AMD Anti-Lag+ is implemented which is done via piggy-backing on the game’s DLL. While a very streamlined approach, necessitates alerting anti-cheat services of their implementation to get whitelisted. Miguel Malvar Molina aka DigitalAnomaly explains it like so:
This is why NVIDIA’s Reflex tech requires explicit implementation by developers, which avoids needing to do DLL injection since the code is built-in.
AMD’s approach (via Detours/DLL injection) is similar to how game capture works in XSplit and OBS but the difference is, game capture doesn’t try to modify how graphics are rendered and XSplit and OBS DLLs are whitelisted in all major anticheat engines, including VAC.
AMD’s approach is commendable though since this allows their tech to theoretically work with any game but of course, they should coordinate with game devs that use anti-cheat protection to avoid getting flagged.
That said, that means that any game supporting Anti-Lag+ but also has Anti-Cheat systems in-place can be hit with false bans and other issues. It has been verified that activating AMD Anti-Lag+ while playing Counter-Strike 2 can trigger a VAC ban. This is because the AMD technology, by accessing the game’s DLL files, introduces unauthorized modifications that are flagged as potential cheating.
AMD has advised players to avoid using their Anti-Lag+ technology with Counter-Strike 2 until a fix is available. While AMD hasn’t clarified if Anti-Lag+ is compatible with other competitive games, it’s evident that activating this feature might lead to unforeseen issues.
Several gamers have noted that titles like Call of Duty MW2 tend to crash more frequently when operated on Radeon RX 7000 series graphics cards. The recommended workaround is to deactivate Anti-Lag+ within the AMD Software. This issue has persisted for about three weeks, with AMD representatives acknowledging ongoing investigations.Some reported issues include:
Call of Duty/Warzone:
Apex Legends
Many gamers wonder why NVIDIA’s Reflex technology doesn’t exhibit similar problems. Although Reflex is prevalent in numerous competitive online games, its mechanism differs from Anti-Lag. Reflex isn’t integrated at the driver level but is provided as a distinct library that game developers incorporate separately.
AMD’s strategy was to offer a simple driver-level solution. However, this method appears to clash with some games, resulting in compatibility issues and unauthorized DLL file modifications. This distinction in deployment might explain why Reflex doesn’t face the challenges currently associated with AMD Anti-Lag+.
For now, gamers are advised to be cautious when activating Anti-Lag+ in online games, at least until AMD provides official guidance. Given the recent issues with Counter-Strike 2, it might be prudent to delay using new features immediately after their driver integration. Fortunately, Anti-Lag+ is designed for the Radeon RX 7000 series, so those on older hardware should remain unaffected.
[ad_2]
Deixe um comentário