5 hours ago, Reset XPDR said:

In any case, I am looking right now at the feasibility of reintroducing VRAM+ for LODs only for MSFS 2020 in the next AutoFPS version, so we shall see soon enough.

It's turning out to be like trying to defuse a bomb with all the MSFS 2024 fingers in there, but I am persevering and it is looking promising.

I still need to get the VRAM+ enable/disable checkbox to show and VRAM+ settings to be logged for MSFS 2020.

Edited August 8, 2025Aug 8 by Reset XPDR

I have a question... about the ideal MSFS settings for TLOD and OLOD.

I like to keep things simple so just have AutoFPS set on Auto (no expert), FG for frame rate detection... and switch between VFR (Caravan) and IFR (iFly 737).

For IFR in the 737, I've tried MSFS settings for TLODs at 300 and 200 (OLODs always at 200):

- At TLOD 200, AutoFPS targets 110 FPS, in flight, my FPS is hitting the limit at 120, and I see dips down to 100FPS on landing where "auto settings LODS reduction initiated" kicks in and TLODs drop to sub 100.  OLOD varies between 200 and 100 on landing.

- At TLOD 300, AutoFPS targets 100FPS. My FPS is still clost to the limit at 117 but I see dips down to 90FPS on landing where "auto settings LODS reduction initiated" kicks in, and TLODs drop to sub 100 and and OLOD varies between 200 and 100 on landing as above. 

In the end, neither of these TLOD settings makes a substantial difference... it's 10FPS difference.

Question 1: What is the best-practice here?

Question 2: Is there a way to force higher OLOD at lower elevations and on the ground rather than letting it dip below 200? Ideally, I'd like to have OLOD at 200 as I'm approaching 1000ft AGL and stay there.  Is there an expert option to force this?

 

 

Edited August 8, 2025Aug 8 by Virtual-Chris

@LIML2020, and anyone else interested in trying, I have released a new AutoFPS test version, available here, that brings back VRAM+ for MSFS 2020 that was removed in 0.4.4.8 due to a focus on MSFS 2024 settings reduction functionality at the time. It is slightly different than in 0.4.4.7 and earlier in that it not only reduces TLOD by up to 50% but also OLOD by a corresponding amount, as these two settings are joined at the hip in the settings reduction code. If anything, it will make VRAM+ more effective than it previously was for MSFS 2020.

There are also some other minor fixes and improvement in there that I have been working on in the background, but nothing that affects this VRAM+ for MSFS 2020 reintroduction for which the scope is currently as follows:

• Added VRAM+ functionality for MSFS 2020.
  • Enabled by checking the VRAM+ checkbox, which will appear on the UI if the GPU-Z companion app is running and providing VRAM usage data.
  • Currently applies only to TLOD and OLOD (LODs-only), with a maximum reduction of 50%.
  • When active, the adjusted values are displayed in the Sim Values UI area.
  • VRAM+ reduce, hold and recover thresholds are as defined for VRAM+ for MSFS 2024.

 

Any feedback on this change will be appreciated.

1 hour ago, Virtual-Chris said:

I have a question... about the ideal MSFS settings for TLOD and OLOD.

I like to keep things simple so just have AutoFPS set on Auto (no expert), FG for frame rate detection... and switch between VFR (Caravan) and IFR (iFly 737).

For IFR in the 737, I've tried MSFS settings for TLODs at 300 and 200 (OLODs always at 200):

- At TLOD 200, AutoFPS targets 110 FPS, in flight, my FPS is hitting the limit at 120, and I see dips down to 100FPS on landing where "auto settings LODS reduction initiated" kicks in and TLODs drop to sub 100.  OLOD varies between 200 and 100 on landing.

- At TLOD 300, AutoFPS targets 100FPS. My FPS is still clost to the limit at 117 but I see dips down to 90FPS on landing where "auto settings LODS reduction initiated" kicks in, and TLODs drop to sub 100 and and OLOD varies between 200 and 100 on landing as above. 

In the end, neither of these TLOD settings makes a substantial difference... it's 10FPS difference.

Question 1: What is the best-practice here?

Question 2: Is there a way to force higher OLOD at lower elevations and on the ground rather than letting it dip below 200? Ideally, I'd like to have OLOD at 200 as I'm approaching 1000ft AGL and stay there.  Is there an expert option to force this?

 

 

Since AutoFPS version 0.4.5.2, the use of auto target FPS disables auto settings reduction per the release notes:

Auto Target FPS System

• Auto target FPS now disables TLOD Min + instead of unchecking it, preserving its config value.
• Auto target FPS setting is now saved and restored per flight type profile, replacing global handling.
• Auto settings reduction is now automatically disabled when enabling auto target FPS with MSFS 2024.
• Recalibration logic updated to trigger only on consistent average FPS drops but with a smaller threshold, to work better with smoothed averages.

I just tried it myself in 0.4.5.4-test1 just release and with non-expert mode if I use auto target FPS then force my FPS to be lower, it does not trigger auto settings reduction and instead will just reduce the calculated target FPS if the drop is significant enough. 

If you are using 0.4.5.2 or later you should not be experiencing what you state. If you are on one of these newer versions and are experiencing what you say, message me your log file and I will take a look.

Re forcing higher OLOD at lower elevations is how non-expert mode should already be functioning. In VFR it should be giving you 150% of your current MSFS OLOD setting on the ground and 100% for IFR on the ground, then down to 10% of the initial value by 10000 ft. The only way they could go lower than this on the ground is with settings reduction kicking in, but that should not be possible with auto target FPS active. Again, if it is not doing this, send me your log.

 

Edited August 8, 2025Aug 8 by Reset XPDR

 

Thankyou!

Tested latest test version, but upon exceeding the Vram threshold of 96%, the TLOD does not decrease but remains locked in red with a padlock.

at cruising altitude (300/350), when I go through clouds with reduced visibility, the VRAM increases but the TLOD does not decrease. Does adjusting the LOD based on VRAM only work within the Alt TLOD Base and Alt TLOD Top range?

My settings: In Expert Options I set

- Auto Method FPS caps (I lock FPS at 60 through RTTS, Frame generation ON)

- TLOD Base: 100

- TLOD Top: 600 (to have very sharp satellite images)

- Alt TLOD Base: 600

- Alt TLOD Top: 15000.

 

Edit: I performed a clean installation with  Redistributables update, the app in on-top mode does not work and does not change the TLOD when I click on the MSFS screen, while if I click on the app screen it starts working again. Reverted to 0.4.5.3 and works again

 

Edited August 8, 2025Aug 8 by LIML2020

1 hour ago, LIML2020 said:

Tested latest test version, but upon exceeding the Vram threshold of 96%, the TLOD does not decrease but remains locked in red with a padlock.

With default thresholds, that behaviour is correct. 96% is the hold threshold and will lock LODs. You have to go above the reduce threshold of 98% before LODs start reducing.

 

1 hour ago, LIML2020 said:

at cruising altitude (300/350), when I go through clouds with reduced visibility, the VRAM increases but the TLOD does not decrease. Does adjusting the LOD based on VRAM only work within the Alt TLOD Base and Alt TLOD Top range?

Again, unless you go above 98%, LODs won't reduce. Reducing LOD based on VRAM usage works at any altitude.

 

1 hour ago, LIML2020 said:

I performed a clean installation with  Redistributables update, the app in on-top mode does not work and does not change the TLOD when I click on the MSFS screen, while if I click on the app screen it starts working again. Reverted to 0.4.5.3 and works again

On-top functionality has not changed for many versions, including this new one. TLOD automation hasn't changed in this version either.

The last time someone experienced TLOD only changing when the app had focus it was because they were in FPS sensitivity mode with a system FPS cap that exactly matched their target FPS, a combination that does not allow TLOD to increase, as explained in the readme. If it is something else then direct message me your associated log file contents (you cannot attach files here, so cut and paste it), located in %appdata%\MSFS_AutoFPS\log, so I can see what is going on. 

42 minutes ago, Reset XPDR said:

The last time someone experienced TLOD only changing when the app had focus it was because they were in FPS sensitivity mode with a system FPS cap that exactly matched their target FPS, a combination that does not allow TLOD to increase, as explained in the readme. If it is something else then direct message me your associated log file contents (you cannot attach files here, so cut and paste it), located in %appdata%\MSFS_AutoFPS\log, so I can see what is going on. 

Thanks, I think it was similar to the FPS sensitivity mode with a system FPS cap situation you described.
I'll do more tests as soon as I can. Thank you so much.

8 hours ago, Reset XPDR said:

Since AutoFPS version 0.4.5.2, the use of auto target FPS disables auto settings reduction per the release notes:

Auto Target FPS System

• Auto target FPS now disables TLOD Min + instead of unchecking it, preserving its config value.
• Auto target FPS setting is now saved and restored per flight type profile, replacing global handling.
• Auto settings reduction is now automatically disabled when enabling auto target FPS with MSFS 2024.
• Recalibration logic updated to trigger only on consistent average FPS drops but with a smaller threshold, to work better with smoothed averages.

I just tried it myself in 0.4.5.4-test1 just release and with non-expert mode if I use auto target FPS then force my FPS to be lower, it does not trigger auto settings reduction and instead will just reduce the calculated target FPS if the drop is significant enough. 

If you are using 0.4.5.2 or later you should not be experiencing what you state. If you are on one of these newer versions and are experiencing what you say, message me your log file and I will take a look.

Re forcing higher OLOD at lower elevations is how non-expert mode should already be functioning. In VFR it should be giving you 150% of your current MSFS OLOD setting on the ground and 100% for IFR on the ground, then down to 10% of the initial value by 10000 ft. The only way they could go lower than this on the ground is with settings reduction kicking in, but that should not be possible with auto target FPS active. Again, if it is not doing this, send me your log.

 

Ah, I haven’t updated since you added the recovery from reduced settings. I knew you were doing a bunch of updates but didn’t think any of it affected my use case. My bad… Will download the latest and give it a go! Thanks!

AutoFPS no longer loads for me. It comes up to NET RUNTIMES needed click to download which of course does nothing but close the app.

I've downloaded .453 and run that, still no app loading. Next time I'm in clean windows with no Asobo updates forcing themselves on me I'll try a clean install?

48 minutes ago, sloppysmusic said:

AutoFPS no longer loads for me. It comes up to NET RUNTIMES needed click to download which of course does nothing but close the app.

I've downloaded .453 and run that, still no app loading. Next time I'm in clean windows with no Asobo updates forcing themselves on me I'll try a clean install?

Give this a try from the readme:

• Try reinstalling the app with the "Install Latest Redistributable" options selected. If any of the redistributables fail to install during this process, try downloading and installing/repairing (as applicable):
  • A Microsoft official version of “Microsoft Visual C++ 2015 - 2022 Redistributable”, which may be missing from your Windows installation. Try installing this and this.
  • The NET desktop runtime from here if still available. Alternatively, go to the Micrsoft .NET 8.0 download page here and download and install the latest .NET Desktop Runtime X64 version.

8 minutes ago, Reset XPDR said:

Give this a try from the readme:

• Try reinstalling the app with the "Install Latest Redistributable" options selected. If any of the redistributables fail to install during this process, try downloading and installing/repairing (as applicable):
  • A Microsoft official version of “Microsoft Visual C++ 2015 - 2022 Redistributable”, which may be missing from your Windows installation. Try installing this and this.
  • The NET desktop runtime from here if still available. Alternatively, go to the Micrsoft .NET 8.0 download page here and download and install the latest .NET Desktop Runtime X64 version.

Hi sir! 

As it happened msfs did a ctd after installing all it's updates anyway so I ran the 453 installer after and it updated successfully. Restarting msfs now will report back if your app starts ok now. Thx as always for your fast support! 

I’ve said it before but I’ll say it again. Thank you for your excellent app and dedication to help making our simulation experience so much better. 

18 hours ago, Reset XPDR said:

Since AutoFPS version 0.4.5.2, the use of auto target FPS disables auto settings reduction per the release notes:

Auto Target FPS System

• Auto target FPS now disables TLOD Min + instead of unchecking it, preserving its config value.
• Auto target FPS setting is now saved and restored per flight type profile, replacing global handling.
• Auto settings reduction is now automatically disabled when enabling auto target FPS with MSFS 2024.
• Recalibration logic updated to trigger only on consistent average FPS drops but with a smaller threshold, to work better with smoothed averages.

I just tried it myself in 0.4.5.4-test1 just release and with non-expert mode if I use auto target FPS then force my FPS to be lower, it does not trigger auto settings reduction and instead will just reduce the calculated target FPS if the drop is significant enough. 

If you are using 0.4.5.2 or later you should not be experiencing what you state. If you are on one of these newer versions and are experiencing what you say, message me your log file and I will take a look.

Re forcing higher OLOD at lower elevations is how non-expert mode should already be functioning. In VFR it should be giving you 150% of your current MSFS OLOD setting on the ground and 100% for IFR on the ground, then down to 10% of the initial value by 10000 ft. The only way they could go lower than this on the ground is with settings reduction kicking in, but that should not be possible with auto target FPS active. Again, if it is not doing this, send me your log.

 

The new version is working great for me! Thanks again!

3 minutes ago, Virtual-Chris said:

The new version is working great for me! Thanks again!

I am glad it is because I specifically wrote the change to disable settings reduction when auto target FPS for you because of issues you had with settings reduction undesriably kicking in on landing. You had me worried for a bit there that I'd messed it up in a recent build, but all seems good now! 😄

2 minutes ago, Reset XPDR said:

I am glad it is because I specifically wrote the change to disable settings reduction when auto target FPS for you because of issues you had with settings reduction undesriably kicking in on landing. You had me worried for a bit there that I'd messed it up in a recent build, but all seems good now! 😄

Yeah, this is perfect for me! Much appreciated!