Official support for Windows Subsystem for Linux (WSL 2) enables users with supported hardware to develop with AMD ROCm™ software on a Windows system, eliminating the need for dual boot set ups.
WSL 2 Support has been added for:
ONNX Runtime
TensorFlow
Beta support on Triton
Find more information on ROCm on Radeon compatibility here and configuration of Windows Subsystem for Linux (WSL 2) here.
Expanded HYPR-Tune Support
HYPR-Tune support allows HYPR-RX to enable in-game technologies like AMD FidelityFX™ Super Resolution and AMD Radeon™ Anti-Lag 2.
Support has been added to automatically configure AMD FidelityFX™ Super Resolution with frame generation in:
Horizon Zero Dawn™ Remastered
MechWarrior 5: Clans
Red Dead Redemption 2
Click HERE for more information regarding HYPR-RX.
Click HERE for more information about other Vulkan® extension support.
Fixed Issues and Improvements
Lower than expected performance may be observed while using llama.cpp. This may also impact Ollama and LM Studio.
Texture corruption may appear while playing The Crew™ Motorfest.
System crash may be observed when first launching SteamVR while using Valve Index® at 144Hz on Radeon™ RX 6000 series graphics products.
Intermittent application freeze may be observed while loading a save file in Monster Hunter: World.
Intermittent application crash may be observed while playing Fortnite on Radeon™ RX 5000 series and above series graphics products.
H.264 encoding may not work as expected while using OBS Studio with Twitch Enhanced Broadcasting.
Known Issues
Intermittent driver timeout or crash may be observed while playing Warhammer 40,000: Space Marine 2 on some AMD Graphics Products, such as the AMD Ryzen™ AI 9 HX 370. Users experiencing this issue can enable Variable Graphics Memory in AMD Software: Adrenalin Edition as a temporary measure (AMD Software: Adrenalin Edition → Performance → Tuning → Variable Graphics Memory).
Intermittent stutter may be observed while playing Marvel Rivals when AMD FidelityFX™ Super Resolution 3 frame generation is enabled. Users experiencing this issue are recommended to disable AMD FidelityFX™ Super Resolution 3 frame generation in the per-game settings as a temporary workaround.
After using the AMD Cleanup Utility for Windows®, the AMD Bug Report Tool may appear intermittently during a new driver install on AMD Ryzen™ 7000 and above series processors paired with AMD Graphics Products.
HEVC encoding may not work as expected while using OBS Studio with Twitch Enhanced Broadcasting.
Limitations for Windows Subsystem for Linux (WSL 2) support can be found here.
Actually it’s second in the list of new supported games! I also hope the Adrenalin software can now recognise the Microsoft Store installation. A new driver was seriously overdue.
Loaded back in with Fenix A320 at Inibuilds KSAT with 24.12.1 and with AFMF on. I’m getting ~40fps natively at the gate and AFMF works to get up to 60-80fps (though with screen tearing that I can’t stand). I’d say it’s marginally smoother on 1% lows, but I’m getting more VRAM use (now at nearly 17.5GB).
Yup. Tried the same scenario in MSFS 2020 and only pulled 12.5GB of VRAM and 20GB of system RAM, though the fps was about the same on average. More stable, though, as I had more memory headspace. Granted, 2020 was on DX11 so it’s not apples-to-apples.
My Vram usage on 6800 has shot up with this driver on both 2020 and 2024. It starts at about 10GB when loading in, then ramps up to over 15GB and then stays there until I leave the flight. It then drops to just under 12GB.
Also noticed that the GPU utilisation fluctuates during the flight, whereas it just stayed at 99% previously.
It’s more of a concern that it’s using over 15GB in clear skies at altitude, there’s no headroom. I noticed a few long stutters/freezes which I didn’t get with 24.10.1 and was wondering if it’s to do with running out of Vram.
On my RX 6650 XT 8GB video card, the VRAM usage increased a lot, before in the FS2024 it was using more or less 5.5GB, now it is using the card’s 8GB, which causes performance problems. I needed to go back to 24.10.1
Just as a friendly reminder, Adrenalin v24.12.1 release notes specifically states it provides support for MSFS 2024. I have found things like AFMF are now working where previously it was broke so it’s running the sim better for me.
I have 2 PC’s, one with a 7900xtx and one with a 7700xt. If I run my 7700xt w/12gig vram in 4k with normal default Tlod/Olod it will use more than 12gig of vram which causes some stuttering as the vram data has to be cached in system RAM which is slower. I therefore bump the resolution down a notch or two or decrease the Tlod/Olod values to decrease the vram useage to keep it under 12gig.
The fact of the matter is the 7700xt is a great gpu but for 1440p so at 4k I was essentially trying to have it do more than it was capable. I think if you adjust a few detail oriented parameters down a little as per above your gpu will run great with Adrenalin v24.12.1. I know my 7700xt is best when I can use Radeon chill to keep the fps at a reasonable level the gpu is capable of and use AFMF to double it (while still being under my monitors refresh rate).
After all, any gpu can me more efficient using more vram!
Yay, I can join this club now as a 7900xt owner. I installed the minimal version and have done several longish flights in numerous Ini planes, Fenix, glorious! Coming from a 3070, I’m very impressed with this card.
I don’t know if AMD wants to give a Christmas present, but the 24.12.1 driver combined with Super Resolution and Fluid Motion brought me back my 2020 frame rate of 100 in Manhattan…
Newest Drivers show up in adrenaline on my laptop. 2024 would launch on my ally. Since updating to preview drivers on ROG ally x and then updating to 24.12 adrenaline still doesn’t see it on my Ally and this launches with a black screen. Reinstalling didn’t work. Anyone have it working on the Ally X with AFMF 2 drivers?
Also slightly improved performance here with the new driver; and also no more crashes of FS2024 caused by Adrenalin crash since (which I had before several times)
