ISSUE DESCRIPTION
Description of the issue:
Enabling the new FSR 4 settings in the sim and within the latest AMD Adrenaline software (v.26.6.4) results in intermittent active/inactive states.
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
-
Enable the AMD FSR upscaling and AMD FSR Frame Generation settings in Adrenaline before launching game.
-
Ensure correct settings in-sim
-
Select flight and begin the flight whilst monitoring the Adrenaline settings tab.
-
Radio buttons in Adrenaline will show green active symbol when flight loads. Shortly after the Frame generation yellow inactive symbol appears, followed by the yellow FSR upscaling. They may flicker off and on briefly before staying inactive for the rest of the flight.
YOUR SETTINGS
What peripherals are you using: Tobii eye tracker
[PC Only] Are you using Developer Mode or have you made any changes to it? No
[PC Only] What GPU (Graphics Card) do you use? Radeon RX 9070 Sapphire Nitro+ (Adrenaline v.26.6.4)
[PC Only] What other relevant PC specs can you share?
Ryzen 7 7800X3D
MSI PRO X670-P WIFI
DeepCool LT720 AIO
Radeon RX 9070 Sapphire Nitro+ 16GB GDDR6
32GB RGB DDR5 6000MHz
Samsung 1TB 980 Pro PCI-E NVMe
Adata 2TB NVMe
Kolink Continuum 1050W 80 Plus Platinum
Hisense 55U7NQTUK - 144Hz, 4k (Main sim screen)
AOC Gaming 27G2U - 144Hz,1ms, IPS, (1920x1080) (Secondary screen for charts etc.)
1GB (up/down) internet connection - LAN to PC
MEDIA
Please add a screenshot or video of the issue occurring.
Are you supposed to enable frame gen in both the driver and the sim?
I thought it was one or the other.
In the full release and all previous betas I only enable in sim to prevent conflicts.
Edit: I was confusing Fluid Motion Frames with the FSR Frame Gen upgrade option.
Same here, but I don’t even know if FSR Redstone Frame Generation ist even supported. It would be very helpful if this could be clarified. At least FSR AA works flawless for me even though it’s not shown active in Adrenalin and Vsync now works with Frame Generation which is a huge improvement for frame pacing. I’mm on a 9070 XT.
Just tested this myself.
As above if both FSR Upscaling AND FSR Frame Gen upgrades are enabled in Adrenaline then they both fail, as in show yellow in Adrenaline.
If I do not enable the Frame Gen upgrade, then the FSR Upscaling stays active in Adrenaline. I still have the in-sim frame gen activated and it works as per SU5.
Yes, some extra clarification is required. From what I understand, by enabling Redstone in Adrenaline, it should upgrade the 3.1 version.
From the AMD FAQ:
Enabling AMD FSR Technologies
There are two methods to enable AMD FSR Upscaling. Some games have native integration of ML-based FSR Upscaling and users can enable it directly from the game menu. In some games, the settings UI may still show the previous name for this technology, AMD FSR 4.
Other games have AMD FSR 3.1 or higher integrated and gamers can use AMD Software to swap DLLs and upgrade their game to ML-based upscaling. If the game has AMD FSR 3.1.4 or higher with frame generation, you can upgrade to ML-based frame generation.
For optimal performance, you should disable FSR frame generation and upscaling in the Adrenaline driver. Note that disabling these settings there activates native FSR 4.1 within MSFS; however, the driver-based update to version 4.1.1 fails and causes errors. In short: disable frame generation and upscaling in the driver, and use the native DLL implementations—version 4.1 for upscaling and 4.0.0 for frame generation. Also, note that using the driver settings results in frame generation artifacts and triggers an error message in Adrenaline.
How did you found out? Any sources? And how do you get FSR4 FG ingame? I only see FSR3.1 in the settings listed
I tried that originally, there is no in-sim way to enable FSR 4 for frame gen. The release notes state:
Added FSR4 support.
- Please note that, from now, in the settings, you only chose to use the AMD FSR or not. Which version will be used is set by your GPU driver.
Which is what I see in the sim, which implies that for FRS 4 frame gen to work, it has to be enabled in Adrenaline. However, the AMD FAQ specifies FSR 3.1.4 or higher for frame generation and it states 3.1 in the sim.
Rest assured, it is active—frame generation runs without artifacts! The FSR 4 DLLs are already implemented in MSFS 2024. The issue is that the driver currently triggers an error due to a conflict, which will likely be fixed by AMD. Specifically, the native version in MSFS 2024 is 4.1, and the frame generation version is 4.0.0. Yes, it is active!
The driver doesn’t yet realize that MSFS 2024 has native support for FSR 4! The driver is running FSR 4.1.1 and Frame Gen 4.0.1. This causes conflicts and artifacts!
All FSR4 DLLs are already implemented natively! Only use the driver if you want to use the latest version, 4.1.1. However, this is causing conflicts.
In my limited testing FSR Upscaling is working just fine, when you just enable that in Adrenaline. I can tell it’s working in-game too.
It’s when you enable Frame Gen in adrenaline that I see the same Adrenaline issues as OP. However to @EricP6825 's point, it’s working. Adrenaline saying upscaling/frame gen isn’t working when it is, that’s a classic thing that happens with Adrenaline across several games. Further, you can tell it’s working because the artifacting is pretty rough, especially around the edges of the screen. But if you enable FSR upscaling and then just use in-game frame gen, not frame gen in adrenaline, it works. However you can tell it’s 3.1 frame gen as it’s a little sizzly.
You also need to enable “AMD FSR frame generation”
Right, however when you enable that you get two issues. 1. you get the issue the OP describes where Adrenaline is not showing them active, even though they are. 2. You will get heavy artifacting with frame gen on, especially when panning around.
My point was to show that when you just enable FSR upscaling, it’s all fine. Frame Gen seems to be the issue.
Seems to be working stable for me and also shows “active” in Adrenalin and also in its overlay.
That is with 7900XTX (so 7000 series, not 9000 series)
Some simple instructions in the release bulletin on how to activate FSR4 would have gone a looooong way! While it’s a beta release for now, hopefully instructions can be improved upon for general release if Adrenalin driver settings are involved to activate FSR4 upscaling/frame gen.
Not everyone is a developer who can make sense of this stuff. 
I did several testings now and for me AA and FG only work properly when activated in Adrenalin. When you activate both they’re shown as “inactive” but they’re still working! It’s even written in the change logs that it’s depending on the driver. Maybe it should be written directly into the settings menu that it must be activated in the driver!
I can confirm it’s working great with my primary sim PC with a 7900xtx and shows AMD FSR 4.1 active when FSR upscaling upgrade option in the Adrenalin driver is turned on (exactly as you showed in your screenshots).
On my other PC with a 9070xt, it’s a totally different story with the FSR4 upscaling and frame gen upgrading indicator in the Adrenalin driver dashboard flipping on/off.
Here is some videos to show the difference. Running on a 7800X3D with 32gb of RAM and a 9070 non-xt. Drivers are version 26.6.4. In the MSFS settings I have FSR 4.1 and FSR 3.1 frame gen enabled.
Video with FSR Upscaling enabled in Adrenaline:
Video with FSR Upcaling and FSR Frame Generation enabled in Adrenaline:
So the second video is definitely injecting FSR 4 FG, it’s just artifacting more than 3.1. For now I will just use FSR upscaling only in Adrenaline until there is a fix found within the sim, or it might require an AMD driver update and we have to wait for that.
Ok I was able to get rid of the artifacting seen in the second video by setting the secondary scaling back to 1.0 instead of 2.0 inside my usercfg. Beta servers are so slow to load it took a while for me to go back and forth to see the difference.
