27 minutes ago, rjack1282 said:

Are you in expert mode?  If so, what is your recovery altitude set at?

Not using expert mode.  Just as simple as possible - let it auto detect the target FPS.  In my two test flights, it targeted 87 and 91 FPS which is no problem, my system generally gets over 100FPS until I land at a busy airport. That's when the FPS dips below the target, and the app seems to go into some mode where it reduces the LODs and never comes out of this mode... so once the FPS recovers from the initial loading of the airport and all the traffic, the LODs remain stuck at these low values.  I have to manually reset the app to get it working properly again for my next flight. Not sure why it can't just resume normal operation on its own.

Edited July 16, 2025Jul 16 by Virtual-Chris

10 hours ago, vbazillio said:

Just find a kind-of-competitor for MSFS2020 (only) https://flightsim.to/file/95050/aerotunemfs that has been released 2 days ago on flightsim.to

No misunderstanding: I'm a satisfied user of MSFS Auto FPS and just wanted to bring attention to Reset XPDR. In french, we say "just in case it might be helpful".

Thanks for the heads up. It is interesting that is being hosted on Flightsim.to where it is required to adhere to Microsoft's game content usage rules, yet apps like this and mine clearly do not and is the main reason why I haven't hosted my app there. In any case, the more of these apps out there that do things better than MSFS does itself, the greater the possibility that MS may open the settings interface up for external access so that apps like these can come out of hiding.

Curious to Reset and others: what are you settings with autofps at places like EGLC or KJFK. These are the biggest CPU loads for me. EGLC I have orbx payware and KJFK is the default scenery in 2024 but its my "go to" for testing. 

2 hours ago, Reset XPDR said:

Thanks for the heads up. It is interesting that is being hosted on Flightsim.to where it is required to adhere to Microsoft's game content usage rules, yet apps like this and mine clearly do not and is the main reason why I haven't hosted my app there. In any case, the more of these apps out there that do things better than MSFS does itself, the greater the possibility that MS may open the settings interface up for external access so that apps like these can come out of hiding.

They/Seb claimed early on when asked about this, that it was a simple setting to change and would turn it on...

59 minutes ago, Sonosusto said:

Curious to Reset and others: what are you settings with autofps at places like EGLC or KJFK. These are the biggest CPU loads for me. EGLC I have orbx payware and KJFK is the default scenery in 2024 but its my "go to" for testing. 

These are the 2D settings I use pretty much everywhere, with system FPS capped to 60 and MSFS on default Ultra, that work well, including complex airports:

VR is the same, except target FPS is 40 for motion reprojection to bring it to 80 FPS.

16 hours ago, Virtual-Chris said:

Not using expert mode.  Just as simple as possible - let it auto detect the target FPS.  In my two test flights, it targeted 87 and 91 FPS which is no problem, my system generally gets over 100FPS until I land at a busy airport. That's when the FPS dips below the target, and the app seems to go into some mode where it reduces the LODs and never comes out of this mode... so once the FPS recovers from the initial loading of the airport and all the traffic, the LODs remain stuck at these low values.  I have to manually reset the app to get it working properly again for my next flight. Not sure why it can't just resume normal operation on its own.

As mentioned on github, 0.4.5.2-test2 available here should hopefully resolve this issue to your satisfaction by now allowing settings reduction recovery to occur on the ground in non-expert mode, provided that ground speed is < 25 kts (ie. you are taxiing or stationary, but not taking off or landing).

11 minutes ago, Reset XPDR said:

As mentioned on github, 0.4.5.2-test2 available here should hopefully resolve this issue to your satisfaction by now allowing settings reduction recovery to occur on the ground in non-expert mode, provided that ground speed is < 25 kts (ie. you are taxiing or stationary, but not taking off or landing).

I thought his issue was occurring because he likes doing touch and goes.  This change isn't going to resolve it if that's the case.

 Thanks Reset,

Great to see your settings you are using.

Can I ask what Custom Reduction Settings you have in the drop down as well?

Great Program Thanks for all the hard work you have continued to put in to it.

 

Hamish

4 minutes ago, Hamish100 said:

 Thanks Reset,

Great to see your settings you are using.

Can I ask what Custom Reduction Settings you have in the drop down as well?

Great Program Thanks for all the hard work you have continued to put in to it.

 

Hamish

I have everything checked except for clouds. I like my clouds 🙂

1 hour ago, rjack1282 said:

I thought his issue was occurring because he likes doing touch and goes.  This change isn't going to resolve it if that's the case.

Yes you are right, and in VFR mode it defaults to recovery being enabled at 100 ft, so settings reduction would have been blocked from recovery for only a very short time. The log I looked at had greater periods of time on the ground than a touch and go and in that case the new change will allow recovery once you are going slow enough on the ground.

Edited July 17, 2025Jul 17 by Reset XPDR

9 hours ago, Reset XPDR said:

These are the 2D settings I use pretty much everywhere, with system FPS capped to 60 and MSFS on default Ultra, that work well, including complex airports:

VR is the same, except target FPS is 40 for motion reprojection to bring it to 80 FPS.

Are some of these MSFS24 specific settings? I'm on 2020 and not seeing the "Auto Reduce settings, Auto Increase Clouds" and everything below that...

1 minute ago, daan_vb said:

Are some of these MSFS24 specific settings? I'm on 2020 and not seeing the "Auto Reduce settings, Auto Increase Clouds" and everything below that...

Yes, they are MSFS 2024 settings only that were introduced back in version 0.4.4.8. They were made only applicable to MSFS 2024, as existing MSFS 2020 functionality was considered acceptable and MSFS 2024 tends to experience VRAM overflow, where such setting reductions are intended to help alleviate, much more frequently.

2 minutes ago, Reset XPDR said:

Yes, they are MSFS 2024 settings only that were introduced back in version 0.4.4.8. They were made only applicable to MSFS 2024, as existing MSFS 2020 functionality was considered acceptable and MSFS 2024 tends to experience VRAM overflow, where such setting reductions are intended to help alleviate, much more frequently.

Ah ok thanks

10 hours ago, rjack1282 said:

I thought his issue was occurring because he likes doing touch and goes.  This change isn't going to resolve it if that's the case.

I can work with this... I'm more often pretending to drop something/someone off anyway so this should do just fine.

10 hours ago, Reset XPDR said:

As mentioned on github, 0.4.5.2-test2 available here should hopefully resolve this issue to your satisfaction by now allowing settings reduction recovery to occur on the ground in non-expert mode, provided that ground speed is < 25 kts (ie. you are taxiing or stationary, but not taking off or landing).

Awesome! Thanks! This should work nicely. Will give it a go after work.