Sorry I meant to say that I check put an tick in the TLOD Top at 200 (little check box to the right of TLOD Top) rather than let it go higher in the Expert Item and that seems to pretty much reduce the audio pops.

I will try FPS Sensitivity not sure why I was FPS Cap...

 

Many Thanks

 

Hamish

4 hours ago, Hamish100 said:

Sorry I meant to say that I check put an tick in the TLOD Top at 200 (little check box to the right of TLOD Top) rather than let it go higher in the Expert Item and that seems to pretty much reduce the audio pops.

I will try FPS Sensitivity not sure why I was FPS Cap...

 

Many Thanks

 

Hamish

The checkbox to the right of TLOD Top is for halving TLOD Top at night ie. it won't make any difference during the day:

If you want a lower TLOD Top, simply set TLOD Top to a lower value, noting that in 0.4.5.8 and earlier TLOD can go up to double this value so just set it to half of the maximum you want. ie. in this case if the max you ever want it to go is 300, then set TLOD Top to 150.

With the new UI redesign, the intention is to be able to set a TLOD Top and uncheck Extra for TLOD Top so that TLOD Top and Max can be one and the same, ie 300 for both is this case:

Also, re:

4 hours ago, Hamish100 said:

I will try FPS Sensitivity not sure why I was FPS Cap...

Given you state your configuration is:

Quote

I am using FPS Cap FSR3 @30FPS 60HZ Monitor running an AMD 7900X3D, Nvidia 4800

you actually should be using FPS Cap mode because with this configuration you have effectively capped your FPS at 60 (after FSR3). FPS Sensitivity mode does not work properly when using an FPS cap like this because the cap cannot produce the FPS above your FPS target for it to work correctly.

 

Edited November 11, 2025Nov 11 by Reset XPDR

10 hours ago, Hamish100 said:

I am using FPS Cap FSR3 @30FPS 60HZ Monitor running an AMD 7900X3D, Nvidia 4800

 

Would be interested if anyone else has found that correlation.

Hi,

I have a similar system to yours, and I also fly the Fenix quite a lot. I run in 4k, but I use Nvidia FG, not FSR3. My system is also capped at 30FPS, with FG 60FPS.

FPS CAP mode works very well for me with no issues.

Great Thank You for all the suggestions above Reset.

I did not know that about the TLOD Night time should have read it correctly.. The UI redesign is even better so Thank You.

Will move back to FS Cap as well.

 

H.

It took me a few days, but I finally think I have the new UI design sorted, front and back end, so 0.4.5.9-test1 is now available for a test drive here. It proved a little trickier than I thought, particularly in making it backwards compatible with 0.4.5.8 in case I get too many rocks thrown at me for changing it and get compelled to change it back. Nonethless, I am pretty confident the changes will provide a better user experience, particularly for new users of the app.

The main functional change of note are:

• "Avg Descent Rate" in FPS Sensitivity and Tolerance modes has been replaced with "Alt TLOD Top", consistent with the two other modes, and is a separately stored setting for backwards compatibility purposes.
• TLOD Extra is no longer available in Auto TLOD mode, as enabling it turns it into FPS Cap mode anyway, so users should use FPS Cap mode if Extra is desired.
• There are also some setting safety checks in case anyone gets carried away with the new multipliers, which would have the potential to set extra minimums higher than native maximums if left unchecked.

Anyway, have a go with it if you are feeling adventurous and let me know if I have inadvertently broken anything while hacking and slashing the code over the last few days.

Old vs New, with exact same settings (avg descent rate and alt TLOD top are separate settings, that just happen to be the same numerical value in this screenshot):

 

I am in flight now, and I updated and did lots of clicking around. So far, so good! I'll report back if I notice a problem.

0.4.5.9 test1 working flawless here. The UI cleanup is GREAT. Thank you!

FYI, there is also a discussion thread for 0.4.5.9-test over on my github page here where it is more appropriate to discuss any complex technical issues identified, as one user already has.

I like it so far but noticed more sound popping/stutters near KSFO and it looked like my vfr tlod at base was 80 and max was 300 but it wasn't reducing fast enough. I manually just changed the max to 150 and it was better. I feel like I just make things worse for me even though this app is really useful. 

I want to keep one for IFR and another for VFR. IFR TLOD should be 45 under 1200 feet and sslloowwllyy climb up to 250 TLOD for me. How can achieve that? And the descent? To have the tlod slowly dwindle down from 250 to 45 without drastic changes? My descent profile changes on how crazy i am or how batc is vectoring me in like a bat out of heck. Any suggestions? 

30 minutes ago, Sonosusto said:

I like it so far but noticed more sound popping/stutters near KSFO and it looked like my vfr tlod at base was 80 and max was 300 but it wasn't reducing fast enough. I manually just changed the max to 150 and it was better. I feel like I just make things worse for me even though this app is really useful. 

I want to keep one for IFR and another for VFR. IFR TLOD should be 45 under 1200 feet and sslloowwllyy climb up to 250 TLOD for me. How can achieve that? And the descent? To have the tlod slowly dwindle down from 250 to 45 without drastic changes? My descent profile changes on how crazy i am or how batc is vectoring me in like a bat out of heck. Any suggestions? 

If you didn't change any of the new settings, the app should be behaving as it did before, except if in Sensitivity mode and the change from avg descent rate to alt TLOD top is causing an issue, but it shouldn't be as it is actually more conservative.

I really need to know what other settings you are using to make any suggestions. Given screenshots are difficult to post here, can I get you to go to your latest log file, located in %appdata%\MSFS_AutoFPS\log, and look for a line similar to the following and post it here:

Quote

2025-11-14 03:38:38.203 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:True Mode:NFR ATgtFPS:False FltType:IFR TgtFPS:30 TLODMethod:Sens Tol:5 LOS-C:True TMin:150 TBaseExtra:true TBaseExtraMult:2 TMax:300 TMtns:False TNightDiv2:False TLODBAlt:1000 TLODTAlt:2000 CustomOLOD:True OLODB:200 OLODT:20 OLODBAlt:2000 OLODTAlt:10000 RSet:True IncCld:True RLvls:2 RFloor:2 RRecov:0 RSuite:2 VRAM+:Max Vrec:93% Vhld:96% Vred:98% 

 

Is there anyway I can make autofps show up in dark mode?

7 minutes ago, usernamerequired said:

Is there anyway I can make autofps show up in dark mode?

Not presently, no.

9 hours ago, Reset XPDR said:

If you didn't change any of the new settings, the app should be behaving as it did before, except if in Sensitivity mode and the change from avg descent rate to alt TLOD top is causing an issue, but it shouldn't be as it is actually more conservative.

I really need to know what other settings you are using to make any suggestions. Given screenshots are difficult to post here, can I get you to go to your latest log file, located in %appdata%\MSFS_AutoFPS\log, and look for a line similar to the following and post it here:

 

I am thinking maybe i should just keep it at non expert settings 

6 hours ago, Sonosusto said:

I am thinking maybe i should just keep it at non expert settings 

If that's what you were using before, then sure. The new app version should work as good, if not slightly more conservative, than the current release. Just be aware that the MSFS servers have recently been having a bad couple of days, causing stutters for many users with or without any particular version of my apps, so it is most likely that which you were experiencing.

1 hour ago, Reset XPDR said:

If that's what you were using before, then sure. The new app version should work as good, if not slightly more conservative, than the current release. Just be aware that the MSFS servers have recently been having a bad couple of days, causing stutters for many users with or without any particular version of my apps, so it is most likely that which you were experiencing.

Ahhhh. So likely little to do anything we're doing.