AMD AFMF 3 Reportedly Unlocked in Radeon Driver: Hidden Modes and Risks Explained

What was reported​

According to VideoCardz, the discovery was shared by user SixPie174632251, who reportedly used DeepSeek 4.1 Flash to investigate the hidden functionality. Wccftech adds that the user did this without modifying the driver files themselves. The target was AMD Software: Adrenalin Edition 26.10.2.

The mechanism is a current-user registry value called afmf3dev, set to 1. The user posted a PowerShell command to create it, then fully restarted the AMD Software app. The poster also reportedly said AFMF 3 may work in older drivers, but they have not tested that. Mezha reports that people can also make the same change by hand in Regedit.

The poster claims it works on RDNA 3 and RDNA 4, which means Radeon RX 7000 and RX 9000 cards. VideoCardz notes there is no confirmation of RDNA 2 compatibility in the report. I can't confirm which exact models were tested.

What the unlocked interface reportedly shows​

The details below are the poster's observations, not AMD statements.

• Two modes: The hidden settings expose Standard and Enhanced frame generation modes.
• Motion data: VideoCardz says Enhanced mode appears to use motion-vector information tied to technologies like FSR, XeSS, TSR and TAA. TweakTown also reports that it can hook into FSR Frame Generation, and reportedly DLSS and XeSS.
• Image quality and latency: The poster says Enhanced mode looks better than Standard and shows no obvious UI artifacts in limited testing. Mezha reports the poster also saw slightly higher latency. TweakTown describes the extra cost as a performance penalty.
• Motion blur: The poster suggests it may work with motion blur enabled.
• Fullscreen limits: Some games may need exclusive fullscreen, while others reportedly work borderless. The AMD overlay (Alt+R) can show the feature's status and requirements.

What is not known​

No benchmarks or measured latency figures were shared. Digital Citizen says no independent benchmarks have established the performance improvements or measured the latency differences. The "Enhanced costs more performance" and "Enhanced adds latency" points are therefore impressions, not measurements.

TweakTown's suggestion that HUD handling could improve through access to motion vectors and depth data is its own inference. It is plausible, but it is not documented by AMD. TweakTown itself hedges with "Assuming these tooltips are real."

The reported Enhanced mode also sits oddly with how AFMF has been described. TweakTown calls AFMF 2.1 strictly limited to driver-side frame generation in spirit, and VideoCardz notes earlier versions generally lacked direct access to game-engine motion vectors. If Enhanced mode really consumes engine data, it would blur the line between AFMF and in-game FSR Frame Generation. That is my reading of the reports, not an AMD claim.

Official status​

AMD's official October 30 release notes for Adrenalin 26.10.2 do not mention AFMF 3. Its current AFMF documentation still lists version 2.1. AMD has not published a release date, supported-GPU list or technical documentation for AFMF 3.

None of this is new, though. References to AFMF 3 and FrameGenV3 were found in Radeon driver files in September 2025. Wccftech's coverage at the time speculated about a possible tie to FSR Redstone. That timing was only speculation then and remains unconfirmed. A hidden flag in a public driver shows code is present. It does not show the feature is finished, stable or coming soon.

Should you try it?​

I would not, at least not on a machine you rely on. VideoCardz says it does not recommend using the command on an actively used system, because the full scope of the function is unknown. It suggests a sandboxed system or a VM with GPU passthrough instead. It also advises backing up the relevant registry key before testing unsupported functionality.

Practical points for anyone tempted:

1. Understand the change. The value lives under the current user's registry hive, so it is not a driver-file modification. That doesn't make it harmless, and no rollback procedure has been tested or published.
2. Expect instability. Undocumented features can misbehave in games, overlays or recording features.
3. Don't extrapolate AFMF 2.1 requirements. AFMF 2.1 has its own documented requirements and supported-card list. They don't carry over to AFMF 3.
4. Skip support requests. AMD has no troubleshooting guidance for a feature it hasn't announced.

Why this matters​

AFMF is AMD's answer for games with no native frame generation. Any improvement in quality or HUD handling would matter to owners of RX 7000 and RX 9000 cards, who often play such games. The story also fits a wider trend. People are using AI assistants to dig through shipping software for hidden flags, which speeds up the discovery of unfinished features and also the spread of risky tweaks.

The takeaway for now is to watch for an official AMD announcement and independent testing. The reported benefits are a single enthusiast's early impressions.