Reset XPDR

No worries. I will have a go at it tomorrow, which will be T-3 days before wife-return panic stations! 😄

@GSalden I've looked into the Night profile pairing idea some more and it is definitely feasible, so I'm happy to add it if it suits what you're after. How it would work: name two profiles the same, with one of them ending in Night, e.g. 'IFR' and 'IFR Night'. When night falls, AutoFPS automatically switches to the Night profile, and back again when it becomes day. A couple of things to be aware of: - Night mode (TLOD halving and cloud reduction at night) will be automatically disabled in both paired profiles for as long as they are paired. Since the Night profile is your night setup, having Night mode reduce things on top of that would double up. Unpair them (rename either profile) and your Night mode settings return as they were. - The switch between profiles happens at the moment day turns to night (or vice versa), so the change in TLOD and settings may be abrupt, much like when switching to VR now. I won't be implementing smooth transitions between profiles, as blending two completely different sets of settings would be a coding nightmare. Also, the Reduce display in Sim Values being hidden by night cloud reduction is fixed in 0.5.5.1-test1 or later. Settings reduction takes priority, with the night cloud reduction shown when you hover over it. Let me know if the Night pairing would work for you and I'll include it in a 0.5.5.1 test release. If it doesn't suit, then the current Night mode is as far as I'll be taking night settings in AutoFPS.

FYI to anyone using tigermaster's OFXR Bridge v0.3.2.0 or later: tigermaster has now graciously added the live status.json feature that djules introduced last week. This allows AutoFPS to obtain live headset FPS data directly from OFXR Bridge, enabling significantly more accurate automation. One important thing to note: the feature is disabled by default after a fresh install or update. To enable it, open OFXR Bridge settings and tick Export status.json under the Display tab. Once enabled, AutoFPS will automatically detect it. You will know it is working when the FPS source icon changes from FS to OFXR after entering VR with OFXR Bridge running. Ignore that I am using 0.5.5.1-test in the screenshot. It works exactly the same in 0.5.5.0 as support for this feature is automatically detected. Enjoy!

Just a general notice. You've probably noticed I've been rather prolific with AutoFPS updates over the last month and have been knocking off quite a few user requests. The simple reason is that my wife has been away travelling, leaving me with far more spare time than usual to work on the app. That all comes to an end on Sunday when she returns home, so expect AutoFPS development activity to slow back down to normal levels. If you have any dormant issues or feature requests you'd like me to look at, now is probably the time to mention them. Anything non-critical raised after this week may take longer than it has over the past month to make it onto the to-do list. On second thought, make that Saturday. I still need to clean the house top to bottom before she gets back! 😄

I am not sure what you mean here. Admittedly, it no longer shows Reduce and the level in Sim Values if Clouds at Night is active which I will address in 0.5.5.1 that is now in its initial development phase, but you can still hover your mouse over that Clouds label or value and the reduction amounts per setting will then appear below as they normally do eg.: If you meant something else, please clarify. The app used to have TLOD min reduce by 50% at night, but it was removed as most users have this set fairly low already and the primary purpose of Night mode is to reduce system load while you are flying, when TLOD Max is the main thing in play. Your suggestion of having a separate TLOD Base and Top at night will add more complexity to this already busy UI and associated config settings arrangement. Nonetheless, I have a cunning plan, which is to offer you what can already be done in the app for auto switching between paired 2D/VR or paired sim rate multipliers by how you name your profiles. eg this is how mine is currently set up for 2 paired 2D and VR profiles, one set for IFR and the other for VFR. If I start my flight on say the IFR profile in 2D and then I switch to VR in MSFS, the profile automatically switches to IFR VR, which has completely different settings. If I did this for Night, it would be a similar arrangement where you would have two profiles with exactly the same name then with one of them you just add the suffix Night eg. 'IFR' and 'IFR Night'. When night falls, it would automatically switch to the IFR Night profile and in the day it would go to the IFR profile. This would be fairly easy to implement as the pairing detect logic is already there and I would just have to add Night and the day/night trigger condition to the mix. Would that satisfy your desire to have completely different night settings than for day?

Not exactly. Per the readme section on the spike protection feature, the specific spike pattern it is looking for can happen at any TLOD level, but the higher the TLOD level is the greater the chance of such spikes. In recent MSFS 2024 releases, those spike patterns are not as prominent, but they can still occur. If you are experiencing stutters at around a 1 second cadence, then it is worth running RTSS to get spike protection and see if it resolves it.

MSFS_AutoFPS v0.5.5.0, created from the final v0.5.4.5 test version, 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 major update introduces a comprehensive rewrite of the readme for vastly improved readability, alongside a next-generation In-Game Toolbar Widget and Web Interface with camera-based auto-hiding, interactive FPS controls, and full desktop visual parity. Other key highlights include dynamic graphics mode management, native MSM and VectorXR frame generation integrations, enhanced OFXR telemetry, dual-layer VR conflict protection, unified Night Mode cloud controls, and refined fixed FPS configuration warnings. Please review the redesigned readme here, which provides a detailed description of the app, installation, features and settings, before asking any questions or raising any issues about the app. For this release, the original format readme is also bundled alongside the new version.

It is an interesting suggestion on paper, but in practice linking OLOD to ground speed introduces a few technical snags that usually make performance worse rather than better in MSFS. The biggest issue comes down to how MSFS handles asset loading. If OLOD is tied to a speed threshold like 30 knots, decelerating below that mark on rollout or runway exit would cause the sim to suddenly request hundreds of extra models, apron clutter, parked vehicles, and ground gear. In MSFS, sharp increases in object counts cause noticeable main thread hitches, so crossing that speed threshold would almost certainly introduce a heavy stutter right as you are clearing the active runway. The same problem would happen in reverse during takeoff, or repeatedly during stop and go taxiing. Another consideration is that taxiing near terminals is often where system load is at its absolute peak, rather than its lightest. At complex payware hubs, having maximum OLOD on the apron spikes draw calls and saturates VRAM because of high-detail jetways, terminal interiors, and ground equipment. Moving at low speed reduces the rate of new scenery streaming, but it does not reduce the rendering cost of having thousands of high-poly airport objects on screen at once. AutoFPS already handles this scenario pretty well through its reactive target frame rate logic. If your system begins to struggle on approach or while moving through a heavy airport, the app dynamically steps down the LODs to protect your target FPS and smooth out frame pacing. Instead of tying OLOD to ground speed, the most reliable setup for heavy hubs is to keep the ground OLOD capped at a sensible, steady value (such as 100 to 150). Maintaining a consistent OLOD avoids asset streaming spikes entirely and preserves vital headroom when manoeuvring around dense terminal gates.

The most likely reasons TLOD is staying that low are: Your Target FPS is set too high, so AutoFPS is keeping TLOD low in an attempt to reach it. Your default MSFS TLOD is set fairly low. For example, when using the IFR profile, an AutoFPS TLOD of 18 corresponds to an MSFS TLOD of 72, which is quite conservative for a 7800X3D/4090 system. To fix it: 1. Review your Target FPS configuration: If using Fixed Target FPS, set it at, or no more than about 5% below, the FPS your system can normally sustain. If using Manual Target FPS, set it at least 5% below the FPS your system can normally sustain. In practice, a little more margin can help, as settings-reduction recovery requires FPS to remain at least 5% above target for several seconds before recovery begins. Alternatively, use Auto Target FPS, which will choose a suitable target automatically and also provide a higher starting TLOD. 2. Review your MSFS TLOD setting: When AutoFPS is not running and you are not in a flight, increase your MSFS TLOD setting. For your hardware, I would recommend at least 100 as a starting point. If you're still seeing TLOD around 18 after that, let us know: Which Target FPS Type you're using (Auto, Fixed or Manual) Your Target FPS value The approximate FPS you normally achieve in the aircraft and airports you typically fly Your MSFS TLOD setting That should be enough information to quickly identify what's keeping TLOD so low.

FYI, in the just-released 0.5.4.5-test17 version, widget v1.5.6 introduces an Auto-Hide dropdown in the header, essentially replacing the old show/hide hotkey setup with a fully automated solution for external and VR flying. You can set it to Off (default and always visible), Chase (hides only in external chase view), or All Ext (hides in chase, drone, and all exterior views, popping back within 1 second in the cockpit). Any previously configured hotkey will still work in the background, but the toolbar button has been retired to keep things clean. You will also notice you can now collapse the General controls section by clicking its header chevron. This tucks away all the dropdowns, steppers, and checkboxes when you don't need them, giving you a much more compact, minimalist widget focused purely on your live Sim Values and status telemetry. Edit: 0.5.4.5-test18, rolling the widget to 1.5.7, was released shortly thereafter as I found a way to make the widget window hide/show much more responsively to the view change, after collaboration with MajorDad from WeSimGlide over on Discord. Behaviour is otherwise the same as Test17.

Let's simplify this so you can stop wrestling with settings and just get in the air. Part of the confusion may come from having two different things called dynamic happening at once. First, turn off the in-game dynamic settings in MSFS. If that is turned on, the sim and AutoFPS will constantly fight each other over your graphics if you have not set the target FPSs for both correctly. Second, switch from dynamic frame gen to standard fixed frame gen. Dynamic frame gen forces AutoFPS to target your raw, pre-doubled framerate, which is really tough to tune. Standard frame gen is much easier because it just targets the final framerate you actually see on your screen. As for your 60 cap in Nvidia, here is how the targets work. If you use Fixed, the app expects your framerate to be very stable. The trick here is, that if it is not super stable, to lower the floor just a tiny bit so small wobbles do not penalise your graphics. If you are capped at 60 and your frames hover right around there, try setting your Fixed target to 59 or 59.5. That gives you just enough padding so tiny dips do not drop your settings to the bottom. If you use Manual, it works on a different system and needs about 5 percent headroom above the target to scale your graphics properly. For a 60 cap, that means setting your Manual target down around 57. Honestly, if you just want low settings on the ground and high visuals in the air without worrying about framerate numbers at all, give Auto TLOD mode a try. It completely ignores your FPS and just handles the transition between the runway and cruise automatically, which might be the simplest solution of all.

DLSS FG works fine as long as you make sure you give MSFS the focus back after doing something else. FSR makes it easy because it doesn't matter what Windows is currently focused upon.

Out of all the 2D FGs, I actually prefer FSR as it doubles FPS regardless of whether MSFS has the focus or not, and that keeps the load on AutoFPS constant rather than all this active/inactive business that nVidia DLSS FG does that presents a different performance load to AutoFPS in each state.

Given that it says DLSS all over the place in the mod's UI, then I'd say it is somehow tricking the graphics driver to give you nVidia DLSS MFG so it will probably behave the same as normal DLSS FG and not multiply on the secondary monitors. There's only one way to know for sure. Fire it up and see!

I have no idea, sorry. Its existence was only revealed to me today and I was able to add it in so quickly because its interface is very similar to LSFG which is already there. I've only tested it to make sure AutoFPS gets the right FPS readings and behaves appropriately and haven't actually used it for a real flight yet.