7 hours ago, CFIJose said:

I recently installed SU4 and I'd like to test AutoFPS. Which stable version do you recommend that I try?

The latest release version 0.4.6.4 is very stable. If you want to use the app with the SU5 beta, you will need to update to 0.4.6.5-test16 or later to achieve compatibility. Even though 0.4.6.5-test16 is a test version, it was very near to formal release when the SU5 beta arrived anyway, so it is also very stable, with the minor limitation that any new features in it have not yet made it into the readme but are otherwise progressively covered in the release notes.

Edited February 23Feb 23 by Reset XPDR

5 minutes ago, Reset XPDR said:

The latest release version 0.4.6.4 is very stable. If you want to use the app with the SU5 beta, you will need to update to 0.4.6.5-test16 or later to achieve compatibility. Even though 0.4.6.5-test16 is a test version, it was very near to formal release when the SU5 beta arrived anyway, so it is also very stable, with the minor limitation that any new features in it have not yet made it into the readme but are otherwise progressively covered in the release notes.

4.6.4 is working really nicely in expert mode. I only had to play with the numbers.

I disabled msfs 2024 dynamic setting for, but will also check the read me and try it enabled. It makes the sim even smoother.

Thanks.

3 hours ago, Reset XPDR said:

Just add to these already helpful replies, AutoFPS is also capable of working with Dynamic Settings enabled when in Expert mode. As long as you follow the guidance I have provided in the readme about how to set Dynamic Settings target FPS relative to AutoFPS's target FPS, with regards to FPS caps being used in particular, then the Dynamic Settings actually complements AutoFPS.

In AutoFPS Non-Expert mode, which is the default and is recommended for new users like you anyway, Dynamic Settings is automatically disabled during a flight session and restored to its original setting when exiting a flight, so you don't need to worry about it in that mode. 

Ok this is good to know because I don't have experience yet with your great utility because you know, I like to "fire and forget" the app so to speak and just profit with the results in the sim, many thanks for your explanations. 

Can I ask a small favour from a few users on the 0.4.6.5-test release series. Can I get to update to the latest test version and let me know here what the following lines look like in your log file, located in %appdata%\MSFS_AutoFPS\log, after the app has attached to MSFS:

2026-02-25 09:18:19.257 [INF] [ MemoryManager:GetOptSettings     ] GPU: NVIDIA GeForce RTX 4090 
2026-02-25 09:18:19.257 [INF] [ MemoryManager:GetOptSettings     ] CPU: AMD Ryzen 7 9800X3D 8-Core Processor            
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 0: LogicalProcessor=[0,1] 
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 1: LogicalProcessor=[2,3] 
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 2: LogicalProcessor=[4,5] 
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 3: LogicalProcessor=[6,7] 
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 4: LogicalProcessor=[8,9] 
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 5: LogicalProcessor=[10,11] 
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 6: LogicalProcessor=[12,13] 
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 7: LogicalProcessor=[14,15] 
2026-02-25 09:18:19.260 [INF] [ MemoryManager:LogCpuSummary      ] CPU Core Summary: Physical=8, Logical=16 
2026-02-25 09:18:19.260 [INF] [ MemoryManager:GetOptSettings     ] RAM: 64 GB 

I am mostly interested in what it states for 12th gen or later Intel CPU owners, as the code should be logging what your P and E core counts are, but I am also interested in it showing correct CPU data for AMD CPUs and also that it is getting your GPU and RAM specs correct.

If you are curious why I am doing this, it is to make the new optional MSFS performance optimisation feature be able to route MSFS to run exclusively on physical and P cores as applicable and if there are enough of them, so the first step is for the app to know what the CPU state of play is.

Edit: It is probably best to PM me with this data, so as not to clutter up the thread. I will advise when I have enough info for the logs to stop coming in.

Thanks.

 

Edited February 24Feb 24 by Reset XPDR

Ok, I know this was asked several times before, but search option is so annoying here on avsim: I currently run my sim with a FPS lock in the MSFS2024 menue set to 36, with frame gen enabled (2x), resulting in 72FPS. Which is exactly half of my 144Hz monitor refresh rate. While this is ok in 90% of the cases, on big hubs with a lot of traffic and complex aircraft addon, the FPS sometimes drop to 32-34, rarely even to 30, resulting in stutters. I realized that using the internal dynamic setting at 35FPS cures a lot of those stutters, it then simply reduces the TLOD by half (you know the story), the default setting I have is 200. Fine for me, but how can I now mimick this with AutoFPS?

- should I keep the frame limit but disable the dynamic settings and use AutoFPS instead for TLOD adjustments? If yes, which FPS limit should I set in the tool?

- should I keep the dynamic settings? Will AutoFPS then e.g. still increase TLOD above 200 (if specified as such) when enough overhead is available? 

9 hours ago, AnkH said:

Ok, I know this was asked several times before, but search option is so annoying here on avsim: I currently run my sim with a FPS lock in the MSFS2024 menue set to 36, with frame gen enabled (2x), resulting in 72FPS. Which is exactly half of my 144Hz monitor refresh rate. While this is ok in 90% of the cases, on big hubs with a lot of traffic and complex aircraft addon, the FPS sometimes drop to 32-34, rarely even to 30, resulting in stutters. I realized that using the internal dynamic setting at 35FPS cures a lot of those stutters, it then simply reduces the TLOD by half (you know the story), the default setting I have is 200. Fine for me, but how can I now mimick this with AutoFPS?

- should I keep the frame limit but disable the dynamic settings and use AutoFPS instead for TLOD adjustments? If yes, which FPS limit should I set in the tool?

- should I keep the dynamic settings? Will AutoFPS then e.g. still increase TLOD above 200 (if specified as such) when enough overhead is available? 

I normally don't give individual settings advice, but you are a regular here and this can be a learning point for others trying to work out how to marry AutoFPS and Dynamic Settings.

I suggest you keep both, keeping Dynamic Settings set to 35 and setting AutoFPS up like this:

 

This will give you the following results for the stated performance conditions:

1. Achieving 36 FPS easily (lots of headroom): Up to TLOD 200 on the ground and 400 in the air, with the extra provided by AutoFPS.
2. Achieving 36 FPS marginally (ie. no headroom): TLOD 100 on the ground and 200 in the air.
3. Unable to achieve 35 FPS: Down to TLOD 50 on the ground and 100 in the air, with the reduction effected by Dynamic Settings.

This gives a total possible TLOD range of 50 on the ground in worst case conditions through to 400 in the air in best case conditions.

If you want TLOD 200 as the marginal ground setting, just double TLOD Base Min and Top Min to 200 and 400 respectively, then all those numbers given above double. ie. worst TLOD 100 on the ground and best 800 in the air. Just be cautious of pushing TLOD too hard as it being very high can induce stutters when panning, even though you are achieving your target FPS.

 

 

Edited February 26Feb 26 by Reset XPDR

22 hours ago, Reset XPDR said:

Can I ask a small favour from a few users on the 0.4.6.5-test release series. Can I get to update to the latest test version and let me know here what the following lines look like in your log file, located in %appdata%\MSFS_AutoFPS\log, after the app has attached to MSFS:

2026-02-25 09:18:19.257 [INF] [ MemoryManager:GetOptSettings     ] GPU: NVIDIA GeForce RTX 4090 
2026-02-25 09:18:19.257 [INF] [ MemoryManager:GetOptSettings     ] CPU: AMD Ryzen 7 9800X3D 8-Core Processor            
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 0: LogicalProcessor=[0,1] 
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 1: LogicalProcessor=[2,3] 
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 2: LogicalProcessor=[4,5] 
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 3: LogicalProcessor=[6,7] 
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 4: LogicalProcessor=[8,9] 
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 5: LogicalProcessor=[10,11] 
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 6: LogicalProcessor=[12,13] 
2026-02-25 09:18:19.259 [INF] [ MemoryManager:LogCpuSummary      ] Core 7: LogicalProcessor=[14,15] 
2026-02-25 09:18:19.260 [INF] [ MemoryManager:LogCpuSummary      ] CPU Core Summary: Physical=8, Logical=16 
2026-02-25 09:18:19.260 [INF] [ MemoryManager:GetOptSettings     ] RAM: 64 GB 

I am mostly interested in what it states for 12th gen or later Intel CPU owners, as the code should be logging what your P and E core counts are, but I am also interested in it showing correct CPU data for AMD CPUs and also that it is getting your GPU and RAM specs correct.

If you are curious why I am doing this, it is to make the new optional MSFS performance optimisation feature be able to route MSFS to run exclusively on physical and P cores as applicable and if there are enough of them, so the first step is for the app to know what the CPU state of play is.

Edit: It is probably best to PM me with this data, so as not to clutter up the thread. I will advise when I have enough info for the logs to stop coming in.

Thanks.

 

Further to this request, I have received a few responses and the AMD CPU data looks fine but the Intel data was not correct, with it showing E cores when they were actually P cores and not showing real E cores at all.

I have just released 0.4.6.5-test18, which will provide me with rawer data for me to interpret. eg. for my system's CPU data it looks like:

2026-02-25 20:41:29.722 [INF] [ MemoryManager:GetOptSettings     ] CPU: AMD Ryzen 7 9800X3D 8-Core Processor            
2026-02-25 20:41:29.724 [INF] [ MemoryManager:LogCpuSummary      ] Core 0: LP=[0,1], EfficiencyClass=0, Flags=0 
2026-02-25 20:41:29.724 [INF] [ MemoryManager:LogCpuSummary      ] Core 1: LP=[2,3], EfficiencyClass=0, Flags=0 
2026-02-25 20:41:29.724 [INF] [ MemoryManager:LogCpuSummary      ] Core 2: LP=[4,5], EfficiencyClass=0, Flags=0 
2026-02-25 20:41:29.724 [INF] [ MemoryManager:LogCpuSummary      ] Core 3: LP=[6,7], EfficiencyClass=0, Flags=0 
2026-02-25 20:41:29.724 [INF] [ MemoryManager:LogCpuSummary      ] Core 4: LP=[8,9], EfficiencyClass=0, Flags=0 
2026-02-25 20:41:29.724 [INF] [ MemoryManager:LogCpuSummary      ] Core 5: LP=[10,11], EfficiencyClass=0, Flags=0 
2026-02-25 20:41:29.724 [INF] [ MemoryManager:LogCpuSummary      ] Core 6: LP=[12,13], EfficiencyClass=0, Flags=0 
2026-02-25 20:41:29.724 [INF] [ MemoryManager:LogCpuSummary      ] Core 7: LP=[14,15], EfficiencyClass=0, Flags=0 
2026-02-25 20:41:29.725 [INF] [ MemoryManager:LogCpuSummary      ] CPU Core Summary: Physical=8, Logical=16 

Again, I am specifically after 12th-gen or later Intel CPU data, so can someone on the test program with such a CPU PM me with their log file contents for all MemoryManager:LogCpuSummary labelled entries and the CPU identifier line that immediately preceeds them, which should be right at the top of the log file. Thanks.

1 hour ago, Reset XPDR said:

 

Lovely, thanks. But should I not put 72 in the limiter when selecting FG as limit?

2 hours ago, AnkH said:

Lovely, thanks. But should I not put 72 in the limiter when selecting FG as limit?

Yes, my bad. I was thinking MSFS settings, which are specified in native frame rate, but AutoFPS settings are scaled according to the mode you are in. ie. in your case you should set 72 for Target FG FPS. I have updated my original response with the corrected AutoFPS settings screenshot.

Edited February 26Feb 26 by Reset XPDR

5 hours ago, Reset XPDR said:

I normally don't give individual settings advice, but you are a regular here and this can be a learning point for others trying to work out how to marry AutoFPS and Dynamic Settings.

I suggest you keep both, keeping Dynamic Settings set to 35 and setting AutoFPS up like this:

 

This will give you the following results for the stated performance conditions:

1. Achieving 36 FPS easily (lots of headroom): Up to TLOD 200 on the ground and 400 in the air, with the extra provided by AutoFPS.
2. Achieving 36 FPS marginally (ie. no headroom): TLOD 100 on the ground and 200 in the air.
3. Unable to achieve 35 FPS: Down to TLOD 50 on the ground and 100 in the air, with the reduction effected by Dynamic Settings.

This gives a total possible TLOD range of 50 on the ground in worst case conditions through to 400 in the air in best case conditions.

If you want TLOD 200 as the marginal ground setting, just double TLOD Base Min and Top Min to 200 and 400 respectively, then all those numbers given above double. ie. worst TLOD 100 on the ground and best 800 in the air. Just be cautious of pushing TLOD too hard as it being very high can induce stutters when panning, even though you are achieving your target FPS.

 

 

Let me do this one again as I messed up the FPS in the description too:

I suggest you keep both, keeping Dynamic Settings set to 35, which is the native framerate of 70 FPS FG, and setting AutoFPS up like this:

This will give you the following results for the stated performance conditions:

1. Achieving 72 FPS easily (lots of headroom): Up to TLOD 200 on the ground and 400 in the air, with the extra provided by AutoFPS.
2. Achieving 72 FPS marginally (ie. no headroom): TLOD 100 on the ground and 200 in the air.
3. Unable to achieve 70 FPS: Down to TLOD 50 on the ground and 100 in the air, with the reduction effected by Dynamic Settings.

This gives a total possible TLOD range of 50 on the ground in worst case conditions through to 400 in the air in best case conditions.

If you want TLOD 200 as the marginal ground setting, just double TLOD Base Min and Top Min to 200 and 400 respectively, then all those numbers given above double. ie. worst TLOD 100 on the ground and best 800 in the air. Just be cautious of pushing TLOD too hard as it being very high can induce stutters when panning, even though you are achieving your target FPS.

23 hours ago, Reset XPDR said:

Again, I am specifically after 12th-gen or later Intel CPU data, so can someone on the test program with such a CPU PM me with their log file contents for all MemoryManager:LogCpuSummary labelled entries and the CPU identifier line that immediately preceeds them, which should be right at the top of the log file. Thanks.

I now have received the information I was seeking (thanks @jdk2), so no further logs will be needed. I now aim to have Intel P & E core logic implemented for the new MSFS performance option in the next test release.

MSFS_AutoFPS v0.4.6.6 has just been formally released, available either through auto update in the app or from here. My thanks goes out to all who provided valuable feedback during the test phase.

This release delivers full MSFS 2024 SU5 Beta 1.7.9.0 compatibility with expected coverage across remaining SU5 betas and the final release via the new automatic memory‑map drift‑recovery system, adds an optional MSFS performance optimiser with safe affinity, priority, and power‑plan controls, improves multi‑window attach reliability, and includes general fixes and expanded diagnostic and developer tooling.

For the observant amongst you, v0.4.6.5 made a brief appearance today until I went to take a screenshot for this post and noticed that the AGL and FPM data in a flight session were showing as n/a on the UI, even though the app was still using the correct values internally. That issue slipped through the entire test program. The problem has now been fixed and the corrected build has been released as v0.4.6.6.

MSFS Performance Option Tooltip:

 

Edited March 5Mar 5 by Reset XPDR

I guess your tool does work with the affinity independent of the type of CPU is installed, correct? But how? I mean a Intel with E- and P-Cores is significantly different from e.g. my AMD with just 8 cores and SMT. Or the other way around: what does the tool do if I set the checkmark there? Because those things (power plan and process priority) I do not really like if a tool is "fumbling" around without me knowing exactly what it does... 

34 minutes ago, AnkH said:

I guess your tool does work with the affinity independent of the type of CPU is installed, correct? But how? I mean a Intel with E- and P-Cores is significantly different from e.g. my AMD with just 8 cores and SMT. Or the other way around: what does the tool do if I set the checkmark there? Because those things (power plan and process priority) I do not really like if a tool is "fumbling" around without me knowing exactly what it does... 

Although Intel and AMD have different architectures, what is common is that their highest performing cores, Performance (P) for Intel and Hyper-Threading (HT) for AMD, are Simultaneous Multithreading (SMT) dual core and that is what the app is looking for.  If you have enough of them (6 is default), the app will disable the non-physical cores and E cores if you have them, which gives plenty of physical core performance to run MSFS at maximum effort.

As for the other settings, they are explained in the recently-updated readme as follows:

• When the MSFS Performance Optimiser is enabled via the "+" checkbox to the left of the Sim Version label:
  • The Sim Values panel reflects optimiser‑controlled states such as CPU affinity, process priority, and power‑plan selection, updating immediately when these values are applied or restored.
  • Designed to change states only when they have not already been modified by other tools (e.g., VR Auto Optimiser, Process Lasso), ensuring no conflict with external managers.
  • The Sim Version text changes to royal blue to indicate the optimiser is active and controlling MSFS.
  • Provides four user‑configurable options in the common config file in the app's root directory:
    • AffinityPhysicalCoreThreshold – sets the logical‑CPU cutoff for physical‑core affinity; default is 6, and set to 32 to effectively disable.
    • AMDUseFirstCCDOnly – enables first‑CCD‑only affinity on dual‑CCD AMD CPUs; default is enabled.
    • MSFSProcessPriority – selects the MSFS process priority; Normal, AboveNormal and High are the only allowable choices; default is High.
    • PowerPlanEnabled – toggles automatic power‑plan switching; default is enabled.
  • The optimiser tooltip dynamically rebuilds on load to show the active configuration, including the selected power plan, physical‑core affinity threshold, and MSFS process priority.

ie. you can set it to control whatever you like, and if that turns out to be none of them simply disable the option completely: it is disabled by default anyway. I am just giving users a choice to auto-enable some common optimisations users configure with MSFS.

Edited March 5Mar 5 by Reset XPDR

from your explanations it sounds like Windows OS and CPU related code now requires a lot more programming knowledge and coding than your genuine program itself. 🤣