v0.5.2.0 Maintenance Update

[ResetXPDR]

MSFS Compatibility: 1.39.12.0, 1.7.35.0, 1.8.9.0.

Release notes for 0.5.2.0

Please review the updated 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.

This release delivers additional profile slots, profile reset capability, Dynamic/Adaptive FG support, periodic spike protection, improved VRAM+, steadier FG‑inactive behaviour, clearer UI and broad reliability fixes.

Detailed Changes:

Additional Profile Slots

• Uses new ProfileCount key in the common config file, defaulting to 8 (+2) profiles and supporting 4–12 total profiles.
• Automatically migrates from legacy FlightTypeExpert to the new FlightTypeExpertExtended index.
• Retains the legacy key unchanged for full backwards compatibility.

Profile Reset Capability

• Available when MSFS has been detected, not in a flight session and in Expert mode.
• Following user confirmation after pressing the Reset button, it restores the active flight type profile to its default values.
• Existing MSFS version‑switch and in‑session TLOD reset behaviours remain unchanged and separate.

Dynamic/Adaptive FG Support

• Added DynFG option to the Manual FG dropdown.
• When selected, the user sets Target FPS using the NFR (1×) value, and the app displays FPS as NFR because DynFG’s dynamic behaviour prevents reliable detection of its actual FG multiplier at any specific point in time.

Periodic Spike Detection/Protection

• Detection is auto enabled in Expert mode, requiring detection of the shared RTSS frame time buffer to activate.
• Detects periodic MSFS frame time spikes (4+ fresh spikes, > 2x median frame time, same 0.3-1.8s cadence), which can occur with high TLOD and photogrammetry conditions and can cause stutters.
• Protection checkbox, enabled by default, is shown only in Expert mode and when RTSS is detected as running; otherwise the controls are removed entirely.
• Automatic TLOD reduction when protection is enabled and periodic frame time spikes are detected, helping reduce stutters in affected areas.
• Automatic TLOD restoration when periodic frame time spikes are no longer detected, using a time‑delayed, continuously‑scaled recovery model driven by distance travelled, altitude above ground, and vertical trend for smooth, scenery‑aware restoration without abrupt jumps.
• Lightning symbols show with the FPS reading and TLOD range in the status line when periodic frame time spikes are detected and when resultant TLOD reduction is active respectively.
• A "SpikeThresholdMultiplier" common config file option, defaulting to 2.0, determines the multiple of the frame time median at which a spike will be counted.
• Log entries show spike detection and protection settings, spike TLOD reduction amount when greater than zero, and when associated TLOD reduction and recovery commence.
• Additional diagnostic logging occurs when Log+ is enabled.

VRAM+ Improvements

• Replaced fixed four-times TLOD Step reduction in VRAM+ reduce mode with a proportional reduction based on how far VRAM usage exceeds the reduce threshold.
• Replaced LTD on the app status line with clearer HLD and RED indicators for VRAM+ hold and reduction events respectively.
• Added logging of VRAM+ settings reduction events and replaced LTD status with more meaningful HLD and RED for hold and reduction events respectively.

FG Inactive Improvements

• Added scaled FPS‑drop dampening for FG‑enabled, unfocused sessions using a proportional offset (1 FPS at 40 FPS target) to prevent TLOD reductions from minor FG micro‑dips.

UI Refinements

• Changed displayed SU version in non-Expert mode to correctly identify SU5.1.
• Renamed all app references from FSR3 to the more generic FSR as both FSR 3 and 4 are now supported in MSFS 2024.
• Updated Paused indicator on the app status line from text to symbol, replacing PAUSED with the standard UI glyph ⏸ for a cleaner, more compact status line.
• Updated TLOD Base visibility so it no longer appears when using Auto Target FPS, since only Fixed TLOD Base is supported and automatically enforced.
• Improved update visibility so updates for the selected upgrade option and channel always appear on the status line outside flight sessions, reducing the chance of missing an available update.
• Removed dominant‑core ID and Top2Avg Avg to shorten the CPU stats line when Log+ is enabled.
• Fixed UI status line so that the upper TLOD range value correctly reflects the maximum active TLOD when FreeTLOD mode is enabled.
• Updated test‑update status line so the app now shows the version number of a newly available test update when advising that one is available.

Auto Exit After Flight Session Capability

• Added "ExitAppAfterFlightSession" common config file option, defaulting to false, which when set to true will cause the app to exit automatically after a flight session ends, rather than remaining in the background.

Auto Update Reliability Improvements

• Improved installer reliability by having it wait for up to 5 seconds for the initiating app to close during auto‑updates, ensuring the update only proceeds once the app has fully exited and preventing any file‑lock issues.

General Bug Fixes/Improvements/Clean-up

• Added new FSRX and FSRXVFR FPS keys to replace legacy FSR3 keys and ensure full backwards compatibility across all profiles.
• Added MSFS 2024 gating to ensure legacy cloud‑recovery settings validity logic only runs in MSFS 2020.
• Removed legacy CloudRecoveryTLOD keys from MSFS 2024 configs during initial‑load migration to eliminate erroneous settings created by older MSFS 2020 logic.
• Streamlined reading of MSFS option file settings to occur only once before the memory compatibility test and once at the start of each flight session.
• Simplified logging of memory compatibility test outcomes when Log Plus is not enabled, reducing log clutter while still providing clear visibility of the test result.
• Fixed issue where FPS settle time was unnecessarily extended by 4 s when the Reduction Settings Suite was set to Full Reduction Suite, even if Auto Reduce Settings was disabled or inactive.
• Fixed issue where MinTLODExtraCapMult could be less than the minimum of 1.5.
• Changed CloudIncreaseGPUMaxLoad to be user‑configurable in the MSFS 2024 config file, defaulting to 90% when not specified.
• Updated settings logging to more clearly indicate whether Expert or Non‑Expert settings are in use.
• Streamlined TLOD/OLOD verification by moving the read/write check out of the Reset function and into the end of the initial memory compatibility check, avoiding repeated runs and preventing false failures after MSFS CTDs.
• Added active OLOD calculation function to centralise the OLOD computation and ensure correct OLOD logging in Non‑Expert mode.
• Removed legacy FPS logging now that Log+ fully replaces the old FPS‑detail logging system.
• Added access to the RTSS frame buffer and its associated position pointer to the RTSS Shared Memory interface, allowing periodic MSFS frame time spikes to be detected.
• Replaced multiple Average FPS function calls in the LOD Controller module with single calls saved to local variables once per tick.
• Moved all VRAM+ state local variables in LOD Controller into Model to provide access to other modules.

---

This discussion was created from the release v0.5.2.0 Maintenance Update.

[jerryyyyy]

First flight with the new build today.

Mixed Germany MSFS_AutoFPS20260729.log

[jerryyyyy]

Learning a new plane (Kodiak) and flew this partial flight in 2D after rebooting and not loading MSI or RTSS. Parenthetically the DLSS is set to Quality here not Balanced.

Test MSFS_AutoFPS20260729.log

[jerryyyyy]

FYI, here is the full flight. Fine performance, I think.

VR Bali MSFS_AutoFPS20260730.log

[ResetXPDR]

Your RTSS data went stale immediately, but in 2D this time, then stayed that way for the rest of your flight, even when switching between VR and 2D.

BTW, I've started 0.5.3.0-test already as there were a few left overs from 0.5.2.0 that I wanted to keep working. Discussion for that build is here #265

[jerryyyyy]

For simplicity's sake did not start MSI and RTSS. If not many stutters, not sure I needed to run them. I can if you want it for testing purposes.

[ResetXPDR]

No need to run them. In fact, it is helpful that you weren't running them as it shows me that I need to suppress spike messaging when they aren't.