On 4/10/2025 at 12:30 AM, Reset XPDR said:

Try this from the readme:

• If after installing and running the app your simconnect always stays red, your TLOD and OLOD values show as zero or you see "Critical Exception occurred: MSFS_AutoFPS - Unable to load DLL 'GpuzShMem.x64.dll' or one of its dependencies" in the log file:
  • Try downloading and installing/repairing a Microsoft official version of “Microsoft Visual C++ 2015 - 2022 Redistributable”, which may be missing from your Windows installation. Try installing this and this.
  • Try downloading and installing/repairing the NET desktop runtime from here and here.
  • If still not resolved and the error code in your AutoFPS log file is Exception 31, you most likely have a corrupt MSFS installation so you can choose to either not run this app or to reinstall MSFS completely.
  • If reinstalling MSFS 2024, you need to do a clean install, as outlined for your MSFS version here, which only takes around 15 minutes to complete and all your settings, controller assignments, career progression and your pilot profile are retained.

 

Hi there, Ive been carrying out tests to narrow down what is triggering my settings to all get reset to low, or off, after a SU2 beta GPU exceeded usage warning.  I dont use nVidia App, nor have it installed, dont have dynamic setting enabled in the sim.  Only thing is AutoFPS, latest test version.  Reduce settings options all disabled yet each time I run it and get the pop up, AutoFPS is dropping my settings.  Settings do not change if AutoFPS not running. Other thread below

 

8 minutes ago, cj-ibbotson said:

Hi there, Ive been carrying out tests to narrow down what is triggering my settings to all get reset to low, or off, after a SU2 beta GPU exceeded usage warning.  I dont use nVidia App, nor have it installed, dont have dynamic setting enabled in the sim.  Only thing is AutoFPS, latest test version.  Reduce settings options all disabled yet each time I run it and get the pop up, AutoFPS is dropping my settings.  Settings do not change if AutoFPS not running. Other thread below

 

If you are running AutoFPS 0.4.4.8-test/RC with GPU-Z in the background then settings reduction will kick in when VRAM use exceeds 98%. This is regardless of whether you have enabled settings reduction or not, as VRAM protection takes priority when your VRAM use is this high. MSFS is warning you this is happening and AutoFPS is doing something about it, which IMO is a good thing.

If you still want to run AutoFPS and NOT have VRAM protection, simply don't have GPU-Z running at the same time, but the side effect is that you will likely eventually overflow VRAM completely which will result in a massive FPS drop as VRAM overflows into system memory and potentially an MSFS CTD as your system struggles to deal with this.

If you are only getting VRAM overflow occurring when AutoFPS is running, then it is most likely because your TLODs are getting much higher than the default MSFS setting you have. The simple solution to this is to lower your TLOD Max/Top until this stops happening.

Finally, if you are getting VRAM overflow occurring regardless of whether AutoFPS is running then, as MS/Asobo would also suggest, your MSFS graphics settings are too high for your GPU's VRAM capacity and you need to turn them down. Another thing users with limited VRAM GPUs are finding helpful in low VRAM situations it to turn off Resizable Bar in their BIOS and to not have browsers running with multiple tabs open when using MSFS as both seem to eat VRAM.

26 minutes ago, Reset XPDR said:

If you are running AutoFPS 0.4.4.8-test/RC with GPU-Z in the background then settings reduction will kick in when VRAM use exceeds 98%. This is regardless of whether you have enabled settings reduction or not, as VRAM protection takes priority when your VRAM use is this high. MSFS is warning you this is happening and AutoFPS is doing something about it, which IMO is a good thing.

If you still want to run AutoFPS and NOT have VRAM protection, simply don't have GPU-Z running at the same time, but the side effect is that you will likely eventually overflow VRAM completely which will result in a massive FPS drop as VRAM overflows into system memory and potentially an MSFS CTD as your system struggles to deal with this.

If you are only getting VRAM overflow occurring when AutoFPS is running, then it is most likely because your TLODs are getting much higher than the default MSFS setting you have. The simple solution to this is to lower your TLOD Max/Top until this stops happening.

Finally, if you are getting VRAM overflow occurring regardless of whether AutoFPS is running then, as MS/Asobo would also suggest, your MSFS graphics settings are too high for your GPU's VRAM capacity and you need to turn them down. Another thing users with limited VRAM GPUs are finding helpful in low VRAM situations it to turn off Resizable Bar in their BIOS and to not have browsers running with multiple tabs open when using MSFS as both seem to eat VRAM.

Ok thanks for clarifying.  Problem is performance is not dropping and settings are already on medium for the Fenix, incl texture quality.  Running 4K but DLSS Quality. The gpu usage is briefly spiking as the flight loads into an airport and the pop up error appears before I even press Fly Now - settings then drop. One in the sim I am getting 60 fps. Even if FPS doesnt drop on the ground my TLOD drops to 25 quite often yet 50 is set in the options. I did rerun the installer to reset the settings, restarted the pc but it still radically dropped the settings when AutoFPS was running. Wonder why there is a tick box if it is always enabled.  GPU-Z is running on system start for the older cloud quality monitoring.  I guess the app is starting to confuse me with all the increased settings. I will need to play around with it.  Is OLED reduction no longer an option as I do not see it? Its a great app, just thrown the past few days at things changing despite the settings.  Didnt know until this evening if it was SU2 Beta causing it or elsewhere.  Also appears the latest ReShade is triggering menu freezes when you go to options or end a flight.  Been getting CTD when doing this and using the Fenix.  Tests with Reshade removed appear to help.  CTD been causing me headaches since the very latest SU2 Beta.  Will test your app tomorrow evening as its late.  Keep up the good work 😀

7 minutes ago, cj-ibbotson said:

Ok thanks for clarifying.  Problem is performance is not dropping and settings are already on medium for the Fenix, incl texture quality.  Running 4K but DLSS Quality. The gpu usage is briefly spiking as the flight loads into an airport and the pop up error appears before I even press Fly Now - settings then drop. One in the sim I am getting 60 fps. Even if FPS doesnt drop on the ground my TLOD drops to 25 quite often yet 50 is set in the options. I did rerun the installer to reset the settings, restarted the pc but it still radically dropped the settings when AutoFPS was running. Wonder why there is a tick box if it is always enabled.  GPU-Z is running on system start for the older cloud quality monitoring.  I guess the app is starting to confuse me with all the increased settings. I will need to play around with it.  Is OLED reduction no longer an option as I do not see it? Its a great app, just thrown the past few days at things changing despite the settings.  Didnt know until this evening if it was SU2 Beta causing it or elsewhere.  Also appears the latest ReShade is triggering menu freezes when you go to options or end a flight.  Been getting CTD when doing this and using the Fenix.  Tests with Reshade removed appear to help.  CTD been causing me headaches since the very latest SU2 Beta.  Will test your app tomorrow evening as its late.  Keep up the good work 😀

Before you retire for the evening, can you message me your log file so I can see what is happening when you load into a flight. It is located in %appdata%\MSFS_AutoFPS\log

Quote

Wonder why there is a tick box if it is always enabled. 

It is always enabled for VRAM protection, which should be an extremely rare event, but is optional for normal use and even then should only activate rarely, hence why there is a checkbox.

Quote

I guess the app is starting to confuse me with all the increased settings.

To be fair, you have installed a test version that does have a lot of changes and the documentation is currently being finalised, so you should expect things to be a little incomplete. The release notes that pop up every auto update do cover every change that has been made, including guidance on how to use them in the test phase, so I suggest you read that.

Quote

Is OLOD reduction no longer an option as I do not see it?

It has been subsumed into the settings reduction feature, as described in the release notes.

If you want a quick workaround, just go back to running the 0.4.4.7 release version, which doesn't have mandatory settings reduction on VRAM overflow except for TLOD, or use 0.4.4.8-RC and just don't run GPU-Z in the background for now.

0.4.4.8 should be formally released in the next few days, probably just after the next SU2 beta drops in case that breaks something. When that occurs, the readme will have been fully updated with the new changes.

Given your experience, if I can't find a workable solution from what I see in your log file if it is only a temporary VRAM overflow, I will add a config line that will allow you to disable VRAM protection completely. As I said in your other thread, that is the functional equivalent of removing seat belts from a car because they are uncomfortable, but I will do so if that is what you really want.

Edited April 13, 20251 yr by Reset XPDR

@cj-ibbotson, I decided to add the ability to disable VRAM+ to the UI. I was going to put it in the config file only which the user would be required to edit, but that's a bit much to expect, especially if the user is non-expert. You can get it in 0.4.4.8-RC2 or later, available here. If you uncheck Auto Reduce Settings and VRAM+ then no settings will be reduced below what you have otherwise set with this app or are set by default by MSFS.

Here's what it looks like enabled (with tooltip showing):

and disabled:

2 minutes ago, Reset XPDR said:

@cj-ibbotson, I decided to add the ability to disable VRAM+ to the UI. I was going to put it in the config file only which the user would be required to edit, but that's a bit much to expect, especially if the user is non-expert. You can get it in 0.4.4.8-RC2 or later, available here. If you uncheck Auto Reduce Settings and VRAM+ then no settings will be reduced below what you have otherwise set with this app or are set by default by MSFS.

Here's what it looks like enabled (with tooltip showing):

and disabled:

Thanks and apologies I went to bed and only seeing your reply this morning.  Just did a quick test on RC1 and got the gpu exceeded message as soon as the Fenix loads into default LEBB, settings then dropped.  I dont know how to attach a log file, I clicked message on your profile but only see link options rather than attaching files. Do I need to use say WeTransfer?  Getting sorted for work so will try to sort if you still need it 

1 hour ago, cj-ibbotson said:

Thanks and apologies I went to bed and only seeing your reply this morning.  Just did a quick test on RC1 and got the gpu exceeded message as soon as the Fenix loads into default LEBB, settings then dropped.  I dont know how to attach a log file, I clicked message on your profile but only see link options rather than attaching files. Do I need to use say WeTransfer?  Getting sorted for work so will try to sort if you still need it 

We must have been composing at the same time as I just put up a post before yours showing I've released 0.4.4.8-RC2 gives you the ability to turn off VRAM+ via the UI.

I'm still interested in seeing the log file as I want to know if there is an issue I am not aware of. Just send a message as you were going to via my profile and copy paste the contents of the log file into the message. I can reconstruct at my end.

Edit: What I suspect is happening is that the temporal spike is causing the settings to immediately reduce. The app is currently configured to use the raw VRAM usage reading from GPU-Z each second, whereas it should probably should average it over a few seconds or at the very least discard readings that are significantly different to the previous second's reading, to filter out such spikes. Your log file may reveal more, but as it only records every 10 seconds that you are actually moving it may lack the granularity I need to see. Regardless, I will come up with something to address it.

Edit2: For the interest of those following the investigation of this issue, the log file revealed it was not a single VRAM use spike rather it was a long-term VRAM overflow lasting over 20 seconds and another that grew a few minutes later that the app responded to appropriately, strongly suggesting the issue lays with how either the departure airport textures or the Fenix A320 are interacting with the latest SU2 beta version. Nonetheless, I will be modifying AutoFPS to only act on two consecutive overflow readings to minimise the chance of false triggering from a one-off spike or erroneous reading.

 

Edited April 14, 20251 yr by Reset XPDR

1 hour ago, Reset XPDR said:

We must have been composing at the same time as I just put up a post before yours showing I've released 0.4.4.8-RC2 gives you the ability to turn off VRAM+ via the UI.

I'm still interested in seeing the log file as I want to know if there is an issue I am not aware of. Just send a message as you were going to via my profile and copy paste the contents of the log file into the message. I can reconstruct at my end.

Edit: What I suspect is happening is that the temporal spike is causing the settings to immediately reduce. The app is currently configured to use the raw VRAM usage reading from GPU-Z each second, whereas it should probably should average it over a few seconds or at the very least discard readings that are significantly different to the previous second's reading, to filter out such spikes. Your log file may reveal more, but as it only records every 10 seconds that you are actually moving it may lack the granularity I need to see. Regardless, I will come up with something to address it.

Edit2: For the interest of those following the investigation of this issue, the log file revealed it was not a single VRAM use spike rather it was a long-term VRAM overflow lasting over 20 seconds and another that grew a few minutes later that the app responded to appropriately, strongly suggesting the issue lays with how either the departure airport textures or the Fenix A320 are interacting with the latest SU2 beta version. Nonetheless, I will be modifying AutoFPS to only act on two consecutive overflow readings to minimise the chance of false triggering from a one-off spike or erroneous reading.

 

From memory the latest update to the Fenix to allow it to work in SU2 Beta had a changelog note about textures and some some of hack to allow it to work.  Perhaps linked.

I will try to find it later.  No current support from Fenix on 2024

Last call for any notable issues of existing scope to be fixed before 0.4.4.8 goes live for formal release as planned for this time tomorrow. If it's anything major or extends beyond one or two posts here, please raise it over on my github discussion page for this release here.

If you want a taste-test right now, the current final release candidate version is available here. The readme has also been updated in ancipation of this release. If you have auto updates enabled, the app will auto update to the formal release version when it drops.

Summary of Changes Outline:

• Performance Optimisation:
  • Automatic settings reduction for MSFS 2024 improves FPS and lowers VRAM usage.
  • Auto cloud quality adjustments based on performance margins.
  • Enhanced FG detection for real-time updates and MSFS 2024 SU2.
• TLOD & VRAM Enhancements:
  • Streamlined TLOD Min + adjustments for faster performance recovery.
  • Refined TLOD Base + logic to prevent unnecessary resets and improve scaling.
  • VRAM protection now triggers auto settings reduction with configurable thresholds.
• User Control & UI Updates:
  • Target FPS selection expanded with dropdown UI indicators.
  • Memory management optimized for faster MSFS 2024 offset detection.
  • Expanded settings visibility with trend indicators for TLOD and reductions.
• Installer & System Updates:
  • "Install Latest Redistributables" option added for Visual C++ and .NET 8 updates.
  •  New FSUIPC7 registry keys for autostart handling.
  • Improved logging, new command-line options, and upgrade to .NET 8.

 

After 41 test and 11 RC releases 😮 , 0.4.4.8 has finally been formally released and is available for download here. Thank you so much to everyone who participated in the test phase and particularly to those who provided regular feedback on progressive changes, which helped shape final product. I am very pleased with what we have achieved together!

Summary of Changes Outline:

• Performance Optimisation:

  • Automatic settings reduction for MSFS 2024 improves FPS and lowers VRAM usage.
  • Auto cloud quality adjustments based on performance margins.
  • Enhanced FG detection for real-time updates and MSFS 2024 SU2.

• TLOD & VRAM Enhancements:

  • Streamlined TLOD Min + adjustments for faster performance recovery.
  • Refined TLOD Base + logic to prevent unnecessary resets and improve scaling.
  • VRAM protection now triggers auto settings reduction with configurable thresholds.

• User Control & UI Updates:

  • Target FPS selection expanded with dropdown UI indicators.
  • Memory management optimized for faster MSFS 2024 offset detection.
  • Expanded settings visibility with trend indicators for LOD and reductions.
  • Sim rate indication and -vfr and -ifr command line options.
  • UserCfg.opt backup before & restoration after flight sessions.

• Installer & System Updates:

  • "Install Latest Redistributables" option added for Visual C++ and .NET 8 updates.
  • New FSUIPC7 registry keys for autostart handling.
  • Improved logging and upgrade to .NET 8.

 

Edited April 19, 20251 yr by Reset XPDR

2 minutes ago, Reset XPDR said:

After 41 test and 11 RC releases 😮 , 0.4.4.8 has finally been formally released and is available for download here. Thank you so much to everyone who participated in the test phase and particularly to those who provided regular feedback on progressive changes, which helped shape final product. I am very pleased with what we have achieved together!

### Summary of Changes Outline:
- **Performance Optimisation**:
  - Automatic settings reduction for MSFS 2024 improves FPS and lowers VRAM usage.
  - Auto cloud quality adjustments based on performance margins.
  - Enhanced FG detection for real-time updates and MSFS 2024 SU2.

- **TLOD & VRAM Enhancements**:
  - Streamlined TLOD Min + adjustments for faster performance recovery.
  - Refined TLOD Base + logic to prevent unnecessary resets and improve scaling.
  - VRAM protection now triggers auto settings reduction with configurable thresholds.

- **User Control & UI Updates**:
  - Target FPS selection expanded with dropdown UI indicators.
  - Memory management optimized for faster MSFS 2024 offset detection.
  - Expanded settings visibility with trend indicators for LOD and reductions.
  - Sim rate indication and -vfr and -ifr command line options.
  - UserCfg.opt backup before & restoration after flight sessions.

- **Installer & System Updates**:
  - "Install Latest Redistributables" option added for Visual C++ and .NET 8 updates.
  - New FSUIPC7 registry keys for autostart handling.
  - Improved logging and upgrade to .NET 8.

 

This is great, thank you. Looking forward to testing. I've had an issue with 4x frame gen and Gsync and Vsync. My FPS are capped at 138 (144hz refresh rate) and the TLOD will not go above 205...I can't figure out why.

16 minutes ago, V1ROTA7E said:

This is great, thank you. Looking forward to testing. I've had an issue with 4x frame gen and Gsync and Vsync. My FPS are capped at 138 (144hz refresh rate) and the TLOD will not go above 205...I can't figure out why.

Message me the contents of your associated log, located in %appdata%\MSFS_AutoFPS\log, and I should be able to you why.

Thank you for your fine work on this project. I have discovered that I need to pay more attention to the documentation and solutions to my issues are there, too.

57 minutes ago, mrbill38119 said:

Thank you for your fine work on this project. I have discovered that I need to pay more attention to the documentation and solutions to my issues are there, too.

You are welcome! 

Yes that is usually the case with issues, but admittedly the readme has grown somewhat large since I started making this app. Still, it is far quicker and more efficient for a user to skim/search the readme for how to use a particular feature, or resolve a particular issue, than to put a post together and have me just point them directly there anyway. In the now rare case that I haven't covered an issue or otherwise haven't been clear in the readme, I update it straight away for it to do so, which is probably how it got so large in the first place. 😄

Edited April 19, 20251 yr by Reset XPDR

Why are my OLOD staying at 50 regardless of the current FPS or VRAM usage?