Reset XPDR

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.

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!

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.

Following reports of some third-party aircraft and add-on camera views utilizing previously unhandled MSFS camera states (which caused DynamicLOD_ResetEdition to remain paused or stuck waiting for a session indefinitely), I have decided to release v0.6.0 ahead of schedule to deliver this fix promptly. DynamicLOD_ResetEdition v0.6.0 is now formally released and available either via the in-app auto-updater or by downloading directly from here. A huge thank you to everyone who provided valuable feedback during the test phase! This maintenance update expands camera state compatibility for third-party aircraft and views (fixing the stuck pause/waiting issue), improves camera state transition resilience, adds pause and unpause transition logging, and updates the bundled SimConnect libraries to the latest MSFS 2024 SDK version.

Following reports of some third-party add-ons utilising previously unused MSFS camera states (which caused AutoFPS 0.5.4.1 and earlier to remain paused indefinitely), I have decided to release v0.5.4.2 ahead of schedule to deliver this fix promptly. MSFS_AutoFPS v0.5.4.2 is now formally released and available either via the in-app auto-updater or by downloading directly from here. A huge thank you to everyone who provided valuable feedback during the test phase! This maintenance update expands Mountains+ in Free TLOD mode to all altitudes, resolves an issue with in-game widget telemetry when starting minimised to the system tray, expands camera state compatibility for third-party aircraft and views, improves camera state detection resilience, and refines upgrade logging and onboarding prompts.

All I was saying is that if you choose to set a custom Community folder location in the AutoFPS installer itself, it requires you to ensure that either MSFS knows of this custom Community folder location directly or, if you are using Addons Linker, that you have enabled the mobiflight and, if applicable, widget simlinks within Addons linker if you expect AutoFPS to find them, regardless of whether MSFS is running or not. ie. you can't configure a custom Community location for MSFS without telling MSFS, and hence AutoFPS, where to find it, and this applies to any addon you choose to configure this way. The fact that AutoFPS could not locate a module suggests you did not enable those symlinks before you ran it. As already mentioned, the installer now gives you a warning to configure proper linking if you choose a new Custom Community location in the installer.

If you don't mind the input lag and visual glitches from dynamic FG when your base FPS drops low, you won't need this app. But if you want to avoid those artifacts caused by keeping TLOD too high during demanding flight phases, the app is worth using.

A base-only toggle would actually work against what Mountains+ is designed to do. It was originally built around the idea that the mountain bump started at TLOD Max, so you get consistently better mountain terrain the higher you go. The change I just made extends that bump to cover all altitudes in TLOD Free mode, including on the ground. Making it apply only at the base would mean deliberately turning that off everywhere except below Alt TLOD Base, which includes being on the ground, and that's really the reverse of the feature's original purpose and would confuse and likely displease other current users of the feature. It's also not a small change under the hood. Quite a few places in the code assume TLOD Max already has Mountains+ factored in, so scoping it to base-only would mean adding protection against TLOD Min + Mountains+ ending up higher than TLOD Max, which gets fragile fast for what's really a fairly narrow use case. Given you've already got six profiles to play with, I'd suggest just setting up one specifically for ground-level mountain flying with a higher TLOD Base to start with. You get the visual improvement you're after on the ground without needing a new, more delicate code path, and you can keep your other profiles exactly as they are for everything else.

@agent00729 , well that was a storm in a teacup on my part! 😄 It turns out it was a simple edit of only one line of code to allow Mountains+ to apply up high, down low and on the ground in TLOD Free mode. Note, this only works in FPS Sensitivity and Tolerance modes. Mountains+ still behaves the way it previously did in AutoTLOD mode, as this mode works to a very specific altitude/TLOD schedule. Imgbb is down for maintenance at the moment so I can't upload and post up the screenshot I did of it working until it is back up. FWIW, the screenshot shows me on the ground at Lukla (9300 ft elevation) with TLOD Base 50, TLOD Top 200, Free TLOD, Mtns+ enabled Mtns Extra +200 and trigger elevation of 5000 ft. Before the change, these settings and location would have achieved TLOD 200 as the maximum. Now with the change it goes all the way up to 400 (ie. 200 + 200). I have released it in 0.5.4.2-RC4 available here or via auto update with the RC+ update channel selected as a minimum, so give it a go and let me know if that is what you were after. Edit: Of course, just as I post this Imgbb comes back up. Here is the screenie:

The Mountains+ feature was really intended for greater than Alt TLOD Top flying, so your suggestion doesn't quite fit with that. You could always use TLOD Base Extra and a high enough multiplier to get you to TLOD Max (albeit without Mountains+, but still better than TLOD Base). Alternatively, you can use TLOD Free mode, which will also give you up to TLOD Max on the ground. Finally, you can do either of those and just set a higher TLOD Max in the first place for such flights, as you have six profiles you can customise. Having said that, while I have 0.5.4.2 in development, I will look at whether I can expand TLOD Free to allow up to TLOD Max + Mountains+ when active on the ground, so that way you have the full band. I am reluctant to extend that to TLOD Extra and Fixed, as in those modes users specifically want a lower TLOD on the ground and this would go against that. No promises though, as my recollection of the code for Mountains+ is a bit complex and it has been a while since I touched it. If it is too hard for 0.5.4.2, which is in the final phase of testing so I don't want to add potentially buggy new features at this late stage, but is still possible, I will aim to put it in the 0.5.4.3 test program.

Thanks for the extra feedback. In your earlier post you said this, which I currently cannot explain: When AutoFPS is not running, there is no interaction with MSFS whatsoever other than the existence of the widget, if you chose that installation option, or the mobiflight module folders in your community folder. The mobiflight module is a requirement for both 0.5.3.0 and 0.5.4.1 and is the same version, so it should not be that. You say you tried without the widget installed, but did you try it without the widget installed AND AutoFPS 0.5.4.1 not running? One thing worth double-checking: did you enable the Auto-Start option during install? If so, AutoFPS would actually launch automatically whenever MSFS starts, even if you never open it yourself. Could you check Task Manager for AutoFPS.exe right after MSFS launches, before you manually open the app, just to confirm it's genuinely not running in that state? I am happy to keep diagnosing this issue, but as we have had a few posts on this now it is probably best we take it to a PM and carry on from there. I really would like to get to the bottom of it!

Further to above, I have gone ahead and created said warning message in the installer. It only shows if you click the custom folder button and pick anything other than the default MSFS Community folder, even if you pick the same custom folder you've already selected before. If you don't click that button, you won't see it.

I'd like to stop this happening and hence first need to understand why. Is it because you think only the Widget, not the mobiflight module, needs enabling in Addons Linker because mobiflight has always lived in your actual Community folder in the past? If so, would providing a warning message in the installer when a custom Community folder has been selected to advise the user to ensure both the Widget AND the Mobiflight module need to be enabled in Addons Linker if that is what is being used?

If you used the custom Community folder location when installing, it moves your mobiflight module to that location and deletes the original, on what I had thought was the reasonable expectation that you would subsequently select it in Addons linker so that its simlink gets placed in your real MSFS Community folder. If you did not do that latter step, it could explain why you are having issues.

Thanks for the detail. That's interesting that it happens even without launching the app, because other than installing the MobiFlight WASM module, and Widget if you chose that option, in your Community folder, there is no other interaction with MSFS when AutoFPS is not running. A couple of quick things that would help me narrow it down: Which version of AutoFPS were you on before this started, and roughly when did it begin? Are you using AutoFPS's custom Community folder option, or just the default one? If you're using a custom location, that could explain why MobiFlight's files ended up somewhere different than expected. Also, could you check your Community folder for anything related to MobiFlight WASM? Just let me know if it shows as a regular folder or as a shortcut/link, a screenshot would work fine too if that's easier. That should give me enough to figure out what's going on.