I've been very happy with DynamicLOD_ResetEdition, just ran the update and all seemed well, but for some reason the interface does not appear, even though the .exe is running shown in TM.  So I removed the old version entirely, I think...just deleted the folder in AppData, reinstalled the 4.9 version, and all went smoothly, and its auto update took it to 5.0 version I think it was, but same same despite a reboot:  the interface where you change the profiles etc doesn't appear.  Any ideas on how to resolve that?  Thanks in advance!

FYI ...

I started receiving an error message after updating to v0.4.5.5-test8. Something about a corrupt WASM directory and finding it at %localappdata% (MS Store version). They must have moved it. I did find it here

%localappdata%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM

Contained both MSFS2020 and MSFS2024 folders. Deleted the 2024 folder and MSFS_AutoFPS then worked.

I see there is a new test version available, so maybe this is already addressed. You're that fast!

7 hours ago, Twenty6 said:

FYI ...

I started receiving an error message after updating to v0.4.5.5-test8. Something about a corrupt WASM directory and finding it at %localappdata% (MS Store version). They must have moved it. I did find it here

%localappdata%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM

Contained both MSFS2020 and MSFS2024 folders. Deleted the 2024 folder and MSFS_AutoFPS then worked.

I see there is a new test version available, so maybe this is already addressed. You're that fast!

You found the directory where it was supposed to be. I kept the instruction short for the message, perhaps too short, to imply that you needed to hunt down in %localappdata% to find it. I will expand it to be more descriptive in the next release.

In any case, the suggested fix worked for you without having to involve me, which was the intent of the new message, so that's good to hear.

8 hours ago, Noel said:

I've been very happy with DynamicLOD_ResetEdition, just ran the update and all seemed well, but for some reason the interface does not appear, even though the .exe is running shown in TM.  So I removed the old version entirely, I think...just deleted the folder in AppData, reinstalled the 4.9 version, and all went smoothly, and its auto update took it to 5.0 version I think it was, but same same despite a reboot:  the interface where you change the profiles etc doesn't appear.  Any ideas on how to resolve that?  Thanks in advance!

This is the first report of this behaviour. There was one change that now forces the app window to appear before compatibility test failed and unable to attach MSFS message boxes as shown, which if anything would make your app window appear more than it previously would have in these instances, and another to get ALT-R working again for the Redetect button but otherwise app's window display code remains the same as in 0.4.9.

Can you message me the contents of your log file, located in %appdata%\DynamicLOD_ResetEdition\log, associated with when you experienced this issue. Can you also message me the contents of your three config files located in %appdata%\DynamicLOD_ResetEdition so I can check to see if there is any corruption in them that could be causing the issue. Thanks.

Edit: Actually, don't worry about sending me the config files as they would have been recreated fresh after you manually deleted the %appdata%\DynamicLOD_ResetEdition folder and reinstalled. The log file may contain something useful though, so still message me the contents of that.

Also, another suggestion is to try running the 0.5.0 installer directly from your downloads folder using the Clean Install and Latest Distributables options checked and tell me if that makes any difference to having the app window appear when you next run the app.

Edited August 21, 2025Aug 21 by Reset XPDR

1 hour ago, Reset XPDR said:

Also, another suggestion is to try running the 0.5.0 installer directly from your downloads folder using the Clean Install and Latest Distributables options checked and tell me if that makes any difference to having the app window appear when you next run the app.

Thank you!  Prior to starting the thread I did try the 0.5.0 directly but no joy.  I just did a complete R&R of the GPU driver, tried one more time w/ 0.5.0 using the Auto-Start w/ MSFS option which I was using w/ pre SU3.  Started MSFS 24 and was able to start DynamicLOD manually as it didn't start auto.  And, was able to get to the panel and it was working normally.  I don't mind starting manually but if it's possible to get the auto-start working that would be preferred, it not no worries glad to have it up and running again!

I am sending the contents of the successful install log.  Thanks again!

1 hour ago, Noel said:

Thank you!  Prior to starting the thread I did try the 0.5.0 directly but no joy.  I just did a complete R&R of the GPU driver, tried one more time w/ 0.5.0 using the Auto-Start w/ MSFS option which I was using w/ pre SU3.  Started MSFS 24 and was able to start DynamicLOD manually as it didn't start auto.  And, was able to get to the panel and it was working normally.  I don't mind starting manually but if it's possible to get the auto-start working that would be preferred, it not no worries glad to have it up and running again!

I am sending the contents of the successful install log.  Thanks again!

Thanks for the quick feedback. I'm am glad you are able to get it working one way or another. I will take a look at auto-start and see if I can reproduce the issue and will take it from there.

I have been tinkering with a new AutoFPS feature to display your default MSFS TLOD, OLOD and cloud settings when you are not in a flight session and also allow them to be updated dynamically if you change them in MSFS settings while in this state so that non-expert users can clearly see what default settings the app is using. 

My apologies for the rapid fire updates of 0.4.5.5-RC today but I was initially going to display an FS icon next to each setting value display I got working but it started to make the UI look cluttered so I have been expermenting with a simpler display of what is going on. I have currently settled on the following and would like to find out whether there is any notable objection to the way I have ended up doing it.

When MSFS is running but you are not in a flight session you will be presented with a UI like the following showing tooltip over the icon first then the underlaying UI:

If you change any of these displayed settings in the MSFS settings menu, they will update to the new values within one second of making the change.

For VR users, they can either change the target FPS type to VR or it will auto detect when in VR to show the default MSFS VR values for these settings:

When you start a flight session, the sim values icon will change to Leo to indicate AutoFPS is now running the show:

I love the updates to the GUI. Everything is working well here.

 

The proposed UI changes for displaying default LODs and cloud settings when not in a flight session seem to be acceptable from the feedback I have received so far so, assuming nothing major arises from 0.4.5.5-RC4 over the next day or so, it is likely I will formally release 0.4.5.5 thereafter. Thanks for your input everyone!

Using MSFS 2020, after installing the latest version of the app, it no longer opens on the desktop or appears in the sys tray.

I've deleted the folder and its contents, reinstalled the app and rebooted the PC. 

57 minutes ago, jdk2 said:

Using MSFS 2020, after installing the latest version of the app, it no longer opens on the desktop or appears in the sys tray.

I've deleted the folder and its contents, reinstalled the app and rebooted the PC. 

Try running the app installer again, but this time enable Clean Install, which will unfortunately reset all your app settings but should get you going again, and Latest Distributables.

BEFORE you do so, if you still have your original config files that were not deleted when you reinstalled the app, go to %appdata%\MSFS_AutoFPS and copy and paste into a direct message to me the contents of  MSFS_AutoFPS.config and MSFS2020_AutoFPS.config as you are the second user in as many days to report such an issue updating to 0.4.5.4 with MSFS 2020 and I would like to see if I can hunt down the issue using your config file contents in my test setup.

Also, have a look in Windows Event Viewer when you have tried to start the app and it failed and look around that time under application and copy and paste the text in a personal message to me if you find one. It should look something like:

and the copied text would come from the General text box. Thanks.

Edited August 22, 2025Aug 22 by Reset XPDR

@Reset XPDR

Thank you for the continueing updates on this great app.

I was wondering what the reason is to display the default LODs as the app takes over when it is running ?

19 minutes ago, GSalden said:

@Reset XPDR

Thank you for the continueing updates on this great app.

I was wondering what the reason is to display the default LODs as the app takes over when it is running ?

It's primarily for non-expert users, who are actually a higher proportion of users than you might think, as the settings the app chooses for them is directly based on these settings, so it is handy for them to know if something does not seem right because of them without having to dig through the log file to find out. Also, the information is already known in the app so it may as well show it when not in a flight rather than n/a because it is actually a(vailable).

Edited August 22, 2025Aug 22 by Reset XPDR

Hi @Reset XPDR fantastic app, been recently using it heavily in VR and Flat Screen, usually when I get to cruise I switch to flat screen. I've been observing some oddities as I've recently been trialing FS24.

On FS20 during climbout im getting about 50fps with 200 TLOD, however on FS24 with the same FPS (NFR btw) the TLOD is stuck to 50. Now I'm not 100% sure what `FPS + Pri Day` means but I get the same in FS20 and paid it no attention. I also don't know if 200 TLOD in FS20 is the same as 50 TLOD in FS24 as again, I've only been recently testing out the sim. I apologise if this is already answer in your wonderful github as I may have missed it.

4 minutes ago, Lucky38i said:

Hi @Reset XPDR fantastic app, been recently using it heavily in VR and Flat Screen, usually when I get to cruise I switch to flat screen. I've been observing some oddities as I've recently been trialing FS24.

On FS20 during climbout im getting about 50fps with 200 TLOD, however on FS24 with the same FPS (NFR btw) the TLOD is stuck to 50. Now I'm not 100% sure what `FPS + Pri Day` means but I get the same in FS20 and paid it no attention. I also don't know if 200 TLOD in FS20 is the same as 50 TLOD in FS24 as again, I've only been recently testing out the sim. I apologise if this is already answer in your wonderful github as I may have missed it.

The log file will tell for sure, but it looks like your default MSFS TLOD and OLOD are set to very low values, which is the basis from which non-expert mode chooses the LODs it sets, per the readme:

• TLOD Minimum - VFR 100% of your current MSFS TLOD setting, IFR 50%
• TLOD Maximum - VFR 300% of your current MSFS TLOD setting, IFR 200%
• Auto OLOD - enabled and VFR 150% of your current MSFS OLOD setting, IFR 100%

From your screenshot it looks as though your default MSFS TLOD is 25 and OLOD no more than 100 (it's hard to tell because it has reduced to the lowest limit)

I suggest that while not if a flight session and back at the main MSFS menu, you check what your default MSFS TLOD and OLOD are set to and if they are as low as they calculate to be then increase them accordingly. BTW, 0.4.5.5 due for imminent release will show you what your default MSFS LODs and clouds are set to on the app UI, without having to go into the MSFS settings menu or wade through the log file.