Has anyone had success with AMD Fluid Motion Frames in VR?

[Kageseigi]

I've got a 5800X3D, 6950XT, and a Quest 2. I saw that AMD just released drivers with FMF for the 6000 series GPUs.

I've been trying to get things working between the Oculus app with Quest Link (cable), Oculus Tray Tool, and OpenXR Toolkit, though still not getting the visuals+performance I'd like. I can't seem to get 72-90fps consistently, so it halves my fps and uses ASW (I believe) to smooth out the visuals, but that causes ghosting to planes.

I'm curious if FMF would perform better than ASW to prevent ghosting. I'm nervous about installing beta drivers, though... everything else it running great on my system. Thanks!

[Tomcat388th]

Here are my Quest2 settings I'm running the same cpu and gpu as you with 64GB ram.  I had trouble with OTT getting corrupted at times so I use the oculus debug tool for the extra settings.  One other setting that I did do was in the amd gpu settings  set max frames to 45 for me it really smoothed things out. If the cockpit seem to large on the dcs vr page change the force ipd num to scale it up or down Hope these help

J

 

[Kageseigi]

On 10/11/2023 at 5:59 AM, Tomcat388th said:

Here are my Quest2 settings I'm running the same cpu and gpu as you with 64GB ram.  I had trouble with OTT getting corrupted at times so I use the oculus debug tool for the extra settings.  One other setting that I did do was in the amd gpu settings  set max frames to 45 for me it really smoothed things out. If the cockpit seem to large on the dcs vr page change the force ipd num to scale it up or down Hope these help

J

 

Thanks a lot! I'll try these out!

[mrsylvestre]

I installed the latest preview drivers from AMD (23.30.01.02 from October 13, not the earlier version of which there are numerous rather unfavourable reviews on Youtube). I didn't expect much but someone on Reddit reported a significant improvement in iRacing so I decided to try these.

These kinda work. On the other, civilian sim and on DCS, these allowed me to bump VR resolution one notch while still getting fluid gameplay. On busy scenes, there would be stuttering without AFMF that is now, with AFMF and for lack of a better word, smoothed out: there might be some inconsistency from one frame to another, as if time was contracting or expanding just a tiny bit, but it is only noticeable if you look for it. So, if this technology is "Fluid Motion", there might be a little bit of turbulence in it, but I'll take that over brutal stutters any day. I did not notice graphical artefacts. Three remarks: 

1. My DCS options were already tuned in such a way to get around 72 fps (native on my Pico 4, no ASW/SSW) before driver update. Don't expect to magically go from 50 fps to 90 fps just with these drivers.
2. For AFMF to kick in, it could be that DCS has to be rendering also the 2D view (mirror of what you get in the headset) in full screen (you can check that AFMF is running by monitoring the AMD overlay activated by CTRL-SHIFT-O, on the flat screen).
3. The AMD overlay is the only tool that will display the true FPS (also counting the interpolated frames). Game counters and utilities that work upstream of the driver may only count the frames that are actually rendered by the game engine.

I didn't play with all options in the drivers, I just set the default profile to "performance" which includes AFMF and some kind of "super resolution" (driver level implementation of FSR upscaling) and disabled the latter as I run 2D native and the VR resolution is set by the streamer. I also did a proper driver clean-up before installing the preview driver, which may have helped. At this early stage, I am tempted to think that AFMF is a better driver-level alternative than the IQ-degrading RSR/FSR or the ghosts-inducing ASW/SSW to improve VR performance on flight and racing simulators (although it does not do miracles and will not replace an RTX 5090 or RX 9900 XT). These could be due to the fact that changes between successive frames in our sims is normally less drastic than in FPS shooters and we can also get by with a bit more latency.

YMMV.

[Sandman1330]

I have gotten it "working" myself. I put air quotes around "working", as I don't see any perceptible difference whatsoever.

AMD Adrenaline tells me it's on, and the AMD FPS overlay reflects the increase in FPS, but in the headset.... nothing. No perception of increased FPS whatsoever, and no frame gen artefacting (which I'd expect to see at least some).

I can only conclude that, while the driver may be generating those extra frames, they aren't making it across the WMR bridge into DCS. I still have a smoother experience using Radeon Chill to lock FPS at 45 (half refresh rate). This removes most micro stutters and greatly smooths out my experience. With FMF on, the stuttering returns as if I was still running around at 60fps.

Note, that in order to get it "working", I had to select "use DCS system resolution in mirror" in the VR settings. This made the mirror full screen and that's when Adrenaline started reporting FMF was working.

[mrsylvestre]

Using Radeon Chill to lock FPS at 45, or half 90 Hz refresh rate, is a neat trick. Thanks!

I just tried it in MSFS 2020 and it allows for a really fluid experience, without retroprojection artefacts with the right level of scenery details. I previously tried to achieve that through limiting frame rate with the OpenXR Toolkit but that didn't entirely cure stutter. Currently, my DCS settings are tuned so that I can have 72 fps native (no retroprojection) on the Pico 4 but I may try to bump refresh up to 90 Hz and set the limiter at 45 to see if I can trade off FPS against increased resolution or scenery complexity while maintaining acceptable fluidity.