On 3/19/2024 at 8:49 AM, mmcmah said:

Reset,

An observation, that may be working as intended, but it seems like it might not be? If the app is started once you are in a flight, and the mode is set to IFR, the app changes the TLOD setting to the TLOD Min value before coming back up to where it needs to be.

More specifically, my default TLOD level is 200 and if I happen to open the app while in flight (for example to change my default graphics settings that can't be changed while the app is open), then as soon as I run the app, if drops to the TLOD Min value (100). If the app is run in VFR mode, this does not happen.

Note that the above behavior happened at 17,000 ft AGL, not on the ground. I am using 0.4.3.1-test.

I just tested this scenario and the TLOD setting stays the same switching between IFR and VFR when at high altitude, even if the app is started in flight. I looked at the code and the only thing it does when switching between these two modes is to reset TLOD Min +, which isn't applicable at high altitude anyway, and Cloud Quality, so I am not sure what was going on with your scenario.

10 minutes ago, Cpt_Piett said:

Thanks, can't wait to try it out! In fact I'll be so brave/silly as to install it while at FL170 over Nice. 

EDIT: Earlier today logging worked, even though it was set to false. After changing to 0.4.3.3, it doesn't seem to, even when set to true (I closed AutoFPS before editing .config): 

<add key="LogSimValues" value="true" />

That's very strange as I haven't touched LogSimValues since one of the later 0.4.2 test builds. All the app does is try to read in that key. If it doesn't find it, it creates a key and sets it to false and if it does find it and is set to true it logs the extra sim values. In fact, with all test versions that key is irrelevant as sim value logging is enabled by default.

Note, the app will only log these sim values if no settle timer is active and only if 10 second have passed and they have changed since the last log time, but this has always been the case. Perhaps message me your latest log file so I can better see what is going on.

2 hours ago, Reset XPDR said:

New AutoFPS 0.4.3.3-test version is available here. @Cpt_PiettThe new auto pause on sim pause/menu may help with the 0 FPS issue you were having the other day when exiting a flight if it is still occurring. This auto pausing code is experimental as simconnect does not have a native way of telling the app that the user is in the menu, so it works off seeing whether your ground speed and AGL are exactly the same as a second ago, implying that you are paused or in the menu, and it does seem to work. Please let me know if it doesn't.

Changes are:

• Added sim pause detection for active pause or when escaped to the settings menu, which will now pause the app to stop making setting changes and to freeze any running FPS settling timer while the sim is paused. This should also improve stability for when exiting a flight as the app will have been paused before the user chooses to exit the flight, thus minimising app changes to MSFS settings. Note it does not work when stopped on the ground but that doesn't really matter as only initial TLOD and cloud quality changes can occur in this state anyway.
• Fixed major issue with certain TLOD Min, Max and Cloud Recovery TLOD setting combinations causing recursive loading of app settings resulting is a stack overflow and crashing the app.

 

 

You nailed it again - Kudos. Stutters and pauses gone. Auto FPS works really well when ticked (went from solid 15 FPS (28 targeted) and 50 LOD without to 12 FPS and LOD way higher and actively changing when checked) but nicer mountains and trees galore! 🙂

 

3 hours ago, Reset XPDR said:

New AutoFPS 0.4.3.3-test version is available here. @Cpt_PiettThe new auto pause on sim pause/menu may help with the 0 FPS issue you were having the other day when exiting a flight if it is still occurring.

Interesting.  I had privately communicated with Cpt Piett about this over past the weekend. I was just now today coming to report that in my eleven 0.4.2 flights I have experienced two mid flight MSFS freeze ups, and three instances where when returning after a flight to the MSFS Main Menu where the sim also froze up.  Took Windows Task Manager to end the sim each of those times.  My specs are in my footer, and I must also report that prior to moving to 0.4.2 I did a fresh install of the Frame Generation hack for pre-4-series RTX GPUs.  So my experience is likely unique in that respect.  Thus my hesitation in reporting this until now. 

When flying, my sim is a blessing of smoothness.  Just the freeze ups are of concern.  Will see what 0.4.3 deals me tomorrow when I have two flights of > 2.5 hours planned.

8 minutes ago, fppilot said:

Interesting.  I had privately communicated with Cpt Piett about this over past the weekend. I was just now today coming to report that in my eleven 0.4.2 flights I have experienced two mid flight MSFS freeze ups, and three instances where when returning after a flight to the MSFS Main Menu where the sim also froze up.  Took Windows Task Manager to end the sim each of those times.  My specs are in my footer, and I must also report that prior to moving to 0.4.2 I did a fresh install of the Frame Generation hack for pre-4-series RTX GPUs.  So my experience is likely unique in that respect.  Thus my hesitation in reporting this until now. 

When flying, my sim is a blessing of smoothness.  Just the freeze ups are of concern.  Will see what 0.4.3 deals me tomorrow when I have two flights of > 2.5 hours planned.

If you do still have freeze issues, try using the old 0.4.1 FPS Tolerance method of TLOD automation that you can now select in 0.4.3.2-test or later. This older method should be friendlier to older hardware that may have trouble keeping up with the constant and smaller TLOD changes the new FPS Sensitivity method imposes. Let me know either way.

Edited March 21, 20242 yr by Reset XPDR

I will try 4.3.3 later - thank you for continuing to dig into reported issues, even if they don't sound like something I've been experiencing.

I wanted to report back that in my usage, FPS Tolerance seemed to create more frequent but smaller stutters than FPS Sensitivity. Note, IFR works best for me overall, but for real GA VFR flying in non urban areas, I would definitely use VFR mode!

35 minutes ago, Reset XPDR said:

If you do still have freeze issues, try using the old 0.4.1 FPS Tolerance method of TLOD automation that you can now select in 0.4.3.2-test or later. This older method should be friendlier to older hardware that may have trouble keeping up with the constant and smaller TLOD changes the new FPS Sensitivity method imposes. Let me know either way.

Thanks for the acknowledgement. Opened the app and made that change so I don't  forget tomorrow.  BTW I really appreciate the "persistence" built into the app, where it retains settings even when removing and replacing test/release versions.

Just now, fppilot said:

Thanks for the acknowledgement. Opened the app and made that change so I don't  forget tomorrow.  BTW I really appreciate the "persistence" built into the app, where it retains settings even when removing and replacing test/release versions.

You can thank my predecessor @Fragtalityfor that. I inherited a pretty solid code base from the DynamicLOD app that does this and many other wonderful functions.

Just to satisfy my insatiable curiosity, I tested VFR expert mode on approach to LFMN Nice in the Fenix. Stutter-fest! Glad I tried it though as it emphasizes the point of using IFR for flying into dense areas.

I'm happy to report that 0.4.3.3 is working fine. My FPS zero issues seems to have been resolved. I've only done one flight so far - Fenix A320 from LIMJ Genoa to Nice, where I did a gazillion go-arounds to try and nail the visual approach into runway 22R. 

I find that I check AutoFPS less and less during flights, as I'm confident it's doing its stellar job in the background. I.e. more flying, less testing 😄

1 hour ago, mmcmah said:

Note, IFR works best for me overall, but for real GA VFR flying in non urban areas, I would definitely use VFR mode!

Same!

Edited March 21, 20242 yr by Cpt_Piett

Sorry, I can't find the info, what is the difference between FPS Sensitivity and FPS Tolerance?

16 minutes ago, abennett said:

Sorry, I can't find the info, what is the difference between FPS Sensitivity and FPS Tolerance?

 

20 hours 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.

https://github.com/ResetXPDR/MSFS2020_AutoFPS?tab=readme-ov-file#readme

Quote

• 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.

 

Edited March 21, 20242 yr by Cpt_Piett

50 minutes ago, Cpt_Piett said:

Just to satisfy my insatiable curiosity, I tested VFR expert mode on approach to LFMN Nice in the Fenix. Stutter-fest! Glad I tried it though as it emphasizes the point of using IFR for flying into dense areas. 

You are not the first person to mention stuttering in VFR mode, although you have very high LOD settings so there is that. FPS Tolerance has a sliding scale of TLOD change effect from 1000 ft to ground being full to nothing respectively. FPS Sensitivity originally had this too but I took it out in one of the later 04.2-test builds, and it's removal could be what is causing this extra stuttering.

As such, I was wondering if you could do the same scenario again in VFR but with the FPS Tolerance TLOD automation setting. If it is smoother, I will put the 0-1000ft smoothing back in the next test build for FPS sensitivity and you could see if it is any better. Just a quick and dirty test for each will do.

Edit: I am just going to go and add back in the 0-1000ft smoothing for VFR mode in the next test build as that is the only notable difference between the 0.4.2 12Mar240940Z test version and 0.4.2 release whereby users experiencing stuttering with the latter do not get it with the former.

Edited March 21, 20242 yr by Reset XPDR

15 minutes ago, Reset XPDR said:

As such, I was wondering if you could do the same scenario again in VFR but with the FPS Tolerance TLOD automation setting. If it is smoother, I will put the 0-1000ft smoothing back in the next test build for FPS sensitivity and you could see if it is any better. Just a quick and dirty test for each will do.

Sure, no problem. Looking at the TLOD values in the log, the stuttering sort of makes sense though: 

Quote

Expert: True Mode: FG ATgtFPS: False FltType: VFR TgtFPS: 77 Tol: 5 TMin: 50 TMax: 975 TMinEx: true CloudQ: True CRecovT: 100 Pause: True TLODBAlt: 1000 MaxDesRate 2000 CustomOLOD: True OLODB: 1000 OLODT: 20 OLODBAlt: 2000 OLODTAlt: 10000 
FPS: 81 FGAct: True Pri: FPS TLOD: 381 OLOD: 893 AGL: 2873 FPM: -17 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 397 OLOD: 893 AGL: 2874 FPM: 13 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 415 OLOD: 899 AGL: 2823 FPM: -751 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 433 OLOD: 912 AGL: 2712 FPM: -774 Clouds: Ultra 
2024-03-21 00:16:40.412 [INF] [ MainWindow:UpdateLiveValues      ] FPS: 80 FGAct: True Pri: FPS TLOD: 451 OLOD: 926 AGL: 2599 FPM: -755 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 467 OLOD: 939 AGL: 2322 FPM: -752 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 483 OLOD: 978 AGL: 2178 FPM: -1125 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 501 OLOD: 998 AGL: 2012 FPM: -1122 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 519 OLOD: 1000 AGL: 1844 FPM: -1118 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 537 OLOD: 1000 AGL: 1677 FPM: -1114 Clouds: Ultra 
FPS: 78 FGAct: True Pri: FPS TLOD: 550 OLOD: 1000 AGL: 1514 FPM: -1109 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 561 OLOD: 1000 AGL: 1349 FPM: -1111 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 579 OLOD: 1000 AGL: 1183 FPM: -1099 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 597 OLOD: 1000 AGL: 1012 FPM: -1187 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 615 OLOD: 1000 AGL: 863 FPM: -627 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 633 OLOD: 1000 AGL: 835 FPM: -142 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 650 OLOD: 1000 AGL: 790 FPM: -513 Clouds: Ultra 
FPS: 78 FGAct: True Pri: FPS TLOD: 662 OLOD: 1000 AGL: 754 FPM: 28 Clouds: Ultra 
FPS: 77 FGAct: True Pri: FPS TLOD: 666 OLOD: 1000 AGL: 763 FPM: -91 Clouds: Ultra 
FPS: 76 FGAct: True Pri: FPS TLOD: 659 OLOD: 1000 AGL: 750 FPM: -211 Clouds: Ultra 
FPS: 77 FGAct: True Pri: FPS TLOD: 656 OLOD: 1000 AGL: 709 FPM: -104 Clouds: Ultra 
FPS: 78 FGAct: True Pri: FPS TLOD: 656 OLOD: 1000 AGL: 686 FPM: -21 Clouds: Ultra 
FPS: 77 FGAct: True Pri: FPS TLOD: 656 OLOD: 1000 AGL: 728 FPM: 131 Clouds: Ultra 
FPS: 77 FGAct: True Pri: FPS TLOD: 662 OLOD: 1000 AGL: 693 FPM: -249 Clouds: Ultra 
FPS: 73 FGAct: True Pri: FPS TLOD: 646 OLOD: 1000 AGL: 627 FPM: -614 Clouds: Ultra 
FPS: 74 FGAct: True Pri: FPS TLOD: 619 OLOD: 1000 AGL: 520 FPM: -657 Clouds: Ultra 
FPS: 71 FGAct: True Pri: FPS TLOD: 576 OLOD: 1000 AGL: 437 FPM: -608 Clouds: Ultra 
FPS: 72 FGAct: True Pri: FPS TLOD: 512 OLOD: 1000 AGL: 299 FPM: -1265 Clouds: Ultra 
FPS: 67 FGAct: True Pri: FPS TLOD: 452 OLOD: 1000 AGL: 124 FPM: -585 Clouds: Ultra 
FPS: 66 FGAct: True Pri: FPS TLOD: 362 OLOD: 1000 AGL: 167 FPM: 1208 Clouds: Ultra 
FPS: 80 FGAct: True Pri: FPS TLOD: 315 OLOD: 1000 AGL: 421 FPM: 1816 Clouds: Ultra 

 

Just loaded a flight, and things look a bit funky. Never seen this before:

1 minute ago, Cpt_Piett said:

Sure, no problem. Looking at the TLOD values in the log, the stuttering sort of makes sense though: 

 

Those are some big TLOD jumps, caused mostly by your high TLOD settings. I'll have the new test build ready shortly.