Sorry everyone, but the 17Feb242100Z MSFS2020_AutoFPS has a serious logic error (thanks to @abennettfor finding it!) that has now been fixed. Download the fixed version here.

New version 18Feb240130Z:
- Fixed an inadvertent logic error introduced in the previous version that caused TLOD not to automatically change when it should.

 

20 minutes ago, Reset XPDR said:

Also, since the 0.3.7 version you are running has automatic advice of updates, you don't even have to read this topic at all until your app notifies you there is something new.

What I cannot keep up with with my availabe time is ths.  Is 0.3.7 the latest version of that app?  I am getting no update notifications.  Has 0.3.7 been replaced with a new app (or apps) with a new name?  Or is some new app to be run concurrently?  Is it one new app?  Or is it two new apps?  What is the difference between the apps. If using more than one at a time is there a pecking order of what to start first?  As a quality developer you are deeply immersed in this.  However it is visible and fleeting.  Perhaps a good summary and guidance, and that kept updated.  67 screens may be a record here, and I have been here since 1998 (site was comprimised and restarted in 2001 or 2002).  

 

Edited February 18, 20242 yr by fppilot

9 minutes ago, fppilot said:

What I cannot keep up with with my availabe time is ths.  Is 0.3.7 the latest version of that app?  I am getting no update notifications.  Has 0.3.7 been replaced with a new app (or apps) with a new name?  Or is some new app to be run concurrently?  Is it one new app?  Or is it two new apps?  What is the difference between the apps. If using more than one at a time is there a pecking order of what to start first?  As a quality developer you are deeply immersed in this.  However it is visible and fleeting.  Perhaps a good summary and guidance, and that kept updated.  67 screens may be a record here, and I have been here since 1998 (system was comprimised and restarted in 2001 or 2002).  Perhaps some submersion ????

 

If you want a summary of any version or variant, it's all there in on github in the release notes and, for the release versions, a detailed readme file telling you how it operates, interoperates and installs, uninstalls, updates, the works. Different variants can be installed but not run at the same time, with later variants self detecting this.

For you I suggest you just stick with 0.3.7, read its release notes and readme on github, ignore everything going on here and, when a new release comes out, choose whether to upgrade or not.

14 minutes ago, Reset XPDR said:

If you want a summary of any version or variant, it's all there in on github in the release notes and, for the release versions, a detailed readme file telling you how it operates, interoperates and installs, uninstalls, updates, the works. Different variants can be installed but not run at the same time, with later variants self detecting this.

For you I suggest you just stick with 0.3.7, read its release notes and readme on github, ignore everything going on here and, when a new release comes out, choose whether to upgrade or not.

OK. Got it.  I am leaving the squirrel cage.  How will we know when you have closed in on a public (non beta) release?  Am certainly interested.  I've bitten off the end of my tail in that cage, attemting to keep up with the now nearly 70 pages.  Admire your work. Just not the public whirlwind.


 

41 minutes ago, Reset XPDR said:

Fixed an inadvertent logic error introduced in the previous version that caused TLOD not to automatically change when it should.

Thanks! 🙏. My system didn’t really enjoy a final approach to KLAX filled with AI traffic and a TLOD of 400. Looking forward to test the updated version - after I go get some daylight 😉

16 minutes ago, fppilot said:

How will we know when you have closed in on a public (non beta) release?  Am certainly interested.

If you are referring to the new MSFS2020_AutoFPS variant, I will create a new topic on formal release, which will probably be in the next week or so. For DynamicLOD_ResetEdition 0.3.7 and onwards, the app itself will notify you.

16 minutes ago, fppilot said:

Admire your work. Just not the public whirlwind.

Thanks and fair point.

1 hour ago, Reset XPDR said:

Sorry everyone, but the 17Feb242100Z MSFS2020_AutoFPS has a serious logic error (thanks to @abennettfor finding it!) that has now been fixed. Download the fixed version here.

New version 18Feb240130Z:
- Fixed an inadvertent logic error introduced in the previous version that caused TLOD not to automatically change when it should.

Just given it a whirl around ini KJFK in the Fenix.

 

Working beautifully, not a single stutter and kept really nice visuals at 90fps!

Hmm... I´m trying to download that demo version but my Windows Defender finds some threats on it and refuse to keep it. 

11 hours ago, fppilot said:

What I cannot keep up with with my availabe time is ths.  Is 0.3.7 the latest version of that app?  I am getting no update notifications.  Has 0.3.7 been replaced with a new app (or apps) with a new name?  Or is some new app to be run concurrently?  Is it one new app?  Or is it two new apps?  What is the difference between the apps. If using more than one at a time is there a pecking order of what to start first?  As a quality developer you are deeply immersed in this.  However it is visible and fleeting.  Perhaps a good summary and guidance, and that kept updated.  67 screens may be a record here, and I have been here since 1998 (site was comprimised and restarted in 2001 or 2002).  

Having followed this from the beginning let me try to give a summary:

 

It all started with a project by muumimorko which basically could automatically change TLOD according to the AGL (Altitude Above Ground Level) of your aircraft. It worked fine for a while until a sim update changed the relevant memory adresses and it seemed to be discontinued.

 

Then @Fragtality stepped in and updated and enhanced this project, still primarily changing TLOD according to AGL. He added changing OLOD as well and introduced a new functionality of "FPS adaption" which still works AGL-dependent but shifts the values down when the FPS dropped. Even though he thankworthy shared his work he considered that just a proof-of-concept and initially discouraged us from using it at all. This tool called DynamicLOD still works fine.

 

Finally @Reset XPDR took over and added more functionalities to the tool, which was now called DynamicLOD_ResetEdition. (Where the name most probably just derives from his username and hasn't anything to do with a reset-function of the app what might be confusing). This tool is currently in version 0.3.7 and still primarily uses the AGL-dependent TLOD (and OLOD) tables. It still works great.

 

Lately @Reset XPDR introduced a new tool called MSFS2020_AutoFPS which works differently. It is independent from AGL and instead adjusts TLOD all the time to keep the FPS inside a customizable target intervall. 

Caveat #1: As this new tool has the FPS fluctuating below and above a target value it does not really work if you use a frame cap, which most probably most users with a VSync monitor do.

Caveat #2: This new tool doesn't touch the OLOD at all any more. I find that regrettable because even though OLOD don't have a large impact on overall FPS I found that on my (slower) system a lower OLOD significantly reduces the risk of stutters on final approach.

 

So I would recommend:

If you use a frame cap or see stutters with a higher OLOD stay with DynamicLOD_ResetEdition 0.3.7.

If you have a GSync monitor or you aren't bothered by the stuttering that comes with fluctuating FPS on a VSync monitor and you don't see stutters with a high OLOD then go for the new MSFS2020_AutoFPS tool.

 

After all it is fantastic that these tools are available because it is really game changing.

I'd like to thank

- muumimorko for starting it all

- @Fragtality for taking over and laying the foundation for all further development

- @Brocky120 for bringing this to the attention of a wider audience

- @Reset XPDR for taking it to the next level.

 

Edited February 18, 20242 yr by RALF9636

Excellent summary @RALF9636 and thank you for your kind words!

As a final offering today after much coding and testing, I'd like to present my hopefully final concept demo version of MSFS2020_AutoFPS before I formally release it soon and start a new discussion topic so as not to further confuse discussion of the the DynamicLOD apps that are the primary topic of this discussion thread.

You can download the new version 18Feb241100Z here, and it offers the following changes since the last version:

• Replaced TLOD Changes on Ground option with much more capable TLOD Min on Ground/Landing option. When enabled your TLOD will immediately change to TLOD minimum when your flight is loaded and will stay that way any time you are on the ground. Once you take off and start climbing, auto TLOD will kick in gradually on a sliding scale up to 1000 ft AGL, then normal range auto operation above that. On descent to landing, when you cross 2000 ft AGL, the app will progressively adjust your TLOD down so that as you cross 1000 ft AGL it will be at TLOD minimum and there it will stay locked all the way to the ground, taxi and shutdown at the gate. If you are level below 1000 ft AGL, then commence descending, TLOD will immediately switch to TLOD minimum with no stepping as it thinks you are landing imminently. If you are using cloud quality reduction options, even though you are at TLOD minimum on the ground which would normally cause cloud quality to reduce straight away, it will only reduce if you are below achieving your FPS target FPS and recover again as normal. It is generally recommended to leave it disabled, as will happen with expert settings disabled, but enable it if you are getting texture corruption with DX12 and 3rd party airports or want your TLOD on the ground or when landing to always be TLOD min.
• Slightly modified normal auto FPS behaviour, ie. when TLOD Min on Ground/Landing is not enabled, so that auto FPS will function when moving on the ground but only a rate of 1 TLOD step per second in the appropriate direction. In my testing, this still provides a stutter free taxi, take off and landing rolls, as the changes are so small, but it now gives you a more consistent FPS when taxiing around large airports as different complexity of scenery, AI and MP traffic come into view.
• Added boundary checking of user inputs. Valid ranges are: Target FPS 10 - 200, FPS Tolerance 1 - 20%, TLOD minimum 10 - 10 less than TLOD maximum, TLOD maximum 10 - 10 more than TLOD minimum, Cloud Recovery TLOD must always be at least 5 more than TLOD minimum and 5 less than TLOD maximum and will auto adjust if TLOD maximum or TLOD minimum changes moves it out of this range.
• Replaced OLOD sim value indication, which is not changed by this program in any case, with an app priority indication to show those times when the FPS target or TLOD Min is the priority, with the latter occuring when the TLOD Min on Ground/Landing option is enabled and conditions are such the TLOD Min has overtaken FPS to be the automation priority. This provided so it is clear to users that FPS tracking, being the main purpose of this app, is no longer the priority because they chose to enable TLOD Min on Ground/Landing and the conditions are such that it has now taken priority.
• Pending no major issues being raised with these latest changes, this will be the last concept demo version and will shortly transition to being a formal release.

I promise I'll slow down from now on. 😁

Edited February 18, 20242 yr by Reset XPDR

Just did a flight into FlyTampa's EHAM in the Fenix, with loads of addons active (FSHud, FSLTL, GSX). Without the mod it probably would've been a stutterfest. Although I didn't reach the target FPS, performance was still decent enough. Love the mod! Now for some more testing in the auto edition (no I haven't seen any daylight yet). 

Taxiing to the gate: 

Edited February 18, 20242 yr by Cpt_Piett

@Reset XPDR there is an (indirect) dependency which your app does not check for but caused issues when I tested your app on my (very) fresh windows 11 installation.
 

I found that simconnect.dll needs to have “Microsoft Visual C++ 2015 - 2022 Redistributable” installed otherwise it refuses to load and the simconnect indicator in your app remains red.

Your log file contained the error “Could not load file or assembly ‘Microsoft.FlightSimulator.SimConnect.dll’ or one of its dependencies”. Of course both of these are in your distribution and so I was confused, however a Google search later and once I installed the vc++ library, all was well. 
 

I think most users PCs will have already had this library installed at sometime by other software and so this won’t be a common issue but thought I’d share my learning with you. 

2 hours ago, Reset XPDR said:

Replaced TLOD Changes on Ground option with much more capable TLOD Min on Ground/Landing option. When enabled your TLOD will immediately change to TLOD minimum when your flight is loaded and will stay that way any time you are on the ground. Once you take off and start climbing, auto TLOD will kick in gradually on a sliding scale up to 1000 ft AGL, then normal range auto operation above that. On descent to landing, when you cross 2000 ft AGL, the app will progressively adjust your TLOD down so that as you cross 1000 ft AGL it will be at TLOD minimum and there it will stay locked all the way to the ground, taxi and shutdown at the gate

I wholeheartedly agree with this approach, thanks so much for including it! 🙏 

2 hours ago, Reset XPDR said:

I promise I'll slow down from now on. 😁

I think you deserve a well-earned break after all the coding, not to mention keeping us updated here on Avsim. Your contribution to the flightsim community has been invaluable 😊

Edited February 18, 20242 yr by Cpt_Piett

Hi all, and thanks for alle the efforts each one and most of all the Authors are putting on it.

I used for weeks the very first version I was satisfied with.

Today I tried the new version (I think the concept demo) and the app says I have FG inactive while on my graphic settings Frame Generation is enabled (4070ti). There is something wrong on my side or the app does not correctly recognize it? Thanks and sorry if this topic was eventually already discussed in the thread