For me, the stutters are intermittent during final/landing (as I am sure most are). Without AutoFPS its a lot worse, I will put it that way.

When I am on descent with any plane, I just move my AutoFPS TLOD down to 100.

Since I can't/dont know how to post a picture of my settings I will just post them here. Any feedback would be great

2024: Target FPS 55

Expert

IFR

FPS Sensitivity 2

TLOD Min 50 (not checked)

TLOD Max 250 (checked)

TLOD Mtn Amt 50.  

The rest are Alt TLOD 1000, Descent rate 2000, Decrease Cloud Quality (unchecked always), Auto OLOD is 200 at base, Alt OLOD Base 2000 and top 10000ft.

 

Monitor is an Acer Gsync (old school) 60hz, Frame Gen working, DLSS4 confirmed. When I get the stutters its obviously near larger towns but it also happens at airports as well. NVCP is capped at 57fps, Vsync on (off in the sim) and Gsync enabled. These last settings are recommened by BlurBustes to have Gsync on but have Vsync on in the control panel. Low Latency is Ultra.

Again, any feedback regarding these settings with AutoFPS would be great.

Edited February 4, 20251 yr by Sonosusto

Hi,

Seems to be working fine and I sent the latest log via message since I had had trouble in the past.  I noticed this in the log:

GPU-Z companion app not running... reading the documentation does this have to be started manually and its config file edited?

I see talk of many updates.  Is this because of some of the updates?  Running 2.62.0.  Anyway started it manually and ran another flight and the results are excellent. 

Will send the revised log.  Nice work! 

My only problem is my FPS is running too high!  🙂  Need to get the details up, but that will be fun!

4 hours ago, Sonosusto said:

For me, the stutters are intermittent during final/landing (as I am sure most are). Without AutoFPS its a lot worse, I will put it that way.

When I am on descent with any plane, I just move my AutoFPS TLOD down to 100.

Since I can't/dont know how to post a picture of my settings I will just post them here. Any feedback would be great

2024: Target FPS 55

Expert

IFR

FPS Sensitivity 2

TLOD Min 50 (not checked)

TLOD Max 250 (checked)

TLOD Mtn Amt 50.  

The rest are Alt TLOD 1000, Descent rate 2000, Decrease Cloud Quality (unchecked always), Auto OLOD is 200 at base, Alt OLOD Base 2000 and top 10000ft.

 

Monitor is an Acer Gsync (old school) 60hz, Frame Gen working, DLSS4 confirmed. When I get the stutters its obviously near larger towns but it also happens at airports as well. NVCP is capped at 57fps, Vsync on (off in the sim) and Gsync enabled. These last settings are recommened by BlurBustes to have Gsync on but have Vsync on in the control panel. Low Latency is Ultra.

Again, any feedback regarding these settings with AutoFPS would be great.

It is very difficult to help someone else with settings as individual systems and expectations vary too much. Nonetheless, if you start with very conservative settings, which it looks like you have for your system specs, then work up (or down) from there you can usually find a suitable setting combination for your taste.

If the stutters are a lot worse without AutoFPS then there's probably not much you can do other than to observe what AutoFPS is doing when the stutters occur. If it hasn't changed your TLOD. OLOD or Cloud Quality for 5+ seconds then it is mostly likely the sim itself and not your AutoFPS settings, so other than setting other sim settings more conservatively there is not much more you can do.

2 hours ago, Jerryyyyy said:

Hi,

Seems to be working fine and I sent the latest log via message since I had had trouble in the past.  I noticed this in the log:

GPU-Z companion app not running... reading the documentation does this have to be started manually and its config file edited?

I see talk of many updates.  Is this because of some of the updates?  Running 2.62.0.  Anyway started it manually and ran another flight and the results are excellent. 

Will send the revised log.  Nice work! 

My only problem is my FPS is running too high!  🙂  Need to get the details up, but that will be fun!

I saw your messages and yes, you had GPU-Z up and running properly for your last flight.

Per the readme, GPU-Z is best set up as follows:

• Recommended GPU-Z settings are to minimise on close, load at windows startup (minimised), and to minimise to the system tray on the general tab, and refresh sensors while GPU-Z is in the background on the sensors tab.
• Ensure the GPU shown on the GPU-Z GPU dropdown list is the same as the GPU being used for MSFS.

This should work for any of the latest AutoFPS updates.

Hey Reset XPDR,

Thanks for the great program (as well as kayjay who kept it alive for 2024 for a while !)

What is the reason behind Alt OLOD Base minimum being 1000ft ? could we have the possibility to set it as low as Alt TLOD Base ? Or even lower like 10 ft ?

Hello,

since the last update, the FPS Cap could not maintain the the target value. Now the FPS deeps under the value (48fps), hiting under 20's and not reducing the TLOD at all. If I change the mode for other method, the app reduces the TLODand can keep the fps at 40s.

Right now it's better to run FS20/24 without the app. Before was working very, very well on both simulators.

I rolled back to version 444 and it works just fine keeping the TLOD low and the FPS cap near to 488fps.

4 hours ago, YankeeMike01 said:

Hey Reset XPDR,

Thanks for the great program (as well as kayjay who kept it alive for 2024 for a while !)

What is the reason behind Alt OLOD Base minimum being 1000ft ? could we have the possibility to set it as low as Alt TLOD Base ? Or even lower like 10 ft ?

The reason Alt OLOD Base minimum is 1000ft is because when the feature was first introduced the testers and I found that any lower than this introduced stutters during critical phases of flight and provided imperceptible object quality improvement for the small extra range you achieved anyway. If I change it to a lower threshold the most likely outcome is that users will start complaining the app is stuttering on final approach when they set it lower and I'd rather just save them from themselves, so no I do not intend changing it.

Edit: I just discovered that you can set a lower Alt OLOD Base than 1000 ft if you go into the config file in the root directory without the app running and edit the following line to whatever lower value you want.

  <add key="AltOLODBase" value="1000" />

This effectively bypasses the input range checking done when you enter a value. I just tried it and it allowed three steps of 5 in OLOD below 1000 ft which was  not visually noticeable to me but if that's what you want you at least have a way to do it.

Edited February 5, 20251 yr by Reset XPDR

3 hours ago, Wundermann said:

Hello,

since the last update, the FPS Cap could not maintain the the target value. Now the FPS deeps under the value (48fps), hiting under 20's and not reducing the TLOD at all. If I change the mode for other method, the app reduces the TLODand can keep the fps at 40s.

Right now it's better to run FS20/24 without the app. Before was working very, very well on both simulators.

I rolled back to version 444 and it works just fine keeping the TLOD low and the FPS cap near to 488fps.

There were no changes between 0.4.4.4 and 0.4.4.5 affecting FPS Cap automation logic, so it was mostly likely an issue with the settings you chose. 

Please make sure your settings for FPS Cap mode are in accordance with the guidance in the readme as follows:

• Ensure TLOD Base and TLOD Top values can be achieved within your FPS cap under the worst performance conditions flight session you expect to experience for the flight profile you are using (IFR or VFR). TLOD Base + can increase if performance allows but won't drop below set values.
• TLOD Base + is applied across the entire altitude schedule, potentially allowing a higher TLOD Top than set if performance conditions are favorable, so be particularly conservative when setting TLOD Top.

I just did a quick test myself wiht 0.4.4.5 where TLOD Base + was active in FPS Cap mode. I intentionally forced a lower FPS and TLOD reduced as expected, noting that once TLOD Base + is no longer active TLOD will not reduce any further (per dot point 1).

If you are still having an issue with 0.4.4.5 after complying with these guidelines, can you message me the log file where this happened and I will take a look.

Edited February 5, 20251 yr by Reset XPDR

I feel bad asking this, as I know the answer is probably in the readme. How high will TLOD Base go in FPS Cap mode? I had enough headroom here, so it was fine. And as I understand it, the TLOD increase will be more conservative when Hr+ is selected. 

34 minutes ago, Cpt_Piett said:

I feel bad asking this, as I know the answer is probably in the readme. How high will TLOD Base go in FPS Cap mode? I had enough headroom here, so it was fine. And as I understand it, the TLOD increase will be more conservative when Hr+ is selected. 

 

You'll be pleased to know the readme doesn't actually tell you how high TLOD Base + will actually go because, more often than not, the seek process will not get there because your system usually runs out of performance headroom before it terminates and it is rather complicated to explain.

To answer your question, the seek process will continue for up to 8 iterations or when the resultant TLOD Base amount (TLOD Base + TLOD Base + amount) is greater than 50% of the current resultant TLOD Top amount plus two extra iteration steps (nominally 2 x 50 = 100 TLOD). 

Where Hr+ comes into play is that when checked TLOD Base + will be backed off 2 steps (ie. 100 TLOD) from this maximum to give plenty of headroom whereas unchecked it will only be 1 step backed off.

In your specific case, your current resultant TLOD Top amount is 750 which means the seek process got TLOD Base + as high as 450, then backed off two steps to give 350 which gets added to your TLOD Base of 100 to give you a TLOD on the ground of 450.

In short, it goes as far as it reasonably can then backs it off, slightly more with Hr+, and that's all you really need to know.

Now do you see why I don't detail the calculation in the readme - I'd get rocks thrown at me! 😂 

 

Edited February 5, 20251 yr by Reset XPDR

1 hour ago, Reset XPDR said:

The reason Alt OLOD Base minimum is 1000ft is because when the feature was first introduced the testers and I found that any lower than this introduced stutters during critical phases of flight and provided imperceptible object quality improvement for the small extra range you achieved anyway. If I change it to a lower threshold the most likely outcome is that users will start complaining the app is stuttering on final approach when they set it lower and I'd rather just save them from themselves, so no I do not intend changing it.

Edit: I just discovered that you can set a lower Alt OLOD Base than 1000 ft if you go into the config file in the root directory without the app running and edit the following line to whatever lower value you want.

  <add key="AltOLODBase" value="1000" />

This effectively bypasses the input range checking done when you enter a value. I just tried it and it allowed three steps of 5 in OLOD below 1000 ft which was  not visually noticeable to me but if that's what you want you at least have a way to do it.

Thanks your answer !

8 minutes ago, Reset XPDR said:

Now do you see why I don't detail the calculation in the readme - I'd get rocks thrown at me! 😂 

Haha, yes that's understandable! Thanks for your elaborate answer, though, appreciated. 

Yeah, pretty sure whatever stutters happens its sim-related, not the app. Though I do notice it when the TLOD changes.

16 hours ago, Reset XPDR said:

There were no changes between 0.4.4.4 and 0.4.4.5 affecting FPS Cap automation logic, so it was mostly likely an issue with the settings you chose. 

Please make sure your settings for FPS Cap mode are in accordance with the guidance in the readme as follows:

• Ensure TLOD Base and TLOD Top values can be achieved within your FPS cap under the worst performance conditions flight session you expect to experience for the flight profile you are using (IFR or VFR). TLOD Base + can increase if performance allows but won't drop below set values.
• TLOD Base + is applied across the entire altitude schedule, potentially allowing a higher TLOD Top than set if performance conditions are favorable, so be particularly conservative when setting TLOD Top.

I just did a quick test myself wiht 0.4.4.5 where TLOD Base + was active in FPS Cap mode. I intentionally forced a lower FPS and TLOD reduced as expected, noting that once TLOD Base + is no longer active TLOD will not reduce any further (per dot point 1).

If you are still having an issue with 0.4.4.5 after complying with these guidelines, can you message me the log file where this happened and I will take a look.

Thanks for your answer.

 

I was using the 444 FPS cap flawlesly. Updated to 445 and it could not keep the TLOD low to respect the treshold, with the TLOD reaching 350 while still on ramp. Went back to 444 and it worked as it should, always with the same exact configuration. I need to do a few more flights with 444 before to test if it's really working, then try the 445 version again. 

Edited February 6, 20251 yr by Wundermann

7 hours ago, Wundermann said:

Thanks for your answer.

 

I was using the 444 FPS cap flawlesly. Updated to 445 and it could not keep the TLOD low to respect the treshold, with the TLOD reaching 350 while still on ramp. Went back to 444 and it worked as it should, always with the same exact configuration. I need to do a few more flights with 444 before to test if it's really working, then try the 445 version again. 

That'd be great as without me being able to reproduce it on my system, the only way I can see what is going on is from a log file where the issue actually occurred.