1 hour ago, daztheman70 said:

Hi All,

 

I have recently had to reformat my PC so need to install this again and went back to the start of this thread and the original download link is not working please could someone kindly post the link to download this again please.

 

Thanks

 

Daz

I just checked and the link on the first page does still work, taking you to an redirect webpage which does contain the link to the latest app version here.

I have a question. I hav RTSS Framerate Limit set to 40. In the sim I don't set max framerate but have Dynamic Settings also set to 40. autoFPS is showing a framerate of 45 (this is in VR). So why, if RTSS has a framerate limit set to 40, am I getting 45 fps? In autoFPS I have it set to use RTSS for framerate.

Thanks.

1 hour ago, Rob G said:

I have a question. I hav RTSS Framerate Limit set to 40. In the sim I don't set max framerate but have Dynamic Settings also set to 40. autoFPS is showing a framerate of 45 (this is in VR). So why, if RTSS has a framerate limit set to 40, am I getting 45 fps? In autoFPS I have it set to use RTSS for framerate.

Thanks.

When set to use RTSS as the source, AutoFPS shows the FPS that RTSS is telling it, without alteration for everything except LSFG. If you can decipher it, the display code is simply this:

                if (serviceModel.fpsSourceRTSS)
                {
                    if (serviceModel.LsModeEnabled) return serviceModel.fpsAverage * serviceModel.LsModeMultiplier;
                    else return (float)Math.Round(serviceModel.fpsAverage);
                }

 

This strongly suggests that your RTSS framerate limit is not currently active. You can verify by using another FPS reporting source, such as the FPS overlay with the OpenXRToolkit, the MSFS in-game FPS view or even the the nVidia overlay. With the latter two methods, you will obviously need to lift your headset off to see them.

My recommendation, for VR in particular and is what I do, is to set Max Frame Rate in MSFS to 40 and remove all doubt about whether the frame rate limit is active or not and also for the optimal experience with having Dynamic Settings set to the same value, which in my testing results in expected behaviour when used in conjunction with AutoFPS.

Ok I will switch over. I have one more question. If I didn’t want to limit the maximum frame but just wanted action taken if it got too low, would it be as simple as just removing the max frame rate or is there something else I would have to do. 

7 minutes ago, Rob G said:

Ok I will switch over. I have one more question. If I didn’t want to limit the maximum frame but just wanted action taken if it got too low, would it be as simple as just removing the max frame rate or is there something else I would have to do. 

I am not understanding what you are trying to achieve. Can you please clarify.

29 minutes ago, Reset XPDR said:

I am not understanding what you are trying to achieve. Can you please clarify.

I want to not limit frame rate upper limit but take action if it falls below a certain limit with your tool. So if I can get say 45 for, great, but if it falls below 35, take action. I know your tool works that way but will it work if I don’t set any max framerate in the sim and just set dynamic settings to say 35. 

48 minutes ago, Rob G said:

I want to not limit frame rate upper limit but take action if it falls below a certain limit with your tool. So if I can get say 45 for, great, but if it falls below 35, take action. I know your tool works that way but will it work if I don’t set any max framerate in the sim and just set dynamic settings to say 35. 

OK, in that case don't set MSFS Max Frame Rate and just use Manual Target FPS and set it to say 40 FPS so that it takes action before getting to your Dynamic Settings 35 FPS threshold. Just be aware that with 0.5.0.0-RC that if you are capping frame rate to 45 somewhere, even it is only in your VR headset, and your FPS sits locked at that FPS because performance conditions are so good, then to the app it is indistguishable from a Fixed FPS and it may warn you via changing the background of affected settings to orange to 30 seconds and providing corrective advice in the tooltip. You can just ignore it of course, as it is not a common occurrence, and you probably won't see it in VR anyway, unless you have AutoFPS visible by something like OpenKneeboard. 

In short, yes what you are suggesting should work 😊

Edited April 29Apr 29 by Reset XPDR

MSFS_AutoFPS 0.5.0.0‑RC (currently RC6) is now very close to release. The README has already been updated with all new and changed features, and recent commits have mostly been final polish. This version was previously tagged as 0.4.6.8‑RC, but the scope and significance of the update — including Fixed Target FPS in FPS Sensitivity mode, Free TLOD in expert mode, update channels, and non‑expert mode improvements — justified rolling the version number forward to 0.5.0.0.

I’m now waiting for the formal release of MSFS 2024 SU5 so I can rebaseline the app, remove SU4 compatibility, and have everything ready for the SU6 beta. In the meantime, if anyone encounters any notable issues with 0.5.0.0‑RC, please report them and I’ll attempt to resolve them before the final 0.5.0.0 release. Thanks.

 

MSFS_AutoFPS v0.5.0.0 has just been formally released, available either through auto update in the app or from here. My thanks goes out to all who provided valuable feedback during the test phase.

This major release introduces a new Fixed Target FPS system and FreeTLOD in FPS Sensitivity and Tolerance modes, delivers major improvements to Fixed FPS detection, TLOD/LOD logic, cloud automation and UI behaviour, enhances non‑expert and Auto Target FPS handling, simplifies the non‑expert UI, rebaselines to MSFS 2024 SU5 and prepares for SU6 beta, and includes targeted update, stability, logging, configuration and session‑management improvements across the app.

 

Using 0.5.0.0

Triple monitor setup. 
tLOD 200 / Olod 100 / Dyn settings enabled

With AutoFPS

 

Without AutoFPS

 

Shortly said : without AutoFPS I am seeing a higher framerate and less load on the RenderThread. And tLOD then is 100 and Olod then is 100.

This behavior I am seeing the last 6 weeks. I also tried another MSFS optimizer tool (Aero….. ) and the results were the same.

AutoFPS without Dyn Settings gives better performance and smoothness than MSFS without Dyn Settings and not using AutoFPS. That is good.

But no AutoFPS and MSFS with Dyn Settings looks superior here.

Has Dynamic Settings become so much better ?

 

 

 

1 hour ago, GSalden said:

Using 0.5.0.0

Triple monitor setup. 
tLOD 200 / Olod 100 / Dyn settings enabled

With AutoFPS

 

Without AutoFPS

 

Shortly said : without AutoFPS I am seeing a higher framerate and less load on the RenderThread. And tLOD then is 100 and Olod then is 100.

This behavior I am seeing the last 6 weeks. I also tried another MSFS optimizer tool (Aero….. ) and the results were the same.

AutoFPS without Dyn Settings gives better performance and smoothness than MSFS without Dyn Settings and not using AutoFPS. That is good.

But no AutoFPS and MSFS with Dyn Settings looks superior here.

Has Dynamic Settings become so much better ?

 

 

 

Have you tried disabling the MSFS Performance Optimiser feature of AutoFPS? It does not always deliver better performance and in some cases it can be worse. If the latter, stop using it. The app now warns you about this the first time you enable or reenable the feature from now on, but not if you are already using it.

Re Dynamic Settings versus AutoFPS, per the Readme FAQ, they manage TLOD quite differently and, if configured correctly, they are actually complimentary. I use Dynamic Settings with AutoFPS all the time and nothing I have seen changes that assessment, including with SU5.

Edited May 1May 1 by Reset XPDR

 

I just tried the new settings with SU5, and the results were astonishing.  I used to have the TLOD tied to altitude, but not with these settings.  AutoFPS started out at DTLOD 50 when I first loaded it up, and it went up to 400 quickly when I was parked at the gate (Fenix A320 at VerticalSim KTPA airport).  I stayed at DTLOD 400 the entire time with no stutters on taxi, takeoff, final approach and rollout.  There was some minor hitching on the ground when doing the snap camera views in the cockpit, but it was very minor.  I don't know what has changed, but even with my powerful CPU I used to have to dial down TLOD quite a bit on the ground because I use a lot of add-ons like the Fenix, Sayintentions ATC, PSXT live traffic and third party airports.

41 minutes ago, LVPack said:

 

I just tried the new settings with SU5, and the results were astonishing.  I used to have the TLOD tied to altitude, but not with these settings.  AutoFPS started out at DTLOD 50 when I first loaded it up, and it went up to 400 quickly when I was parked at the gate (Fenix A320 at VerticalSim KTPA airport).  I stayed at DTLOD 400 the entire time with no stutters on taxi, takeoff, final approach and rollout.  There was some minor hitching on the ground when doing the snap camera views in the cockpit, but it was very minor.  I don't know what has changed, but even with my powerful CPU I used to have to dial down TLOD quite a bit on the ground because I use a lot of add-ons like the Fenix, Sayintentions ATC, PSXT live traffic and third party airports.

I am really glad to hear it is running that smoothly for you. The recent tweaks in AutoFPS help with the stability side, but the big jump you are seeing on the ground is probably thanks to SU5. MSFS 2024 is simply much more tolerant of TLOD changes close to the ground now, so AutoFPS benefits from that rather than being the main reason for it.

Disregard, trying new settings. I had to update from 4.6.4 because of SU5. SU4 was running perfectly, my performance was incredible but now I’m seeing a hit. I’m using the same settings in both the sim and AutoFPS. When I turn off AutoFPS my FPS hold solid but my LOD remain static. I wish I could have stayed on SU4 with 4.6.4 as it was running perfectly. 

Edited May 2May 2 by Wise87

On 5/1/2026 at 10:45 AM, Reset XPDR said:

Have you tried disabling the MSFS Performance Optimiser feature of AutoFPS? It does not always deliver better performance and in some cases it can be worse. If the latter, stop using it. The app now warns you about this the first time you enable or reenable the feature from now on, but not if you are already using it.

Re Dynamic Settings versus AutoFPS, per the Readme FAQ, they manage TLOD quite differently and, if configured correctly, they are actually complimentary. I use Dynamic Settings with AutoFPS all the time and nothing I have seen changes that assessment, including with SU5.

Thank you very much 

Disabling the Performance Optimizer did the trick !

I now have tLOD set to 25 on the ground and with almost 40 live parked and moving AC I have a stready 60 fps ( FSR3 2x ) on every screen.

Will try with tLOD set to 50 in AutoFPS later .

Btw : oLOD load has dropped too

Edited May 2May 2 by GSalden