I seem to have gotten myself in a bit of problem with AutoFPS and wonder if this is the right place to ask for help.

AutoFPS has been working well on my FS2020 sim, and I have enjoyed it greatly. I'm a user who hates tweaking and so just avoid the expert settings completely. Everything was fine until last week at which point I decided to experiment with the Frame Generation mod. After a couple of days of messing with it, I decided it wasn't for me, and I removed the two frame gen files from the MSFS folder. That restored MSFS to its normal operation, but now AutoFPS thinks that I'm running at double the frame rate and that wreaks havoc with the values of TLOD that AutoFPS tries to use.

I looked at the log file generated by AutoFPS and see the line

2025-01-01 09:45:12.567 [DBG] [ Address Verification             ] FG Mode Value: True 

which may mean that the software still thinks that frame generation is in use. I deleted AutoFPS entirely by disposing of the corresponding folder inside of AppData, but the behavior after doing a fresh install is still the same.

I must be doing something stupid, but can't figure out what that might be. Any suggestions would be appreciated.

Many thanks and best wishes for a most successful 2025 for all.

@Reset XPDR

Just tested RC1 icw GPU-Z on my Left View client.

This pc uses a 4080 so 16 Gb VRAM. Even with the bad weather of today above the Netherlands the highest VRAM I saw was 9.77 Gb. ( 4K - high / ultra settings )

As this pc is more CPU bound than GPU bound I probably better use TLOD for cloud instead of GPU load if I am correct.

 

19 hours ago, Reset XPDR said:

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.

Many thanks, that fixed it!

2 hours ago, jrw4 said:

I seem to have gotten myself in a bit of problem with AutoFPS and wonder if this is the right place to ask for help.

AutoFPS has been working well on my FS2020 sim, and I have enjoyed it greatly. I'm a user who hates tweaking and so just avoid the expert settings completely. Everything was fine until last week at which point I decided to experiment with the Frame Generation mod. After a couple of days of messing with it, I decided it wasn't for me, and I removed the two frame gen files from the MSFS folder. That restored MSFS to its normal operation, but now AutoFPS thinks that I'm running at double the frame rate and that wreaks havoc with the values of TLOD that AutoFPS tries to use.

I looked at the log file generated by AutoFPS and see the line

2025-01-01 09:45:12.567 [DBG] [ Address Verification             ] FG Mode Value: True 

which may mean that the software still thinks that frame generation is in use. I deleted AutoFPS entirely by disposing of the corresponding folder inside of AppData, but the behavior after doing a fresh install is still the same.

I must be doing something stupid, but can't figure out what that might be. Any suggestions would be appreciated.

Many thanks and best wishes for a most successful 2025 for all.

Per the readme FAQ:

• If MSFS FG is being incorrectly reported as enabled by the app, the likely reason is that either the FG mod had been installed and removed or you have disabled Hardware Accelerated Graphics Scheduling under Windows settings and the now the now greyed out MSFS FG setting may show that it is off but it is still set to on internally to MSFS. To fix, change the DLSSG line in your UserCfg.opt file to be DLSSG 0.

UserCfg.opt for MSFS 2020 is located in either:

• MS Store %localappdata%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt 
• Steam %appdata%\Microsoft Flight Simulator\UserCfg.opt

If that doesn't fix it, message me the whole log file and I will take a closer look.

2 hours ago, GSalden said:

@Reset XPDR

Just tested RC1 icw GPU-Z on my Left View client.

This pc uses a 4080 so 16 Gb VRAM. Even with the bad weather of today above the Netherlands the highest VRAM I saw was 9.77 Gb. ( 4K - high / ultra settings )

As this pc is more CPU bound than GPU bound I probably better use TLOD for cloud instead of GPU load if I am correct.

 

Most likely yes.

18 minutes ago, Reset XPDR said:

If that doesn't fix it, message me the whole log file and I will take a closer look.

That fixed it! Many thanks both for the fine app and the quick support. Happy New Year.

 

0.4.4.2-RC2 has been released and is available here https://github.com/ResetXPDR/MSFS_AutoFPS/releases/tag/v0.4.4.2-test

Yes, I said was nearly done, but those pesky little bugs kept crawling out today while I was playing with the app, so I wanted to stomp them out.

Of significance with this update is that I have now reduced the compatibility test requirement to only have to occur once for a given MSFS/app/offset combo as testing this over and over again each time the app is started is unnecessary and can cause nuisance compatibility fails if the app is restarted in the middle of a flight, as  @Cpt_Piett experienced the other day.

The other side to that is that if any one of those three things change between app startups, including app test version updates, the compatibility test will be run again but it is only once and you shouldn't even notice it unless it fails, which is what I want it to do.

If you are curious, the only way to see that it is working is by looking in the log file.

On the initial run you will see the following example entries:
 

Quote

 

2025-01-02 10:44:11.686 [DBG] [ MemoryManager:MemoryManager      ] Running compatibility test for new MSFS/app/offset combo

2025-01-02 10:44:14.155 [DBG] [ MemoryManager:MemoryManager      ] Compatibility test pass for MSFS/app/offset combo saved to config file

 

Then on subsequent runs with the same combo you will see:

Quote

2025-01-02 10:45:09.824 [DBG] [ MemoryManager:MemoryManager      ] Compatibility test bypassed due to previous saved pass found for current MSFS/app/offset combo

 

 

 

RC2 working on Steam with GPU-Z, wow ! Man of the year is Reset XPDR !

Sorry for putting you into a retirement home. I will get you out, please wait. Loading..... 😁

Edited January 2, 20251 yr by deepstar

4 hours ago, Reset XPDR said:

0.4.4.2-RC2 has been released

I appreciate the changes - thanks! I was able to restart AutoFPS mid-flight - and the GPU-Z info is there all the time now 🙂

I'm currently testing in a GA flight - will report back if I discover anything strange. 

2 hours ago, Cpt_Piett said:

I'm currently testing in a GA flight - will report back if I discover anything strange. 

Just to say that everything seems to be working almost 100%. With the latest version and the previous one, I've flown around the European Alps in the Black Square TBM 850. From Venice, through Slovenia, Austria, Switzerland and France - back to Venice. Yes - it did take a while 😅 

I've configured AutoFPS so that I'm getting a TLOD of 200 below 1000ft, and a max of 600 above a terrain altitude of 1000ft. I've got TLOD Min Extra, auto-OLOD and auto-clouds disabled. 

I've done a lot of climbing and descending, highest altitude of 13,000ft, lots of approaches and landings. Everything has been very smooth for the whole trip. 

The only situation where the app struggles, is when flying relatively fast and low (3000ft and 200kts or so) over photogrammetry areas. The app then doesn't have enough time to reduce the TLOD to avoid stutters. Once TLOD has been reduced sufficiently, everything goes back to smooth. 

There's perhaps one more situation, which also makes sense. That's when I've done very steep descents (4000 fpm or so - I've set the average descent rate to 2000). 

But overall - the app works amazingly well and makes the whole MSFS2024 experience a lot better!

EDIT: One more thing, unrelated to AutoFPS. When changing to external view from cockpit view, FPS drops by as much as 20. 

Edited January 2, 20251 yr by Cpt_Piett

19 hours ago, GSalden said:

@Reset XPDR

Just tested RC1 icw GPU-Z on my Left View client.

This pc uses a 4080 so 16 Gb VRAM. Even with the bad weather of today above the Netherlands the highest VRAM I saw was 9.77 Gb. ( 4K - high / ultra settings )

As this pc is more CPU bound than GPU bound I probably better use TLOD for cloud instead of GPU load if I am correct.

 

I’m wondering why I seem to have a much higher VRAM-usage. Yesterday I flew over the Australian outback (it was quite cloudy) and also had about 90%-VRAM usage (of the 16Gb I have). Settings are generally on ‘high’ in 4K.

17 minutes ago, JWvdH said:

I’m wondering why I seem to have a much higher VRAM-usage. Yesterday I flew over the Australian outback (it was quite cloudy) and also had about 90%-VRAM usage (of the 16Gb I have). Settings are generally on ‘high’ in 4K.

I really don’t know. Never have I seen 80+ % GPU loads on both server (4090) and client (4080).

 

1 hour ago, GSalden said:

I really don’t know. Never have I seen 80+ % GPU loads on both server (4090) and client (4080).

You're using MSFS2020, right?

It seems VRAM usage (and RAM!) is even higher in 2024. I just took off from KSFO in the Fenix A319 then did a little sightseeing around the CBD at 3000ft. I very quickly got "VRAM LTD" in the status bar. And AutoFPS reduced TLOD accordingly. I think that feature is going to be very helpful. Even for 4090-owners with 24GB of VRAM like me. 

In the screenshot below*, I was flying northwest from Oakland (which is photogrammetry). 

*Yes it looks weird. It's because I used PRT SCRN to include AutoFPS and I've got HDR enabled. I cropped it to include the important parts. 

It can also be seen that TLOD Max Extra ("Mtns+) is active, as the terrain altitude below me within the last 5 minutes was higher than 1000ft. 

Also, I've increased target FPS from 65 to 70 in order to (hopefully) prevent a stutterfest when flying over PG-areas. With a higher FPS target, TLOD won't go as high, so hopefully there is no need for a drastic reduction when approaching a PG area. Not sure if my logic is correct here though. I could of course reduce TLOD max and disable TLOD max extra. But that's unnecessary at higher altitude where I have a lot of headroom. 

Bit of a dilemma. Suggestions are welcome 🙂

Edited January 2, 20251 yr by Cpt_Piett

I get high VRAM usage on my 4090 as well in 2024 once the TLODs go up. Think this is a great setting in autoFPS, similarly as above I’ve increased my FPS from 60 to 80 as in cruise I can normally easily maintain this with TLOD 400 and then the VRAM doesn’t overflow and I get stutter free. Will try if there’s other settings that impact it, not sure of texture resolution from ultra to high will make a big difference in either visuals and VRAM usage, potentially allowing for a higher LOD.

textures at ultra and LOD 400 still look blurry anyway compared to 2020.. 

Edited January 2, 20251 yr by AlexMD11

54 minutes ago, AlexMD11 said:

I get high VRAM usage on my 4090 as well in 2024 once the TLODs go up. Think this is a great setting in autoFPS, similarly as above I’ve increased my FPS from 60 to 80 as in cruise I can normally easily maintain this with TLOD 400 and then the VRAM doesn’t overflow and I get stutter free. Will try if there’s other settings that impact it, not sure of texture resolution from ultra to high will make a big difference in either visuals and VRAM usage, potentially allowing for a higher LOD.

textures at ultra and LOD 400 still look blurry anyway compared to 2020.. 

2024 is ridiculous in my opinion, running out of Vram with 24GB of V Ram and needing 64 GB of Ram, what's next, 128 GB Ram and 48GB Vram?  ☹️