On 8/4/2025 at 7:44 AM, Reset XPDR said:

BTW, I was aware that this tool existed but had not tried it until now. It will actually be very useful for me as I can now test AutoFPS in VR and actually see what it is doing without having to lift my headset off to peer at the 2D screen, so thanks for bringing this app to my attention!

Ooohh that's an excellent find thank you both I'll have to investigate, I also lift the headset every five seconds to watch what the apps doing 😄

I am running MSFS_AutoFPS 0.4.4.9 and i love it !   This marvelous peace of software is essential to reasonably fly in msfs 2024, what a gain in performance and visual candy at the same time - dramatic !!!

Nevertheless I am unable to update to 4.5.x. The installer misses .NET 8 although it is present and even a compete uninstall/reinstall did not change anything. What am i doing wrong?

Is autofps working for the latest build? It's not connecting for me. 

39 minutes ago, usernamerequired said:

Is autofps working for the latest build? It's not connecting for me. 

Not sure which "build" you're talking about. But no problemo, here. With MSFS2024 1.5.23 or MSFS2020 1.39.9.0 + MSFS_AutoFPS 0.4.5.3

Edited August 6, 2025Aug 6 by vbazillio

I needed to update the app, thanks. 

Hmmmm….it stopped working for me on 1.5.23 (SU3 Beta) and won’t connect.  I am also on the latest app version.

I read in the readme that the LOD control feature based on GPU-Z VRAM value is only valid for MSFS2024. In previous versions of autoFPS, it was also valid for 2020. Why was it removed? It was also useful for 2020.

40 minutes ago, LIML2020 said:

I read in the readme that the LOD control feature based on GPU-Z VRAM value is only valid for MSFS2024. In previous versions of autoFPS, it was also valid for 2020. Why was it removed? It was also useful for 2020.

What specifically are you referring to in the readme? GPU-Z will show GPU load and VRAM usage with both 2020 and 2024, but VRAM+ only works with 2024 and has always been that way.

You can clearly see this in the screenshots in @vbazillio's post just above 

 

Edited August 7, 2025Aug 7 by Reset XPDR

1 hour ago, thetford569 said:

Hmmmm….it stopped working for me on 1.5.23 (SU3 Beta) and won’t connect.  I am also on the latest app version.

I am just clean installing 1.5.23.0 per MS recommendation then I will check this.

Just checked and it is working fine on my end, with the log showing both primary and secondary compatibility tests passed.

If you did a clean install of 1.5.23.0 like I did, you will need to rerun the AutoFPS installer if the mobiflight-event-module, which is required for the app to work, is no longer in your community folder. Just run the AutoFPS installer and click update and nothing else and all your AutoFPS settings will be retained.

Edited August 7, 2025Aug 7 by Reset XPDR

54 minutes ago, Reset XPDR said:

What specifically are you referring to in the readme? GPU-Z will show GPU load and VRAM usage with both 2020 and 2024, but VRAM+ only works with 2024 and has always been that way.

Does the VRAM functionality with GPU-z enabled allow for lowering the TLOD in MSFS2020 when the VRAM exceeds the maximum levels?

In previous versions, when the VRAM exceeded 96%, the TLOD would drop; now with the latest version, I have 99% VRAM usage but the TLOD doesn't drop and stutters occur. I am not interested in decreasing the quality of the clouds but only in acting on the LOD.

EDIT: the reduction of TLOD based on VRAM only works when expert options are not enabled

Edited August 7, 2025Aug 7 by LIML2020

1 hour ago, LIML2020 said:

Does the VRAM functionality with GPU-z enabled allow for lowering the TLOD in MSFS2020 when the VRAM exceeds the maximum levels?

In previous versions, when the VRAM exceeded 96%, the TLOD would drop; now with the latest version, I have 99% VRAM usage but the TLOD doesn't drop and stutters occur. I am not interested in decreasing the quality of the clouds but only in acting on the LOD.

EDIT: the reduction of TLOD based on VRAM only works when expert options are not enabled

VRAM+ was originally introduced in v0.4.4.2 back in January this year. It was restricted to TLOD changes only but worked with both MSFS 2020 and 2024. Later, when v0.4.4.8 was released, VRAM+ was subsumed into settings reduction, which was designed as an MSFS 2024-only feature as it affects many more settings not currently configured for MSFS 2020.

As such, you are correct in stating that VRAM+ used to work with MSFS 2020, albeit limited only to TLOD, and now doesn't, even when it shows VRAM+ on the app status line. Depending on how restrictive I have made the setting reduction logic to MSFS-2024 only, it may be possible for me to allow VRAM+ in a LOD-only way to work again with MSFS 2020. I will take a look the next time I work on an app update and see if it is possible to do this without too much modification effort.

 

 

 

Edited August 7, 2025Aug 7 by Reset XPDR

1 hour ago, Reset XPDR said:

VRAM+ was originally introduced in v0.4.4.2 back in January this year. It was restricted to TLOD changes only but worked with both MSFS 2020 and 2024. Later, when v0.4.4.8 was released, VRAM+ was subsumed into settings reduction, which was designed as an MSFS 2024-only feature as it affects many more settings not currently configured for MSFS 2020.

As such, you are correct in stating that VRAM+ used to work with MSFS 2020, albeit limited only to TLOD, and now doesn't, even when it shows VRAM+ on the app status line. Depending on how restrictive I have made the setting reduction logic to MSFS-2024 only, it may be possible for me to allow VRAM+ in a LOD-only way to work again with MSFS 2020. I will take a look the next time I work on an app update and see if it is possible to do this without too much modification effort.

 

 

 

Exactly, I remembered that it was a feature of the MSFS2020 app. It could be very useful again to many MSFS2020 users; I would be grateful if you could restore it.

Thank you for your great contribution to our community.

 

PS: in the meantime can i use the 0.4.4.7 version or is it outdated?

Edited August 7, 2025Aug 7 by LIML2020

1 hour ago, LIML2020 said:

Exactly, I remembered that it was a feature of the MSFS2020 app. It could be very useful again to many MSFS2020 users; I would be grateful if you could restore it.

Thank you for your great contribution to our community.

 

PS: in the meantime can i use the 0.4.4.7 version or is it outdated?

You should be able to use 0.4.4.7 with SU16, as MSFS 2020 hasn't changed for a very long time from a compatibility perspective. The only thing you will miss out on is bug fixes and improvements made since then. Essentially, if it does what you want it to do without any notable bugs affecting you, then have at it.

Edit: I just tried that combo. Yes, SU16 does work with 0.4.4.7.

Edited August 7, 2025Aug 7 by Reset XPDR

3 hours ago, Reset XPDR said:

You should be able to use 0.4.4.7 with SU16, as MSFS 2020 hasn't changed for a very long time from a compatibility perspective. The only thing you will miss out on is bug fixes and improvements made since then. Essentially, if it does what you want it to do without any notable bugs affecting you, then have at it.

Edit: I just tried that combo. Yes, SU16 does work with 0.4.4.7.

I ran some tests with version 0.4.4.7 and during the approach to EDDF runway 25L, it reports 98/99% VRAM, lowering my LOD due to exceeding the threshold, and even with the LOD lowered by the app, the VRAM remains at 98%. Meanwhile, with version 0.4.5.3, in the same conditions and same settings, it reports 89/92% VRAM and the LOD decreases gradually and is at higher values. It seems that something is not working well with the VRAM detection or LOD modulation in 0.4.4.7 with MSFS2020 SU16. I use GPU-Z 2.67.0.

Edited August 7, 2025Aug 7 by LIML2020

8 hours ago, LIML2020 said:

I ran some tests with version 0.4.4.7 and during the approach to EDDF runway 25L, it reports 98/99% VRAM, lowering my LOD due to exceeding the threshold, and even with the LOD lowered by the app, the VRAM remains at 98%. Meanwhile, with version 0.4.5.3, in the same conditions and same settings, it reports 89/92% VRAM and the LOD decreases gradually and is at higher values. It seems that something is not working well with the VRAM detection or LOD modulation in 0.4.4.7 with MSFS2020 SU16. I use GPU-Z 2.67.0.

Other than minor logging and exception handling differences when initially connecting up to GPU-Z, the code that does VRAM usage monitoring is identical between 0.4.4.7 and 0.4.5.3. As such, it was likely either a difference in VRAM load between the two same scenarios in MSFS, which can happen in my experience, or as previously mentioned, there may be other issues that have been fixed since 0.4.4.7 that could be be contributing to this.

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.