50 minutes ago, turbomax said:

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. 🤣

Yes it can be quite technical, but I have enjoyed working out the nuances of these performance parameters. I have tried all combinations on both of my high and low end systems, and while I can't say for sure there is a marked improvement in using them, it certainly has not been detrimental either. 

I erred on the side of brevity in describing this new feature for release, as the readme is already large enough as it is, but it looks like I probably need to expand the description of each performance parameter for clarity. I will revisit tomorrow.

 

 

As promised, I have reworked the new MSFS Performance Optimiser Option section of the readme to be more descriptive, without too many extra words:

• MSFS Performance Optimiser - 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 are at their default levels and 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.
  • Can be fine‑tuned with four user‑configurable options in the common config file in the app’s root directory.
  • CPU Affinity:
    • Uses a universal physical‑core rule based on SMT that gives consistent behaviour across AMD, Intel hybrid, and SMT‑off systems.
    • On Intel hybrid CPUs, this means MSFS runs on the P‑cores only, since E‑cores don’t support SMT and aren’t counted as physical cores in this rule.
    • The AffinityPhysicalCoreThreshold key, defaulting to 6, controls the SMT‑core threshold at which physical‑core‑only affinity is applied.
    • The AMDUseFirstCCDOnly key, defaulting to true, activates first‑CCD affinity mode on dual‑CCD AMD CPUs. The tooltip appends "CCD+" to the physical‑core affinity line when this mode is active.
  • MSFS Process Priority:
    • Only changes priority when MSFS is currently running at the default Normal level, switching it to High when available and leaving any user‑set AboveNormal or RealTime priority untouched.
    • The MSFSProcessPriority key, defaulting to High, controls the target MSFS process priority (Normal / AboveNormal / High). RealTime is intentionally excluded because using it would require AutoFPS itself to run elevated.
  • Windows Power Plan:
    • Only overrides the power plan when starting from the default Balanced plan, choosing Ultimate Performance or High Performance depending on availability.
    • The PowerPlanEnabled key, defaulting to true, explicitly enables or disables automatic power‑plan switching.
  • 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.

Edited March 5Mar 5 by Reset XPDR

Still dont really get it. Should I change any of those parameters using a 9800X3D with SMT on? Or leave it on default for 6 cores? 

13 minutes ago, AnkH said:

Still dont really get it. Should I change any of those parameters using a 9800X3D with SMT on? Or leave it on default for 6 cores? 

As with anything technical like this, if you don't really get it, you shouldn't be tweaking anything and that is why they are buried in the config file. Just go with the defaults and you will be fine. I have a 9800X3D and that's what I do, which will give you 8 physical cores running MSFS. Just try it!

Edited March 5Mar 5 by Reset XPDR

2 hours ago, Reset XPDR said:

Just go with the defaults and you will be fine.

I did a fair bit of tweaking when AutoFPS first came out. I set my defaults to something sensible back then and haven't changed them since. It really is a "no nonsense" little app: set it - and forget it! I can't imagine running MSFS without it. Many thanks, Reset XPDR - goodness knows how you keep finding things to improve!!

Is there a way to have the TLOD at 100 till 3000 and then jump to 300 instead of increasing incrementally to 300?

Or it does Nd i am using it all wrong lol?

 

Thanks

Mike 

On 2/25/2026 at 9:55 PM, Reset XPDR said:

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.

I'm trying a similar setup. Maybe I'm misunderstanding this, but if I set MSFS Dynamic Settings to 35 native FPS (70 FPS with FG), then the sim will never actually reach the 72 FPS FG target in AutoFPS. If that's the case, wouldn't TLOD stay at the base value and never increase?  

Edited March 7Mar 7 by LVPack

23 hours ago, mikeymike said:

Is there a way to have the TLOD at 100 till 3000 and then jump to 300 instead of increasing incrementally to 300?

Or it does Nd i am using it all wrong lol?

 

Thanks

Mike 

Yes there is, but not within AutoFPS. Use DynamicLOD_ResetEdition instead, where you can define large steps like this with no incrementing (LOD Step Max unchecked) if you choose. 

Edited March 7Mar 7 by Reset XPDR

6 hours ago, LVPack said:

I'm trying a similar setup. Maybe I'm misunderstanding this, but if I set MSFS Dynamic Settings to 35 native FPS (70 FPS with FG), then the sim will never actually reach the 72 FPS FG target in AutoFPS. If that's the case, wouldn't TLOD stay at the base value and never increase?  

Dynamic Settings target frame rate determines the FPS at which TLOD and OLOD will reduce up to 50% in your system goes below that FPS threshold and does not limit FPS at all. In the subject scenario, the FPS can go up to 72 (36 native) and for best results in an FPS capped scenario like this set MSFS max frame rate to 36 so that it does cap interally at that threshold and works a lot better with Dynamic Settings set just 1 FPS lower like here.

Just wanted to say yes… dynamic_lod_resetedition, but reset beat me to it. Probably the best software i have, and i waste a lot of money on flight simming! I still cant believe its free. And a shout out to @Reset XPDR whilst im at it. You are a star mate!

I hope you can make a video explaining three performance levels for PCs: low-end, mid-range, and high-end. I’ve asked about this before, and it would really help if you could also explain what the numbers/settings mean. I know you’re busy and that you like to do your work with quality and precision, and we truly appreciate that. Thank you again.

9 hours ago, SylvesterSS said:

I hope you can make a video explaining three performance levels for PCs: low-end, mid-range, and high-end. I’ve asked about this before, and it would really help if you could also explain what the numbers/settings mean. I know you’re busy and that you like to do your work with quality and precision, and we truly appreciate that. Thank you again.

I don't think there is enough to say to make a video about it. Non-expert mode is designed to centre around whatever graphics settings you normally use for the performance level of your PC. Expert mode settings default to what you would get using the high graphics preset in non-expert mode and you can take it up and down for there. The tooltips give a brief overview of what each setting does and the readme provides more detail if you need it. That's pretty much it.

Just wondering how your latest version of AutoFPS compares to VR Auto‑Optimizer...does the latest AutoFPS basically incorporate the same features as VR Auto‑Optimizer?

4 hours ago, flyblueskies said:

Just wondering how your latest version of AutoFPS compares to VR Auto‑Optimizer...does the latest AutoFPS basically incorporate the same features as VR Auto‑Optimizer?

The new MSFS Performance Optimisation feature in AutoFPS was based on similar CPU core affinity, MSFS process high priority and best power plan selection functionality in VR Auto‑Optimizer, with the developer's permission of course, and works in 2D and VR, but otherwise the apps are completely different. I have designed AutoFPS (and DynamicLOD_ResetEdition) such that it will not override any such similar settings made by VR Auto‑Optimizer.

Edited March 9Mar 9 by Reset XPDR

Hi,

I am using your tool with great delight in MSFS2024. Thank you for your hard work.

I am using the tool as per a scenario similar to the one specified above for AnKH, so FPS cap setting in AutoFPS with Dynamic setting ON in game. Until now my target FPS was set at 30 in game and also in AutoFPS (with FG x 2.)

I see in your exemple that you set autofps to 72. 

Do you confirm we need to set target FPS after FG, so 60 in autofps if capped at 30 in game ?

Also, should I set in game limit to 30 or 31 FPS native ? Then accordingly, Autofps target fps should be set to 60 or 62 (I have a 60Hz screen) ?

Sorry for such noob questions but I am unsure if am setting up things well.

Best regards,

Pierre