DynamicLOD_ResetEdition 0.5.1 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 update leaves core functionality untouched and delivers MSFS 2024 SU4 beta support, smarter compatibility handling, improved installer intelligence, and a wide range of stability and usability fixes:

• MSFS 2024 SU4 Beta Support: Added compatibility for MSFS2024 version 1.6.15.0.
• Smarter Compatibility Updates: When MSFS memory maps change, the app now offers fallback auto‑updates with clear probability labels, preserves user update preferences, and provides a direct “Report” action to GitHub.
• Improved MSFS Attachment: More reliable version detection, streamlined attachment logic, and clearer SimConnect error guidance.
• Installer Enhancements: Detects MSFS installs at startup, aborts cleanly if none are found, and lets users choose which versions auto‑start.
• Fixes & Optimisations: Stronger config validation and self‑repair, earlier logging initialisation, clearer error messages, embedded app icon, improved LOD automation, and multiple installer/UI fixes.

Edited October 13, 2025Oct 13 by Reset XPDR

Thanks Reset!

DynamicLOD_ResetEdition 0.5.2 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 update leaves core functionality untouched, introduces a rollback option for test users, improves update handling for speed and resilience and improves commonality with AutoFPS.

Executive Summary

This release strengthens update handling, adds rollback support for test users and improves commonality with AutoFPS:

• Test Version Rollback: Users opting out of + Test are now offered a one‑time automatic reversion to the latest formal release.
• Smarter Updates: Update checks are faster, safer, and more resilient, with reuse of recent data, URL verification, and protection against missing files.
• Fixes & Optimisations: Improved commonality with AutoFPS via a matching system tray icon setting.

 

DynamicLOD_ResetEdition 0.5.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 update leaves core functionality untouched and incorporates common improvements recently developed in MSFS_AutoFPS, strengthening update logic, adding Silent Updates, improving MSFS config handling, enhancing graphics and display features, refining compatibility and error messaging, and streamlining code maintenance.

9 hours ago, Reset XPDR said:

DynamicLOD_ResetEdition 0.5.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 update leaves core functionality untouched and incorporates common improvements recently developed in MSFS_AutoFPS, strengthening update logic, adding Silent Updates, improving MSFS config handling, enhancing graphics and display features, refining compatibility and error messaging, and streamlining code maintenance.

hey @Reset XPDR, your link sends users to the 0.5.2 maintenance update. just thought i would let you know. thanks for the steady updates.

4 hours ago, Fromage_Flippant said:

hey @Reset XPDR, your link sends users to the 0.5.2 maintenance update. just thought i would let you know. thanks for the steady updates.

Oops, thanks for letting me know. Unfortunately, I am unable to edit the post as it is beyond the edit time limit. The correct link is here.

DynamicLOD_ResetEdition 0.5.4 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 leaves core functionality untouched and delivers major SimConnect changes to minimise and resolve Exception 31 occurrences, introduces a new Repair Install option and installer UI clarity improvements, and includes general improvements and fixes across the app.

I had planned to wait for the MSFS SU5 beta before publishing the next DynamicLOD_ResetEdition maintenance test build, but an issue I hit today while updating FSUIPC brought that forward. The problem was the file format used by recent versions of AutoFPS when saving the MSFS exe.xml after enabling the Auto‑start with MSFS option. The format works fine for MSFS itself but is now incompatible with the FSUIPC installer. DynamicLOD_ResetEdition uses the same code for this feature, so it’s affected as well.

The fix is already in an AutoFPS test release and will be formally published shortly. It automatically detects this legacy format and rewrites the exe.xml into a fully compatible one without changing any of its contents. I’m now applying the same correction to DynamicLOD_ResetEdition.

As mentioned in the AutoFPS discussion thread, if this affects you, the fix is available in 0.5.5‑test1 or later and will be formally released soon. Please don’t report this to the FSUIPC developer if you encounter the issue after using DynamicLOD_ResetEdition with Auto‑start enabled. This is a DynamicLOD_ResetEdition issue and it’s already being resolved for everyone.

DynamicLOD_ResetEdition 0.5.5 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 update fixes EXE.xml formatting for reliable MSFS tool compatibility, introduces MFG auto‑detection, and includes installer refinements and clearer Exception 31 guidance.

Sorry to put out another test release so soon, but I found a couple of issues with how the new Auto MFG behaviour carried over from AutoFPS, along with a long‑standing bug where an MFG‑related setting wasn’t loading correctly. These are not major issues, because the app will default to MFG Off, which is actually Auto internally and works correctly, and that remains the preferred way to configure MFG. As such, there is no pressing need to update unless you use MFG and want the best experience with it.

Intended MFG functionality for DLOD_RE is as follows:

• Multi Frame Generation (MFG), when set within MSFS settings, can now be auto detected in MSFS 2024 but may also be manually set in the app if MFG has been configured in nVidia settings instead.
  • Users with 5000 series nVidia GPUs will be presented with an MFG Multiplier dropdown control on the UI.
  • When set to Auto, the app will read the MFG setting from MSFS and configure the FPS display accordingly.
  • When set to any other value, match the app's MFG multiplier with the MFG value you have configured for MSFS in nVidia settings.
  • The app will remember this MFG setting on next startup.

Here is what it should look like when set to Auto and DLOD_RE has the focus (ie. MFG is inactive).

Then here is what it should look like if MSFS is configured for 4X MFG:

As I don’t have an nVidia 5000‑series GPU to test with directly, I’ve had to simulate MFG being active in my environment, so there may still be minor issues with how the app handles MFG. I’d appreciate feedback from anyone using MFG with DLOD_RE v0.5.6-test1 or later, available here, so I can roll any remaining fixes into the next release.

Thanks.

 

Edited February 7Feb 7 by Reset XPDR

Another update on MFG. Mere hours after I put out 0.5.6‑test1 I discover here that there is now a mod to fool MSFS into setting and giving MFG to the unwashed non‑nVidia‑5000 series GPU masses. While you'll see in that link it is currently not working visually for me, functionally it is. As such, I should now be able to test all MFG functionality myself, thus it no longer being essential that I get feedback from 5000 series GPU owners on 0.5.6‑test1. Nonetheless, as with any test version, if you do have any specific feedback, I still want to get it.

The other upshot of the discovery of this mod is that I can assume it will become reasonably mainstream, like the FG mod did when it appeared a few years ago, which means I may as well reconfigure the app to provide the graphics selection drop‑down for all users, defaulting to Auto so there will be no net impact on most users, and allowing manual FG selections if desired. This is very similar to how I already do it for AutoFPS, and maximum commonality works well for me. As such, expect to see a new test version soon that provides this. With that, I will stop promoting this test build and let you get back to your normal flying activities.

FYI, I am aware that SU5 Beta has been released and is not compatible with DLOD_RE. I have actually fixed it in 0.5.6-test5, but for some uknown reason github won't let me upload it at the moment, so I will keep trying until it does. 

Thanks Reset!

9 hours ago, Benjamin H said:

As always, hats off to you for your contribution to your fellow simmers, both AutoFPS and DynamicLOD has been the most set and forget addons I have installed (I am still on DynamicLOD due to a little bit more manual control over the steps for OLOD/TLOD, but AutoFPS is also used from time to time of course), and when others asks me for any recommendations for better performance during all stages of flights, I bring up both of them everytime and tell them about the more manual control you have with DynamicLOD, but if you have it in you to "set and forget" the settings, AutoFPS is the one (given that the person has one or the other use of the sim, in a Cessna below or an airliner above FL100).

I am wondering if it is possible in a future version of DynamicLOD to have a compact window like AutoFPS has? The way you can click your way through it is actually very useful if you are doing testing and can have a small window on top with the most important info visible. Like it is with AutoFPS in this image.

@Benjamin HI will reply to this here in the adaptive LOD thread, as it is specific to DLOD_RE. 

Good news! I managed to get what you have asked for to work similarly in DLOD_RE without too much sweat, namely:

Added progressive UI‑collapse behaviour when double‑clicking anywhere that is not a control:

• First double‑click hides the two LOD Levels panels.

• Next double‑click hides all panels except Connection Status and Sim Values.
  
  

• Next double‑click restores all hidden settings sections to the full UI.
  
  

• The last state in use is restored automatically on next app start.

I know you didn't ask for the first one, but AutoFPS has that intermediate size and it should be useful in collapsing large LOD tables and still be able to see the update options, GFX mode and status line.

If I don't get any strong objection to how i've implemented it, this will appear in the next DLOD_RE test release in the next day or so as I have another minor fix to put in that release too.

 

 

30 minutes ago, Reset XPDR said:

@Benjamin HI will reply to this here in the adaptive LOD thread, as it is specific to DLOD_RE. 

Good news! I managed to get what you have asked for to work similarly in DLOD_RE without too much sweat, namely:

Added progressive UI‑collapse behaviour when double‑clicking anywhere that is not a control:

• First double‑click hides the two LOD Levels panels.

• Next double‑click hides all panels except Connection Status and Sim Values.

• Next double‑click restores all hidden settings sections to the full UI.
  The last state in use is restored automatically on next app start.

I know you didn't ask for the first one, but AutoFPS has that intermediate size and it should be useful in collapsing large LOD tables and still be able to see the update options, GFX mode and status line.

If I don't get any strong objection to how i've implemented it, this will appear in the next DLOD_RE test release in the next day or so as I have another minor fix to put in that release too.

 

 

Yes, I see that I mentioned a few pints as the edit reason, and I noticed that I posted in the wrong thread afterwards, but really appreciate getting it in here and also sharing the great news, and actually, this was just about exactly how I thought it could be solved (but I took a professional decision of not attempting an explanation of that at the current time😇) so I am really looking forward to it, and I can also test it out since I opted in for the test versions a little while ago. How it should be really when you request a feature, participate in it and provide feedback.