“Above 4G Decoding” in your PC’s BIOS (UEFI) is a crucial setting for modern graphics cards, allowing them to access memory above the 4GB address space, essential for features like Resizable BAR (ReBAR) or AMD Smart Access Memory (SAM) to boost performance in many games by enabling larger data transfers between the CPU and GPU, though it’s found in the Advanced Settings under PCI Subsystem Settings and must often be enabled for ReBAR/SAM to work.
What it Does & Why You Need It
Removes 4GB Limit: It maps the GPU’s video memory (VRAM) into the CPU’s large address space, overcoming older 32-bit limitations.
Enables ReBAR/SAM: It’s a prerequisite for Resizable BAR (NVIDIA) or Smart Access Memory (AMD), which dynamically resize the GPU’s memory access window for faster data flow and better frame rates
For Powerful Rigs: Necessary for multi-GPU setups (like SLI/Crossfire), mining rigs, or professional compute tasks (GPGPU).
Moderator Note: Edited to remove font formatting. Please be aware that some devices / browsers / translation services add formatting to text that can cause it to display incorrectly on this forum.
I am thinking about getting this card once Asobo deals with the glitch of the artifacts at night. What are your thoughts on FSR4 vs DLSS? Anyone who has tested both can comment on the differences? I may miss DLSS but to be honest, the price difference with Nvidia for a similar card is huge
If you use the amd_fidelityfx_dx12 files from the Redstone SDK 2.1, you’ll have better performance.
That said, I have since decided not to use FG or upscaling. I use TAA and have adjusted my graphics settings to get a smooth and consistent 60 FPS with my 120hz monitor and set the game to 1/2 refresh.
The only artifacts I notice with Framegen FSR 3 are the flickering of the aircraft’s shadow projected on the ground. But frankly, you have to be close to the ground and at a certain angle, so in everyday use, it’s barely noticeable. It hardly happens at all with Framegen FSR 4.
Not quite. Though I have 3 displays, I only render MSFS on the main 55" TV. The two 32" displays are only used if I need items like the EFB in their own window, and for apps like Little NavMap.
Anyone else is having a stutter fest with “26th” series Adrenaline drivers? I even went all the length to see if installing the 26.2.2 + Chipset drivers via DDU in Safe mode is going to cure it, which I never did before, but nope - still the same on the ground. In cruise - it’s almost unnoticeable, I would say, on par with 25.12.1, but on the ground - it’s just bad! Don’t really want to roll it back to 25.12.1, as I think 26.2.2 is also helping to eliminate graphics artefacts at night, widely discussed in the other thread, even when not in SU5 Beta. But, for goodness sake, I can’t stand these stutters either! How did you guys cope with it, is your 26.2.2 work alright?
Hi Narva_61, so I’ve got a very similar system to you - 9800X3d, Aorus 9070XT & using the latest drivers: 26.2.2
I looked back at your April ‘25 post: “New PC for MSFS24”, & I’ve got to be honest - there’s loads of spec there I don’t understand!!, but it should be more than capable of running FS24 at Ultra settings.. Mine does without stutters - it did before when on the stable SU4, & also now on the SU5 Beta. I joined the Beta program partly to get rid of the windscreen artifacts at night, & also plain curiosity as I was always reading the Beta threads anyway.
Sorry but I don’t think I’ve been of any help, but you did ask if anyone with the same card & drivers was having a smoother time!
Edit: just started it up & went to Free Flight, zooming into Edinburgh for the start of flight ..& CTD
Don’t know about others, but as I figured it out on my machine, 26.2.2 had something to do with the frame gen.
Switched it OFF completely, now just TAA, no FSR, locked 60 FPS monitor resolution, 61 FPS set in Sim, Vsync ON with “full monitor refresh rate” rather than “half” set previously - somehow made the magic and now I am back in butter smooth sim again . A few more tests to do, but so far, a much better experience overall.
That said, I also wiped the Direct X shader cache, reset Sim scenery indexes, wiped off and reset the Rolling cache and once again reset the Shader cache in Adrenalin. Maybe that also helped a bit, but until I completely switched off the frame gen - micro (or not so micro at times) stutters were still evident, especially when panning the view on the ground and up to 2500ft altitude overland.
Yeah I had those switched off (these below ones you mean, right?), that was my initial thought too after seeing your earlier post in another thread, but no it did not help at all.
In my case, I also am not experiencing any stutters. I have the 9800X3D with the Asus Prime RX 9070xt.
I leave Adrenaline all at its defaults, other than setting it for performance. In Windows HAGs is disabled, VRR is enabled. ReBar is enabled as well but I keep my FS graphics settings at a level that it doesn’t fully saturate the VRAM, especially when on the ground. I use TAA and no FG. My monitor has FreeSync enabled and Windows set at 120 Hz. I enable vsync in FS at 1/2 refresh rate to get a nice smooth 60 FPS at all times.
Chiming in here
9800X3D/32GB DDR5/ 9070XT Asrock Taichi on a 3440X1440 ultrawide
I have always received my best performance in terms of visuals and frame pacing by
Turning off the monitors Variable refresh rate (Introduces flickering on most VA panels even in VRR range)
Using TAA if able to (Minimizes artifacting)…
Locking the in sim frame rate to (1/4 with Framegen) or 1/2 of your monitors refresh rate. For monitors with high refresh rates (165+) you have the option to knock the refresh rate down in windows or in your monitor settings.
Using VSYNC ( I use the adrenalin option not the in game one.)
and then setting up the game profile in the adrenaline software to handle the frame gen if desired. I find that using the in game FSR framegen introduces artifacts (eg PMDG 777 engine fan anomalies).
As long as VRAM is in check as RogueNaught1 posted these cards perform pretty darned well. Its a shame it didn’t come with more VRAM.
