Friday, September 29th 2023

AMD Releases Adrenalin Edition Preview Driver for AMD Fluid Motion Frames

by
GFreeman
 Discuss (53 Comments)
AMD has released the AMD Software Adrenalin Edition Preview Driver which add support for AMD Fluid Motion Frames (AFMF) technical preview which is available in several games and only works on AMD Radeon RX 7000 series graphics cards. AMD Fluid Motion Frames (AFMF) will be available as a part of FidelityFX Super Resolution 3.0 (FSR3), which is expected to launch tomorrow and supported in Forspoken and Immortals of Aveum games.

With the new AMD Software Adrenalin Edition Preview Driver, AMD enables Frame Generation on a driver level as "Fluid Motion Frame" option, which can be enabled via HYPR-X, or individually for each game by using the Global Graphics Settings page. AMD has an extensive list of over 20 titles, including Star Wars Jedi: Survivor, Starfield, Hogwarts Legacy, The Last of Us Part 1, Far Cry 6, Shadow Of The Tomb Raider, The Witcher 3: Wild Hunt, and others. AMD also notes that AFMF can also be manually for any title such as Cyberpunk 2077 using the per-app settings within AMD Software: Adrenalin Edition.

DOWNLOAD: AMD Software: Adrenalin Edition Preview Driver for AMD Fluid Motion Frames
The AMD Software Adrenalin Edition Preview Driver only supports Radeon RX 7000 series graphics cards, and AMD recommends that the AFMF is enabled for games running at a minimum of 55 FPS on 1080p and 70 FPS on 1440p or above displays.

Here are the full release notes.

Important Notes
  • This preview driver is intended to provide users an early first-look into upcoming features within AMD Software; feedback is encouraged and can be submitted through the AMD Bug Report Tool. If issues arise or persist during the usage of the Preview Driver, please use the AMD Auto-Detect and Install Tool to revert the latest recommended AMD Software: Adrenalin Edition driver.
New Feature Highlights
  • AMD Fluid Motion Frames (AFMF) Technical Preview - Boost FPS with frame generation technology for a smoother gaming experience.
  • AFMF adds frame generation technology to DirectX 11 and 12 games on AMD Radeon RX 7000 Series Desktop Graphics.
  • AFMF preserves image quality by dynamically disabling frame generation during fast motion.
What to know
  • AMD Fluid Motion Frames (AFMF)
  • AFMF can be automatically enabled using HYPR-RX or toggled individually using the Global Graphics Settings page for these select titles;
  • A Plague Tale - Requiem
  • Borderlands 3
  • Control
  • Dead Space
  • Deep Rock Galactic
  • Dying Light 2
  • Far Cry 6
  • Ghostwire: Tokyo
  • Hitman 3
  • Hogwarts Legacy
  • Horizon Zero Dawn
  • Metro Exodus Enhanced Edition
  • Red Dead Redemption 2
  • Resident Evil 3
  • Resident Evil 4
  • Shadow Of The Tomb Raider
  • Star Wars Jedi: Survivor
  • Starfield
  • The Last of Us Part 1
  • The Witcher 3: Wild Hunt
  • In addition to these select titles, AFMF may be manually enabled for any title such as Cyberpunk 2077 using the per-app settings within AMD Software: Adrenalin Edition.
  • The AFMF technical preview currently requires the game to be played in fullscreen mode with HDR disabled and VSYNC disabled.
  • For the optimal experience, AFMF is recommended to be used on AMD FreeSync displays.
  • Users are recommended to disable HDR in Windows Display Settings, or disable HDR in the game (as well as Auto-HDR).
  • AFMF features an activity monitor similar to AMD Radeon Super Resolution to confirm the frame generation status using AMD Software: Adrenalin Edition 's in-game overlay (use the default hotkey of Alt-R for the fullscreen overlay, or Alt-Z for the sidebar overlay)
  • AFMF can introduce additional latency in games and is recommended to be combined with AMD Radeon Anti-Lag/Anti-Lag+ for the optimal experience.
  • As AFMF may introduce additional latency in games, AFMF may not offer the optimal experience in fast-paced competitive titles.
  • AFMF is recommended to be enabled for games running at a minimum FPS of 55 FPS for 1080p displays, and 70 FPS for 1440p or above displays.
Known Issues
  • Intermittent driver crashes have been observed while AFMF is enabled and the game's resolution is changed or a task switch happens (such as alt-tab between different windows).
  • Brief corruption may be observed when switching between windows with AFMF enabled on some 144 Hz or greater monitors.
  • Brief stutter may be experienced after closing the Xbox Game Bar.
  • FreeSync displays may report an erratic FPS when AFMF is enabled.
  • Some metrics such as frame time may show inconsistent results when AFMF is enabled.
Radeon Product Compatibility
AMD Software: Adrenalin Edition Technical Preview Driver for AMD Fluid Motion Frames Version 23.30.01.02 is compatible with the following AMD Radeon products.
  • Radeon RX 7900/7800/7700/7600 Series Graphics
Compatible Operating Systems
AMD Software: Adrenalin Edition Technical Preview Driver for AMD Fluid Motion Frames Version 23.30.01.02 is designed to support the following Microsoft Windows platforms. Operating System support may vary depending on your specific AMD Radeon product.
  • Windows 11 version 21H2 and later
  • Windows 10 64-bit version 1809 and later
Sources: AMD Blog, via Videocardz

Related News

Add your own comment

53 Comments on AMD Releases Adrenalin Edition Preview Driver for AMD Fluid Motion Frames

#26
oxrufiioxo
Dr. DroSo, how's the fake frames :D
I actually found the image impressive considering the fact that nvidia says it's not possible with their BS flow acceleration or whatever. The only issue with it on a GeForce gpu is it's hard to tell it's even on and framepacing feels worse. Also there is some noticeable input lag becuase it disables reflex on GeForce.

Overall my first impression are good and if it's even better with HyperRX or whatever it's called on 7000 series cards good for them.

Hoping CP2077 gets native support becuase frame generation is quite good in that game so it'll be a better comparison.
Posted on Reply
#27
Space Lynx
Astronaut
oxrufiioxoI actually found the image impressive considering the fact that nvidia says it's not possible with their BS flow acceleration or whatever. The only issue with it on a GeForce gpu is it's hard to tell it's even on and framepacing feels worse. Also there is some noticeable input lag becuase it disables reflex on GeForce.

Overall my first impression are good and if it's even better with HyperRX or whatever it's called on 7000 series cards good for them.

Hoping CP2077 gets native support becuase frame generation is quite good in that game so it'll be a better comparison.
yeah I imagine this software, even being open to all, is probably going to be best on RDNA3, so Nvidia owners should probably stick with DLSS frame gen when viable.

I'm going to wait for polish and the first WHQL release of it, I plan to do a clean install of windows 11 at end of October with the feature update for Win 11 comes out. I usually do a clean install every year, as it doesn't take me very long.



i should have a new bios update then for my mobo too as well as hopefully chipset drivers. should a be a very good clean install with the latest of everything updated. then away I go!
Posted on Reply
#28
Dr. Dro
oxrufiioxoI actually found the image impressive considering the fact that nvidia says it's not possible with their BS flow acceleration or whatever. The only issue with it on a GeForce gpu is it's hard to tell it's even on and framepacing feels worse. Also there is some noticeable input lag becuase it disables reflex on GeForce.

Overall my first impression are good and if it's even better with HyperRX or whatever it's called on 7000 series cards good for them.

Hoping CP2077 gets native support becuase frame generation is quite good in that game so it'll be a better comparison.
I said from day one Nvidia was lying, they'll backport it to Ampere and Turing perhaps even Pascal if this gains any traction lol

Still I've been seeing some bizarre screenshots of FSR 3 floating around, mostly on Forspoken, the implementation is either completely horrible, or we have a problem. I'm told it's not this bad on Aveum, though.



still, even with Nvidia's shenanigans, you can only appreciate DLSS-G 3.5's accuracy, it processes even motion blur correctly. This is a capture of the output stage by Special K, so basically it's the same frame residing in the GPU's framebuffer unmodified:



With quite manageable latency as well, thanks to a good Reflex implementation, 5.62 ms of present latency, next to no frame variation, not too bad:



Hopefully as the FSR 3 implementations begin to spread we see what the tech can truly do - and perhaps Nvidia "suddenly figures out" how to have DLSS frame generation working on their previous generation hardware :rolleyes:
Posted on Reply
#29
oxrufiioxo
Space Lynxyeah I imagine this software, even being open to all, is probably going to be best on RDNA3, so Nvidia owners should probably stick with DLSS frame gen when viable.

I'm going to wait for polish and the first WHQL release of it, I plan to do a clean install of windows 11 at end of October with the feature update for Win 11 comes out. I usually do a clean install every year, as it doesn't take me very long.



i should have a new bios update then for my mobo too as well as hopefully chipset drivers. should a be a very good clean install with the latest of everything updated. then away I go!
Needing to use FSR or no upscaling makes it useless for me to begin with so it really doesn't matter that its open till they improve that.

It also disables VRR which is a big nope.
Dr. DroI said from day one Nvidia was lying, they'll backport it to Ampere and Turing perhaps even Pascal if this gains any traction lol

Still I've been seeing some bizarre screenshots of FSR 3 floating around, mostly on Forspoken, the implementation is either completely horrible, or we have a problem. I'm told it's not this bad on Aveum, though.



still, even with Nvidia's shenanigans, you can only appreciate DLSS-G 3.5's accuracy, it processes even motion blur correctly. This is a capture of the output stage by Special K, so basically it's the same frame residing in the GPU's framebuffer unmodified:



With quite manageable latency as well, thanks to a good Reflex implementation, 5.62 ms of present latency, next to no frame variation, not too bad:



Hopefully as the FSR 3 implementations begin to spread we see what the tech can truly do - and perhaps Nvidia "suddenly figures out" how to have DLSS frame generation working on their previous generation hardware :rolleyes:
My base framerate was 80 without FSR and 100 with at either framerate artifacts where impossible to notice like with anything if you capture frame by frame and pick out bad ones I am sure you can find them just in normal gameplay it isn't more or less noticeable than frame generation. The bigger problem for GeForce owners is having to use the really really bad FSR if you want upscaling.

I haven't tried it recently but artifacts in starfield made it unusable for me.
Posted on Reply
#30
john_
Dr. Drothey'll backport it to Ampere and Turing perhaps even Pascal if this gains any traction lol
No they will not. With 80% market share they don't give a --beeep-- about AMD's or Intel's competing technologies gaining any traction, because their goal is to keep selling GPUs. And the only way to do it, is by limiting new features in the current series, not give it to owners of older cards. Let's not forget that today, most users will get angry with Nvidia only to buy an Nvidia card again, so really, no reason for Nvidia to do anything.

Also with everyone everywhere and all at once saying how horrible FSR is in every implementation out there (even with the monitor turned off I am pretty sure they will see problems), Nvidia will use it as a proof that it is impossible to offer a DLSS solution for GTX owners and a Frame Generation solution for RTX 2000 and RTX 3000 owners that will be acceptable.
Posted on Reply
#31
Dr. Dro
john_No they will not. With 80% market share they don't give a --beeep-- about AMD's or Intel's competing technologies gaining any traction, because their goal is to keep selling GPUs. And the only way to do it, is by limiting new features in the current series, not give it to owners of older cards. Let's not forget that today, most users will get angry with Nvidia only to buy an Nvidia card again, so really, no reason for Nvidia to do anything.

Also with everyone everywhere and all at once saying how horrible FSR is in every implementation out there (even with the monitor turned off I am pretty sure they will see problems), Nvidia will use it as a proof that it is impossible to offer a DLSS solution for GTX owners and a Frame Generation solution for RTX 2000 and RTX 3000 owners that will be acceptable.
I'll get angry with Nvidia and buy an Nvidia card again because I know that AMD will make me even angrier, really.
Posted on Reply
#32
john_
Dr. DroI'll get angry with Nvidia and buy an Nvidia card again because I know that AMD will make me even angrier, really.
Many think that going AMD will be worst and that's why Nvidia does whatever it does today, not caring if it will make it's customers angry. For many there is only one option.
Posted on Reply
#33
StefanM
john_Has anyone hacked RSR to work on Vega or Polaris?
As announced earlier on several news sites, Vega and Polaris support has been physically removed from this driver series (23.30.x.x).

If you try to modify and force install this driver on those GPU's, you will end up with code 43

You cannot even extract and use the new OpenCL driver (procedure entry points missing).
Posted on Reply
#34
john_
StefanMhas been physically removed
To have something physically removed, it needs to be there in the first place. Any indication that Vega and Polaris had at some time RSR support?

In any case, my point was that AMD seems to be keeping some driver based features exclusive to it's latest series of cards or limit them to specific architectures. I don't think they are features that can be hacked and used easily with products that aren't officially supported.
Posted on Reply
#35
StefanM
john_To have something physically removed, it needs to be there in the first place. Any indication that Vega and Polaris had at some time RSR support?
I meant support for Vega and Polaris in general.

EDIT:
This happens with OpenCL on Vega

.
Posted on Reply
#36
john_
StefanMI meant support for Vega and Polaris in general.

EDIT:
This happens with OpenCL on Vega

.
Posted on Reply
#37
Zubasa
Dr. DroSo, how's the fake frames :D
I find it the most useful for emulators. They often have a 30FPS cap and the game often breaks if you try to uncap the native FPS.
This feature gets around that since it doesn't mess with the game engine speed.
Posted on Reply
#38
StefanM
john_
Yeah, driver 23.9.2 works fine on my Vega (Cezanne)
It is from the older series 23.20
Posted on Reply
#39
john_
StefanMYeah, driver 23.9.2 works fine on my Vega (Cezanne)
It is from the older series 23.20
It does say "RDNA" in that folder name, so probably a driver meant for RDNA only GPUs, never meant for Polaris or Vega in the first place.
Posted on Reply
#40
Vya Domus
One thing I don't understand is why they don't offer the option to keep it on at all times even if the mouse movement is too rapid, this does not make sense because you can have big changes between frames regardless of mouse movement and it doesn't look that bad when that happens, actually it looks no different to me. It's kind of jarring when it switches off if the base framerate isn't very high.
Posted on Reply
#41
Ferrum Master
Tested, well... It is just a tickbox for benchmarks.

Not sure it makes anything usable. If the FPS sucks, it will continue to suck, if it good it is good, you don't need it.
Posted on Reply
#42
ViperXTR
Dr. DroI said from day one Nvidia was lying, they'll backport it to Ampere and Turing perhaps even Pascal if this gains any traction lol
AMD seems to use Asycn compute for the generated frames, and pascal sucks with async compute unless nvidia uses other means
Posted on Reply
#43
wNotyarD
ViperXTRAMD seems to use Asycn compute for the generated frames, and pascal sucks with async compute unless nvidia uses other means
Pascal may have an issue, but what about Turing and Ampere? Can't NVIDIA develop a method, albeit inferior to Ada's it may be, so it can do similar on those generations?
Posted on Reply
#44
Vya Domus
wNotyarDPascal may have an issue, but what about Turing and Ampere? Can't NVIDIA develop a method, albeit inferior to Ada's it may be, so it can do similar on those generations?
We already know it works, FSR3 is out and frame generation works fine on those cards.

This isn't a technical limitation, Nvidia wont add it because they paraded those features as being 4000 series only, it's one of their main selling points. They wont turn around and go "Hey guys you know that feature we pretended couldn't work on older cards so you can buy the new ones ? Yeah, what do you know, we actually just lied to you, heh".
Posted on Reply
#45
john_
wNotyarDPascal may have an issue, but what about Turing and Ampere? Can't NVIDIA develop a method, albeit inferior to Ada's it may be, so it can do similar on those generations?
Imagine Nvidia offering FG to 3000 series. RTX 3060 and RTX 4060 are already very close in performance. If you remove the FG advantage from RTX 4060, you'll get a gazillion of articles/videos PROVING that Nvidia RTX 4060 is more or less the same performance/card 2 years latter and without a 12GB version selling for less than $300.
Posted on Reply
#46
Bruno_O
so many old games....

Elden Ring???? DLC is coming
Posted on Reply
#49
Vya Domus
oxrufiioxoHopefully they improve it just as fast because it's basically useless with how it behaves with VRR and only being able to use FSR2 with it.
Works fine for me with freesync.
Posted on Reply
#50
oxrufiioxo
Vya DomusWorks fine for me with freesync.
On my 6700XT, 3080ti, and 4090 its terrible and unusable.
Posted on Reply
Add your own comment
Nov 24th, 2024 12:16 EST change timezone

Latest GPU Drivers

New Forum Posts

Popular Reviews

Controversial News Posts