MSFS 2020 Auto FPS App v0.4.2

[Reset XPDR 1,271]

1 hour ago, Sonosusto said:

I actually have it unchecked and and it keeps dropping it to high immediately.

 

As soon as I click off expert settings. FPS stays in the green zone. I want it Ultra but it immediately changes to high. Again, FPS stays the same.

It is dropping to high in non-expert mode because that is what your MSFS default cloud setting is without the app running. The readme covers how to fix it:

• Do not change TLOD, OLOD and Cloud Quality MSFS settings manually while in a flight with this app running as it will conflict with what the app is managing and they will not restore to what you set when you exit your flight. If you wish to change the defaults for these MSFS settings, you must do so either without this app running or, if it is, only while you are in the MSFS main menu (ie not in a flight).

[Reset XPDR 1,271]

19 hours ago, Reset XPDR said:

GPU-Z can be installed anywhere but just needs to be already running when AutoFPS starts. I did it this way so the app isn't continually looking for GPU-Z, so it only checks once on start up.

@f.skywalkerI should clarify this advice in that the app actually checks whether GPU-Z is running at the start of each flight session, not on starting the app. I have updated the readme to clarify this.

Edited March 29 by Reset XPDR

[Pochi 68]

Say I want my cloud to be at Ultra if my system can handle it but do not want them to drop below High. Currently my cloud are set to High in MSFS.

 how should I set AutoFPS for this to work ?

Pierre

[Harrier77 60]

2 hours ago, Pochi said:

Say I want my cloud to be at Ultra if my system can handle it but do not want them to drop below High. Currently my cloud are set to High in MSFS.

 how should I set AutoFPS for this to work ?

Pierre

Hi Pierre,

I have clouds at Ultra in MSFS settings and decrease cloud quality ticked in Experts Settings. This works well for me giving me Ultra clouds most of the time with the occasional drop to High in dense areas.

Peter

[Pochi 68]

Thanks I will try that next flight !

[Reset XPDR 1,271]

New Test Version 0.4.2.9-test available here.

TL;DR - Only a minor update, which I mainly want out there to confirm I didn't break anything because of how much code changed when streamlining active LODs code. Formal release is imminent.

Changes are:

• Changed some of the non-expert internal settings for VFR mode to be slightly higher than IFR mode for the extra anticipated performance. The changes are highlighted in green:
  • Auto Target FPS - user selectable
  • FPS Sensitivity - 5%
  • VFR or IFR flight type - user selectable
  • Alt TLOD Base - VFR 100 ft, IFR 1000 ft
  • Avg Descent Rate - VFR 1000 fpm, IFR 2000 fpm
  • TLOD Minimum - VFR 100% of your current MSFS TLOD setting, IFR 50%
  • TLOD Maximum - VFR 300% of your current MSFS TLOD setting, IFR 200%
  • TLOD Min + - enabled
  • Decrease Cloud Quality - enabled
  • Cloud Recovery TLOD
    • 2/5 between TLOD Minimum and TLOD Maximum or + 50 over TLOD Min, whichever is lower.
    • If excessive changing of cloud quality levels are detected, the app will automatically increase its calculated cloud recovery TLOD.
  • Auto OLOD - enabled and VFR 150% of your current MSFS OLOD setting, IFR 100%
  • Pause when MSFS loses focus - disabled, unless using FG then enabled
• Changed window position saving to be inactive when VR is active as VR can interfere with correct window position data when starting the app up back in 2D.
• Removed duplicate code structures for determining active LODs and now have a single function that regularly updates them for use across the app.
• Fixed issue with graphics mode changes on startup where initial TLODs were being halved before saving and causing incorrect TLODs to be restored on exit.

Summary of changes since 0.4.2 formal release:

• Due to stutter issues being experienced by some users, the VFR flight type is now a special case of IFR automation behaviour with a very low default TLOD altitude base and higher default LODs to account for the greater performance expectation that GA flights in rural areas will have. In Non-Expert mode these setting are preset but in Expert mode they are fully customisable.
• FPS Tolerance, which was the automation method in the original release version that had larger TLOD changes but they occurred less often, has been reintroduced in Expert mode as an alternative to FPS Sensitivity as some users find the original FPS automation method to provide a smoother flight experience.
• In addition to Target FPS being remembered between the three graphics modes (PC, FG and VR), Target FPS will also be remembered between VFR and IFR flight types for each of these modes, giving up to six saved Target FPSs.
• Added full expert profile saving per flight type, not just target FPS. This means all settings in the expert settings area will be saved to a separate profile for IFR and VFR flight types, allowing the user to customise each of these flight types as desired and the app will remember them.
• The app's window position will be remembered between sessions, except movements to it made while in VR due to window restoration issues.
• Auto pause will activate if in flight and either MSFS is in active pause or the MSFS settings menu is being accessed.
• 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.

Edited March 30 by Reset XPDR

[GSalden 4,673]

Made an IFR flight from Amsterdam to Trabzon and everything worked very well ( 0.4.2.8 ) from start to finish.

Using FG here and my 4K TV’s @ 60 hertz. 
FPS 80 up to 140+ on my server ( 2 TV’s) and 100-200+ on my client ( 1 TV ).

Limiting the FPS leads to small stutters now and then so Unlimited. Its a pity that all FPS above 60 get lost ….

[Cpt_Piett 4,703]

9 hours ago, Reset XPDR said:

New Test Version 0.4.2.9-test available here.

TL;DR - Only a minor update, which I mainly want out there to confirm I didn't break anything because of how much code changed when streamlining active LODs code. Formal release is imminent.

I’ll do some testing later today in non-expert mode. Been testing 0.4.2.8 extensively in expert IFR and VFR mode. Yesterday in my newly acquired 146 around the London area. IFR w/ TLOD min 50, TLOD Max 400 with target FPS 65. No FPS drops and very little stuttering, even when overflying EGLL full of AI traffic at 3000ft.

9 hours ago, Reset XPDR said:

• TLOD Minimum - VFR 100% of your current MSFS TLOD setting, IFR 50%
• TLOD Maximum - VFR 300% of your current MSFS TLOD setting, IFR 200%

Just have to remember this when changing the settings in MSFS menu. I might test IFR around the London area and find a remote location in Norway (shouldn’t be very hard, lol!) for VFR.

Edited March 30 by Cpt_Piett

[Old_As_Dirt 160]

The only regression I have noted in the last few releases is the introduction of micro-stutters when using Track IR.  It is so small that it is almost inperceptable, but I am just trying to report as you have asked.  It's almost nothing in the whole scheme of things, but it's there.  I only notice it in the yaw mode when looking left or right - nothing while in a fixed position.  There is no loss of Framerates, during the observed very small deviation from perfect.

[Bobsk8 12,754]

3 minutes ago, Old_As_Dirt said:

The only regression I have noted in the last few releases is the introduction of micro-stutters when using Track IR.  It is so small that it is almost inperceptable, but I am just trying to report as you have asked.  It's almost nothing in the whole scheme of things, but it's there.  I only notice it in the yaw mode when looking left or right - nothing while in a fixed position.  There is no loss of Framerates, during the observed very small deviation from perfect.

What do you see if you exit Auto FPS?

Edited March 30 by Bobsk8

[Cpt_Piett 4,703]

Just did an approach into ENCN (rural area) in the 146. Non-expert VFR mode, stable FPS, smooth, no hiccups. 

Quote

• Expert: False Mode: FG ATgtFPS: False FltType: VFR TgtFPS: 65 TLODAMtd: 0 Tol: 5 TMin: 100 TMax: 300 OLODB: 300
• OLODT: 30 OLODBAlt: 2000 TMinEx: true CloudQ: True CRecovT: 150 Pause: True TLODBAlt: 100 MaxDesRate 2000
• CustomOLOD: False OLODTAlt: 10000 

2024-03-30 19:22:08.211 FPS: 65 FGAct: True Pri: FPS TLOD: 254 OLOD: 262 AGL: 3107 FPM: -1501 Clouds: Ultra 
2024-03-30 19:29:06.207 FPS: 33 FGAct: False Pri: FPS TLOD: 274 OLOD: 296 AGL: 2105 FPM: -883 Clouds: Ultra 
2024-03-30 19:30:15.214 FPS: 65 FGAct: True Pri: FPS TLOD: 274 OLOD: 300 AGL: 1486 FPM: -904 Clouds: Ultra 
2024-03-30 19:30:24.205 FPS: 65 FGAct: True Pri: FPS TLOD: 274 OLOD: 300 AGL: 1446 FPM: -778 Clouds: Ultra 
2024-03-30 19:30:51.208 FPS: 65 FGAct: True Pri: TLOD TLOD: 275 OLOD: 300 AGL: 1049 FPM: -652 Clouds: Ultra 
2024-03-30 19:31:54.213 FPS: 65 FGAct: True Pri: TLOD TLOD: 194 OLOD: 300 AGL: 563 FPM: -256 Clouds: Ultra 
2024-03-30 19:32:03.214 FPS: 65 FGAct: True Pri: TLOD TLOD: 194 OLOD: 300 AGL: 480 FPM: -695 Clouds: Ultra 
2024-03-30 19:32:12.212 FPS: 65 FGAct: True Pri: TLOD TLOD: 190 OLOD: 300 AGL: 362 FPM: -763 Clouds: Ultra 
2024-03-30 19:32:21.208 FPS: 65 FGAct: True Pri: TLOD TLOD: 174 OLOD: 300 AGL: 257 FPM: -517 Clouds: Ultra 
2024-03-30 19:32:30.212 FPS: 65 FGAct: True Pri: TLOD TLOD: 162 OLOD: 300 AGL: 183 FPM: -354 Clouds: Ultra 
2024-03-30 19:32:39.214 FPS: 66 FGAct: True Pri: TLOD TLOD: 150 OLOD: 300 AGL: 65 FPM: -562 Clouds: Ultra 
2024-03-30 19:32:48.212 FPS: 66 FGAct: True Pri: TLOD TLOD: 150 OLOD: 300 AGL: 11 FPM: -220 Clouds: Ultra 
2024-03-30 19:32:57.211 FPS: 65 FGAct: True Pri: TLOD TLOD: 150 OLOD: 300 AGL: 9 FPM: 30 Clouds: Ultra 
2024-03-30 19:34:16.212 FPS: 65 FGAct: True Pri: TLOD TLOD: 150 OLOD: 300 AGL: 595 FPM: -440 Clouds: Ultra 

I made a short video of two approaches: https://youtu.be/MW-aDfSySJQ

1. EKCH non-expert IFR mode
2. ENCN non-expert VFR mode

Edited March 30 by Cpt_Piett

[Old_As_Dirt 160]

5 hours ago, Bobsk8 said:

What do you see if you exit Auto FPS?

Every release that I have tried has been better than not using Auto FPS.  As stated, the noted micro, micro, micro stutter is almost unnoticable.  It was noticed by these 81 year old eyeballs and I was just reporting it in case even it could be something that Reset XPDR might find useful.  I think his work has been above and beyond.

[mmcmah 413]

52 minutes ago, Old_As_Dirt said:

Every release that I have tried has been better than not using Auto FPS.  As stated, the noted micro, micro, micro stutter is almost unnoticable.  It was noticed by these 81 year old eyeballs and I was just reporting it in case even it could be something that Reset XPDR might find useful.  I think his work has been above and beyond.

Check that you haven't tweaked your TrackIR curves in its software. I found that I had set nonlinear curves and so every time I centered my view, it stuttered as the velocity of the view change reduced all of a sudden. Once I made my curve straight lines, the stuttering went away (and I'm my case was before and unrelated to AutoFPS).

[kevinfirth 1,396]

13 hours ago, GSalden said:

Made an IFR flight from Amsterdam to Trabzon and everything worked very well ( 0.4.2.8 ) from start to finish.

Using FG here and my 4K TV’s @ 60 hertz. 
FPS 80 up to 140+ on my server ( 2 TV’s) and 100-200+ on my client ( 1 TV ).

Limiting the FPS leads to small stutters now and then so Unlimited. Its a pity that all FPS above 60 get lost ….

What tvs do you have? I have a 2023 Samsung which does up to 144hz VRR with gsync

[Old_As_Dirt 160]

1 hour ago, mmcmah said:

Check that you haven't tweaked your TrackIR curves in its software. I found that I had set nonlinear curves and so every time I centered my view, it stuttered as the velocity of the view change reduced all of a sudden. Once I made my curve straight lines, the stuttering went away (and I'm my case was before and unrelated to AutoFPS).

Good idea.  I have tweaked my curves as it is easier to turn my head to the right than the left.  I'll give it a try.  Thanks.  EDIT - That was it.  Thanks mmcmah and of course, thanks Reset XPDR.

Edited March 30 by Old_As_Dirt
Acknowleged a "fix" for something that wasn't broken.