12 hours ago, Reset XPDR said:

What beta are you referring to?

Should not have used the word "beta":

 0.4.3.1-test

Edited March 19, 20242 yr by Flyfaster_MTN002

8 hours ago, mmcmah said:

I primarily use IFR mode since it seems to give a more controlled experience (where you can define more of the parameters). However, I wanted to see if VFR mode got rid of some unnecessary TLOD changes just to hit the TLOD Min at landing/ground value.

I looked at the tooltips, and both modes seem to want to achieve TLOD Min (or TLM+) on the ground, which made me doubt what would happen. I was trying to see if VFR mode would keep my TLOD high - even low and on the ground - if my FPS was high enough. What I found taking off from LSZH is that even though I had PSXT running, I had plenty of FPS and I had my TLOD Min showing before taking off in VFR mode.

Quickly after takeoff, my TLOD changed from 100 to 800 and it worked great. No stutters and no obvious issues with the settings, despite only getting about 1500-2000 ft AGL. I did a quick and tight circuit and started descending to see if the high TLOD values would remain. What I found is that the app tried to decrease my TLOD rapidly as well, as if it was trying to get to the TLOD min for when I was on the ground. This was despite having a good amount of FPS still. However, it was inducing big stutters during the descent, which was causing momentary changes in the FPS values. I ended up landing with a TLOD of 500 and AutoFPS was happy with the value on the ground.

From the log:

2024-03-19 08:56:47.257 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 70 FGAct: True Pri: TLOD TLOD: 100 OLOD: 500 AGL: 5 FPM: 65 Clouds: High
2024-03-19 08:56:56.260 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 70 FGAct: True Pri: FPS TLOD: 108 OLOD: 500 AGL: 104 FPM: 634 Clouds: High
2024-03-19 08:57:05.264 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 70 FGAct: True Pri: FPS TLOD: 180 OLOD: 500 AGL: 340 FPM: 2289 Clouds: High
2024-03-19 08:57:14.265 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 70 FGAct: True Pri: FPS TLOD: 252 OLOD: 500 AGL: 569 FPM: 1718 Clouds: High
2024-03-19 08:57:23.259 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 70 FGAct: True Pri: FPS TLOD: 324 OLOD: 500 AGL: 766 FPM: 1677 Clouds: High
2024-03-19 08:57:32.262 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 70 FGAct: True Pri: FPS TLOD: 388 OLOD: 500 AGL: 1102 FPM: 2682 Clouds: High
2024-03-19 08:57:41.260 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 70 FGAct: True Pri: FPS TLOD: 460 OLOD: 500 AGL: 1320 FPM: 2089 Clouds: High
2024-03-19 08:57:50.263 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 69 FGAct: True Pri: FPS TLOD: 532 OLOD: 500 AGL: 1598 FPM: 382 Clouds: High
2024-03-19 08:57:59.269 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 69 FGAct: True Pri: FPS TLOD: 604 OLOD: 500 AGL: 1574 FPM: 1136 Clouds: High
2024-03-19 08:58:08.268 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 62 FGAct: True Pri: FPS TLOD: 671 OLOD: 500 AGL: 1647 FPM: 268 Clouds: High
2024-03-19 08:58:17.272 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 67 FGAct: True Pri: FPS TLOD: 682 OLOD: 500 AGL: 1751 FPM: 38 Clouds: High
2024-03-19 08:58:26.261 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 63 FGAct: True Pri: FPS TLOD: 724 OLOD: 500 AGL: 1879 FPM: 663 Clouds: High
2024-03-19 08:58:35.269 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 64 FGAct: True Pri: FPS TLOD: 752 OLOD: 500 AGL: 1935 FPM: -144 Clouds: High
2024-03-19 08:58:44.263 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 64 FGAct: True Pri: FPS TLOD: 776 OLOD: 500 AGL: 1804 FPM: -294 Clouds: High
2024-03-19 08:58:53.272 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 63 FGAct: True Pri: FPS TLOD: 800 OLOD: 500 AGL: 1778 FPM: -602 Clouds: High
2024-03-19 08:59:02.270 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 65 FGAct: True Pri: FPS TLOD: 800 OLOD: 500 AGL: 1643 FPM: -718 Clouds: High
2024-03-19 08:59:11.262 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 64 FGAct: True Pri: FPS TLOD: 800 OLOD: 500 AGL: 1512 FPM: -1055 Clouds: High
2024-03-19 08:59:20.266 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 58 FGAct: True Pri: FPS TLOD: 800 OLOD: 500 AGL: 1356 FPM: -713 Clouds: High
2024-03-19 08:59:29.260 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 62 FGAct: True Pri: FPS TLOD: 793 OLOD: 500 AGL: 1246 FPM: -788 Clouds: High
2024-03-19 08:59:38.271 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 60 FGAct: True Pri: FPS TLOD: 795 OLOD: 500 AGL: 1176 FPM: -787 Clouds: High
2024-03-19 08:59:47.257 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 59 FGAct: True Pri: FPS TLOD: 798 OLOD: 500 AGL: 1146 FPM: -899 Clouds: High
2024-03-19 08:59:56.265 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 62 FGAct: True Pri: FPS TLOD: 794 OLOD: 500 AGL: 990 FPM: -1431 Clouds: High
2024-03-19 09:00:05.258 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 60 FGAct: True Pri: FPS TLOD: 793 OLOD: 500 AGL: 818 FPM: -1648 Clouds: High
2024-03-19 09:00:14.261 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 56 FGAct: True Pri: FPS TLOD: 791 OLOD: 500 AGL: 682 FPM: -803 Clouds: High
2024-03-19 09:00:23.258 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 49 FGAct: True Pri: FPS TLOD: 730 OLOD: 500 AGL: 552 FPM: -1119 Clouds: High
2024-03-19 09:00:32.270 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 44 FGAct: True Pri: FPS TLOD: 658 OLOD: 500 AGL: 383 FPM: -1181 Clouds: High
2024-03-19 09:00:41.262 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 45 FGAct: True Pri: FPS TLOD: 586 OLOD: 500 AGL: 213 FPM: -1043 Clouds: High
2024-03-19 09:00:50.260 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 47 FGAct: True Pri: TLOD TLOD: 530 OLOD: 500 AGL: 84 FPM: -747 Clouds: High
2024-03-19 09:00:59.260 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 51 FGAct: True Pri: TLOD TLOD: 530 OLOD: 500 AGL: 8 FPM: -522 Clouds: High
2024-03-19 09:01:08.258 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 50 FGAct: True Pri: TLOD TLOD: 530 OLOD: 500 AGL: 4 FPM: -114 Clouds: High

 

 

Futher to @Cpt_Piett's response (and I agree: 800 to 100 in IFR - major TLOD change just asking for stutters!), VFR mode only sets TLOD Min on the ground (+ if you are getting extra performance and have + enabled), but then after that it will not work down to TLOD Min unless performance conditions have deteriorated, which your log file clearly shows has happened and again it is due to have such a larger TLOD range. I suggest you reduce it significantly.

6 hours ago, Flyfaster_MTN002 said:

Should not have used the word "beta":

 0.4.3.1-test

That's OK. So 0.4.2 release works fine but 0.4.3.1-test causes stutters?

1 hour ago, Reset XPDR said:

That's OK. So 0.4.2 release works fine but 0.4.3.1-test causes stutters?

Correct. As a baseline went back to DynamicLod today it had lots of stutters and long pauses as well. Will need to play with settings and try and figure out what is going on.

Not running the SU15 beta. Given it's release is imminent, will wait for it to drop for more testing unless you have suggestion(s).

2 hours ago, Reset XPDR said:

That's OK. So 0.4.2 release works fine but 0.4.3.1-test causes stutters?

With 0.4.3.1-test, I only have stutters in very demanding situations. I am slowly learning the settings I need for my type of flying.

I have put out a new AutoFPS test version here that primarily allows the user to select between the old 0.4.1 and new 0.4.2 TLOD automation algorithms by selecting FPS Tolerance or FPS Sensitivity respectively, to help out those that have been experiencing smoothness with 0.4.1 and stutters with 0.4.2 with having an option to try either TLOD automation method in the one version. As always, please let me know if one or the other, or both, work for those having this issue.

New Test Version 0.4.3.2-test:

• Added drop down option for FPS automation method for the user to choose between the original stepped automation method used in 0.4.1 (FPS Tolerance) or the gradual TLOD automation formula introduced in 0.4.2 (FPS Sensitivity), the latter being the default. This was done to help a few users for whom the new automation formula has introduced significant stuttering, perhaps due to smaller but more frequent TLOD changes.
• Fixed cloud recovery TLOD + symbol and label showing when cloud quality decrease is deselected.

2 hours ago, Flyfaster_MTN002 said:

Correct. As a baseline went back to DynamicLod today it had lots of stutters and long pauses as well. Will need to play with settings and try and figure out what is going on.

Not running the SU15 beta. Given it's release is imminent, will wait for it to drop for more testing unless you have suggestion(s).

The usual cause of stutters with AutoFPS is users having too low an FPS target for the FPS they are actually achieving, causing the app to rapidly increase TLOD to use up what it sees as excess performance capacity, thus causing stutters. In most cases, setting a higher target FPS resolves it. While you don't have to use the Auto Target FPS, enabling it briefly will tell you what the app thinks is the most appropriate target FPS for your current situation.

1 hour ago, Reset XPDR said:

I have put out a new AutoFPS test version here that primarily allows the user to select between the old 0.4.1 and new 0.4.2 TLOD automation algorithms by selecting FPS Tolerance or FPS Sensitivity respectively, to help out those that have been experiencing smoothness with 0.4.1 and stutters with 0.4.2 with having an option to try either TLOD automation method in the one version. As always, please let me know if one or the other, or both, work for those having this issue.

New Test Version 0.4.3.2-test:

• Added drop down option for FPS automation method for the user to choose between the original stepped automation method used in 0.4.1 (FPS Tolerance) or the gradual TLOD automation formula introduced in 0.4.2 (FPS Sensitivity), the latter being the default. This was done to help a few users for whom the new automation formula has introduced significant stuttering, perhaps due to smaller but more frequent TLOD changes.
• Fixed cloud recovery TLOD + symbol and label showing when cloud quality decrease is deselected.

Thank you. It will be interesting to see the difference. How does FPS Tolerance differ? I had never played around with the parameter until I started changing the sensitivity values in the recent versions.

2 minutes ago, mmcmah said:

Thank you. It will be interesting to see the difference. How does FPS Tolerance differ? I had never played around with the parameter until I started changing the sensitivity values in the recent versions.

FPS tolerance is the old method where you have to be higher or lower than the tolerance percentage before anything happens and uses more discrete larger TLOD steps.

1 minute ago, Reset XPDR said:

FPS tolerance is the old method where you have to be higher or lower than the tolerance percentage before anything happens and uses more discrete larger TLOD steps.

Thank you. By the way, a higher sensitivity values is actually less sensitive to FPS fluctuations as well?

3 minutes ago, mmcmah said:

Thank you. By the way, a higher sensitivity values is actually less sensitive to FPS fluctuations as well?

A higher sensitivity value actually makes the automation more aggressive in bringing down FPS fluctuations.

20 minutes ago, Reset XPDR said:

The usual cause of stutters with AutoFPS is users having too low an FPS target for the FPS they are actually achieving, causing the app to rapidly increase TLOD to use up what it sees as excess performance capacity, thus causing stutters. In most cases, setting a higher target FPS resolves it. While you don't have to use the Auto Target FPS, enabling it briefly will tell you what the app thinks is the most appropriate target FPS for your current situation.

Yes, I have seen big jumps cause stutters. I have also seen jumps (even small ones that decrease the TLOD) cause stutters that cause the FPS to dive down, causing another change (even a smallish one), that continues the cycle of driving down the FPS because of repeated stutters.

I agree that a high FPS cushion can cause it to rise too quickly, which can be a problem when trying to descend to bleed off the excess TLOD. I find that photogrammetry and larger airports (3rd party, not even the mega hubs), will cause stutters that can turn into a vicious cycle when you start turning to get the scenery in view.

As such, I've settled on a relatively high TLOD Min (200) at a relatively high altitude (1000 ft) to get things stabilized before getting too close to the ground.

1 minute ago, Reset XPDR said:

A higher sensitivity value actually makes the automation more aggressive in bringing down FPS fluctuations.

I must have misread the Readme. I thought the steps would be bigger, but the variance from the FPS target needed to be greater as well to trigger a change.

2 minutes ago, mmcmah said:

I must have misread the Readme. I thought the steps would be bigger, but the variance from the FPS target needed to be greater as well to trigger a change.

I might need to revise that as it was originally written with FPS tolerance in mind. I'll get back to you with what I come up with.

38 minutes ago, mmcmah said:

I must have misread the Readme. I thought the steps would be bigger, but the variance from the FPS target needed to be greater as well to trigger a change.

Revised readme states:

FPS Sensitivity

• Determines how sensitive the app will be to the variance between your current and target FPS.
• Also determines the largest TLOD step size you will see, being double the FPS sensitivity number.
• The lower the setting the smaller the changes will be, which is useful if you are experiencing stuttering with the default value of 5. Vice versa for higher settings.