That must be a limitation with your 6000 series gpu but it didn’t seem to impact @Maxisone that way so it’s a headscratcher. Have you tried capping your framerate at 60 instead of 30? AMD’s Adrenalin driver has a fairly new option to cap framerates that you could try also if you haven’t already.
Yes and yes. Capping my frame rate at 60 did nothing. Capping in Adrenalin doesn’t work. At least not in conjunction with FMF. I know others got the in sim vsync to work, but AMD has been publishing that vsync should be disabled. Not surprising that it didn’t work for me, but is surprising that I’m getting tearing when it is capped at a synced frame rate. Unless maybe the tearing is actually artifacting that happens to mimic tearing?
Ok, this is a long shot and apologies in advance if you’ve already been down this path. Freesync has several tiers with additional features as you move up to the higher tiers - see link below.
I don’t know the make/model of your monitor and what resolution you are using but you did say it had a 60Hz refresh rate so I’m assuming it supports the first level of freesync. You also mentioned you were trying to cap the fps at around 30 and I don’t think freesync will really work or do much at 30fps. The monitor I use is a Samsung Qled and it supports 120Hz refresh along with freesyn premium pro (required to sync the HDR data). In the Adrenalin driver under display specs it states:
So it’s alluding that freesync doesn’t really do much at under 48Hz for my monitor. From what I can research it seems common that monitors have a lower end threshold similar to mine where freesync will be questionable.
You’ve got a really good gpu - have you ever tried your PC with a different monitor?
I don’t remember the exact number off hand, but my monitor’s Freesync is good down to 40-45 fps. The reason for capping at 30 real frames is so the generated frames bring the final output to 60 fps, which theoretically keeps it naively synced. Even if it dipped any, the Freesync should still be kicking in.
I don’t have another monitor to test with. If it were a big deal to me, I could test on my Freesync capable 4k120 TV, but that would require a lot of setup to move things into place.
This now has me wondering when the Freesync actually kicks in. In other words, if it applies only to the real frames, to the final output including the generated frames, and how it’s interpreted by the monitor. Maybe you or someone else could test this?
Compare and test for tearing under these conditions.
-
Adjust settings so the real frames AND FMF frame rates both fall in your monitor’s Freesync range.
-
Adjust settings so the real frames fall within the Freesync range, BUT the FMF frame rate is above your monitor’s refresh rate.
-
Adjust settings so the real frames fall below your monitor’s Freesync range BUT the FMF frame rate falls within the Freesync range.
I haven’t seen anything regarding this specifically, but my working hypothesis is that to prevent tearing, scenario 1 has to be true. Scenario 2 causes tearing due to the sim unable to prevent it at the render level, so it remains in the generated frames. Scenario 3 tears because while the sim renders without tears, the generated frames push it above the monitor’s capabilities and vsync isn’t allowed (for whatever reason) to keep things in check.
Who knows, maybe I’m way off base here.
Did some testing based upon your 3 points in your last post.
This is my set up:
- PC w/7900x3d, 32gig DDR5-7200, RX 7900XTX (full specs in profile)
- MSFS 2020
- Graphics - 4k full screen, TAA, HDR10, vsync on at 100% of monitor refresh, DX12, everything else Ultra.
- Traffic - Real time, vehicle, ground aircraft, & worker density all at 60%
- Weather - Real time
- Rolling cache - off
- 3rd party add-ons - none
- AMD Adrenalin driver: all defaults except:
- FMF - on
- Anti-lag - on (as per AMD recommendations)
- Freesync - on (as per AMD recommendations)
- Turned on performance monitoring so as to capture fps rates
- Monitor: 55" 4k Qled 120HZ refresh rate supports all 3 tiers of freesync, freesync range 48-120Hz
- A320 Neo sitting on runway at EGLL: 50-60fps real/100-120 FML
- No tearing while extreme panning in cockpit. Not quite smooth as butter but no tearing (as smooth as your going to get sitting on EGLL runway).
- A320 Neo above London: 60-70fps real/120-140 FML
- No tearing while extreme panning in cockpit and external camera. Buttery smooth. Note, fps indicator on Qled TV never went above 120fps so confirmed frames were dropped.
- A320 Neo sitting on runway at EGLL: 40-55fps real/80-110 FMF
- Minimal tearing while extreme panning w/external camera.
Added additional point:
4. Adjust settings so both the real frames and FML frames exceed the monitor’s Freesync range.
- Sitting at main MSFS menu at real time frame rate ~240/FML ~480, sequencing through menus and spinning the globe to set up flight plan.
- No tearing - buttery smooth. Note, the fps counter on Qled TV pegged at 120fps & never went above 120fps so frames were dropped.
Anyone using GSX Pro with the sim and AFMF? I can’t seem to get it to work as the AMD Adrenaline software sees the active exe file as couatl64_msfs.exe instead of the flightsimulator.exe. I cannot see a way to force the and software to recognise only the msfs exe
Just installed the currect AMD “preview driver” for the FMF and tested it for the first time. It immediately worked as intended and drastically increased the FPS.
Tried “easy” environments but also mainly “intensive” areas like NYC and LA low level flight.
I must say, I’m pretty impressed! From what I have seen, there is no noticeable degradation in visual quality, except maybe a little when quickly rotating the camera outside. So for now I’m planning to keep it enabled, for me it seems to be a big improvement for FS2020.
P.S.: unfortunately the FMF cannot recognize the “low power mode” setting of FS2020 (experimental menu), which I have switched on to reduce power draw and heat in the menus. GPU is blazing quite high now there.
I assume this driver is only for AMD graphics cards?
Yes on NVIDIA side they call it “frame generation” with their driver
Yes I have it already thanks.
I was under the impression AFMF only worked in exclusive fullscreen mode, which isn’t available in MSFS?
Works with msfs “fullscreen mode”…
AFMF Stopped for me too. I played only once with it enabled and after this a simple reboot deactivated it.
I play with a Ryzen 5800X + RX 7800XT in fullscreen without Vsync on a Freesync 144hz 1440 monitor.
So now I’m capped @ 80fps (with it fonctionnal I was +/- @ 150)
Not particularly impressed up until now. OK yeah it more than doubles fps but I’m using head tracking so the camera keeps moving ever so slightly 100% of the time. Which means I have constant bluriness, as if I had enabled lower scale rendering. Not to mention the tearing regardless of Vsync.
It’s good in situations where I have way too low fps (e.g. unoptimized 3rd party airports where fps can drop to 25-30), but most of the time elsewhere or when in the air, AFMF may be doubling my original 50-60 fps but to the cost of bluriness and tearing.
So I’ll probably end up using it sparingly and will also prioritize upgrading 5600X to 5800X3D because whenever fps decreased is always due to CPU bottleneck according to dev mode stats.
Have you installed the v24.1.1 driver? If you turn on AFMF both in the general section and the game specific MSFS section it should stay on. He’s a link on how I did it. Turn on AMD Frame Gen
Don’t cap it - turn vsync off in the sim (or maybe leave it on at 100% of monitors refresh rate).
Edit: Also turn on all 4 of these parameters in Windows:
Theses 4 parameters are ON since years and yes AFMF is ACTIVATED in Adrenalin in all sections (game and general)
Like I said Vsync is NOT activated and I play in FullScreen
So I match with ALL parameters needed to run AFMF.
Please read before reply and post for nothing. TY
Hello, I cannot run AFMF I get following failure code: please use direct x 11 or 12 api (german: bitte verwenden sie das direct x 11 oder 12 api). May be its because I have the steam version and steam is running in the backround? Im running fullscreen with V-sync switched off.
Greetings Uli
I don’t wanna be a “boomer”, but this feature is like a placebo, yes you get a double frame when you keep static the camera view, but if you move it, you will get your original fps for a few seconds, then after a while you will recover the double fps.
If you will keep a static view when you fly, maybe this feature will works fine for your, otherwise don’t bother.
But always, try it and get your own conclusions.
Sorry for my english.
TAA or FSR2?