Looking for clarity on something.  If I use the FPS Cap method, do I use what I'm locking my frames to (say 60), or what I expect my FPS to be if using Frame Gen or Lossless Scaling (120)?

6 hours ago, CitationX said:

Right now I’m using just the autofps mode. It is because there is too much to load at the last minute as I fly into an airport? It usually happens about 20-30 feet above the runway. Just as I approach flare.

 

would using expert help me out more?

Probably not. If it is happening just above the runway, your TLOD would have already been stable at its minimum 1000 ft a minute or so out.

In non-expert mode, AutoFPS uses your default MSFS TLOD effectively as a centre point, giving you half of it below 1000 ft and double it above around 3000 ft in IFR mode. As such, it should stutter less on or near the ground than without this app.

Make sure you are using the IFR profile as the base altitude for the TLOD minimum is 1000 ft. If you have been using VFR it is 100 ft and that could be your issue.

4 hours ago, Randall Fortee22 said:

Looking for clarity on something.  If I use the FPS Cap method, do I use what I'm locking my frames to (say 60), or what I expect my FPS to be if using Frame Gen or Lossless Scaling (120)?

You use your FG or Lossless Scaling FPS. The target FPS label will tell you what it is expecting eg. Target FG Active FPS Cap.

I had a thought today that I can modify non-expert mode to be a bit smarter if Auto Target FPS is checked. Rather than assume the user wants FPS Sensitivity mode like it currently does the app can detect whether an FPS cap is in use, like it already does if Auto Target FPS is unchecked, and use the detected FPS cap as the target FPS and use FPS Cap mode instead.

I think this will give a better experience for non-expert users and has no impact on the UI. I'll code up a test version tomorrow.

Edited January 28, 20251 yr by Reset XPDR

On 1/24/2025 at 6:27 AM, Reset XPDR said:

Test3 version, which fixes these offsets, is now available here. Please report back on any issues encountered.

I just noticed that the link is now invalid (I downloaded it a few days ago though).

Just installed v0.4.4.4 using clean install as I have switched to the Su1 beta but the app opens but when I start msfs2024 I get a error message and the app closes have I got the wrong version for the beta

19 minutes ago, Cpt_Piett said:

I just noticed that the link is now invalid (I downloaded it a few days ago though).

Yes it is because it has been superseded by test4 here. I am using tags like this so that when I delete an old one that is how testers get notified in the app there is a new test version so I don't have to make a post here about it, but the unfortunate side effect is that it invalidates older links in my posts which I can't go back and edit.

In recent posts I have started stating that if the link is dead it is because the test version has been superseded and to go to the general release page here and look for the latest test version link yourself.

 

5 minutes ago, jimimac said:

Just installed v0.4.4.4 using clean install as I have switched to the Su1 beta but the app opens but when I start msfs2024 I get a error message and the app closes have I got the wrong version for the beta

You need to use the latest test version, currently test4, available here which is compatible with MSFS 2024 SU1. If the link is dead it is because the test version has been superseded so you will need to go to the general release page here and look for the latest test version link yourself.

Edited January 28, 20251 yr by Reset XPDR

4 minutes ago, Reset XPDR said:

In recent posts I have started stating that if the link is dead it is because the test version has been superseded and to go to the general release page here and look for the latest test version link yourself.

Ah yes, understood. I missed the link to test4, must have skipped that post somehow. 

8 minutes ago, Cpt_Piett said:

Ah yes, understood. I missed the link to test4, must have skipped that post somehow. 

I am not announcing all test releases here as it seems to upset some readers here that I am cluttering up my own thread with test version information (like right now! 😄). As I mentioned, if you are running an earlier test version and I release a new version, the app will tell you that a newer test version is available.

9 minutes ago, Reset XPDR said:

I am not announcing all test releases here as it seems to upset some readers here that I am cluttering up my own thread with test version information (like right now! 😄). As I mentioned, if you are running an earlier test version and I release a new version, the app will tell you that a newer test version is available.

How dare you clog(inform) your own thread with new versions of a fantastic FREEWARE. These opinions must be the minority and the majority of us appreciate and love your work. Thanks for a great app.

In my (humble) opinion, I'd prefer having a post from the dev every time there's a new test version. 

I have just installed the DLSS 4 stuff into my MSFS2024 system. Now the AutoFPS program says I have a compatibillity error. I have the latest version of AutoFPS. I don't know what's wrong or what to do to correct the issue. Can I get any help? Thanks.

42 minutes ago, Rob G said:

I have just installed the DLSS 4 stuff into my MSFS2024 system. Now the AutoFPS program says I have a compatibillity error. I have the latest version of AutoFPS. I don't know what's wrong or what to do to correct the issue. Can I get any help? Thanks.

DLSS 4 has nothing to do with compatibility between AutoFPS and MSFS. If you are on the release version of MSFS 2024 you should be on AutoFPS version 0.4.4.4 and if on the SU1 Beta you should be on AutoFPS 0.4.4.5-test which is at test 4 currently. Is this the case?

Edited January 28, 20251 yr by Reset XPDR

13 hours ago, Reset XPDR said:

Probably not. If it is happening just above the runway, your TLOD would have already been stable at its minimum 1000 ft a minute or so out.

In non-expert mode, AutoFPS uses your default MSFS TLOD effectively as a centre point, giving you half of it below 1000 ft and double it above around 3000 ft in IFR mode. As such, it should stutter less on or near the ground than without this app.

Make sure you are using the IFR profile as the base altitude for the TLOD minimum is 1000 ft. If you have been using VFR it is 100 ft and that could be your issue.

What is my best bet on setting up expert mode? I definitely have IFR checked. Could it be because the amount of objects the sim is injecting into the scenery when I’m about to touchdown?