As of now there has been 35 downloads of the new test1 version, so hopefully at least a few of you here are using it.

I have just updated the app to test2 with nothing other than the version number changing, to see how the auto upgrade process goes for testers. It should happen as described pictorially here.

Please let me know if it works as advertised and whether any other issues occurred.

 

1 hour ago, Reset XPDR said:

As of now there has been 35 downloads of the new test1 version, so hopefully at least a few of you here are using it.

I have just updated the app to test2 with nothing other than the version number changing, to see how the auto upgrade process goes for testers. It should happen as described pictorially here.

Please let me know if it works as advertised and whether any other issues occurred.

 

Worked flawlessly for me!

3 minutes ago, outermarker said:

Worked flawlessly for me!

Awesome! Thanks for the feedback.

Working great for me too...in MSFS2020 and 2024.

Automatic update worked well too.

I was a bit worried that user permissions might thwart auto update on some user's systems, but it should be OK as the installer is downloaded to the user's downloads directory, which the user should definitely have permission to use, then run the same installer that otherwise works without the quick update option. So far so good!

Edit: One thing I have found is that when the auto update message box is shown, the app will continue to connect to MSFS if it is running, which is not a big deal if the user chooses no but if they take their time and choose yes after the session connects, the app terminates rather abruptly and may not restore MSFS settings correctly. I am going to modify the code so that while the message box is showing that the app will not connect a session but then will resume afterwards if no is chosen, which will avoid this potential situation.

Edited February 12, 20251 yr by Reset XPDR

Hi Reset,

Thanks for considering the cloud/visibility mod; I understand why it's not possible at the moment. No worries.

Another question for you: I have Vsync enabled with a frame rate cap of 60. Would it cause any problems in AutoFPS if I set my Target PC FPS to 60 as well? Does AutoFPS need a range of FPS to play with, or can my MSFS max be equal to AutoFPS's min?

1 hour ago, prolixindec said:

Hi Reset,

Thanks for considering the cloud/visibility mod; I understand why it's not possible at the moment. No worries.

Another question for you: I have Vsync enabled with a frame rate cap of 60. Would it cause any problems in AutoFPS if I set my Target PC FPS to 60 as well? Does AutoFPS need a range of FPS to play with, or can my MSFS max be equal to AutoFPS's min?

FPS Cap TLOD automation mode is what you are looking for, as described in detail in the readme.

• FPS Cap - a specific configuration of Auto TLOD optimised for when a system FPS cap is in use.

       ...

 

Edited February 13, 20251 yr by Reset XPDR

@Reset XPDR working great here too! One question, it seemed like some versions ago when we closed the app with the "x", it would minimize to the taskbar tray, now it closes. Is there a tick box or setting I might be missing to bring that back? Sometimes I bring the app up (in front) and wish to use the "x" button to just minimize to tray. Not a big deal, but thought I would ask or see if I was hallucinating about that past "feature" lol.

Thank you for such a useful app, I wouldn't run MSFS without it!

22 minutes ago, KERNEL32 said:

@Reset XPDR working great here too! One question, it seemed like some versions ago when we closed the app with the "x", it would minimize to the taskbar tray, now it closes. Is there a tick box or setting I might be missing to bring that back? Sometimes I bring the app up (in front) and wish to use the "x" button to just minimize to tray. Not a big deal, but thought I would ask or see if I was hallucinating about that past "feature" lol.

Thank you for such a useful app, I wouldn't run MSFS without it!

It's still there but is now an option you choose when you run the installer. Just rerun the installer and select the sys tray option.

Is there any way to get it to always use the TLOD base setting when below the AT TLOD Base number when using FPS Cap? I currently have a TLOD Base setting of 100 but when I start the sim up it runs it's checks and it decides that my system can run 200. Sometimes more, sometimes less. Trouble is, it can't and I have to put up with jerking and micro pauses until it decides that it really can't and then defaults down to the TLOD baase setting of 100.

My AT TLOD Base setting is 500 so I would assume that below 500ft it should always default to TLOD 100. This works fine when I'm landing but for some reason, when I load into the sim it tries to push it's luck when it really shouldn't.

What am I missing?

41 minutes ago, Jazz said:

Is there any way to get it to always use the TLOD base setting when below the AT TLOD Base number when using FPS Cap? I currently have a TLOD Base setting of 100 but when I start the sim up it runs it's checks and it decides that my system can run 200. Sometimes more, sometimes less. Trouble is, it can't and I have to put up with jerking and micro pauses until it decides that it really can't and then defaults down to the TLOD baase setting of 100.

My AT TLOD Base setting is 500 so I would assume that below 500ft it should always default to TLOD 100. This works fine when I'm landing but for some reason, when I load into the sim it tries to push it's luck when it really shouldn't.

What am I missing?

Check out my post and Reset's response on Page 158. 

What I ultimately decided was best for me and what I would recommend you use is FPS Sensitivity and set your frame limit a couple FPS below your target.  I found FPS Cap mode to not be good for resource hungry airliners at pay ware airports because of the issue you describe.  

I use FPS cap exclusively. I also have the issue that sometimes (huge airports, lots of traffic) TLOD can end up too high. I’m wondering whether it might help to hit the reset button in external view. Reason being that it’s often more demanding than cockpit view (in MSFS2024 at least). Hopefully then, AutoFPS will set a lower TLOD. 

3 hours ago, Jazz said:

Is there any way to get it to always use the TLOD base setting when below the AT TLOD Base number when using FPS Cap? I currently have a TLOD Base setting of 100 but when I start the sim up it runs it's checks and it decides that my system can run 200. Sometimes more, sometimes less. Trouble is, it can't and I have to put up with jerking and micro pauses until it decides that it really can't and then defaults down to the TLOD baase setting of 100.

My AT TLOD Base setting is 500 so I would assume that below 500ft it should always default to TLOD 100. This works fine when I'm landing but for some reason, when I load into the sim it tries to push it's luck when it really shouldn't.

What am I missing?

The app tries to push its luck in FPS Cap mode when loading the sim as that is the only way for it to find at what TLOD level the FPS Cap is breached. Then, if you have Hr+ set as you should for more conservative headroom, it backs it off by 100 TLOD to give you good headroom margin. This entire process should take less than 60 seconds, which IMO is a reasonable tuning time.

If you don't like this tuning process, but otherwise like FPS Cap mode, try switching to Auto TLOD mode and make sure you have TLOD Base + unchecked. You will lose the ability to set a target FPS, but that's because your TLOD Base and Top should be conservative enough that any FPS cap you have set externally should not be breached, so it doesn't really matter.

Alternatively, as @rjack1282suggests, try FPS Sensitivity mode with the FPS target set at least 5-10% below any FPS cap you have set, otherwise the automation logic won't work.

 

5 hours ago, Cpt_Piett said:

I use FPS cap exclusively. I also have the issue that sometimes (huge airports, lots of traffic) TLOD can end up too high. I’m wondering whether it might help to hit the reset button in external view. Reason being that it’s often more demanding than cockpit view (in MSFS2024 at least). Hopefully then, AutoFPS will set a lower TLOD. 

So are you saying that even though TLOD gets backed off by 100 from the FPS cap breaching TLOD level, which should give plenty of performance headroom, that you are still getting stuttering while holding that TLOD level or is the stuttering only when TLOD is being auto reduced when you pan the external view?

If this is a common experience, I could change Hr+ to be numerical so that the higher the number the more conservative the final TLOD will be. eg. a setting of 1, 2 or 3 etc could result in an FPS cap breaching TLOD backing off of 50, 100, and 150 TLOD etc respectively. Note, the process will still need to initially seek the FPS cap breach to know how far to back things off, so the tuning phase will still be required.

Alternatively, I could just limit the amount of TLOD extra on the ground to +100 in IFR mode, regardless of how high it could go.

Before I go making any such changes, it would be helpful if you could make a quick video demonstrating exactly what the issue is with TLOD being too high at huge airports, with AutoFPS showing on top of MSFS so I can see what is going on with both. Thanks.

Edited February 13, 20251 yr by Reset XPDR

I posted this in the MSFS Adaptive LOD thread as it was where the idea originated but it is equally applicable to AutoFPS and is in fact where I am first trying to implement it.

The background to this is that currently the only way to set MFG (Multi Frame Generation) in MSFS is via the nVidia app or inspector, both of which required admin access and these settings are buried deep within an unknown file structure. As such, the only way for my LOD apps to show MFG FPS correctly is for the user to manually tell the app what MFG multiplier, if any, is in use. Yes it is not ideal, but until Asobo allows MFG to be enabled and its multiplier set in the MSFS settings in a future MSFS update, this is the only practical way to achieve this right now.

In consideration of this, comments on this proposed interim implementation are welcome.

Edit: I released the concept demonstrator in test5 available here so I'd appreciate it if anyone with a 5000 series card using MFG gives it a whirl and reports back on success or otherwise.

Edited February 14, 20251 yr by Reset XPDR