MSFS 2020 Auto FPS App v0.4.2

[Sonosusto 707]

I am enjoying to latest build (not beta etc). Tried a bunch of different planes in different flights and loved it. Recently left from New Orleans to KBYY (Bay City) in the Black Square Bonanza and loved it.

I used VFR settings but left Expert settings opened.

[mikeymike 366]

Did some further testing with 4.2.9 

so on a clear day with scattered showers 

it works fine , then I had taken off in kslc in word not allowed weather.

during climb i would get stuttering 

auto target fps 

fps sensitivity 5

tlod min 150 max is 300 + not checked 

auto lod 200 base  and max 200 top

decrease cloud also checked + not checked  

Mike 

[Flyfaster_MTN002 412]

Just did awful weather IFR to mins low clouds/fog, in mountins snow/rain on latest Nvidia driver(s). No stutters, couple pauses.

[Cpt_Piett 4,838]

9 minutes ago, Flyfaster_MTN002 said:

Just did awful weather IFR to mins low clouds/fog, in mountins snow/rain on latest Nvidia driver(s). No stutters, couple pauses.

Same! Smooth all the way to touchdown on the approach with TLOD Min set to 100, Max 400. 

[reecemj 153]

Are you gents using dlss and framegen with this app? 

[Reset XPDR 1,372]

New TLOD automation method, working the same way OLOD automation currently works, coming very soon ...

Edited March 31 by Reset XPDR

[Reset XPDR 1,372]

New Test Version 0.4.2.10-test available here.

Yes, I said I was pretty much done with functionality in this release, however the new TLOD automation method called Auto TLOD I have implemented in this release was fairly easy to do, is something that has been on my wish list for a while now and actually serves as a concept demonstrator for MS/Asobo as to how simple TLOD automation could function. Most importantly however, it helps those using FPS caps who have been struggling with the conflicting FPS cap and target requirements that the other automation methods impose.

Amusingly, that now includes me since I upgraded to a Quest 3 and now run an FPS cap of 40 to use SSW (motion reprojection) so I can finally fully appreciate the plight of FPS cap users trying to pick a target FPS that would work with their FPS cap and it sort of works but not really. In my case, I ended up using DynamicLOD_ResetEdition again then I had an epiphany last night that I could set up something similar (not quite as customisable) in my beloved AutoFPS app. As it turns out, I happen to know the developer very well so a kind word to myself and here we are! 😄

Please give it a go, particularly those who gave up on this app because of the FPS cap conflict, and let me know how it goes.

Changes are:

• Added new TLOD automation method called Auto TLOD which functions the same way that Auto OLOD does ie. independent of FPS. As well as being a concept demonstrator of how to implement a simple TLOD automation method within MSFS, this mode will be useful to those using an FPS cap who would otherwise need to use a DynamicLOD app variant due to conflicting FPS cap and target requirements that the other automation methods impose.
  • TLOD will adjust based on an altitude band with a base and top level and with TLOD values defined for each of these altitudes.
  • The app will set TLOD @ Base at or below the Alt TLOD Base (AGL), set the TLOD @ Top at or above Alt TLOD Top (AGL) and interpolate in between.
  • As this function completely ignores FPS, all FPS-related settings are removed from the UI when using this method. These are Target FPS, Auto Target FPS, TLOD Min + and Pause on MSFS losing Focus.
  • FPS settling time is also disabled as it does not apply to this automation method.
• Revised Auto OLOD stepping to be the same as the new Auto TLOD stepping, whereby the smallest OLOD change will be 5 and the largest will be 10. This is to minimise the frequency of LOD changes so as not to potentially overload the MSFS render engine and cause stutters.
• Swapped TLOD UI rows around to match the layout of Auto OLOD for consistency purposes.
• Moved Pause when MSFS loses focus option down lower on the UI to make room for the TLOD Automation Method label which is needed to describe the accompanying drop down list.

 

Edited March 31 by Reset XPDR

[GSalden 4,701]

10 hours ago, kevinfirth said:

What tvs do you have? I have a 2023 Samsung which does up to 144hz VRR with gsync

Hi Kevin,

Here I have 3 Sony Bravia 4K TV’s. They are from 2020/21. 

The TV’s are 100 hertz but connected to a pc they are up to 60 hertz.

 

[GSalden 4,701]

16 minutes ago, Reset XPDR said:

New Test Version 0.4.2.10-test available here.

Yes, I said I was pretty much done with functionality in this release, however the new TLOD automation method called Auto TLOD I have implemented in this release was fairly easy to do, is something that has been on my wish list for a while now and actually serves as a concept demonstrator for MS/Asobo as to how simple TLOD automation could function. Most importantly however, it helps those using FPS caps who have been struggling with the conflicting FPS cap and target requirements that the other automation methods impose.

Amusingly, that now includes me since I upgraded to a Quest 3 and now run an FPS cap of 40 to use SSW (motion reprojection) so I can finally fully appreciate the plight of FPS cap users trying to pick a target FPS that would work with their FPS cap and it sort of works but not really. In my case, I ended up using DynamicLOD_ResetEdition again then I had an epiphany last night that I could set up something similar (not quite as customisable) in my beloved AutoFPS app. As it turns out, I happen to know the developer very well so a kind word to myself and here we are! 😄

Please give it a go, particularly those who gave up on this app because of the FPS cap conflict, and let me know how it goes.

Changes are:

• Added new TLOD automation method called Auto TLOD which functions the same way that Auto OLOD does ie. independent of FPS. As well as being a concept demonstrator of how to implement a simple TLOD automation method within MSFS, this mode will be useful to those using an FPS cap who would otherwise need to use a DynamicLOD app variant due to conflicting FPS cap and target requirements that the other automation methods impose.
  • TLOD will adjust based on an altitude band with a base and top level and with TLOD values defined for each of these altitudes.
  • The app will set TLOD @ Base at or below the Alt TLOD Base (AGL), set the TLOD @ Top at or above Alt TLOD Top (AGL) and interpolate in between.
  • As this function completely ignores FPS, all FPS-related settings are removed from the UI when using this method. These are Target FPS, Auto Target FPS, TLOD Min + and Pause on MSFS losing Focus.
  • FPS settling time is also disabled as it does not apply to this automation method.
• Revised Auto OLOD stepping to be the same as the new Auto TLOD stepping, whereby the smallest OLOD change will be 5 and the largest will be 10. This is to minimise the frequency of LOD changes so as not to potentially overload the MSFS render engine and cause stutters.
• Swapped TLOD UI rows around to match the layout of Auto OLOD for consistency purposes.
• Moved Pause when MSFS loses focus option down lower on the UI to make room for the TLOD Automation Method label which is needed to describe the accompanying drop down list.

 

It starts to look a little bit confusing to me.

Am I correct that the when using autoTLOD it is like using Dynamic LOD ?

 

[Reset XPDR 1,372]

13 minutes ago, GSalden said:

It starts to look a little bit confusing to me.

Am I correct that the when using autoTLOD it is like using Dynamic LOD ?

 

If you don't select this automation mode, the app is exactly the same as before. And if you do, the UI gets simpler so I'm not sure why it is confusing.

It's not really the same as Dynamic LOD as you can only pick a lower and upper TLOD and an altitude band within which it will automatically scale between them, just like the app already does with OLOD automation. DynamicLOD is still far more customisable.

[Cpt_Piett 4,838]

4 hours ago, Reset XPDR said:

Yes, I said I was pretty much done with functionality in this release, however the new TLOD automation method called Auto TLOD I have implemented in this release was fairly easy to do, is something that has been on my wish list for a while now and actually serves as a concept demonstrator for MS/Asobo as to how simple TLOD automation could function.

Great idea Reset! I've been thinking about having automated TLODs within an altitude band much like OLODs. Didn't think you would actually implement it though. I'll jump into the A300-600RF flight deck and do a test run.

Quote

As this function completely ignores FPS, all FPS-related settings are removed from the UI when using this method. These are Target FPS, Auto Target FPS, TLOD Min + and Pause on MSFS losing Focus.

I'm excited to see how AutoFPS functions without having a target FPS set. Soon I'll know I guess 🙂

[FalconAF 213]

5 hours ago, Reset XPDR said:

If you don't select this automation mode, the app is exactly the same as before. And if you do, the UI gets simpler so I'm not sure why it is confusing.

 

Well, I'm a bit confused now too.  The screencaps show the new settings being used with the VFR mode selected.  Are these new options ONLY for the VFR mode?  Or are they for IFR mode too?  Do they only benefit the VFR mode?  Would I possibly want to use them in IFR mode?  Neither the above posts nor the readme explain that.

Edited March 31 by FalconAF

[Cpt_Piett 4,838]

47 minutes ago, FalconAF said:

Well, I'm a bit confused now too.  The screencaps show the new settings being used with the VFR mode selected.  Are these new options ONLY for the VFR mode?  Or are they for IFR mode too?  Do they only benefit the VFR mode?  Would I possibly want to use them in IFR mode?  Neither the above posts nor the readme explain that.

It's very easy to use and can be combined with both IFR and VFR mode. 

I'm currently climbing to FL310 in the A300. First flight with 0.4.2.10. These are my settings:

As you can see there is no longer any target FPS option (I've got FPS locked to 65 with RTSS). 

Just select Auto TLOD, then set the desired values. 

I'm back in the SU15 beta (had some issues and needed to do a complete re-installation). Not using any AI traffic on this flight (wanted to keep things simple). Departure from ENGM was exceptionally smooth (almost zero frame time variability). Not sure if this is due to being back in the beta, no AI traffic - or both. 

Edited March 31 by Cpt_Piett

[Cpt_Piett 4,838]

Just finished my first flight with 0.4.2.10 in iniBuilds A300 ENGM-EGLL. Probably the smoothest flight so far! Approach into Heathrow (no AI traffic though) was silky smooth, and the CapFrameX graphs reflect this: 

A few frame time spikes when changing views (as should be expected), otherwise negligible stuttering and amazing frame time consistency. It cannot get better then this. I'll throw in some traffic now and ruin the blissful experience 😆

Edited March 31 by Cpt_Piett

[kevinfirth 1,442]

10 hours ago, GSalden said:

Hi Kevin,

Here I have 3 Sony Bravia 4K TV’s. They are from 2020/21. 

The TV’s are 100 hertz but connected to a pc they are up to 60 hertz.

 

You may be able to unlock them to their full potential.  My Samsung did only 60Hz until I enabled Input Signal +, (together with a HDMI 2.1 cable), and it unlocked 144Hz settings in NVidia control panel.