16 minutes ago, mikeymike said:

Think ill go back to 4.5.7 test 3 

Worked extremely well before the latest you have.

Regards

Mike

What's the issue with the newer version? It should perform pretty much identically.

8 hours ago, Reset XPDR said:

What's the issue with the newer version? It should perform pretty much identically.

Im still on 2020

Thou it seems a little more jittery.

Setting have not changed.

Thanks

Mike

Hey @Reset XPDR You obviously have access to manipulate a number of the MSFS variables. Do you have access to alter the Anti Aislising setting? I.e., do you know if its possible to dynamically shift from TAA to DLSS? Even on my 5090 I struggle with TAA at night when there are lots of light points. In those situations I have to switch to DLSS (Quality) and then back to TAA when I'm airborne.

Would love it if this was something that could be changed dynamically!! 🙂

 

15 minutes ago, KL Oo said:

Hey @Reset XPDR You obviously have access to manipulate a number of the MSFS variables. Do you have access to alter the Anti Aislising setting? I.e., do you know if its possible to dynamically shift from TAA to DLSS? Even on my 5090 I struggle with TAA at night when there are lots of light points. In those situations I have to switch to DLSS (Quality) and then back to TAA when I'm airborne.

Would love it if this was something that could be changed dynamically!! 🙂

 

I looked at this 6 months ago and it was not good news unfortunately. It turned out that changing those values on the fly like the app does for TLOD, OLOD and clouds results in either no change, a frozen image or a black screen, all of which are recoverable if you go to the settings menu and change any other setting and then the AA/DLSS Quality change is enacted, but not without this user intervention which of course is unacceptable.

20 minutes ago, Reset XPDR said:

I looked at this 6 months ago and it was not good news unfortunately. It turned out that changing those values on the fly like the app does for TLOD, OLOD and clouds results in either no change, a frozen image or a black screen, all of which are recoverable if you go to the settings menu and change any other setting and then the AA/DLSS Quality change is enacted, but not without this user intervention which of course is unacceptable.

No problem at all mate - Thanks for the quick response even if it isn't good news 🙂

 

50 minutes ago, mikeymike said:

Im still on 2020

Thou it seems a little more jittery.

Setting have not changed.

Thanks

Mike

Looking through the change log, there aren't actually any changes that affect LOD automation for MSFS 2020 since 0.4.5.6 until now, so you should get an identical experience with the latest releases, plus the improved features of course.

FYI, I am considering a reversion feature whereby if you choose to update to a test version, then change your mind and wish to leave the test program, it will give you an option to auto install the latest formal release rather than have to go digging around for it yourself. This wouldn't help in your particular case, as you wanted to go back to a test version that is no longer hosted on my github, but it will help those that want to go back to the last stable release for whatever reason.

3 hours ago, Reset XPDR said:

Looking through the change log, there aren't actually any changes that affect LOD automation for MSFS 2020 since 0.4.5.6 until now, so you should get an identical experience with the latest releases, plus the improved features of course.

FYI, I am considering a reversion feature whereby if you choose to update to a test version, then change your mind and wish to leave the test program, it will give you an option to auto install the latest formal release rather than have to go digging around for it yourself. This wouldn't help in your particular case, as you wanted to go back to a test version that is no longer hosted on my github, but it will help those that want to go back to the last stable release for whatever reason.

I will test further.

Thats great to have that option.

Much appreciated 

Hello, 

unfortunately I wasn't able to flightsim for a few weeks and after updating everything now I found the new option which makes autofps compatible with the msfs default dynamic settings. 
I'd like to understand whats the purpose of that mode. Does it bring any advantage to use autofps together with the default dynamic settings? 
Until now I only use autofps and have default dynamic settings off. Do you recommend using autofps together with msfs dynamic settings now? 

Thanks for all your development work, it's so vital for the sim. 

2 hours ago, skylane182 said:

Hello, 

unfortunately I wasn't able to flightsim for a few weeks and after updating everything now I found the new option which makes autofps compatible with the msfs default dynamic settings. 
I'd like to understand whats the purpose of that mode. Does it bring any advantage to use autofps together with the default dynamic settings? 
Until now I only use autofps and have default dynamic settings off. Do you recommend using autofps together with msfs dynamic settings now? 

Thanks for all your development work, it's so vital for the sim. 

There is a FAQ entry in the readme covering this:

How does AutoFPS compare to the in-built Dynamic Setting feature that MS included in MSFS 2024?

• Dynamic Setting adjusts both TLOD and OLOD, the former initially then the latter if still significantly under target FPS. AutoFPS adjusts these settings independently, with OLOD changing inversely proportional to altitude by default, and can also change a lot more settings when auto settings reduction and VRAM+ are active.
• Dynamic Setting only ever adjusts down to as low as 50% of your currently set TLOD and/or OLOD, whereas AutoFPS in non-expert mode uses the default values as a centre point for adjustments and in expert mode is configurable to whatever range you want, including above the max of 400 settable within the MSFS settings menu.
• Dynamic Settings is much quicker than AutoFPS at responding to FPS reductions, due to it having internal access to MSFS performance metrics that AutoFPS does not, which also means it tends to overreact to short term stutters which are quite common now.
• Dynamic Setting uses a native frame rate target FPS rather than actual FPS when frame generation is in use, so you need to be mindful of this when using it with FG. ie. You can be achieving 150 FPS with DLSS FG with a target FPS of 100 and it will still reduce OLOD and TLOD to 50%. AutoFPS accommodates most mainstream FG types and allows an applicable target FPS to be set for each FG type.
• Hybrid dynamic settings / AutoFPS automation is now available in Expert Mode and leverages the strengths of both MSFS dynamic settings and AutoFPS:
  • MSFS’s built-in dynamic settings engine is highly responsive, using internal performance metrics not accessible externally. This allows it to adjust LODs more precisely and rapidly than AutoFPS alone.
  • AutoFPS complements this by adjusting the base LOD values that MSFS dynamic settings operate within. It responds to longer-term performance trends, especially increasing LODs in favourable conditions — extending the usable range beyond the default 50–100% window imposed by MSFS dynamic settings.
  • AutoFPS also manages a broader set of performance-critical graphics settings — including Cloud Quality and ten others — offering a more comprehensive performance management regime than dynamic LODs alone.
  • Together, MSFS dynamic settings and AutoFPS now work in tandem to manage both performance and visual quality, each addressing different layers of the optimisation stack.
  • See the Usage / Configuration section for details on how to optimally configure this feature.

I now use it all the time in VR with an FPS cap of 40 and with dynamic settings and max frame rate set to 40 in MSFS and it gives a very good result. Note that in SU4 max frame rate is somewhat broken and does not actually set the max frame rate you think it does. In my case, I need to set it to 41 to acheive 40 FPS.

Hello Reset XPDR,

Thank you for your great app. I have used it in MSFS 2020 very well. I have MSFS 2024 as well, but the performance is not as great as it is with MSFS 2020. I don't understand my autoFPS settings. I am on the latest stable version also on MSFS 2024 SU3. 
I play with a 1440p screen, 50hz, so I want a target native FPS of 50, but it seems during cruise that it does not go above 40 fps. During approach and landing it is even lower. I am on a 7950x3d and 4090, 64 gb ram 6000mhz. Almost everything on ultra and I tried to lower the TLOD, but the fps stays around 40 fps max.

Do you know why that it is maxed at 40 fps?

Thanks in advance!

edit: i don't know how to post a screenshot here.

Edited October 19, 2025Oct 19 by AMSPilot06
edit: i don't know how to post a screenshot here.

4 minutes ago, AMSPilot06 said:

Hello Reset XPDR,

Thank you for your great app. I have used it in MSFS 2020 very well. I have MSFS 2024 as well, but the performance is not as great as it is with MSFS 2020. I don't understand my autoFPS settings. I am on the latest stable version also on MSFS 2024 SU3. 
I play with a 1440p screen, 50hz, so I want a target native FPS of 50, but it seems during cruise that it does not go above 40 fps. During approach and landing it is even lower. I am on a 7950x3d and 4090, 64 gb ram 6000mhz. Almost everything on ultra and I tried to lower the TLOD, but the fps stays around 40 fps max.

Do you know why that it is maxed at 40 fps?

Thanks in advance!

edit: i don't know how to post a screenshot here.

Do you have a system FPS cap set to 40 somewhere else eg. nVidia CP/App or RTSS? Do you have max frame rate enabled or vsync enabled and set to less that 100% monitor refresh in MSFS? What FPS do you get in MSFS without running AutoFPS, which you can see by turning on developer mode and showing the FPS view in MSFS?

13 minutes ago, Reset XPDR said:

Do you have a system FPS cap set to 40 somewhere else eg. nVidia CP/App or RTSS? Do you have max frame rate enabled or vsync enabled and set to less that 100% monitor refresh in MSFS? What FPS do you get in MSFS without running AutoFPS, which you can see by turning on developer mode and showing the FPS view in MSFS?

I will test again a new flight tommorow, because it is late now and have to work in the morning. I will get back to you with my test.

49 minutes ago, AMSPilot06 said:

I will test again a new flight tommorow, because it is late now and have to work in the morning. I will get back to you with my test.

No worries. FYI, AutoFPS will not actually cap FPS, rather it will work to your target FPS and just happens to have an FPS cap mode optimised for when you are using an externally set FPS cap. If you are not achieving your target FPS, it is generally because your AutoFPS LOD settings and/or MSFS graphics settings are too high. Having said that, 40 FPS is a very low maximum for your system spec, which is very similar to mine in which I can achieve 100 FPS+ in low complexity areas at 4K Ultra settings, so something external to AutoFPS is bringing your system down like this.

2 hours ago, Reset XPDR said:

There is a FAQ entry in the readme covering this:

How does AutoFPS compare to the in-built Dynamic Setting feature that MS included in MSFS 2024?

• Dynamic Setting adjusts both TLOD and OLOD, the former initially then the latter if still significantly under target FPS. AutoFPS adjusts these settings independently, with OLOD changing inversely proportional to altitude by default, and can also change a lot more settings when auto settings reduction and VRAM+ are active.
• Dynamic Setting only ever adjusts down to as low as 50% of your currently set TLOD and/or OLOD, whereas AutoFPS in non-expert mode uses the default values as a centre point for adjustments and in expert mode is configurable to whatever range you want, including above the max of 400 settable within the MSFS settings menu.
• Dynamic Settings is much quicker than AutoFPS at responding to FPS reductions, due to it having internal access to MSFS performance metrics that AutoFPS does not, which also means it tends to overreact to short term stutters which are quite common now.
• Dynamic Setting uses a native frame rate target FPS rather than actual FPS when frame generation is in use, so you need to be mindful of this when using it with FG. ie. You can be achieving 150 FPS with DLSS FG with a target FPS of 100 and it will still reduce OLOD and TLOD to 50%. AutoFPS accommodates most mainstream FG types and allows an applicable target FPS to be set for each FG type.
• Hybrid dynamic settings / AutoFPS automation is now available in Expert Mode and leverages the strengths of both MSFS dynamic settings and AutoFPS:
  • MSFS’s built-in dynamic settings engine is highly responsive, using internal performance metrics not accessible externally. This allows it to adjust LODs more precisely and rapidly than AutoFPS alone.
  • AutoFPS complements this by adjusting the base LOD values that MSFS dynamic settings operate within. It responds to longer-term performance trends, especially increasing LODs in favourable conditions — extending the usable range beyond the default 50–100% window imposed by MSFS dynamic settings.
  • AutoFPS also manages a broader set of performance-critical graphics settings — including Cloud Quality and ten others — offering a more comprehensive performance management regime than dynamic LODs alone.
  • Together, MSFS dynamic settings and AutoFPS now work in tandem to manage both performance and visual quality, each addressing different layers of the optimisation stack.
  • See the Usage / Configuration section for details on how to optimally configure this feature.

I now use it all the time in VR with an FPS cap of 40 and with dynamic settings and max frame rate set to 40 in MSFS and it gives a very good result. Note that in SU4 max frame rate is somewhat broken and does not actually set the max frame rate you think it does. In my case, I need to set it to 41 to acheive 40 FPS.

Thank you, I looked into the readme but i didn't find this part, sorry for that. 
Regarding the fps limit for the internal dynamic settings. Do I understand correctly that I have to set the target value for the native fps there, and in autofps the target value with frame generation? 
E.g. if I want to achieve 60fps after frame gen 2x, I have to set 30fps in the dynamic settings and 60fps in autofps with the applicable FG mode? 

3 hours ago, skylane182 said:

Thank you, I looked into the readme but i didn't find this part, sorry for that. 
Regarding the fps limit for the internal dynamic settings. Do I understand correctly that I have to set the target value for the native fps there, and in autofps the target value with frame generation? 
E.g. if I want to achieve 60fps after frame gen 2x, I have to set 30fps in the dynamic settings and 60fps in autofps with the applicable FG mode? 

That is correct.