On 9/27/2026 at 12:53 AM, Reset XPDR said:

I haven't seen or heard of that Steam overlay behaviour before. My best guess is either a GPU driver issue, where it's mistaking the AutoFPS window for a rendered game window, or a Steam update has changed something that makes the overlay appear on non-game windows like AutoFPS's UI.

If it's the driver, and you've updated it recently, I'd roll back to your previous version. If it's Steam, and it keeps happening, disabling the Steam overlay until they fix it on their end would be worth trying.

As for the poor performance and the game not feeling focused, a driver rollback might help with that too. Also, since you're using 2X in-game FG, try changing the AutoFPS Target FPS Type to Auto and letting it auto detect. Man FG is really only for situations where auto detect doesn't auto detect properly.

Follow up.

Did a clean install of 617.74 driver, disabled the FPS overlay and set type to Auto. Quite smooth now again. Cheers.

@Reset XPDR The wonderful world of FrameGen for VR users has arrived in the form of the following;

Original; Releases · tig3rmast3r/OFXR-Bridge

There's a Fork I'm currently using as it has a 3x FrameGen option which works great;
Releases · djules75/OFXR-Bridge

Now this opens up all new possibilities with MSFS2024 mainly revolving around increasing some graphical settings, but before I go down that rabbit hole I want to get AutoFPS playing as nicely as I can with it.

So with the pic below should I have the FPS target at 30 to yield best results? (bearing in mind using the 3x FrameGen option in the mod to achieve 90fps).
I'm also seeing the TLOD numbers go Orange but it's still rising when it does.

Also anything else in there strike you as "odd" or in need of change? thanks 🙂

10 hours ago, MarcG said:

@Reset XPDR The wonderful world of FrameGen for VR users has arrived in the form of the following;

Original; Releases · tig3rmast3r/OFXR-Bridge

There's a Fork I'm currently using as it has a 3x FrameGen option which works great;
Releases · djules75/OFXR-Bridge

Now this opens up all new possibilities with MSFS2024 mainly revolving around increasing some graphical settings, but before I go down that rabbit hole I want to get AutoFPS playing as nicely as I can with it.

So with the pic below should I have the FPS target at 30 to yield best results? (bearing in mind using the 3x FrameGen option in the mod to achieve 90fps).
I'm also seeing the TLOD numbers go Orange but it's still rising when it does.

Also anything else in there strike you as "odd" or in need of change? thanks 🙂

I had a feeling support for this new mod would be coming my way shortly, and here we are! 😄

At the moment, AutoFPS is FG for VR unaware. In fact, it is also Motion Reprojection (MR), the predecessor to this FG mod that does a similar thing, unaware because there is no way for the app to detect it.

As such, until I work out whether the FG multiplier for this FG mod is detectable or not, just do what you always did if you used MR - just set your target VR FPS as pre-FG/MR.

As for whether to set 29 or 30 FPS in your scenario, if you have capped your VR FPS to 30 and it maintains that pretty much all the time, then switch to Fixed target FPS type and use 30 as the target. If you regularly dip below 30, then set a target of 28 (29 is too close to 30) and stay on Manual target FPS type.

Awesome thanks I'll look into that later, the mods fairly new so constantly being updated, things are bound to change with it but it's certainly becoming something very decent for VR users.

On 10/5/2026 at 5:19 PM, MarcG said:

Awesome thanks I'll look into that later, the mods fairly new so constantly being updated, things are bound to change with it but it's certainly becoming something very decent for VR users.

Some good news! I have added full OFXR for VR support to the app, available for early access testing in 0.5.4.3-test3 here or via auto-update via the Test+ update channel in the app.

Relevant release notes are:

• Added Optical Flow OpenXR (OFXR) for VR support:

  • Automatically detected whenever OFXR Bridge Tray is running and armed while in VR mode.

  • Dynamically tracks active and paused states in real time: applies the detected frame generation multiplier (2X or 3X) when active, and displays native sim FPS when paused via hotkey.

  • Automatically pauses LOD adjustments and displays "OFXR ⏸" while paused to keep visual quality locked steady for seamless A/B comparison without exiting the OFXR profile.

  • Automatically reverts to standard VR mode if the bridge is disarmed.

  • Adds a dedicated OFXR Target FPS graphics mode with its own independently saved target FPS setting.

  • Displays the live OFXR status and multiplier (e.g. OFXR 3X, OFXR ⏸) directly on the app status line and UI.

In action with 3X FG active:

Now with OFXR paused via OFXR's hotkey, showing LOD changes are currently paused as a result:

As an aside, this is the first time I have tried this mod and I have to say I am pretty impressed with it for VR users. Prior to this mod, I had my FPS locked in MSFS to 40 and used my Quest 3's motion reprojection to double that to 80. Now with OFXR I have lowered my FPS lock to 30 and with 3X FG get 90 FPS in headset, and it looks just as good to me. So not only do I get slightly higher FPS but I am able to increase AutoFPS TLOD settings because the target FPS has been reduced by 25%. Finally, a win for Team VR!

Absolutely awesome as ever @Reset XPDR , when I get the chance I'll have a test with it 👍

Oh yeah this is awesome!

FYI, djules75, the maintainer of the current 0.2.X version of OFXR Bridge, reached out to me about my recent integration with AutoFPS. djules75 is happy to collaborate so our two apps stay aligned as reliably as possible, which is great news moving forward.

Edited Thursday at 10:24 PM5 days by Reset XPDR

Hey just a heads up...I'm not sure everything is working properly with the new OFXR addtition. With OFXR mode on, AutoFPS still shows my fps at 25 (1/3 refresh) when it's supposed to show 75. Because of that...My TLOD never increases.

6 minutes ago, FakeWayne said:

Hey just a heads up...I'm not sure everything is working properly with the new OFXR addtition. With OFXR mode on, AutoFPS still shows my fps at 25 (1/3 refresh) when it's supposed to show 75. Because of that...My TLOD never increases.

Are using 0.5.4.3-test version test3, which is what introduced OFXR support, or newer? If not you need to update to that first.

FYI, the app is looking for the OFXR Bridge Tray app to be running before you switch to VR and for the bridge to be enabled (should be by default). It should look something like this in your system tray, with the tooltip showing when you hover over it:

Once you switch to VR it should auto detect in the app. If still not working, can you message me the first section of your AutoFPS log file, located in %appdata%\MSFS_AutoFPS\log, which will show what the app detected.

16 hours ago, Reset XPDR said:

Are using 0.5.4.3-test version test3, which is what introduced OFXR support, or newer? If not you need to update to that first.

FYI, the app is looking for the OFXR Bridge Tray app to be running before you switch to VR and for the bridge to be enabled (should be by default). It should look something like this in your system tray, with the tooltip showing when you hover over it:

Once you switch to VR it should auto detect in the app. If still not working, can you message me the first section of your AutoFPS log file, located in %appdata%\MSFS_AutoFPS\log, which will show what the app detected.

@FakeWayne , did you manage to sort that out or is it still an issue. 0.5.4.3 has entered RC status now, meaning I intend to release it soon, and I would like to resolve your issue beforehand if it still exists.

@Reset XPDR I installed sboys3’s native SteamVR driver, configured PIMAX EVO and installed OFXR Bridge this afternoon. I then installed AutoFPS 5.4.3 Test 5, and everything worked seamlessly with my Pimax Crystal Light.

The updates you’ve made to incorporate OFXR have worked flawlessly. Much appreciated, and thanks for your work on this!

Regards,
pngmikel

MSFS_AutoFPS v0.5.4.3 has just been formally released, available either through auto update in the app or from here. My thanks goes out to all who provided valuable feedback during the test phase.

This release introduces comprehensive Optical Flow OpenXR (OFXR) frame generation support for VR users and delivers major enhancements to the In-Game Widget—including automatic vertical window sizing, a persistent show/hide toggle hotkey, and improved visual scaling—alongside installation and version detection refinements for custom Community folder configurations.

I recently discovered that a side effect of the new Widget auto-height adjustment is that, due to current limitations (or perhaps shenanigans 😄) in the MSFS widget panel interface, MSFS displays the correct widget height but internally remembers the original window height when it is opened, which is often much taller than the widget actually shown.

The result is that in 2D mode you may not be able to move the widget as close to the bottom of the screen as expected because MSFS thinks the window is taller than it really is. This is not an issue in VR because there is effectively no screen edge limiting widget placement.

I've now found an alternative resizing method that completely eliminates this false floor in 2D. The trade-off is that in VR, if the widget is closed and reopened, it will revert to its default size due to more MSFS shenanigans. Fortunately, the widget's 3D position is retained and the default size is generally quite usable, so I expect little to no impact for most VR users.

To test this approach, I have released 0.5.4.4-exp1, available via auto-update on the Exp+ channel or from here. This build contains only this change. If you've been frustrated by not being able to position the widget fully at the bottom of the screen in 2D, this should resolve that issue.

VR users may be less enthusiastic about the size-reset behaviour, but if you're happy with the default widget size or don't mind doing a quick resize in the rare event you do close then reopen the widget in a flight session, I'd still appreciate feedback on how it behaves in general use.

If the word "experimental" concerns you, don't worry. If you decide you don't like the change, simply restart AutoFPS and switch to any channel above Exp+. Auto-update will immediately return you to the current 0.5.4.3 formal release.

The reason this experimental build is being released so quickly is that I'll be away from my development PC for a few days. I suspect someone would eventually run into this issue while I'm gone, so I'd rather make a potential solution available now than leave it unresolved.

On 10/11/2026 at 1:56 AM, Reset XPDR said:

@FakeWayne , did you manage to sort that out or is it still an issue. 0.5.4.3 has entered RC status now, meaning I intend to release it soon, and I would like to resolve your issue beforehand if it still exists.

Hey sorry for not responding, I was out of town until today. But yes, I just figured it out. For some reason AutoFPS was thinking OFXR was paused, even though it wasn't. So I toggled the Pause function on and off, and that straightened things out for me.

It's awesome to hear you and djules are collaborating on this. Thanks for the hard work!