5 minutes ago, 0stones0 said:

Found the issue:

<Descr>Launch</Descr>
<Filename>exe.xml</Filename>

The "exe" file in msfs2024 is all caps. Changed the filename above to EXE and we're good to go.

One other question. Do I still need to run GPUZ when using Dynamic setting in game?

Thanks again.

 

No, in MSFS 2024 you only need to run GPU-Z if you want VRAM+ to function. See the readme for more.

FYI to anyone using MSFS Dynamic Settings with AutoFPS and not using and FPS cap, previous Readme documents advised to set the MSFS dynamic settings target frame rate to 10 FPS higher than the native frame rate equivalent of the AutoFPS target FPS for best results.

It should in fact be the other direction, ie. lower, as you want your free ranging FPS tracking around a higher target FPS so that Dynamic Settings is not being activated around your normal FPS. In the testing I have done, if you don't set MSFS dynamic settings target frame rate at least 10 FPS lower than your target FPS, then dynamic settings may be active around your target FPS, which you don't want.

With an FPS Cap, dynamic settings behaves itself and does not activate until your FPS is below the MSFS dynamic settings target frame rate, probably because MSFS knows it has sufficient headroom when operating at the FPS cap, but it seems to be more pessimistic with free ranging FPS, activating even when you are achieving its set target frame rate. It's just the way it currently has been implemented in MSFS, so the the recommendations provided are for AutoFPS to play nicely with it.

As such, the Readme recommended setting has been updated as follows:

• If not using an FPS cap, it is recommended to set the MSFS dynamic settings target frame rate to at least 10 FPS lower than the native frame rate equivalent of the AutoFPS target FPS for best results.

 

Edited November 23, 2025Nov 23 by Reset XPDR

24 minutes ago, Reset XPDR said:

FYI to anyone using MSFS Dynamic Settings with AutoFPS and not using and FPS cap, previous Readme documents advised to set the MSFS dynamic settings target frame rate to 10 FPS higher than the native frame rate equivalent of the AutoFPS target FPS for best results.

It should in fact be the other direction, ie. lower, as you want your free ranging FPS tracking around a higher target FPS so that Dynamic Settings is not being activated around your normal FPS. In the testing I have done, if you don't set MSFS dynamic settings target frame rate at least 10 FPS lower than your target FPS, then dynamic settings may be active around your target FPS, which you don't want.

With an FPS Cap, dynamic settings behaves itself and does not activate until your FPS is below the MSFS dynamic settings target frame rate, probably because MSFS knows it has sufficient headroom when operating at the FPS cap, but it seems to be more pessimistic with free ranging FPS, activating even when you are achieving its set target frame rate. It's just the way it currently has been implemented in MSFS, so the the recommendations provided are for AutoFPS to play nicely with it.

As such, the Readme recommended setting has been updated as follows:

• If not using an FPS cap, it is recommended to set the MSFS dynamic settings target frame rate to at least 10 FPS lower than the native frame rate equivalent of the AutoFPS target FPS for best results.

 

you mean the fps cap in autofps? 

1 hour ago, Sonosusto said:

you mean the fps cap in autofps? 

FPS cap, by itself, means that you have set a system or MSFS-specific FPS cap limiting your FPS to that cap. FPS Cap in AutoFPS is a TLOD Auto Method (or mode) that works best with an aforementioned FPS cap. Specifically, FPS Cap mode in AutoFPS does not actually limit in-game FPS, it just optimises TLOD automation to work with an actual FPS cap set elsewhere.

Edited November 23, 2025Nov 23 by Reset XPDR

53 minutes ago, Reset XPDR said:

FPS cap, by itself, means that you have set a system or MSFS-specific FPS cap limiting your FPS to that cap. FPS Cap in AutoFPS is a TLOD Auto Method (or mode) that works best with and aforementioned FPS cap. Specificlaly, FPS Cap mode in AutoFPS does not actually limit in-game FPS, it just optimises TLOD automation to work with an actual FPS cap set elsewhere.

Roger that! 

I'm currently on the latest release in 2024 Beta4, and Ive just noticed that the AutoFPS GPU value doesnt seem to be correct.

I'm using 2 GPUs

•    AMD Radeon mainboard for non-MSFS output
•    Nvidia 4070Ti Super for MSFS output on 4K screen, plus 2 other screens for non MSFS output

I'm running GPU-Z v2.68.0, as well as HWInfo 64 (plus Rainmeter to draw all my perf graphs/system monitored datapoints read from HWInfo64).
I've also just moved to a new MB and updated CPU (which may or may not be part of the problem).

Previously, the AutoFPS GPU load % matched what I see in my Rainmeter realtime graph, as well as what GPU-Z reports for the NVidia card.

But since updating AutoFPS on my new MB/CPU combo, I'm now seeing AutoFPS under-report the GPU load by 18-20%.

For example, GPU-Z and Rainmeter (via HWInfo64 output) where showing GPU load of 73%, whereas at the same time Auto-FPS GPU load value was only 55%.

Could it be that GPU-Z, can track both GPUs, that perhaps AutoFPS is getting a combined GPU value (AMD Radeon plus Nvidia), as the AMD has very little load, and therefore if AutoFPS is getting an average value of the 2, it could explain the lower number.

 

 

 

47 minutes ago, c912039 said:

I'm currently on the latest release in 2024 Beta4, and Ive just noticed that the AutoFPS GPU value doesnt seem to be correct.

I'm using 2 GPUs

•    AMD Radeon mainboard for non-MSFS output
•    Nvidia 4070Ti Super for MSFS output on 4K screen, plus 2 other screens for non MSFS output

I'm running GPU-Z v2.68.0, as well as HWInfo 64 (plus Rainmeter to draw all my perf graphs/system monitored datapoints read from HWInfo64).
I've also just moved to a new MB and updated CPU (which may or may not be part of the problem).

Previously, the AutoFPS GPU load % matched what I see in my Rainmeter realtime graph, as well as what GPU-Z reports for the NVidia card.

But since updating AutoFPS on my new MB/CPU combo, I'm now seeing AutoFPS under-report the GPU load by 18-20%.

For example, GPU-Z and Rainmeter (via HWInfo64 output) where showing GPU load of 73%, whereas at the same time Auto-FPS GPU load value was only 55%.

Could it be that GPU-Z, can track both GPUs, that perhaps AutoFPS is getting a combined GPU value (AMD Radeon plus Nvidia), as the AMD has very little load, and therefore if AutoFPS is getting an average value of the 2, it could explain the lower number.

 

 

 

Up until now at least, AutoFPS has been showing the GPU load of whatever GPU is currently selected in GPU-Z. How does what AutoFPS shows compare to what GPU-Z shows for GPU load?

1 hour ago, c912039 said:

I'm currently on the latest release in 2024 Beta4, and Ive just noticed that the AutoFPS GPU value doesnt seem to be correct.

I'm using 2 GPUs

•    AMD Radeon mainboard for non-MSFS output
•    Nvidia 4070Ti Super for MSFS output on 4K screen, plus 2 other screens for non MSFS output

I'm running GPU-Z v2.68.0, as well as HWInfo 64 (plus Rainmeter to draw all my perf graphs/system monitored datapoints read from HWInfo64).
I've also just moved to a new MB and updated CPU (which may or may not be part of the problem).

Previously, the AutoFPS GPU load % matched what I see in my Rainmeter realtime graph, as well as what GPU-Z reports for the NVidia card.

But since updating AutoFPS on my new MB/CPU combo, I'm now seeing AutoFPS under-report the GPU load by 18-20%.

For example, GPU-Z and Rainmeter (via HWInfo64 output) where showing GPU load of 73%, whereas at the same time Auto-FPS GPU load value was only 55%.

Could it be that GPU-Z, can track both GPUs, that perhaps AutoFPS is getting a combined GPU value (AMD Radeon plus Nvidia), as the AMD has very little load, and therefore if AutoFPS is getting an average value of the 2, it could explain the lower number.

 

 

 

FYI, I just had a look at my system, which is configured similar to yours in that I am using the AMD iGPU in my 9800X3D to drive two screens and my 4090 to drive my main screen and VR. 

Here's a screenshot of what it shows with GPU-Z set to the GPU of interest for MSFS ie. the 4090, and as you can see all GPU load readings align between AutoFPS, GPU-Z and MSI AB/RTSS:

 

I have my FPS capped to 38 (half vr refresh rate), via the in sim setting.  I'm using Dynamic Settings with FPS cap mode AutoFPS.  Target in AutoFPS is also set to 38.

MSFS Dynamic Settings will only let me choose either 30, or 40 for my "target" fps.  If I choose 40, will Dynamic Settings hold my TLOD at the lowest value, since I'm not actually achieving 40 fps due to my lock of 38?  Am I better off choosing 30 for my target?

Edited November 25, 2025Nov 25 by FakeWayne

5 hours ago, FakeWayne said:

I have my FPS capped to 38 (half vr refresh rate), via the in sim setting.  I'm using Dynamic Settings with FPS cap mode AutoFPS.  Target in AutoFPS is also set to 38.

MSFS Dynamic Settings will only let me choose either 30, or 40 for my "target" fps.  If I choose 40, will Dynamic Settings hold my TLOD at the lowest value, since I'm not actually achieving 40 fps due to my lock of 38?  Am I better off choosing 30 for my target?

As you suggest, using a Dynamic Setting of 40 will likely activate MSFS TLOD reduction as it is above your actual FPS, so you should set Dynamic Setting to the next lower value. MSFS Dynamic Settings is adjustable in increments of 5, so you should be able to set 35. eg.

Your question has prompted me to add another bullet point at the end of the  dynamic settings section in the Readme as follows:

• Since Dynamic Settings Target Frame Rate is only configurable in 5 FPS increments, choose the next lowest value if your desired setting is not a direct multiple of 5.

 

17 minutes ago, Reset XPDR said:

As you suggest, using a Dynamic Setting of 40 will likely activate MSFS TLOD reduction as it is above your actual FPS, so you should set Dynamic Setting to the next lower value. MSFS Dynamic Settings is adjustable in increments of 5, so you should be able to set 35. eg.

Your question has prompted me to add another bullet point at the end of the  dynamic settings section in the Readme as follows:

• Since Dynamic Settings Target Frame Rate is only configurable in 5 FPS increments, choose the next lowest value if your desired setting is not a direct multiple of 5.

 

Oh nice, I didn't realize it was increments of 5.  I'll give that a go and see how it works.  Thanks for the info!

Not working with the new SU4 Beta on Steam 🙂

10 minutes ago, iFlySimX said:

Not working with the new SU4 Beta on Steam 🙂

It should be. It worked with my Steam install this morning:

2025-11-27 09:25:35.645 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.5.9 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2025-11-27 09:25:37.682 [INF] [ IPCManager:WaitForSimulator      ] Simulator started 
2025-11-27 09:25:39.753 [INF] [ MemoryManager:MemoryManager      ] MSFS successfully attached after 1 attempt 
2025-11-27 09:25:39.753 [INF] [ MemoryManager:GetActiveDXVersion ] Steam MSFS2024 version 1.6.30.0 detected - DX12 
2025-11-27 09:25:39.753 [DBG] [ MemoryManager:MemoryManager      ] New MSFS/app/offset combo detected
2025-11-27 09:25:40.487 [DBG] [ MemoryManager:MemoryManager      ] Primary compatibility test pass for MSFS/app/offset combo saved to config file
2025-11-27 09:25:40.506 [DBG] [ MemoryManager:BoundaryTest2      ] Reduction setting boundary tests passed - reduction setting memory writes enabled 
2025-11-27 09:25:40.511 [DBG] [ MemoryManager:MemoryManager      ] Secondary compatibility test pass for MSFS/app/offset combo saved to config file

I suggest you try again, rebooting if needed.

If it still doesn't work, message me the contents of your latest log file, located in %appdata%\MSFS_AutoFPS\log.

 

 

 

 

Ok, after multiple restarts, it's now working. Thank you for the quick reply.

Hey I have MSFS 2020 on Steam, and Im having the MSFS compatibility test failed - app disabled error when I try to use the app. Ive tried all of the recommendations, like adding the exception, running as admin, and toggling on a simple setting + restarting the game, and the issue still persists. My game is installed on my D drive.