I guess the profile part is the part i missed 

43 minutes ago, Reset XPDR said:

The readme does say under the Expert Settings option 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:

....

• Otherwise, FPS Senstivity will be used with the following settings:

ie. It will try and see if an FPS cap is present that matches the target FPS you have set and will then use FPS Cap mode, otherwise it will default to FPS Sensitivity mode like it always has. You do not need to go to Expert mode at all.

Thanks for the clarification. For me as non-native-english-speaker obviously using "FPS cap" and "FPS Cap" for two different issues was a little bit confusing 🙃.

 

32 minutes ago, ohny said:

Thanks for the clarification. For me as non-native-english-speaker obviously using "FPS cap" and "FPS Cap" for two different issues was a little bit confusing 🙃.

 

Fair point. When I use a capital C for Cap I am referring to the TLOD automation mode whereas with lower case c I am talking about an actual FPS cap. I will reword the readme to make it clearer.

Edit: Revised wording in the readme is as follows:

• Use Expert Options
  • Non-Expert Mode (unchecked and default)
    • Allows the app to use default settings in conjunction with your chosen target FPS that should produce good automated FPS tracking, provided you have set reasonable MSFS TLOD, OLOD and Cloud settings and a realistic FPS target within your system's performance capability.
    • The app will first attempt to automatically detect if an FPS cap is use by checking to see if the FPS matches the target FPS over a 10 second period at the end of the initial 20 second settling period.
    • If an FPS cap is detected, the FPS Cap TLOD automation method will be used 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
    • Otherwise, FPS Sensitivity will be used with the following settings:

...

Please let me know if this is now clear enough.

Edited January 19, 20251 yr by Reset XPDR

28 minutes ago, flieger28 said:

I guess the profile part is the part i missed 

I will make it clearer in the readme.

Ah this has got so confusing for my little lawyer brain ha.

Edited January 19, 20251 yr by abennett

1 hour ago, abennett said:

Ah this has got so confusing for my little lawyer brain ha.

If you are referring about the description for non-expert mode, I expect most non-expert users wouldn't even read it and will be happy with what the app does automatically. The description I provide here is really for those who are just a little more curious, even if they only read up to the point where I start outlining what the specific settings are.

7 hours ago, Reset XPDR said:

Please let me know if this is now clear enough.

It's clear. 

8 hours ago, Reset XPDR said:

Fair point. When I use a capital C for Cap I am referring to the TLOD automation mode whereas with lower case c I am talking about an actual FPS cap. I will reword the readme to make it clearer.

Edit: Revised wording in the readme is as follows:

• Use Expert Options
  • Non-Expert Mode (unchecked and default)
    • Allows the app to use default settings in conjunction with your chosen target FPS that should produce good automated FPS tracking, provided you have set reasonable MSFS TLOD, OLOD and Cloud settings and a realistic FPS target within your system's performance capability.
    • The app will first attempt to automatically detect if an FPS cap is use by checking to see if the FPS matches the target FPS over a 10 second period at the end of the initial 20 second settling period.
    • If an FPS cap is detected, the FPS Cap TLOD automation method will be used 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
    • Otherwise, FPS Sensitivity will be used with the following settings:

...

Please let me know if this is now clear enough.

Thank you for clarification. Now it is clear even for an almost 80 years old user like me!

Reading the README, I noticed that the threshold for VRAM can be adjusted (which is set to 96 and 98% by default). I’d like to modify it to be a bit more conservative (92 and 95%) because sometimes my 8 GB struggles in the area where I fly (in the PNW, as I mentioned before). I’ve been looking for the file (MSFS2024_AutoFPS.config) to make this change, but I haven’t found the parameters. How can I do it? I'm referring to this part:

Quote

Uses two thresholds for VRAM usage, both changeable in the app root directory config file after running the app once after updating

Don’t you think it would be interesting to include these two parameters in the Expert mode? I suspect that the VRAM issue for 8 GB graphics cards is going to stick around for a while, and I think it would be useful to have the option to adjust it based on the area or type of flight.

32 minutes ago, Maddormo said:

Reading the README, I noticed that the threshold for VRAM can be adjusted (which is set to 96 and 98% by default). I’d like to modify it to be a bit more conservative (92 and 95%) because sometimes my 8 GB struggles in the area where I fly (in the PNW, as I mentioned before). I’ve been looking for the file (MSFS2024_AutoFPS.config) to make this change, but I haven’t found the parameters. How can I do it? I'm referring to this part:

Look for and change accordingly:

  <add key="VRAMOverflowHoldTLOD" value="96" />
  <add key="VRAMOverflowReduceTLOD" value="98" />

And make sure it is in the config files found in the root, not bin, directory.

35 minutes ago, Maddormo said:

Don’t you think it would be interesting to include these two parameters in the Expert mode? I suspect that the VRAM issue for 8 GB graphics cards is going to stick around for a while, and I think it would be useful to have the option to adjust it based on the area or type of flight.

No I don't. Firstly, I don't want to add anything more to the already plentiful set of controls on the UI unless it is really necessary, and this is not for the majority of users. Secondly, I don't really want users playing with these settings unless they know what they are doing. 

If I get a lot of requests to change this value for lower VRAM GPUs I will consider automatically changing the thresholds lower, but you are the first one. I'd first like to hear back from you whether the lower values are more suitable before I go down that path, so please let me know.

31 minutes ago, Reset XPDR said:

And make sure it is in the config files found in the root, not bin, directory.

Sorry, I was checking the bin folder. I’ve found the right one now.

33 minutes ago, Reset XPDR said:

I'd first like to hear back from you whether the lower values are more suitable before I go down that path, so please let me know.

No problem, I understand this is a request for a very specific case. That said, I’ll share my impressions about this more conservative setup. I’m going to test around Packwood (55s), which is in the ulta high mesh of Mount Rainier. It’s pretty easy to fill the VRAM with a simple plane, and sometimes it can easily go from 96 to 99, so I want to limit it a bit more.

MSFS_AutoFPS version 0.4.4.4 has just been formally released and is available to download here. Thanks to those who identified and clarified the issues for me to resolve.

Summary of Changes:

• This minor maintenance release addresses three key issues:
  • Fixed the Auto OLOD function in non-expert mode that was not working in version 0.4.4.3.
  • Resolved a rare but significant issue with TLOD Min + that could cause TLOD Min to be locked too high.
  • Fixed the target FPS checkbox not always showing when it should when FPS Cap was in use.
• Additionally, it includes a few other bug fixes and enhancements for overall robustness.

Edited January 21, 20251 yr by Reset XPDR

Huge thanks ❤️

13 hours ago, Reset XPDR said:

I'd first like to hear back from you whether the lower values are more suitable before I go down that path, so please let me know.

Like I promised, I was testing those two values (92 and 95%) last night, and for a highly detailed scenario, I found that with my 8GB of VRAM, the results were way better. At no point did I see the app trigger the alarm by dropping the TLOD to 20 due to VRAM overload. I noticed it was fighting with the TLOD values while trying to maintain the frames, but I didn’t see a massive drop in detail like I did with the previous settings. But, to be fair, we’re talking about a pretty specific situation, and maybe most people won’t need these kinds of tweaks.

But I encourage anyone visiting very complex airports, using study-level planes, or flying in highly detailed scenarios (like photogrammetry or digitized national parks) to check if the app often drops to TLOD20. If that’s the case, they should try these other thresholds. This way, everything will be more controlled without having to take drastic measures by dropping all the way down to 20.

If you want to give it a shot, I recommend Packwood (55s). Head north, climb to 5000', and do a few 360s. You'll see the VRAM go up like a rocket.

Are there recommended settings or a guide that describes how to set up Auto FPS?  I have mine working but it always sets the TLOD to 30 in the sim and It makes it look awful