AMD’s Radeon Anti-Lag 2 promises the same input-lag cuts that made Nvidia Reflex a staple in competitive shooters, but the driver panel gives almost no hint of what you’re actually turning on or whether your game even supports it. Radeon owners running Counter-Strike 2, Valorant, or Dota 2 in September 2026 are stuck guessing between three overlapping features (Anti-Lag, Anti-Lag+, and Anti-Lag 2) that AMD has rebuilt twice since 2023. This guide walks through the current setup process step by step, on AMD Software: Adrenalin Edition 26.x, and flags exactly which games get the full benefit and which don’t.

Most driver-panel writeups treat Anti-Lag 2 as a single checkbox you flip once and forget. That’s not how it works in practice. The feature depends on a matching driver version, a specific GPU architecture, and a game that has shipped AMD’s SDK integration on its own release schedule, and those three things drift out of sync more often than AMD’s marketing suggests. By the end of this walkthrough you’ll know exactly which of your games can use it today, which ones are stuck on a fallback, and how to prove the improvement with your own numbers instead of trusting a driver release note.

What AMD Anti-Lag 2 Actually Does

Anti-Lag 2 shortens the gap between a mouse click and the frame that shows the result on screen. It does this by timing when the CPU hands work to the GPU, holding back CPU-bound frames just enough that the render queue never builds a backlog. AMD’s own release notes for the Adrenalin 24.5.1 technical preview claimed “up to an average of 37%” latency reduction in Counter-Strike 2, measured across an RX 7900 GRE, RX 7800 XT, RX 7600 XT, RX 7700S, and a Ryzen 7 8700G with Radeon 780M graphics. Tom’s Hardware later measured Anti-Lag 2 pushing CS2 input lag down to roughly 11 ms, which the outlet called on par with Nvidia Reflex’s advertised sub-15 ms figures in the same game.

The version that matters here replaced an older, riskier one. Anti-Lag+ launched on RX 7000-series cards using shader injection at the driver level, and by late 2023 AMD confirmed it was triggering anti-cheat bans in Call of Duty and other titles. AMD shipped Adrenalin 23.10.2 specifically to disable Anti-Lag+ across every supported game while it rebuilt the feature from scratch. Anti-Lag 2 is that rebuild. Instead of injecting code into a game’s shaders, it requires the developer to integrate AMD’s SDK directly, which is why it only works in a short list of titles rather than as a universal toggle.

The mechanics matter for troubleshooting later, so it’s worth understanding the pipeline in plain terms. A normal render loop lets the CPU queue up several frames of work ahead of what the GPU is currently drawing, which keeps the GPU fed but means the frame you see was decided on several milliseconds before it appeared. Anti-Lag 2 inserts a pacing signal that tells the CPU to wait until just before the GPU needs the next frame’s input, shrinking that queue down to roughly one frame instead of three to five. AMD’s SDK, published publicly on GitHub, documents this as the difference between a “green counter” of 3 to 5 frames without the feature and 1.0 to 2.0 frames with it active and working correctly. That’s the number you’ll be checking for once the setup steps below are done.

Prerequisites: GPU, Driver, and Game Requirements

Before touching any settings, confirm you actually qualify. Anti-Lag 2 needs three things lined up: RDNA-based hardware, a driver new enough to include the SDK hooks, and a game that has done the integration work on its end.

  • GPU: any RDNA-architecture Radeon card or APU, from the RX 5000 series (RDNA 1) through RDNA 2, RDNA 3, and RDNA 4, plus Ryzen 6000-series and newer APUs that use RDNA graphics instead of older GCN silicon
  • Driver: AMD Software: Adrenalin Edition 24.6.1 or newer for DirectX 11 titles, 24.7.1 or newer for DirectX 12 titles. As of September 2026 the current branch is Adrenalin 26.8.1 (WHQL Recommended, released August 20, 2026) with 26.9.1 available as an optional update
  • OS: Windows 10 or Windows 11, 64-bit
  • Game: officially, only Counter-Strike 2, Dota 2 (DirectX 11 path), and Ghost of Tsushima DIRECTOR’S CUT ship with native Anti-Lag 2 integration as of this writing, with AMD listing more titles as “coming soon”
  • Free disk space: roughly 2 GB for the driver package plus temporary extraction files

If your card predates RDNA (a GCN-based RX 500 or Vega card, for example), you can still use the older driver-level Radeon Anti-Lag, which covers RX 400-series and newer plus Ryzen 2000-series APUs. It’s a cruder tool with no per-game tuning, but it’s better than nothing on older silicon.

Which Radeon GPUs Support Anti-Lag 2

AMD’s product pages describe eligibility in architecture terms rather than listing every SKU, which leaves a lot of owners unsure whether their specific card qualifies. The table below maps each RDNA generation to what it actually gets, based on AMD’s Anti-Lag 2 SDK notes and the driver release history for each family.

ArchitectureExample cardsAnti-Lag 2 eligibleLegacy Anti-Lag
RDNA 1RX 5500, RX 5600 XT, RX 5700 XTYesYes
RDNA 2RX 6600, RX 6700 XT, RX 6800 XT, RX 6950 XTYesYes
RDNA 3RX 7600, RX 7700 XT, RX 7800 XT, RX 7900 GRE, RX 7900 XTXYes (AMD’s own test bed)Yes
RDNA 4RX 9070, RX 9070 XT and newerYes, with a known DX11/CS2 bug on some modelsYes
GCN (Polaris, Vega)RX 570, RX 580, Vega 56, Vega 64NoYes

Ryzen APUs follow the same rule as discrete cards: anything built on RDNA graphics (Ryzen 6000-series and newer, including the Radeon 780M and 890M found in current handhelds and thin laptops) qualifies for Anti-Lag 2, while older Vega-based APUs are limited to the legacy Anti-Lag toggle.

Step 1: Confirm Your GPU Supports Anti-Lag 2

Open PowerShell and pull your GPU model and current driver version directly from Windows Management Instrumentation. This avoids relying on the Adrenalin splash screen, which sometimes lags behind the actual installed version after a partial update.

Get-WmiObject Win32_VideoController | Select-Object Name, DriverVersion, DriverDate

Output on a typical RDNA 3 setup looks like this:

Name                                    DriverVersion    DriverDate
----                                    -------------    ----------
AMD Radeon RX 7800 XT                  32.0.31041.3013  20260820000000.000000-000

Match the card name against RDNA 1 through RDNA 4 (RX 5000, 6000, 7000, and the newest RX 9000-class parts). Anything older, such as an RX 590 or Vega 56, only gets the legacy driver-level Anti-Lag, not Anti-Lag 2.

Step 2: Update to AMD Software Adrenalin Edition 26.x

Open AMD Software: Adrenalin Edition, go to the Settings gear, then Updates, and click Check for Updates. If you’re running anything older than the 24.7.1 baseline, install the newest 26.x package rather than stepping through intermediate versions, since AMD folds Anti-Lag 2 bug fixes into every branch after that point. The 26.8.1 release is the current WHQL-certified build as of early September 2026, with 26.9.1 available if you want the latest optional fixes ahead of the next Recommended tag.

Download directly from AMD’s Radeon Software Anti-Lag support page if the in-app updater is slow or fails, which happens more often on machines with aggressive third-party firewall rules blocking AMD’s update servers.

Step 3: Clean-Install With AMD Cleanup Utility

Leftover files from an old Anti-Lag+ era install are a common source of the “toggle just won’t appear” problem covered later in this guide. Before installing a fresh 26.x driver, stop the AMD services so the installer isn’t fighting a locked file.

Get-Service -DisplayName "AMD*" | Stop-Service -Force -ErrorAction SilentlyContinue
Get-Service -DisplayName "AMD*" | Select-Object DisplayName, Status

Then run AMD Cleanup Utility from Safe Mode, reboot into normal Windows, and install the 26.x package fresh. This adds ten to fifteen minutes to the process but resolves most cases where Anti-Lag 2 settings silently fail to save.

Step 4: Enable Anti-Lag 2 in Counter-Strike 2 and Dota 2

These are the two titles with mature Anti-Lag 2 integration. In Counter-Strike 2, the feature has been on by default since Adrenalin 24.6.1 moved it out of technical preview, so most players don’t need to touch anything beyond confirming the driver version. To check or force it manually, open Adrenalin, go to the Gaming tab, select the Counter-Strike 2 profile, and look under Graphics for the Radeon Anti-Lag 2 toggle.

Dota 2 support arrived in Adrenalin 24.7.1, but only through the DirectX 11 rendering path. If you’ve switched Dota 2 to Vulkan for the frame rate bump, you’ll lose Anti-Lag 2 entirely until you switch back, since AMD hasn’t extended the SDK integration to that path yet.

GameAPI pathMinimum driverStatus
Counter-Strike 2DirectX 11 and DirectX 12Adrenalin 24.6.1Native, on by default
Dota 2DirectX 11 onlyAdrenalin 24.7.1Native, manual toggle
Ghost of Tsushima DIRECTOR’S CUTDirectX 12Adrenalin 24.7.1+Native, manual toggle
ValorantDirectX 11N/ANot integrated
FortniteDirectX 12N/ANot integrated

Step 5: What Actually Works in Valorant and Other Unsupported Games

This is the part most driver-panel tutorials skip. Valorant does not have Anti-Lag 2 integration as of September 2026, and won’t get it until Riot builds the SDK hooks into their engine. Riot’s own anti-cheat, Vanguard, is also kernel-level and cautious about any driver behavior that touches memory near the game process, which is precisely the category of interference that caused Anti-Lag+’s ban wave in 2023.

For Valorant, Fortnite, Apex Legends, and other unsupported titles, three things still help without needing a game-side integration: the legacy driver-level Radeon Anti-Lag toggle (found under Adrenalin’s Gaming tab for any profile, supported and unsupported alike), keeping frame rates uncapped or capped just below your monitor’s refresh rate rather than left unbounded, and disabling Radeon Chill, which throttles frame rate to save power and works directly against low-latency goals. None of these deliver the 37% figure AMD advertises for CS2, but they typically shave a few milliseconds without any risk of anti-cheat flags, since the legacy Anti-Lag toggle has run without incident since well before the Anti-Lag+ controversy.

It’s worth setting expectations correctly here rather than chasing a number that isn’t coming. Riot has never publicly committed to an Anti-Lag 2 integration timeline, and kernel-level anti-cheat vendors in general have been slow to greenlight any driver feature that touches frame timing after the 2023 Anti-Lag+ incidents made every anti-cheat team more cautious about GPU-vendor code running near their process. If Valorant latency is your main concern and you’re choosing hardware from scratch, that’s a legitimate reason to weigh Nvidia’s broader Reflex support against AMD’s pricing and raw rasterization performance rather than assuming the driver will catch up on its own timeline.

Step 6: Turn Off Settings That Cancel Out Anti-Lag 2

Anti-Lag 2 can be fully enabled and still show zero measurable improvement if a handful of other settings are fighting it. V-Sync is the biggest offender, since it deliberately buffers frames to eliminate tearing, which directly conflicts with the frame-pacing trick Anti-Lag 2 relies on. Radeon Chill is the second, because it caps your frame rate dynamically based on in-game motion, and a lower frame rate means more render queue backlog regardless of what Anti-Lag 2 is doing underneath.

  • Disable V-Sync in both the game’s video settings and in Adrenalin’s global graphics profile
  • Disable Radeon Chill for any profile where you want maximum responsiveness over battery or thermal savings
  • Set a frame rate cap only if your GPU is pushing frames well past your monitor’s refresh rate, and cap it 2 to 3 frames below the panel’s max refresh, not at an arbitrary round number
  • Leave FreeSync enabled. It doesn’t conflict with Anti-Lag 2 on its own, but aggressive frame pacing under FreeSync can make latency numbers harder to read on the overlay

Step 7: Read the Built-In Latency Overlay

AMD ships a latency monitor directly in the driver. Press Alt+Shift+L in-game to cycle through overlay modes. The full mode shows three numbers: FPS in yellow, latency in milliseconds in white, and latency measured in frames in green.

FPS: 241 (yellow)
Latency: 11.3 ms (white)
Frames: 1.4 (green)

AMD’s SDK documentation notes that native latency without Anti-Lag 2 typically sits at 3 to 5 frames, and a healthy Anti-Lag 2 session should show the green frame counter between 1.0 and 2.0. If you see a number above 3 with Anti-Lag 2 supposedly active, the integration in that specific game build isn’t working correctly and you should treat it as disabled until a patch fixes it. Also confirm you’re not running V-Sync, since the SDK notes state the white millisecond figure should roughly match AMD’s separate Frame Latency Meter only when V-Sync is off.

Step 8: Lock In Fullscreen Exclusive Mode

Windows’ borderless fullscreen optimizations layer adds a compositor pass that increases latency, and it silently overrides some DirectX 11 games even when you’ve selected “Fullscreen” in their settings menu. Force it off per-executable with a registry entry rather than relying on the game’s own toggle.

$exePath = "C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\bin\win64\cs2.exe"
New-ItemProperty -Path "HKCU:\System\GameConfigStore" `
  -Name $exePath `
  -PropertyType String `
  -Value "~ DISABLEDXMAXIMIZEDWINDOWEDMODE" `
  -Force

Repeat with the correct install path for each game you’re tuning. Restart the game afterward for the change to take effect.

Step 9: Combine Anti-Lag 2 With FSR 3.1 and RSR

AMD promotes FSR 3.1 and Anti-Lag 2 together in the same driver branches, and the two coexist without conflict in the titles that support both. The catch is Frame Generation, the interpolation half of FSR 3.1 that inserts synthetic frames between rendered ones. Frame Generation raises your displayed FPS but adds a frame of latency to generate the interpolated image, which works against Anti-Lag 2’s entire purpose. For competitive play, run FSR 3.1’s upscaling without Frame Generation, and save Frame Generation for single-player titles where visual smoothness matters more than reaction time.

Radeon Super Resolution (RSR) works at the driver level rather than in-game and generally runs fine alongside Anti-Lag 2, though it shifts GPU workload in a way that can nudge your latency numbers slightly. If you’re benchmarking before-and-after latency for this guide’s later steps, disable RSR during testing so you’re isolating Anti-Lag 2’s effect specifically.

Step 10: Save Per-Game Profiles

Adrenalin stores settings per executable, but a driver update can occasionally reset profile-specific toggles back to default, especially after a jump between major branches like 25.x to 26.x. After any driver update, reopen the Gaming tab and spot-check your Anti-Lag 2, V-Sync, and Chill settings for each profile you’ve tuned rather than assuming they carried over.

Export your Adrenalin profile from Settings, then Presets, then Export, before any major driver upgrade. It won’t restore Anti-Lag 2’s per-game toggle automatically, since that setting lives partly in the game’s own configuration, but it does save you from rebuilding your entire graphics profile list from scratch.

Step 11: Run a Before/After Latency Benchmark

Don’t take AMD’s 37% figure on faith for your own hardware. PresentMon, a free and open-source capture tool from Intel’s GameTechDev team, logs frame time and click-to-photon data you can compare directly.

# Anti-Lag 2 OFF baseline, 60-second capture
.\PresentMon-2.3.1-x64.exe -process_name cs2.exe -output_file baseline_off.csv -timed 60

# Anti-Lag 2 ON, same map, same 60-second capture
.\PresentMon-2.3.1-x64.exe -process_name cs2.exe -output_file antilag2_on.csv -timed 60

Run both captures on the same map, same server, ideally against a bot so network variance doesn’t muddy the comparison. Compare the average and 99th-percentile “MsBetweenPresents” and click-to-photon columns in the resulting CSVs. A working Anti-Lag 2 setup should show a visible drop in both the average and the latency spikes, not just a marginal shift in the mean.

Step 12: Automate the Whole Setup With a PowerShell Script

If you’re setting this up across a home LAN party rig or a small esports practice room with several identical machines, wrap the checks from Steps 1, 6, and 8 into a single script rather than repeating them by hand on every PC.

# antilag2-setup-check.ps1
# Verifies GPU eligibility, driver version, and fullscreen-optimization
# overrides for a list of competitive titles. Run as Administrator.

$minDriverDate = Get-Date "2024-07-01"
$gpu = Get-WmiObject Win32_VideoController | Where-Object { $_.Name -match "AMD|Radeon" }

if (-not $gpu) {
    Write-Host "No AMD GPU detected." -ForegroundColor Red
    exit 1
}

Write-Host "GPU: $($gpu.Name)"
Write-Host "Driver: $($gpu.DriverVersion)"

$games = @{
    "cs2.exe"      = "C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\bin\win64\cs2.exe"
    "dota2.exe"    = "C:\Program Files (x86)\Steam\steamapps\common\dota 2 beta\game\bin\win64\dota2.exe"
}

foreach ($exe in $games.Keys) {
    $path = $games[$exe]
    if (Test-Path $path) {
        New-ItemProperty -Path "HKCU:\System\GameConfigStore" `
            -Name $path -PropertyType String `
            -Value "~ DISABLEDXMAXIMIZEDWINDOWEDMODE" `
            -Force | Out-Null
        Write-Host "Fullscreen optimization disabled for $exe" -ForegroundColor Green
    } else {
        Write-Host "$exe not found at expected path, skipping" -ForegroundColor Yellow
    }
}

Write-Host "Done. Open Adrenalin > Gaming and confirm Anti-Lag 2 per game."

Save this as antilag2-setup-check.ps1, right-click and run with PowerShell as Administrator, and adjust the file paths under the $games hash table to match your actual install locations. This gives you a repeatable baseline check you can run again after every driver update instead of manually reopening five different menus.

AMD Anti-Lag 2 vs Nvidia Reflex: The Numbers Side by Side

Anti-Lag 2 and Nvidia Reflex solve the same problem in similar ways, and reviewers have generally found them landing in the same performance range in the one game both fully support: Counter-Strike 2. Tom’s Hardware described Anti-Lag 2’s roughly 11 ms result there as on par with Reflex’s advertised sub-15 ms figures, framing Anti-Lag 2 as a legitimate alternative rather than a lesser copy. Where the two diverge is game support. Nvidia has years of head start integrating Reflex into a much longer list of competitive titles, including Valorant, while AMD’s list is still limited to three names as of this writing.

MetricAMD Anti-Lag 2Nvidia Reflex
CS2 measured latency~11 ms (Tom’s Hardware)Sub-15 ms (Nvidia advertised)
Activation methodDeveloper SDK integration requiredDeveloper SDK integration required
Confirmed game count (2026)3 titles (CS2, Dota 2, Ghost of Tsushima DC)Dozens, including Valorant, Fortnite, Apex Legends
Anti-cheat incident historyPredecessor (Anti-Lag+) caused 2023 bans; Anti-Lag 2 clean since launchNo public anti-cheat ban incidents reported
In-driver latency overlayYes (Alt+Shift+L)Yes (Nvidia Stats overlay)

An open-source project documented by TweakTown even ported both technologies to work on any GPU under Linux, testing Counter-Strike 2, Cyberpunk 2077, Resident Evil Requiem, and Marvel Rivals on an RX 7900 XTX. The project reported comparable percentage reductions for both Anti-Lag 2 and Reflex, reinforcing that the underlying approach, holding back CPU frames to prevent render queue buildup, produces similar results regardless of vendor once a game actually integrates the SDK.

The practical takeaway for anyone building or upgrading a competitive rig right now is that raw latency technology shouldn’t be the deciding factor between an AMD and Nvidia purchase on its own. If you already own a Radeon GPU and mainly play Counter-Strike 2 or Dota 2, Anti-Lag 2 gets you into the same latency range Nvidia users see with Reflex, at no extra cost and with no separate setup beyond a driver update. If your primary game is Valorant, Fortnite, or another Reflex-only title and latency is the deciding factor in a new GPU purchase, Nvidia’s broader support list is the more reliable path today, since AMD hasn’t published a public roadmap for which games get Anti-Lag 2 integration next.

Common Pitfalls When Setting Up Anti-Lag 2

Most support threads about Anti-Lag 2 “not working” trace back to one of these mistakes rather than an actual driver bug.

  • Assuming it works everywhere. Anti-Lag 2 needs per-game developer integration. Toggling it in Adrenalin for Valorant, Fortnite, or any other unsupported title does nothing measurable.
  • Leaving V-Sync on. This is the single most common reason someone reports zero latency improvement after enabling Anti-Lag 2 correctly.
  • Skipping the clean install. Upgrading over an old Anti-Lag+ era driver without running the Cleanup Utility leaves orphaned registry entries that can make the toggle disappear or fail to save.
  • Confusing Anti-Lag with Anti-Lag 2 in the UI. The legacy driver-level toggle and the new SDK-based one sit in similar menus with similar names. Only Anti-Lag 2 needs game-side support to function.
  • Running Radeon Chill at the same time. Chill actively caps frame rate for power savings, which works directly against everything Anti-Lag 2 is trying to do.
  • Testing with Frame Generation enabled. FSR 3.1’s Frame Generation adds a frame of latency to interpolate, which can mask or even reverse Anti-Lag 2’s benefit during a benchmark.
  • Trusting the vendor’s headline number. AMD’s 37% figure came from a specific set of RDNA 3 cards in one game. Your mileage on RDNA 2 hardware or a different title will vary, sometimes significantly.

Troubleshooting Anti-Lag 2 Problems

Work through these in order before assuming your hardware doesn’t support the feature.

  • Toggle missing entirely in CS2 under DX11 on an RX 9070 XT. AMD’s own 25.10.2 release notes acknowledge this issue on select RDNA 4 cards. Switch CS2 to the Vulkan renderer as a temporary workaround until a fix ships.
  • Alt+Shift+L does nothing. Another overlay is likely eating the hotkey. Close Discord’s in-game overlay, MSI Afterburner’s RivaTuner Statistics Server, and Xbox Game Bar, then retry.
  • Overlay shows numbers but they don’t change with the toggle. Confirm V-Sync is off in both the game and Adrenalin. The SDK explicitly states its latency figures only align with actual measured latency when V-Sync is disabled.
  • Driver installation fails or rolls back mid-install. Run AMD Cleanup Utility in Safe Mode first, disconnect from the internet during installation to prevent Windows Update from grabbing a conflicting driver package, then reinstall.
  • Anti-Lag 2 option is grayed out for a specific game. That title isn’t on AMD’s supported list yet. Check AMD’s Anti-Lag technology page for the current roster before assuming it’s a bug.
  • FreeSync flickers after enabling Anti-Lag 2. Update your monitor’s firmware if an update is available, then toggle FreeSync off and back on in Adrenalin to force a clean renegotiation with the panel.
  • Stuttering appears after adding FSR 3.1 Frame Generation on top of Anti-Lag 2. Disable Frame Generation specifically for latency-sensitive sessions. Upscaling alone doesn’t cause this. The interpolation step does.
  • Per-game settings reset after a driver update. This is common across major version jumps (25.x to 26.x, for example). Re-check and re-apply your Anti-Lag 2, V-Sync, and Chill settings for each profile after any driver update.
  • Old Anti-Lag+ toggle still visible and confusing. It’s a legacy holdover from before the 2023 rollback. It’s effectively disabled at the driver level in modern builds and safe to ignore.

Advanced Tips for Competitive Players

Once the basic setup is stable, a few additional tweaks compound with Anti-Lag 2’s gains rather than replacing them. Switch Windows’ power plan to High Performance or Ultimate Performance, since the balanced default plan throttles CPU clocks between frames in ways that add jitter regardless of what your GPU driver is doing. Disable Xbox Game Bar entirely (Settings, Gaming, Xbox Game Bar) rather than just closing its overlay, since the background service still polls periodically even when the overlay itself is hidden.

Pair Anti-Lag 2 with a mouse polling rate of at least 1000 Hz if your peripheral supports it. Anti-Lag 2 tightens the render pipeline, but a mouse polling at 125 Hz still only reports position 125 times per second, creating a bottleneck upstream of anything the GPU driver can fix. Finally, treat monitor overdrive settings as part of the same latency budget. An overshoot-heavy overdrive setting can add visible ghosting that feels like extra input lag even when the measured numbers from PresentMon look identical, so tune overdrive with a pursuit-camera test rather than by eye alone.

Background bandwidth is another quiet source of latency that has nothing to do with your GPU driver. A cloud backup client, a Windows Update download, or a second monitor running a browser with dozens of tabs open can all steal CPU scheduling slices from the game thread at exactly the moment Anti-Lag 2 is trying to time frame submission precisely. Close anything with a background sync or update check running before a benchmark pass, and consider setting the game’s process priority to High in Task Manager on machines with fewer than eight CPU cores, where scheduling contention is more likely to show up as latency spikes.

If you’re on a laptop with hybrid graphics, confirm Windows is actually routing the competitive title to the discrete Radeon GPU rather than an integrated one. Go to Settings, System, Display, Graphics, and set the game’s executable to High Performance manually rather than trusting the automatic switching, since Anti-Lag 2’s SDK hooks only apply to the GPU actually rendering the frame.

For anyone managing several PCs, the SDK repository AMD maintains on GitHub is worth a look even if you’re not a developer. It documents the exact frame-count thresholds the driver uses to decide whether Anti-Lag 2 is functioning correctly in a given title, which is useful context if you ever need to judge whether a game’s implementation is actually working or just present in name.

The Complete Working Setup, Start to Finish

Here’s every piece from this guide assembled into a single checklist. Run through it top to bottom on a fresh install, or use it to audit a machine that’s already been tuned by someone else.

  • Confirm GPU architecture with Get-WmiObject Win32_VideoController (Step 1)
  • Install Adrenalin 26.8.1 or newer, running the Cleanup Utility first on any machine coming from a pre-24.6.1 driver (Steps 2 to 3)
  • Verify Anti-Lag 2 is active in Counter-Strike 2 and Dota 2, and confirm the legacy Anti-Lag fallback is on for everything else, including Valorant (Steps 4 to 5)
  • Disable V-Sync and Radeon Chill globally and per profile (Step 6)
  • Check the Alt+Shift+L overlay and confirm the green frame counter reads under 2.0 in a supported title (Step 7)
  • Apply the DISABLEDXMAXIMIZEDWINDOWEDMODE registry entry for each competitive title (Step 8)
  • Leave FSR 3.1 upscaling on but Frame Generation off during competitive sessions (Step 9)
  • Export your Adrenalin profile before any driver upgrade, and re-verify per-game toggles afterward (Step 10)
  • Capture a 60-second PresentMon baseline with the feature off, then a matching capture with it on, and compare the 99th-percentile figures, not just the average (Step 11)
  • Run the antilag2-setup-check.ps1 script from Step 12 on every additional PC in a shared setup so the registry and driver checks don’t have to be repeated by hand

A machine that passes every item on this list should show a visibly tighter click-to-photon result in the PresentMon CSVs from Step 11, typically in the 20 to 37 percent range AMD and independent reviewers have both reported for Counter-Strike 2, with the caveat that games outside AMD’s supported list will only see the smaller gains from the legacy Anti-Lag path and general system tuning.

Frequently Asked Questions

Does AMD Anti-Lag 2 work in Valorant?

No, not as of September 2026. Valorant hasn’t integrated AMD’s SDK, so the Anti-Lag 2 toggle has no effect there. The legacy driver-level Radeon Anti-Lag setting still works and provides a smaller improvement.

What’s the difference between Anti-Lag, Anti-Lag+, and Anti-Lag 2?

Anti-Lag is the original driver-level feature that works in any game on RX 400-series cards and newer. Anti-Lag+ was a 2023 RDNA 3-only feature that used shader injection and got pulled after causing anti-cheat bans in Call of Duty and other titles. Anti-Lag 2 is the 2024 rebuild that requires explicit developer integration instead of injection, trading universal compatibility for anti-cheat safety.

Which driver version do I need for Anti-Lag 2?

Adrenalin 24.6.1 or newer for DirectX 11 titles, and 24.7.1 or newer for DirectX 12 titles. Any current 25.x or 26.x driver satisfies both requirements.

Can I use Anti-Lag 2 and Nvidia Reflex on the same PC?

Only if you have both an AMD and Nvidia GPU active, which is unusual outside of specific multi-GPU workstation setups. Anti-Lag 2 is exclusive to Radeon hardware, and Reflex is exclusive to GeForce hardware.

Will Anti-Lag 2 get me banned in Counter-Strike 2?

No. Anti-Lag 2 was built specifically to avoid the shader-injection behavior that caused Anti-Lag+’s ban issues in 2023. Since Anti-Lag 2 launched with official Valve integration in Adrenalin 24.6.1, there have been no reported VAC ban incidents tied to it.

Does Anti-Lag 2 lower my frame rate?

No. Anti-Lag 2 changes frame pacing and timing, not frame count. If you see a frame rate drop after enabling it, check whether Radeon Chill or a frame rate cap is also active, since those are the actual causes in almost every reported case.

Why don’t I see the Anti-Lag 2 toggle for my game?

As of September 2026, only Counter-Strike 2, Dota 2, and Ghost of Tsushima DIRECTOR’S CUT have shipped the required developer integration. If your game isn’t on that list, the toggle won’t appear because there’s nothing on the game’s side for it to control.

Is the 37% latency reduction figure accurate for every RDNA card?

AMD’s 37% average figure came from testing on an RX 7900 GRE, RX 7800 XT, RX 7600 XT, RX 7700S, and a Ryzen 7 8700G with Radeon 780M graphics, all in Counter-Strike 2. Older RDNA 2 hardware and other games will likely see a different result, which is why running your own before-and-after PresentMon capture, as covered in Step 11, is worth the extra ten minutes.

Does Anti-Lag 2 work on Linux?

Not natively through AMD’s own Adrenalin stack, since that’s a Windows-only application. An open-source project documented by TweakTown ported both Anti-Lag 2 and Nvidia Reflex to work on any GPU under Linux, with test results across Counter-Strike 2, Cyberpunk 2077, Resident Evil Requiem, and Marvel Rivals on an RX 7900 XTX. It’s a community project rather than an official AMD release, so treat it as experimental if you’re setting up a competitive rig on a Linux distribution.

Does Anti-Lag 2 cost anything extra?

No. It ships as part of AMD Software: Adrenalin Edition, which is free for anyone with a supported Radeon GPU or APU. There’s no separate purchase, subscription, or unlock key involved, unlike some GPU vendor features that are tied to specific product tiers.