1 hour ago, ConairMSFS said:

Looks like it's working, just loaded fbw a380 at eddf in 2024, later will try better during a flight.

fsautofps+gpuz:

Heere is log file:

https://jumpshare.com/s/YamEKPfDSAruUpWpfuuq

https://ibb.co/nDN29Mb

 

That looks correct now. Thanks for the feedback.

1 hour ago, TVOpium said:

Add the command into *.config

Nevermind, your message with your log file supercedes what I had responded with here. We'll deal with it in messages.

Edited December 31, 20241 yr by Reset XPDR

New test version 20 here https://github.com/ResetXPDR/MSFS_AutoFPS/releases/tag/v0.4.4.2-test fixing an issue found by @TVOpiumwhere TLOD could go above TLOD Min on ground when recovering from VRAM limiting. Also log file updates adding  new VRAM usage, limit events and associated settings.

I am hoping after this test release we are pretty much done with 0.4.4.2 scope. I'm sure you'll tell me if something is broken, otherwise I will release 0.4.4.2 in a day or so.

That'll do me for this year (50 mins to midnight here in Australia). Thanks everyone for your support and feedback over the year that has shaped this app to where it is today. Happy New Year to everyone!

I was just going to mention that test19 seems to be working in every way. I didn’t try to simulate any crazy VRAM overflow situations though 🙂

Happy new year - and thanks for getting AutoFPS to work in 2024 @Reset XPDR! 🎆🎇

52 minutes ago, Reset XPDR said:

New test version 20 here https://github.com/ResetXPDR/MSFS_AutoFPS/releases/tag/v0.4.4.2-test fixing an issue found by @TVOpiumwhere TLOD could go above TLOD Min on ground when recovering from VRAM limiting. Also log file updates adding  new VRAM usage, limit events and associated settings.

I am hoping after this test release we are pretty much done with 0.4.4.2 scope. I'm sure you'll tell me if something is broken, otherwise I will release 0.4.4.2 in a day or so.

That'll do me for this year (50 mins to midnight here in Australia). Thanks everyone for your support and feedback over the year that has shaped this app to where it is today. Happy New Year to everyone!

Whichever version you released, they all work just fine. Thank you for your contributions. Happy new year!

Edited December 31, 20241 yr by History

Hi, I've just downloaded and installed V 4.4.1, but when I run it I get the message MSFS_AutoFPS.exe - Bad Image:

Any ideas?

2 hours ago, Peter W said:

Hi, I've just downloaded and installed V 4.4.1, but when I run it I get the message MSFS_AutoFPS.exe - Bad Image:

Any ideas?

It looks like you have a corrupt .NET 7 install. Try downloading https://download.visualstudio.microsoft.com/download/pr/08bbfe8f-812d-479f-803b-23ea0bffce47/c320e4b037f3e92ab7ea92c3d7ea3ca1/windowsdesktop-runtime-7.0.20-win-x64.exe and select the Repair option then reboot. If that doesn't work try again but Uninstall this time, reboot, Install then reboot.

12 hours ago, Reset XPDR said:

I am hoping after this test release we are pretty much done with 0.4.4.2 scope. I'm sure you'll tell me if something is broken, otherwise I will release 0.4.4.2 in a day or so.

 

I recognize that the most recent development incorporates GPU-Z as a feeder so to speak to support an enhancement.  But I for one do not believe that enhancement is beneficial to me.  I have some difficulties with GPU-Z not loading properly to the Windows task area, which stalls my startups until I respond.  It is not something I believe I need.  Rather than two versions floating around, one with GPU-z assisting, and one that does not utilize GPU-z, are you able to find a method to provide that utilization as a selectable option in AutoFPS?

24 minutes ago, fppilot said:

I recognize that the most recent development incorporates GPU-Z as a feeder so to speak to support an enhancement.  But I for one do not believe that enhancement is beneficial to me.  I have some difficulties with GPU-Z not loading properly to the Windows task area, which stalls my startups until I respond.  It is not something I believe I need.  Rather than two versions floating around, one with GPU-z assisting, and one that does not utilize GPU-z, are you able to find a method to provide that utilization as a selectable option in AutoFPS?

There will only be one version of AutoFPS. If it detects you are running gpu-z it will give you automatic VRAM overflow protection, hereafter called VRAM+. If you choose not to run gpu-z then the app will work as normal without this new feature being active. The only thing you will have to put up with if you don't run gpu-z is a 20 second long reminder on the status screen when starting a flight suggesting you start gpu-z for VRAM+, which you can completely ignore if you want.

Edited January 1, 20251 yr by Reset XPDR

RC1, which is basically just a bit of spit and polish on test 20, is now up here https://github.com/ResetXPDR/MSFS_AutoFPS/releases/tag/v0.4.4.2-test

Nearly there!

Edited January 1, 20251 yr by Reset XPDR

45 minutes ago, fppilot said:

I recognize that the most recent development incorporates GPU-Z as a feeder so to speak to support an enhancement.  But I for one do not believe that enhancement is beneficial to me.  I have some difficulties with GPU-Z not loading properly to the Windows task area, which stalls my startups until I respond.  It is not something I believe I need.  Rather than two versions floating around, one with GPU-z assisting, and one that does not utilize GPU-z, are you able to find a method to provide that utilization as a selectable option in AutoFPS?

You don't need to use GPU-Z, AutoFPS works 100% fine without it. 

35 minutes ago, Reset XPDR said:

RC1, which is basically just a bit of spit and polish on test 20, is now up here https://github.com/ResetXPDR/MSFS_AutoFPS/releases/tag/v0.4.4.2-test

Nearly there!

Quote

Added TestMode setting in config file which, when set to true, will enable test version like logging in release versions for diagnostic purposes.

Could you explain a bit more about what this does? I guess this does not enable the log file, as that is present, even though TestMode is disabled. 

Edited January 1, 20251 yr by Cpt_Piett

Also, I quit the app and then restarted in the middle of a flight. Now I'm getting the compatibility test failed. I didn't change any settings in the sim in between closing and restarting the app. 

I'm familiar with this: 

Quote

Important Note - The new compatibility test uses a snapshot of your MSFS settings when MSFS starts to compare when it searches through memory. If you start MSFS and then make changes to MSFS settings and then start this app, it may fail this compatibility test. If you do accidentally perform this forbidden sequence and get a compatibility test failure, just restart MSFS and start this app BEFORE you make any changes to MSFS settings.

 

Just now, Cpt_Piett said:

Could you explain a bit more about what this does?

I use a flag to enable extra logging in the test versions (eg. the full memory test with MSFS 2024, even if it passes the initial test), which gets disabled when I put out a release version. If a user then has an issue with the release version, sometimes I don't have enough information in the log file to help them, so this new TestMode config file setting allows me to get them to enable full logging until I can work out what is going on. You can enable it at anytime yourself if you want but it will mean your log file gets cluttered up with diagnostic information.

28 minutes ago, Cpt_Piett said:

Also, I quit the app and then restarted in the middle of a flight. Now I'm getting the compatibility test failed. I didn't change any settings in the sim in between closing and restarting the app. 

I'm familiar with this: 

 

Well first of all, try not to quit the app in the middle of the flight as you are asking for trouble 😄

If you do restart the app while in a flight and experience this, you can just quit the app, go in to the MSFS settings menu, toggle a setting like vsync, save setttings and go back to your flight then run the app again and it should pass. This process resets your UserCfg.opt file to the current sim setting state, which the app needs find a match with when it runs the compatibility test.

Edit: I realise that you probably restarted the app mid flight because I came out with yet another version while you were mid-flight, so I'm probably to blame for you doing that.

Nonetheless I will make it clear in the readme that the preferred starting sequence is this app then MSFS or at the very least MSFS then this app via autostart or manually before MSFS gets to the main menu, then leave the app running until you have finished with MSFS.

Edited January 1, 20251 yr by Reset XPDR