MSFS2020_AutoFPS version 0.4.3.1 has been formally released, which you can obtain here. This should be it until MSFS 2024 comes out next month that hopefully includes similar functionality and therefore takes away the need for this app! My thanks go out to @Cpt_Piettwho have been very thorough in his testing efforts of the 0.4.3.1 test versions.

Executive summary of changes since 0.4.3.0:

• Added an automatic TLOD reduction at night option.
• Improved TLOD Min/Base + and TLOD Max/Top + functionality.
• Added support for an MSFS2020-specific profile with Lossless Scaling.
• Added GPU-Z controllable cloud quality reduction in non-expert mode.
• Updated UI and logging with revised functionality.

Edited October 2, 20241 yr by Reset XPDR

While it would be great if it happens, I don't expect 2024 to include the wealth of flexibility that Auto_FPS does, it's an invaluable part of the SIM experience for me.  I for one would be grateful if you do carry over it's full functionality if 2024 doesn't. Thank you!

5 hours ago, kevinfirth said:

While it would be great if it happens, I don't expect 2024 to include the wealth of flexibility that Auto_FPS does, it's an invaluable part of the SIM experience for me.  I for one would be grateful if you do carry over it's full functionality if 2024 doesn't. Thank you!

Agreed.  Asobo currently has dynamic LOD in Xbox but it is very poorly implemented and doesn't have enough user flexibility as AutoFPS does.  If they don't improve it for the PC version, it will essentially be useless.

Well MS/Asobo has had public access to my code base on github for more than six months, so if they needed to see how I did certain functionality it has been right there for the taking. At the very least I hope MSFS 2024 will publish the MSFS settings that AutoFPS changes, and hopefully all of the rest of them, as SimVars so that I can make AutoFPS fully compliant with their Terms of Service by allowing it to make all changes through simconnect.

Edited October 3, 20241 yr by Reset XPDR

Hi, I don't want the TLOAD on the ground to go above 100.

If the FPS drops, the TLOAD should drop to 50 as set.

This also seems to work with the Auto FPS version 0.4.2.16. Unfortunately, I can't get this setting on the ground TLOAD maximum of 100 to work with the current version.

 

https://drive.google.com/file/d/1aQ8BAQTXN5Ew2rNUjL-JIEkYvhYzVuFX/view?usp=sharing

 

 

Edited October 3, 20241 yr by derex17

Hi, I have a problem that I noticed today morning after updating my msfs and autoFPS (i tried to revert to previos auto fps version but it didnt help, also tried reinstall)

I use lossless scaling with autoFPS app and I started to have a problem with fps sensitivity setting (2 days ago it was running fine i dont know what happened). 

So when i set my target FPS to 142 (LS gives me 144 locked so 142 is good aamount i guess) and set fps sensitivity to 1 then when i am out of minimal TLOD zone (1500ft), the TLOD doesnt increase, and just stay at 60 minimal amount. The problem wipes out when i set my sensitivity to 5, then it works normal. Also the 1 sensitivity works when descending (i have to change the sensitivity before so i can get max tlod), so from max given before it lowers correctly

No problem with auto OLOD

So basicly, TLOD doesnt increase from minimal, if the target fps is set to: 143, 142, 141, 140. And just stays on minimal whole flight no metter flight level.

When i set target fps lower then 140 ex.139, and set sensitivity to 1 then it works normally. So sensitivity 1 doesnt work if the target fps is higher then 139

 

Here is a tip to an app now available on TO that may help your performance even more.  It is named FPS 4 MSFS.  It is a .bat file, not an addon app.  What it does is recognize the location of several MSFS related cache files and deletes them so MSFS will rebuild them.  For a chuckle I DL it and tried it.  I was amazed at the before and after.  AGAIN, it is not an app that runs during use of MSFS, or AutoFPS, or Lossless Scaling.  It is simply a .bat file to run (as Administrator) to clear the cobwebs from the MSFS closet.

With my system, specs below, with MSFS graphics settings mostly on Ultra, DLSS Super, FG on, DX12 (Beta), true 4K; and normal settings in AutoFPS, after using FPS 4 MSFS to clear out the various caches my  performance rose from an AutoFPS reported FPS in the high 60's to slightly over 100.  I increased my AutoFPS settings to double the values for respective TLOD's and still found AutoFPS reporting FPS in the low 90's.

Both of those were from the same parking position I normally use at LVFR's KBWI.

Because FPS 4 MSFS is a housekeeping utility, so to speak, it only needs to be executed occasionally.  Again, it is not a utility that runs during MSFS sessions.  You could certainly clear the respective cache files out manually, but FPS 4 MSFS makes it easy.

Edited October 3, 20241 yr by fppilot

52 minutes ago, fppilot said:

Here is a tip to an app now available on TO that may help your performance even more.  It is named FPS 4 MSFS.  It is a .bat file, not an addon app.  What it does is recognize the location of several MSFS related cache files and deletes them so MSFS will rebuild them.  For a chuckle I DL it and tried it.  I was amazed at the before and after.  AGAIN, it is not an app that runs during use of MSFS, or AutoFPS, or Lossless Scaling.  It is simply a .bat file to run (as Administrator) to clear the cobwebs from the MSFS closet.

With my system, specs below, with MSFS graphics settings mostly on Ultra, DLSS Super, FG on, DX12 (Beta), true 4K; and normal settings in AutoFPS, after using FPS 4 MSFS to clear out the various caches my  performance rose from an AutoFPS reported FPS in the high 60's to slightly over 100.  I increased my AutoFPS settings to double the values for respective TLOD's and still found AutoFPS reporting FPS in the low 90's.

Both of those were from the same parking position I normally use at LVFR's KBWI.

Because FPS 4 MSFS is a housekeeping utility, so to speak, it only needs to be executed occasionally.  Again, it is not a utility that runs during MSFS sessions.  You could certainly clear the respective cache files out manually, but FPS 4 MSFS makes it easy.

 

Is it different from the MSFS cache cleaner bat file?

8 hours ago, derex17 said:

Hi, I don't want the TLOAD on the ground to go above 100.

If the FPS drops, the TLOAD should drop to 50 as set.

This also seems to work with the Auto FPS version 0.4.2.16. Unfortunately, I can't get this setting on the ground TLOAD maximum of 100 to work with the current version.

 

It's not dropping to 50 TLOD on the ground because you have the + box (next to TLOD Min) checked.  Uncheck that box and it should give you your 50 TLOD on the ground.

Checking that box tells AutoFPS to give you more than your minimum if it can.

1 hour ago, fppilot said:

Here is a tip to an app now available on TO that may help your performance even more.  It is named FPS 4 MSFS.  It is a .bat file, not an addon app.  What it does is recognize the location of several MSFS related cache files and deletes them so MSFS will rebuild them.  For a chuckle I DL it and tried it.  I was amazed at the before and after.  AGAIN, it is not an app that runs during use of MSFS, or AutoFPS, or Lossless Scaling.  It is simply a .bat file to run (as Administrator) to clear the cobwebs from the MSFS closet.

 

Doesn't clearing the rolling cache within the sim do the same?  I keep rolling cache off myself so don't know.

I wonder if it is also clearing nVidia cache files as well because that will also give a performance boost.  I'll have to see if I can find the .BAT file and take a look at what it is doing.

Edit: Ok, yeah, it's doing what I thought.  It is deleting both the MSFS rolling cache file as well as the nVidia DXCache and GLCache files.  I typically delete the nVidia cache files manually and the MSFS rolling cache file in game (when I used to use it) but can see how this little .BAT file would be of use as it's just one double-click and all cache files are deleted.

Edited October 3, 20241 yr by jaxgator

10 hours ago, derex17 said:

Hi, I don't want the TLOAD on the ground to go above 100.

You could try disabling TLOD Min Extra. Then TLOD on the ground will not increase above the value that you’ve set.

3 hours ago, FelipeThePilot said:

So basicly, TLOD doesnt increase from minimal, if the target fps is set to: 143, 142, 141, 140. And just stays on minimal whole flight no metter flight level.

Try setting a much lower target FPS. With a target FPS that high, AutoFPS will interpret the situation as no headroom above your target, hence TLOD will not increase.

E.g.: I’m not using lossless scaling, but got a target FPS of 65. Whenever my FPS is higher than that, TLOD will increase.

If you’ve enabled TLOD Min Extra, TLOD can potentially increase to TLOD Max on the ground. If you’ve enabled TLOD Max Extra, TLOD can potentially increase even further when terrain altitude is above the threshold.

Auto OLOD changes depending on the altitude range you’ve set, regardless of FPS.

Also, when locking FPS and using FPS sensitivity/tolerance mode, the FPS lock should be at least 15% higher than target FPS. When using Auto TLOD mode, locked FPS can be only a few FPS above target.

And as I mentioned in the thread you started, a sensitivity setting of 1 is very low. This can cause issues when using a very large TLOD range. E.g. TLOD might not have time to increase to TLOD Max Extra. Or will decrease too slowly upon descent, resulting in a potentially too high TLOD on approach, which can impact performance negatively. 

Edited October 4, 20241 yr by Cpt_Piett

2 hours ago, fppilot said:

Here is a tip to an app now available on TO that may help your performance even more.  It is named FPS 4 MSFS.  It is a .bat file, not an addon app.

Thanks for the heads up on this. It might be worthwhile opening a separate thread for discussion. I’ll give it a go tomorrow. 

3 hours ago, Cpt_Piett said:

Try setting a much lower target FPS. With a target FPS that high, AutoFPS will interpret the situation as no headroom above your target, hence TLOD will not increase.

E.g.: I’m not using lossless scaling, but got a target FPS of 65. Whenever my FPS is higher than that, TLOD will increase.

If you’ve enabled TLOD Min Extra, TLOD can potentially increase to TLOD Max on the ground. If you’ve enabled TLOD Max Extra, TLOD can potentially increase even further when terrain altitude is above the threshold.

Auto OLOD changes depending on the altitude range you’ve set, regardless of FPS.

Also, when locking FPS and using FPS sensitivity/tolerance mode, the FPS lock should be at least 15% higher than target FPS. When using Auto TLOD mode, locked FPS can be only a few FPS above target.

And as I mentioned in the thread you started, a sensitivity setting of 1 is very low. This can cause issues when using a very large TLOD range. E.g. TLOD might not have time to increase to TLOD Max Extra. Or will decrease too slowly upon descent, resulting in a potentially too high TLOD on approach, which can impact performance negatively. 

The thing is that it worked, but one day stoped working. Sensitivity 1 was Ok for me until now. 

Also I noticed that senstivity 1 is working when lossless scaling is disabled, so it might be problem with it.

 

14 hours ago, derex17 said:

Hi, I don't want the TLOAD on the ground to go above 100.

If the FPS drops, the TLOAD should drop to 50 as set.

This also seems to work with the Auto FPS version 0.4.2.16. Unfortunately, I can't get this setting on the ground TLOAD maximum of 100 to work with the current version.

 

https://drive.google.com/file/d/1aQ8BAQTXN5Ew2rNUjL-JIEkYvhYzVuFX/view?usp=sharing

 

 

Per your screenshot, AutoFPS is working as it should. You are geting TLOD 100 on the ground because you have enabled TLOD Min + and your current FPS is more than 15% higher than your target. If you only want TLOD Min of 50 on the ground always, uncheck TLOD Min +. This is all described in detail in the readme.