1 hour ago, Reset XPDR said:

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?

I found V0.4.4.5 and installed it. That was the problem. I am just learning about AutoFPS and didn't know the SU1 version of MSFS2024 required a new version. Thank you very much for the insight. I was really getting frustrated.

Edited January 28, 20251 yr by Rob G

1 hour ago, CitationX said:

What is my best bet on setting up expert mode?

I gave you some suggested settings to try here. Have you tried them yet?

1 hour ago, CitationX said:

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?

If you have IFR checked then the app hasn't been changing anything in MSFS for the last minute or so before touchdown. Normally all airport scenery is loaded in well before then so it is possible some scenery a little bit past the airport that is loading in coincidentally as you touch down.

Edited January 28, 20251 yr by Reset XPDR

2 hours ago, Rob G said:

I found V0.4.4.5 and installed it. That was the problem. I am just learning about AutoFPS and didn't know the SU1 version of MSFS2024 required a new version. Thank you very much for the insight. I was really getting frustrated.

In future I suggest you follow the instructions on the message box that pops up advising you of the incompatibility before getting frustrated. Specifically, the third suggestion states:

Quote

3. If MSFS has just been updated, it may no longer be compatible with this app. Raise an issue on github if one has not already been raised.

If you had done so you would have discovered there is an issue already raised there about MSFS 2024 SU1 incompatibility that tells you to download and install the latest test version as you have now done.

Perhaps you weren't sure where to go on github to find where issues are raised for this app. I didn't put a URL to the github issues page at the time I coded this as they are not possible with standard Windows message boxes but I have subsequently made a custom message box that does allow them so I will update the text to include that URL for suggestion number 3 which will make it easier for users to locate such information.

Edit: Here's the new message I have coded in to 0.4.4.5-test5 that should be released today that includes a github issues URL link:

Edited January 29, 20251 yr by Reset XPDR

16 hours ago, Reset XPDR said:

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.

I tried coding this up today and while it worked with an actual FPS cap it was also falsely detecting FPS caps when the FPS just happened to be stable when not capped. While I could tightened up the FPS cap detection code, it could end up missing detecting legitimate FPS caps if there was a transient change in FPS while the detection process was active.

As such, I have decided not to go ahead with this idea as it was too unreliable to be automated. Users can still achieve auto FPS cap detection the way it has already been working by leaving auto target FPS unchecked and manually entering the FPS cap they have set on their system.

FYI, I have just released a new test version 0.4.4.5-RC1 that you can grab here. I have advanced the test version to release candidate as I am finding more users are joining the MSFS SU1 Beta and I am now confident that 0.4.4.5 is fully compatible with at least the first SU1 Beta version.

As such, I am planning on formally releasing 0.4.4.5 tomorrow so it is easier for users to know there is a new version compatible with everything currently out there. Please let me know if there are any notable issues I need to resolve with RC1 before I do so.

Changes in RC1 are:

• Added the github issues page URL link to the message that pops up if the memory compatibility test fails so that users can be better informed of the status of app compatibility with new MSFS versions.
• Fixed logic issue with non-expert mode where the settle timer could be triggered indefinitely when using Auto Target FPS.

MSFS_AutoFPS version 0.4.4.5 has now been formally released and is available here. No changes since RC1.

Summary of Changes:

• Added MSFS 2024 SU1 Beta 1 (1.3.7.0) Compatibility to the app
• Various minor bug fixes and improvements.

Detailed Changes:

• Added MSFS 2024 SU1 Beta 1 (1.3.7.0) Compatibility to the app
• Updated camera state checking to handle one new camera state introduced in the MSFS 2024 SU1 Beta 1.
• Added the github issues page URL link to the message that pops up if the memory compatibility test fails so that users can be better informed of the status of app compatibility with new MSFS versions.
• Fixed logic issue with non-expert mode where the settle timer could be triggered indefinitely when using Auto Target FPS.
• Added Force2024MSStore config file item that defaults to false for users to be able to force the app to use the MS Store MSFS 2024 version only in very rare instances where it is not being detected correctly.
• Revised GPU detection code to ignore all spaces in detected GPU name strings to resolve the issue where a leading space for the GPU name in the UserCfg.opt file would fail the detection process of an otherwise acceptable and matching GPU.
• Fixed issue where the expert panel in non-expert mode was not being hidden and contained zero values if you switched MSFS versions using the button in the app and the other MSFS version was in expert mode.
• Fixed log file showing ATLOD when FPS Cap auto mode was in use.

Edited January 29, 20251 yr by Reset XPDR

1 hour ago, Reset XPDR said:

MSFS_AutoFPS version 0.4.4.5 has now been formally released and is available here. No changes since RC1.

Summary of Changes:

• Added MSFS 2024 SU1 Beta 1 (1.3.7.0) Compatibility to the app
• Various minor bug fixes and improvements.

Detailed Changes:

• Added MSFS 2024 SU1 Beta 1 (1.3.7.0) Compatibility to the app
• Updated camera state checking to handle one new camera state introduced in the MSFS 2024 SU1 Beta 1.
• Added the github issues page URL link to the message that pops up if the memory compatibility test fails so that users can be better informed of the status of app compatibility with new MSFS versions.
• Fixed logic issue with non-expert mode where the settle timer could be triggered indefinitely when using Auto Target FPS.
• Added Force2024MSStore config file item that defaults to false for users to be able to force the app to use the MS Store MSFS 2024 version only in very rare instances where it is not being detected correctly.
• Revised GPU detection code to ignore all spaces in detected GPU name strings to resolve the issue where a leading space for the GPU name in the UserCfg.opt file would fail the detection process of an otherwise acceptable and matching GPU.
• Fixed issue where the expert panel in non-expert mode was not being hidden and contained zero values if you switched MSFS versions using the button in the app and the other MSFS version was in expert mode.
• Fixed log file showing ATLOD when FPS Cap auto mode was in use.

The previous post link is a 404 error and this one does not contain the file link...

It does however appear here top of page:

https://github.com/ResetXPDR/MSFS_AutoFPS/releases/

Edited January 29, 20251 yr by Flyfaster_MTN002

6 minutes ago, Flyfaster_MTN002 said:

The previous post link is a 404 error and this one does not contain the file link...

It does however appear here top of page:

https://github.com/ResetXPDR/MSFS_AutoFPS/releases/

Fixed

anyone else having issues with the app working with DLSS4?

3 hours ago, Shrek1970 said:

anyone else having issues with the app working with DLSS4?

DLSS 4 has nothing to do with how this app interacts with MSFS. What issue are you having?

Good news today is that for the first time in MSFS 2024 update history, AutoFPS survived the SU1 Beta 2 update process and found the new memory offset all by its little self. Gotta celebrate the small things! 😁

Edited February 1, 20251 yr by Reset XPDR

Congrats! @Reset XPDR, you deserve it!

The app cannot check Vram usage;  GPU-Z don't recognize my rtx 5080 

Edited February 1, 20251 yr by LIML2020

4 minutes ago, LIML2020 said:

The app cannot check Vram usage;  GPU-Z don't recognize my rtx 5080 

Sorry but you'll just have to wait for a GPU-Z version to come out that detects 5000 series GPUs.

On 1/26/2025 at 8:25 PM, Reset XPDR said:

I just saw his post, which is a shame but family should come first.  While I have been working a lot on my app lately, the vast majority of that work has been maintaining and improving what was already there.

I've only added three features that you could call new since the original MSFS2020_Auto FPS version 0.4.3.1, namely the Check for Updates option to slightly modify the update checking the app already did,  VRAM+ because MSFS 2024 was desperately crying out for it in its current state and the foundation for it was already in the code, and FPS Cap, which is not actually new at all as it is just a specific config of the existing Auto TLOD mode.

Regarding the VR code you speak of, I have looked at the code up on github and it too is a specific case of Auto TLOD like FPS Cap, but with the ability for TLOD Min to go lower by half if required to maintain the FPS target. From my assessment, this is not really any different than using FPS Cap in my app but setting your TLOD Base yourself to just half of what you would have set in his app then let TLOD Base + do the rest.

As such, I am not really sure what you would want me to incorporate. What is it that you are looking for that my AutoFPS cannot already be configured to achieve in a very similar manner?

Hi,  

I wanted to explain some changes I made to improve performance, particularly for VR mode.  

 

1. **Average FPS Calculation Time**:  

   I reduced the average FPS calculation time from 5 seconds to 1 second. This makes the app more responsive to changes, and I observed a significant improvement in performance. This adjustment was initially tested in Flight Sim 2020 before the 2024 release, and it had a very positive impact.  

 

2. **Dynamic TLOD Adjustment Based on FPS Drops**:  

   I modified the FPS mode, which originally relied on altitude, to include logic that monitors FPS drops. If a drop is detected, the app dynamically lowers the TLOD. This makes the system more adaptive compared to the static altitude-based approach.  

 

3. **TLOD Adjustment Based on Aircraft Performance**:  

   I added functionality to adjust the minimum and maximum TLOD values based on the aircraft’s performance. Since performance varies significantly between different planes, this change ensures better optimization for each aircraft type.  

 

4. **Half of Minimum TLOD for Performance Stability**:  

   The "half of the minimum TLOD" setting works as follows: if there are no FPS drops, the TLOD remains at the user-set level. However, if FPS drops occur, the app is allowed to reduce the TLOD to half of the set value. This helps maintain performance stability, especially for users who may have set their TLOD too high initially.  

 

5. **Ground-Level TLOD Adjustment**:  

   I enabled the reduction to half of the TLOD to occur on the ground. This improves performance at complex airports and with complex planes, where ground-level visibility is limited and high TLOD values are unnecessary.  

 

These were my changes to enhance performance and responsiveness, particularly in demanding scenarios like VR mode or complex environments.