22 minutes ago, CFIJose said:

I understand.

I sim only with MSFS 2020 and your version is MSFS_AutoFPS-installer-v0.4.4.1.

Thanks!

The current release v0.4.4.2 contains a lot of app robustness improvements and, apart from my username appearing in the app's window title and the ability to use the old systray icon app running location, the UI and core functionality you use for MSFS2020 is pretty much the same, so I suggest updating to it.

As stated earlier, it is super simple to go back to v0.4.4.1 (as long as you have kept your installer as I remove them from github when a newer version is available). You can even do it in the middle of a flight by closing the app, running the installer then rerunning the app.

As I am still working on v0.4.4.3, I can take a look to see if I can introduce a temporary checkbox on the status line to allow users like you to opt out of non-mandatory updates.

Edited January 15, 20251 yr by Reset XPDR

18 minutes ago, Reset XPDR said:

The current release v0.4.4.2 contains a lot of app robustness improvements and, apart from my username appearing in the app's window title and the ability to use the old systray icon app running location, the UI and core functionality you use for MSFS2020 is pretty much the same, so I suggest updating to it.

As stated earlier, it is super simple to go back to v0.4.4.1 (as long as you have kept your installer as I remove them from github when a newer version is available). You can even do it in the middle of a flight by closing the app, running the installer then rerunning the app.

As I am still working on v0.4.4.3, I can take a look to see if I can introduce a temporary checkbox on the status line to allow users like you to opt out of non-mandatory updates.

Thank you.

You get a GOLD Star from me, but you already know how I feel about this ap.

@CFIJosesomething like this?

Default:

 

Check For Updates unchecked:

Once you have started your first flight session, the Check for Updates checkbox disappears until you next start the app:

 

Note, if I tag an update as mandatory, you will see the following regardless of whether you have Check For Updates checked or not and will have to update the app for it to function again:

 

Edited January 15, 20251 yr by Reset XPDR

I can live with your non-stop updates and with how for now the app was checking update and warning me.

Awesome customer services, driven by passion sharing I suppose.

Edited January 15, 20251 yr by vbazillio

While I am putting in the check for updates, I am also changing the test version so that they always check for test updates rather than me having to announce them here and cluttering up the thread. ie. if you are participating in the test phase of a new version, the app will tell you when there is something newer to test or the final version has been released. The release notes where you download the update will tell you what has changed.

Luv the update message - well done 

I just touched down after a short hop from KSEA to a small airstrip in the PNW. The new FSCap mode is truly impressive: everything was incredibly smooth throughout the flight and during the approach. While cruising, I hit a TLOD of 430, which I've never experienced before! The GPU temperatures stayed stable, and there were no stutters; it was all seamless.

The only downside I noticed was while taxiing at KSEA. The app recognized that I had enough headroom to increase the TLOD to 150, but that was too demanding for my VRAM, so it quickly dropped it back down to 20. It might be beneficial for the ground rules to be a bit stricter regarding VRAM usage, perhaps preventing TLOD increases if VRAM usage exceeds 95%, for instance.

I'm not saying this only because of super-detailed airports; I've noticed some small airstrips located in remote areas that use the new ultra-detailed terrain technology (the Mount Rainier area for example) that devours VRAM even with the most basic aircrafts.

Anyway, it's a minor comment, I think it a great new feature. Thank you so much.

1 minute ago, Maddormo said:

I just touched down after a short hop from KSEA to a small airstrip in the PNW. The new FSCap mode is truly impressive: everything was incredibly smooth throughout the flight and during the approach. While cruising, I hit a TLOD of 430, which I've never experienced before! The GPU temperatures stayed stable, and there were no stutters; it was all seamless.

The only downside I noticed was while taxiing at KSEA. The app recognized that I had enough headroom to increase the TLOD to 150, but that was too demanding for my VRAM, so it quickly dropped it back down to 20. It might be beneficial for the ground rules to be a bit stricter regarding VRAM usage, perhaps preventing TLOD increases if VRAM usage exceeds 95%, for instance.

I'm not saying this only because of super-detailed airports; I've noticed some small airstrips located in remote areas that use the new ultra-detailed terrain technology (the Mount Rainier area for example) that devours VRAM even with the most basic aircrafts.

Anyway, it's a minor comment, I think it a great new feature. Thank you so much.

That's actually a really good idea, not just for FPS Cap but TLOD Min/Base + in the other automation modes. I will set it so that TLOD Min/Base + stops seeking if the VRAM overflow hold threshold is breached, nominally 95%.  Thanks for the feedback and great suggestion.

6 minutes ago, Reset XPDR said:

Thanks for the feedback and great suggestion.

It’s truly an honor for me. Honestly, I believe this tool is one of the best things that has happened to this new generation of FS.

 

0.4.4.3-RC2 is now available for download here. 

This version adds a check for updates option ( @CFIJosenot for test versions sorry, but it will look like this in the formal release version), checking for test version updates if running a test version (something I should have done a long time ago) and cancelling/resetting of TLOD Min/Base + if VRAM limiting is in play (thanks @Maddormo!)

I am hoping this is pretty much it before formal release. Let me know if otherwise.

 

4 hours ago, Reset XPDR said:

@CFIJosesomething like this?

Default:

 

Check For Updates unchecked:

Once you have started your first flight session, the Check for Updates checkbox disappears until you next start the app:

 

Note, if I tag an update as mandatory, you will see the following regardless of whether you have Check For Updates checked or not and will have to update the app for it to function again:

 

Love it!

1 hour ago, Reset XPDR said:

0.4.4.3-RC2 is now available for download here. 

This version adds a check for updates option ( @CFIJosenot for test versions sorry, but it will look like this in the formal release version), checking for test version updates if running a test version (something I should have done a long time ago) and cancelling/resetting of TLOD Min/Base + if VRAM limiting is in play (thanks @Maddormo!)

I am hoping this is pretty much it before formal release. Let me know if otherwise.

 

Thank you.

RC2, FPS Cap, non-expert, IFR, default TLOD 200, FG-FPS locked at 62. Fenix A321 CYYZ-KSFO with BATC+AIG. Very nice performance for the whole 5hr flight, even with a decent amount of traffic.

I was happy with TLOD Max 400 at cruise and TLOD 100 on the ground. Very reasonable settings with my hardware. 

FPS Cap non-expert = highly recommended. Just need to find an appropriate default TLOD (sim menu) and FPS lock+target. 

Last 13 minutes of flight until full stop on the runway. Some visible stutters but not bad at all. 

Edited January 16, 20251 yr by Cpt_Piett

23 hours ago, Reset XPDR said:

so I am bowing out

As am I. Still totally an advocate for AutoFPS.  Has worked so well for me. Just struggling how to make best use.  And not got my arms around that yet.

Edited January 16, 20251 yr by fppilot

In anticipation of 0.4.4.3 formal release, likely tomorrow morning my time (Australia), I have created draft release notes and have updated the readme with the new or changed features. Of particular note are the new sections on FPS Cap Mode, FG limitations, FPS cap detection in non-expert mode and the new Check for Updates option per the following excerpts:

Summary Section

• An Expert Option, which allows user customisation of the following:
  • A choice of TLOD automation method, each suitable for different specific uses of the app, namely FPS Sensitivity, FPS Tolerance, Auto TLOD and FPS Cap,

FG FAQ:

• Only one type of FG can be active at a time for the app to show FPS correctly. In particular, using native nVidia or the FG mod AND LSFG will cause incorrect FPS calculations in the app because they function differently when MSFS loses focus. Choose one or the other if you want to use them with this app.

Installation section:

• The app will automatically check for updates on startup by default and will notify you accordingly on the app status line.
  • If you wish to only be notified of mandatory updates, uncheck the Check For Updates checkbox.
  • In test versions, all app updates will be enabled by default regardless of what you have previously chosen for update notification in order to maintain a current test baseline.

Usage section:

• If an FPS cap is automatically detected (ie. the FPS matches the target FPS over a 10 second period at the end of the initial 20 second settling period), non-expert mode will use the FPS Cap TLOD automation method with the following settings:
  • Auto Target FPS - disabled and hidden as a user-specified FPS cap is in use
  • LOD Step - 5
  • Alt TLOD Top - VFR 3000 ft, IFR 5000 ft
  • TLOD Base - VFR 50% of your current MSFS TLOD setting, IFR 25%
  • TLOD Top - VFR 150% of your current MSFS TLOD setting, IFR 100%
  • TLOD Base + - enabled
  • Headroom + - enabled
  • TLOD Top + - disabled
  • TLOD Top - - enabled

• Auto Method - FPS Sensitivity generally gives the best results for most users and hence is the default. Use FPS Tolerance if you experience stuttering issues. Use Auto TLOD if you want a DynamicLOD-like experience. Use FPS Cap if you use an FPS cap on your system.
  • FPS Cap - a specific configuration of Auto TLOD optimised for when a system FPS cap is in use.
    • TLOD Base + and TLOD Top + are automatically enabled and disabled respectively, and their associated checkboxes are removed from the UI.
    • A "Headroom+" (Hr+) checkbox in expert mode (automatically enabled in non-expert mode) allows more performance headroom, reducing stuttering and FPS cap breaches, but at the cost of a potentially higher achievable TLOD.
    • The following guidelines should be observed to get the best result from this mode:
      • 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. 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.
      • The initial seek process may cause FPS instability as it identifies performance boundaries and this is a normal part of the process. It stabilises once the ideal TLOD is found, usually within 60 seconds.
      • After the seek process, you might experience stuttering when panning due to how MSFS loads scenery with high TLODs, regardless of whether you or this app has set them that high.
      • If stuttering is still unacceptable after following these guidelines, consider using AutoTLOD with TLOD Base + disabled instead to give you the lowest possible TLOD when on the ground.

Please let me know if this is suitable, noting what is written needs to strike a balance between being succinct and still providing enough information for someone with a reasonable grasp of what the app can do but is unfamiliar with a specific feature.