4 hours ago, Ron Lefebvre said:

I see you are very busy, but I have a question...

Having major problems with stutters only on landing 1000 feet and less. Rest of the time its perfect.

Auto FPS has not helped nor has MSFS version of Dynamic Mode.

I see you have something called DynamicLod

Do you believe DynamicLod  is better suited for this particular problem.

You could try DynamicLOD, which has more discretely definable LOD/altitude pairings, but I suspect you'll experience the same issue with your current MSFS settings.

Generally speaking, if your system is experiencing stutters on landing where no one elses does it is because some of your MSFS settings are too high. TLOD is usually one of the main culprits, so setting MSFS default TLOD for non-expert mode, or TLOD Min in the app in expert mode, much lower can help a lot.

MSFS_AutoFPS 0.4.5.4 has now been formally released. It will be offered up for automatic installation when you next start earlier versions of the app if you have auto updates enabled in the app, otherwise it is available for download here. Thanks everyone for the responsive feedback, particularly just after 1.5.24.0 was released, which helped me achieve app compatibility so quickly.

Executive Summary

This release adds compatibility with MSFS 2024 SU3 Beta (1.5.24.0), adds advanced FPS cap detection using histogram-based clustering, and enables VRAM+ functionality for LODs-only for MSFS 2020. It also includes session-based automation safeguards, UI clarity enhancements, and backend cleanup.

So I have dropped the tlod to 150 instead of 200 in msfs + other small adjustment and it seems to help. One flight is not enough of a sample.

In your app is it better to leave it at 100 for landing purposes.

I have read "on the internet"

That a higher value may be beneficial since it will load things earlier then later at crunch time.

 

48 minutes ago, Ron Lefebvre said:

So I have dropped the tlod to 150 instead of 200 in msfs + other small adjustment and it seems to help. One flight is not enough of a sample.

In your app is it better to leave it at 100 for landing purposes.

I have read "on the internet"

That a higher value may be beneficial since it will load things earlier then later at crunch time.

 

Possibly, but then that higher TLOD is making MSFS load in a greater radius of scenery just as as you are coming in, right when its graphics load is highest, which has the opposite effect of continuing that crunch time for the entire approach phase.

At the end of the day, it's really up to you what side effects you are prepared to accept with different TLOD values. Myself, I don't care if TLOD is 50, or even 25 if settings reduction kicks in, on final approach at a major airport in a complex airliner, as long as I am getting a smooth experience at my 40 FPS cap in VR, because I am not looking at pretty scenery way off in the distance at that time.

 

Edited August 13, 2025Aug 13 by Reset XPDR

41 minutes ago, Reset XPDR said:

as long as I am getting a smooth experience

 

https://photos.google.com/photo/AF1QipOJ5RTXOzd0fpXRU9FnBqULu4UHbObi6T6SXh-s

 

Using these setting. In flight now. Will see when I land. I just want to be able to land.

No connect.. Steam 1.5.24 AUTOFPS 0.4.5.4..

Edited August 13, 2025Aug 13 by Siberier

No connect.. Steam 1.5.24 AUTOFPS 0.4.5.4..

34 minutes ago, Siberier said:

No connect.. Steam 1.5.24 AUTOFPS 0.4.5.4..

 

31 minutes ago, Metall4You said:

No connect.. Steam 1.5.24 AUTOFPS 0.4.5.4..

I am using this exact combo right now and it is connecting and working.

If you haven't done all this, please do so:

If after installing and running the app your simconnect always stays red, your TLOD and OLOD values show as zero or you see "Critical Exception occurred: MSFS_AutoFPS - Unable to load DLL 'GpuzShMem.x64.dll' or one of its dependencies" in the log file:

• 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.
• If still not resolved and the error code in your AutoFPS log file is Exception 31, you most likely have a corrupt MSFS WASM installation.
  • First, try deleting the MSFS WASM folder, located under the Microsoft Flight Simulator directory in either %appdata% or %localappdata% for Steam and MS Store install directories respectively, which will rebuild when you next run MSFS.
  • If that doesn't fix it, a full clean reinstall of MSFS will be required, which can be done in less than 15 minutes for MSFS 2024 but may take many hours for MSFS 2020.
    • If reinstalling MSFS 2024, you need to do a clean install, as outlined for your MSFS version here.
      • Ensure you backup/relocate your Community folder BEFORE you do this, then put it back when the reinstallation is complete.
      • All your settings, controller assignments, career progression and your pilot profile are retained.

Just want to say I appreciate the command line option to set VFR or IFR mode… that helped me automate my startup profiles in Addon Linker for both types of flights. Thanks!

9 hours ago, Ron Lefebvre said:

https://photos.google.com/photo/AF1QipOJ5RTXOzd0fpXRU9FnBqULu4UHbObi6T6SXh-s

 

Using these setting. In flight now. Will see when I land. I just want to be able to land.

Well, those settings seem to work.

The Tlod got really low. That surprised me. It was JFK however. (I figured if I was going to test his thing, go for the jugular)

I used to run no problem until one of the MSFS updates . Now its pull your hair out time.

If any settings could or should be changed, let me know.

Thanks for all the help. 

All seams to be OK with MSFS_AutoFPS 0.4.5.4 and MSFS2024 SU3 Beta 1.5.25.0

The tool is really good.

Now I wanted to use the Alt-R key combination to reset, but I only hear a warning tone, but it doesn't reset. What's wrong, or is there a different key combination I can use?

1 hour ago, PlantsAreDead said:

The tool is really good.

Now I wanted to use the Alt-R key combination to reset, but I only hear a warning tone, but it doesn't reset. What's wrong, or is there a different key combination I can use?

I haven't tested this for a long time and you are right, it no longer works. I shall investigate further.

2 hours ago, PlantsAreDead said:

The tool is really good.

Now I wanted to use the Alt-R key combination to reset, but I only hear a warning tone, but it doesn't reset. What's wrong, or is there a different key combination I can use?

It was a bit of a doozy to work out why ALT-R was no longer functioning, but it was entertaining and I believe I have fixed in now in 0.4.5.5-test1 here, so if you could give it a try to confirm it now works I would appreciate it.

Edited August 14, 2025Aug 14 by Reset XPDR

It works, but only if you've previously selected AutoFPS as the active window. If the simulator is running and the window is displayed in the simulator, it doesn't work.