AutoFPS Masterclass

Lesson Overview

Welcome to Module 14 of the Flight Sim Mastery Academy.

This module focuses on MSFS AutoFPS, a community-developed performance utility that dynamically adjusts demanding simulator settings while you fly.

Its main purpose is not to create extra performance from nowhere.

Instead, it attempts to maintain a chosen level of smoothness by changing settings such as:

Terrain Level of Detail.
Object Level of Detail.
Selected graphics options.
Cloud quality in supported MSFS 2020 configurations.
Performance-related settings in MSFS 2024.
Altitude-based visual settings.

The current unified AutoFPS application supports both Microsoft Flight Simulator 2020 and Microsoft Flight Simulator 2024. It includes separate VFR and IFR profiles, automatic or fixed target-FPS options, dynamic TLOD and OLOD control, Frame Generation awareness and automatic restoration of changed simulator settings when a flight ends.

AutoFPS can be very useful for systems that perform well in cruise but struggle at:

Detailed airports.
Dense cities.
Low-altitude approaches.
Heavy weather.
Complex aircraft.
High traffic levels.

However, it can also create:

Visible scenery changes.
Object popping.
Inconsistent benchmark conditions.
Conflicts with other dynamic-performance utilities.
Poor results when unrealistic targets are selected.

The objective of this lesson is to teach students how to use AutoFPS carefully rather than treating it as a one-click miracle fix.

Lesson Objectives

By the end of this module, students will be able to:

Download AutoFPS from the correct source.

Understand the risks of unsigned community software.

Install the required application components.

Configure it for MSFS 2020 or MSFS 2024.

Update or remove it correctly.

Choose a realistic target FPS.

Configure minimum and maximum Terrain LOD.

Understand dynamic Object LOD behaviour.

Create suitable IFR and VFR profiles.

Use AutoFPS with Frame Generation.

Configure the utility for CPU-limited and GPU-limited systems.

Compare AutoFPS on and off fairly.

Measure average FPS, 1% lows and frame pacing.

Identify visual popping caused by dynamic settings.

Test performance at demanding airports.

Avoid conflicts with other performance tools.

Understand why normal benchmarking becomes harder when settings change dynamically.

Important Safety and Compatibility Information

AutoFPS is not an official Microsoft or Asobo product.

It is a community utility that reads and changes active simulator settings while MSFS is running. The developer explains that it validates the relevant memory locations before making changes and enters a restricted read-only mode if those locations cannot be confirmed. The software is still supplied on an as-is, use-at-your-own-risk basis.

Students must understand three important points:

Only download it from the developer’s official GitHub repository.
Do not run AutoFPS immediately after a major Sim Update unless compatibility has been confirmed.
Do not run it alongside another tool that is changing the same simulator settings.

The current application automatically detects whether MSFS 2020 or MSFS 2024 is running and supports both within one program.

STEP 1 – INSTALLATION, UPDATES AND REMOVAL

Estimated Time: 10–12 Minutes

1. What AutoFPS Actually Does

AutoFPS monitors simulator performance and adjusts selected settings dynamically.

A basic example:

The student sets a target of 40 FPS.
The aircraft approaches a demanding airport.
MainThread performance begins falling.
AutoFPS reduces Terrain LOD.
CPU workload decreases.
FPS or frame-time consistency improves.
After departure, performance headroom increases.
AutoFPS raises Terrain LOD again.

The application may also use altitude schedules, meaning lower detail near airports and higher detail at cruise altitude.

AutoFPS currently supports several automation methods, including target-FPS-based adjustment, altitude schedules and more advanced Expert-mode strategies.

2. Safe Download Source

Use only the official repository maintained by:

ResetXPDR – MSFS_AutoFPS

Avoid:

Random file-hosting websites.
Social-media download links.
Repacked installers.
Old versions of MSFS2020_AutoFPS.
Unofficial forks unless there is a specific reason to test one.
Bundled “performance packs.”

The older dedicated MSFS 2020 AutoFPS project has been replaced by the unified MSFS_AutoFPS application.

3. Unsigned Application Warning

AutoFPS is unsigned community software.

Windows, a browser or security software may display a warning.

The developer explains that code-signing certification is not used because of its cost, so antivirus or browser warnings can occur even with the official installer.

Students should:

Confirm the repository owner.
Download from the official release page.
Scan the installer with security software.
Check the file name and release version.
Avoid disabling all Windows security protections.
Do not install if they are uncomfortable with the risk.

A warning should not be ignored blindly, but it also does not automatically prove the official file is malicious.

4. Required Components

The installer normally provides the application components it requires.

Depending on the release, the utility may require or use:

Microsoft .NET desktop components.
SimConnect-related communication.
GPU-Z for optional VRAM monitoring features.
Administrator permission in some troubleshooting situations.

The application itself should not be placed inside the MSFS Community Folder.

It runs externally alongside the simulator.

5. Installing AutoFPS

Recommended procedure:

Close Microsoft Flight Simulator.
Download the latest stable release from the official GitHub release page.
Extract the download if required.
Run the installer.
Allow the installation to finish.
Create a desktop shortcut if offered.
Open AutoFPS.
Confirm the application starts without an error.
Leave Expert Mode disabled initially.
Do not change advanced values yet.

The newest release should always be checked before recording or teaching the lesson because MSFS updates can change compatibility.

6. First Launch

On first launch, review:

Application version.
Detected simulator version.
Connection status.
IFR or VFR profile.
Target FPS mode.
Expert Mode state.
TLOD values.
OLOD values.
Update settings.

The status indicators should show that AutoFPS has attached to the correct simulator after MSFS is running.

If the simulator version appears incorrectly, the application provides a simulator-version selection control so the user can prepare settings for MSFS 2020 or MSFS 2024.

7. MSFS 2020 Setup

For MSFS 2020:

Start AutoFPS.
Launch MSFS 2020.
Load the required flight.
Confirm AutoFPS identifies MSFS 2020.
Select IFR or VFR.
Leave Expert Mode disabled.
Select Manual, Auto or Fixed target FPS.
Wait for the initial calibration process to settle.
Begin the flight.

MSFS 2020-specific features can include automatic cloud-quality reduction when the FPS target cannot be achieved at the minimum desired Terrain LOD or when GPU load is excessive.

8. MSFS 2024 Setup

For MSFS 2024:

Use the latest compatible AutoFPS version.
Launch AutoFPS.
Launch MSFS 2024.
Confirm the correct simulator version is detected.
Select the flight type.
Choose the target-FPS method.
Leave Expert Mode disabled for the first test.
Wait for settings to settle before taxi.

The current app supports MSFS 2024-specific automatic settings reduction intended to improve FPS and reduce VRAM pressure under marginal performance conditions. It can also work alongside MSFS 2024 dynamic settings in supported Expert-mode configurations.

Do not assume a version compatible with one Sim Update will automatically remain fully compatible with every future update.

9. Updates

AutoFPS can provide automatic update behaviour, including mandatory updates when required.

Before updating:

Close MSFS.
Close AutoFPS.
Record the current version.
Export or photograph the current settings.
Install the update.
Restart the application.
Check release notes.
Test a short benchmark flight.
Confirm original MSFS settings restore correctly after closing.

Major releases may change:

Target-FPS automation.
TLOD behaviour.
VRAM protection.
Sim Update compatibility.
Frame Generation detection.
Expert-mode controls.

10. After a Simulator Update

After an MSFS Sim Update:

Do not assume AutoFPS is safe to use immediately.
Open the official release or discussion page.
Check listed simulator compatibility.
Update AutoFPS where required.
Launch the simulator at the main menu.
Confirm AutoFPS passes its compatibility test.
Use Non-Expert Mode.
Complete a short default-airport test.
Confirm settings restore after exiting.

The application attempts to validate and recover changed memory locations, but if it cannot safely confirm them, it restricts itself rather than continuing to make changes.

11. Correct Removal

To remove AutoFPS:

Close Microsoft Flight Simulator.
Close AutoFPS.
Use Windows Installed Apps or the official uninstaller.
Remove the application.
Delete residual configuration files only if a full reset is required.
Restart Windows.
Launch MSFS.
Check Terrain LOD and Object LOD.
Confirm graphics settings match the student’s normal baseline.

AutoFPS is designed to restore the original settings it changed after a flight or when the program closes, including additional protection after simulator CTDs.

Do not manually delete simulator configuration files unless the normal uninstall process has failed and a backup exists.

STEP 2 – CONFIGURATION AND REAL-WORLD USE

Estimated Time: 23–25 Minutes

12. Start With Non-Expert Mode

New students should begin with Non-Expert Mode.

The developer’s recommended simple workflow is:

Leave normal MSFS settings as they would be without AutoFPS.
Start the application before loading the flight.
Leave Expert Mode disabled.
Select VFR or IFR.
Choose Manual, Auto or Fixed Target FPS.
Return to the simulator.
Allow the application to settle.
Fly normally.

Expert Mode should be introduced only after the student understands:

Their normal MainThread performance.
Their normal GPU limit.
Their acceptable LOD range.
Their real native FPS.
Their Frame Generation behaviour.

13. Choosing IFR or VFR

IFR Profile

Designed mainly for:

Airliners.
Complex aircraft.
High-altitude routes.
Major airports.
Departure and arrival transitions.

The profile generally prioritises:

Lower workload near airports.
Higher scenery detail at altitude.
Smooth approaches.
Predictable airliner operation.

VFR Profile

Designed mainly for:

General aviation.
Helicopters.
Low-altitude sightseeing.
Bush flying.
Detailed terrain viewing.

The VFR profile generally preserves more ground detail at lower altitude because terrain visibility is more important during this type of flying.

Do not use an airliner profile for low-level sightseeing and then complain that the terrain looks too soft.

14. Understanding Target FPS

Target FPS is the performance level AutoFPS attempts to maintain.

It is not a guaranteed result.

The system cannot achieve 60 FPS on hardware that normally produces only 30 FPS at a demanding airport without making major visual sacrifices.

A realistic target should be based on:

Native FPS.
CPU performance.
GPU performance.
Aircraft.
Airport.
Traffic.
Resolution.
Frame Generation.
Refresh rate.

15. Manual Target FPS

Manual mode allows the student to choose a target.

Example:

A system normally delivers:

55 FPS in cruise.
38 FPS at a medium airport.
30 FPS at Heathrow.

A sensible target may be:

35 FPS native.
Not 60 FPS.

AutoFPS will then try to keep the simulator near that target by adjusting the available settings.

Choose a value the system can usually achieve under reasonably demanding conditions.

16. Auto Target FPS

Auto Target FPS is useful when:

The student does not know what target to select.
Aircraft and flight types vary greatly.
The system is sometimes native and sometimes Frame Generated.
VR and monitor modes change.

The application can choose a suitable target based on observed performance.

Auto mode is a strong starting point for beginners, but students should still review the resulting:

TLOD.
Visual quality.
1% lows.
Approach smoothness.

17. Fixed Target FPS

Fixed Target FPS should be used only when FPS is genuinely locked to one nearly constant number.

Example

40 – 40 – 40 – 40 – 40 FPS

The developer distinguishes this from an ordinary FPS cap where the frame rate still moves below the cap. In that case, Fixed mode should not be selected.

Use Fixed mode when:

V-Sync creates a true fixed rate.
A reliable external or in-simulator limiter holds the value exactly.
Frame Generation output is consistently locked.

Do not select Fixed simply because an FPS cap has been configured.

18. Frame Generation Considerations

AutoFPS supports:

Native frame rate.
NVIDIA Frame Generation.
Multi Frame Generation.
FSR 3 Frame Generation.
Frame Generation mods.
Lossless Scaling.
VR modes.

It can display the correct generated FPS and maintain separate targets for different graphics modes.

Students must understand the difference between:

Native FPS

Frames actually rendered by the simulator engine.

Generated FPS

Additional interpolated frames created between native frames.

Example:

Native FPS: 35.
Frame Generation output: 70 FPS.

A 70-FPS generated output does not mean the CPU is producing 70 simulation frames.

Set the target based on how the application detects and handles the chosen mode, and confirm the displayed FPS is being interpreted correctly.

19. Choosing a Frame Generation Target

A sensible Frame Generation configuration should preserve enough native FPS for:

Responsive controls.
Stable input.
Reliable frame pacing.
Good image quality.

Do not attempt to generate 120 FPS from an unstable native 20 FPS.

Example starting points:

60 Hz Display

Native target around 30 FPS.
Generated output around 60 FPS.

120 Hz Display

Native target around 40 FPS.
Generated output around 80 FPS.
Or 60 native to 120 generated on stronger systems.

144 Hz Display

Native target around 45–60 FPS.
Generated output according to the selected FG mode.

The correct target depends on the hardware and workload rather than the monitor’s maximum refresh rate alone.

20. Terrain LOD Minimum

Minimum Terrain LOD controls how far AutoFPS may reduce terrain detail during demanding conditions.

A lower minimum provides:

More CPU relief.
Better airport FPS.
Improved MainThread performance.

But it may also create:

Softer terrain.
Reduced draw distance.
More visible terrain changes.
Less detailed city approaches.

Do not set the minimum lower than the visual quality the student is willing to accept.

21. Terrain LOD Maximum

Maximum Terrain LOD controls how far the application may raise terrain detail when performance headroom exists.

A higher maximum provides:

Better long-range terrain.
Improved mountain detail.
Better VFR visibility.
More scenery at cruise.

But it increases:

MainThread load.
Object processing.
Terrain streaming.
Potential approach instability if it does not reduce quickly enough.

An extremely high maximum does not automatically improve the overall experience.

22. Sensible TLOD Ranges

Example starting ranges:

Lower-End System

Minimum: 50.
Maximum: 100–150.

Mid-Range System

Minimum: 75–100.
Maximum: 150–250.

High-End System

Minimum: 100–150.
Maximum: 250–350.

Very High-End System

Minimum: 150.
Maximum: 300–400.

These are starting examples, not universal rules.

A demanding aircraft at a premium airport may require lower values than a Cessna over countryside.

23. Object LOD Behaviour

Object LOD controls the distance and complexity at which:

Buildings.
Airport objects.
Trees.
Ground equipment.
Scenery objects.

remain visible.

AutoFPS can automatically adjust OLOD within a selected range and altitude band.

OLOD is particularly important near:

Major airports.
Detailed cities.
Photogrammetry areas.
Premium scenery.

Reducing OLOD near airports can improve MainThread performance, but objects may appear closer to the aircraft.

24. Visual Popping

Dynamic LOD changes can cause:

Buildings appearing.
Trees changing detail.
Airport objects appearing late.
Terrain detail changing.
Distant scenery becoming sharper or softer.

Some degree of change is unavoidable when settings are being altered in flight.

The objective is to find a range that:

Produces a useful performance improvement.
Does not create distracting visual shifts.

If popping is excessive:

Raise the minimum LOD.
Narrow the LOD range.
Reduce adjustment sensitivity.
Use smaller adjustment steps.
Choose a lower target FPS.
Reduce the default simulator workload.

25. Ground and Flight Profiles

A useful AutoFPS profile recognises that the simulator has different needs at different stages.

On the Ground

Priority:

MainThread performance.
Smooth taxi.
Stable 1% lows.
Traffic handling.
Detailed cockpit operation.

Accept:

Lower distant terrain detail.
Lower object draw distance.

Climb

Priority:

Smooth transition away from the airport.
Gradual LOD increase.
Avoid sudden scenery changes.

Cruise

Priority:

Higher terrain detail.
Distant mountains.
Reduced airport-object workload.
Stable long-range scenery.

Descent and Approach

Priority:

Early LOD reduction.
Stable MainThread.
Smooth approach.
Controlled object loading.
Avoid late large changes.

26. Airport Behaviour

Airports are the most important AutoFPS testing environment.

At a demanding airport, the utility may reduce:

TLOD.
OLOD.
Other supported graphics options.

Students should monitor:

Whether reductions occur early enough.
Whether FPS recovers.
Whether visual quality remains acceptable.
Whether settings jump repeatedly.
Whether objects appear too late.
Whether the target is unrealistic.

A profile that works in cruise but collapses at Heathrow is not properly balanced.

27. Night-Time LOD

AutoFPS can reduce maximum Terrain LOD at night because distant terrain is less visible and therefore provides less visual value.

This can help:

Reduce CPU workload.
Improve night approaches.
Preserve performance at city airports.
Avoid rendering unseen detail.

Check that the reduction does not make illuminated cities or mountains disappear too aggressively.

28. CPU-Limited Systems

AutoFPS is most useful when the simulator is MainThread limited.

Common signs:

GPU utilisation below maximum.
MainThread limitation shown in Developer Mode.
Performance falls at airports.
TLOD and traffic strongly affect FPS.
Lowering resolution does not improve FPS much.

Recommended approach:

Use realistic target FPS.
Allow useful TLOD reduction.
Use moderate OLOD.
Reduce traffic separately.
Keep a lower airport minimum.
Test complex aircraft.

AutoFPS cannot fully solve CPU load created by:

Excessive AI traffic.
Complex aircraft systems.
Poorly optimised airports.
Airport workers.
GSX passengers.
Background applications.

29. GPU-Limited Systems

Signs of GPU limitation:

GPU utilisation around 95–100%.
MainThread has headroom.
Lower resolution improves FPS.
Clouds and render scaling have strong effects.
VRAM is near capacity.

Reducing TLOD may produce limited benefit in a strongly GPU-limited situation.

Instead review:

Resolution.
Render Scaling.
Clouds.
Shadows.
Reflections.
Texture Resolution.
Frame Generation.
VRAM.

MSFS 2020 can use AutoFPS cloud reduction in supported configurations, while MSFS 2024 can use automatic settings reduction to help under marginal performance or VRAM conditions.

30. Recommended Approach by Hardware Class

Budget System

Example:

Ryzen 5 or Core i5.
RTX 3060-class GPU.
16–32 GB RAM.

Starting approach:

Target 30 FPS native.
Moderate TLOD range.
Conservative OLOD.
High rather than Ultra clouds.
Frame Generation only where supported and stable.
Traffic kept low.

Mid-Range System

Example:

Ryzen 7 7700 or 7800X3D.
RTX 4070-class GPU.
32 GB RAM.

Starting approach:

Target 35–45 FPS native.
Wider TLOD range.
Moderate-to-high OLOD.
Frame Generation where appropriate.
Balanced traffic.

High-End System

Example:

9800X3D.
RTX 5080.
32–64 GB RAM.

Starting approach:

Target 45–60 FPS native.
Higher TLOD minimum.
High cruise maximum.
Strong airport minimum.
Frame Generation or MFG tuned to monitor.
Avoid unrealistic 120-FPS targets at heavy hubs.

Ultra-End System

Example:

9950X3D.
RTX 5090.
64 GB RAM.

Starting approach:

High minimum visual quality.
Higher TLOD range.
Target based on heavy airports rather than empty cruise.
AutoFPS used mainly for consistency rather than major visual reduction.
Traffic and scenery still tested separately.

Even a flagship system can become MainThread limited at a detailed airport with complex traffic.

31. Do Not Change Managed Settings Manually

While AutoFPS is actively controlling a flight, do not manually alter the same graphics settings inside MSFS.

The developer warns that AutoFPS may override those changes and later restore the original values. Default changes should be made while AutoFPS is closed or while the simulator is at the main menu rather than inside an active flight.

This avoids:

Conflicting values.
Unexpected restoration.
Inconsistent behaviour.
Invalid benchmark results.

32. Advanced Expert Mode

Expert Mode can control:

TLOD automation method.
Adjustment sensitivity.
Tolerance.
Minimum and maximum ranges.
OLOD altitude bands.
Night-time reduction.
Auto settings reduction.
Dynamic-setting coordination.
VR and Frame Generation profiles.

Expert Mode should be taught only after the student has completed a stable Non-Expert benchmark.

One of the most common causes of poor AutoFPS behaviour is unrealistic Expert values that exceed what the system could handle even without the application. The developer recommends resetting configuration and returning to Non-Expert IFR settings when troubleshooting.

STEP 3 – BENCHMARKING, PERFORMANCE AND CONFLICT TESTING

Estimated Time: 10–12 Minutes

33. Why AutoFPS Benchmarking Is Difficult

Traditional benchmarking requires identical graphics settings.

AutoFPS changes settings during the benchmark.

This means two runs may use different:

Terrain LOD.
Object LOD.
Cloud quality.
Performance reductions.
Altitude schedules.

Therefore, a simple FPS comparison is incomplete.

Students must record both:

Performance.
Visual-setting behaviour.

34. Establish a Static Baseline

First run the benchmark with AutoFPS disabled.

Record:

TLOD.
OLOD.
Cloud Quality.
Average FPS.
1% lows.
0.1% lows.
MainThread status.
GPU utilisation.
VRAM.
Frame times.
Visual quality.

This is the fixed-settings baseline.

35. AutoFPS Test

Repeat with AutoFPS enabled.

Record:

Target FPS.
Lowest TLOD.
Highest TLOD.
Lowest OLOD.
Highest OLOD.
Average FPS.
1% lows.
Frame times.
MainThread status.
GPU utilisation.
VRAM.
Visible popping.
Settings-reduction events.

The question is not only:

“Did FPS increase?”

It is also:

“What visual quality was traded to achieve it?”

36. AutoFPS On vs Off Table

Measurement	AutoFPS Off	AutoFPS On
Average FPS
1% Low
0.1% Low
MainThread status
GPU utilisation
VRAM usage
Lowest TLOD	Fixed
Highest TLOD	Fixed
Lowest OLOD	Fixed
Highest OLOD	Fixed
Visual popping
Approach smoothness

37. FPS Stability

AutoFPS may not always increase the maximum FPS.

Its greater benefit may be:

Smaller drops.
Better 1% lows.
More consistent frame times.
Smoother approach.
Less severe MainThread limitation.

A result such as:

Maximum FPS unchanged.
Average FPS slightly higher.
1% lows significantly improved.
Fewer frame-time spikes.

can represent a successful configuration.

38. 1% Low Testing

Measure 1% lows during:

Gate preparation.
Taxi.
Take-off.
City overflight.
Approach.
Landing.

The most important result is often approach performance, not cruise FPS.

AutoFPS should ideally reduce severe low-performance periods without creating repeated visual changes.

39. MainThread Testing

Monitor the simulator’s Developer Mode FPS display.

Compare:

AutoFPS Off

Fixed TLOD.
Fixed OLOD.
MainThread status.

AutoFPS On

Dynamic TLOD.
Dynamic OLOD.
MainThread status.

If MainThread improves as TLOD falls, the system is behaving logically.

If TLOD falls but GPU remains fully limited and FPS does not improve, the real bottleneck may be GPU-related.

40. Airport Test

Use three airports:

Small default airport.
Medium regional airport.
Major premium airport.

Record:

TLOD on the ground.
OLOD on the ground.
Average FPS.
1% lows.
MainThread.
Visible object popping.
Recovery after take-off.

A strong profile should adapt differently to each environment.

41. Approach Test

Approach is the most important AutoFPS test.

Record:

TLOD at 10,000 feet.
TLOD at 5,000 feet.
TLOD at 2,000 feet.
TLOD on final.
OLOD changes.
Frame-time spikes.
MainThread status.
Visible scenery changes.
FPS at touchdown.

A poor profile may wait too long and make severe reductions close to the runway.

A better profile begins reducing workload gradually before the airport becomes fully active.

42. Visual-Popping Test

Use a camera facing:

Airport terminals.
City buildings.
Trees.
Runway objects.
Mountain terrain.

Observe while:

Descending.
Panning.
Taxiing.
Changing altitude.
AutoFPS adjusts settings.

Record whether:

Objects appear suddenly.
Buildings change detail.
Terrain shifts.
Popping distracts from the flight.

43. Frame Generation Test

Test:

Native mode with AutoFPS off.
Native mode with AutoFPS on.
Frame Generation with AutoFPS off.
Frame Generation with AutoFPS on.

Record

Configuration	Native FPS	Displayed FPS	1% Low	TLOD Range
Native, off
Native, on
FG, off
FG, on

Check that AutoFPS is interpreting generated FPS correctly.

44. Conflict Testing With MSFS Dynamic Settings

MSFS 2024 includes its own dynamic-settings behaviour.

Do not allow two systems to change the same values independently unless the AutoFPS mode specifically supports coordinated operation.

Test:

MSFS dynamic settings only.
AutoFPS only.
Supported hybrid mode.
Compare stability and visual behaviour.

The current AutoFPS application supports hybrid dynamic-settings coordination in Expert Mode, while Non-Expert Mode avoids that complexity.

45. Conflict Testing With Other Utilities

Do not simultaneously use another tool that adjusts:

Terrain LOD.
Object LOD.
Cloud quality.
FPS targets.
Dynamic simulator settings.
Process priority.
CPU affinity.

Possible conflicting tools include:

Alternative Dynamic LOD utilities.
Older AutoFPS versions.
MSFS2024_AutoFPS forks.
Other performance automation programs.
Manual scripts.
Some optimiser utilities.

Run only one main dynamic-settings controller.

46. MSFS Performance Optimiser Test

AutoFPS includes an optional optimiser that may adjust:

CPU affinity.
Process priority.
Power plan.

The developer notes that this feature can cause stutters on some systems, particularly sound-related stutters, so it should be tested separately rather than enabled automatically.

Test:

AutoFPS dynamic settings only.
Performance Optimiser enabled.
Compare 1% lows.
Check audio.
Check frame times.
Keep it only if evidence supports it.

47. Long-Flight Stability

During a longer flight, record:

TLOD behaviour.
OLOD behaviour.
FPS.
RAM.
VRAM.
MainThread.
Settings restoration.
App connection.
Any crashes.

Check at:

Departure.
Cruise.
Descent.
Landing.
After returning to the main menu.

Confirm that the original simulator settings return after the session.

48. Common Problems

AutoFPS Cannot Attach to MSFS

Check:

Simulator fully loaded.
Same Windows permission level.
Antivirus blocking.
Correct application version.
Restart AutoFPS after reaching the main menu.

The developer recommends restarting AutoFPS after MSFS reaches the main menu and checking permissions or security exclusions when attachment fails.

Compatibility Test Failed

Check:

Current AutoFPS release.
Recent Sim Update.
Unsupported simulator build.
Manually edited UserCfg.opt.
Graphics values outside normal MSFS menu ranges.
Incorrect simulator version.

The application may disable itself when safe settings locations cannot be verified.

FPS Target Is Never Reached

Possible causes:

Target too high.
GPU limitation.
Excessive traffic.
Premium scenery.
Complex aircraft.
Minimum TLOD too high.
Other settings already too demanding.

Reduce the target rather than forcing the lowest possible visual settings.

TLOD Changes Too Often

Try:

Lower sensitivity.
Smaller adjustment steps.
A tolerance-based method.
Narrower TLOD range.
More realistic target FPS.

Visual Popping Is Excessive

Try:

Higher minimum LOD.
Lower maximum LOD.
Narrower range.
Slower adjustment behaviour.
Reduced airport workload.
Lower target FPS.

Audio Stutters

Disable the optional MSFS Performance Optimiser and retest.

Settings Keep Reverting

AutoFPS is still active and controlling the same settings.

Exit AutoFPS or return to the simulator main menu before changing defaults.

AutoFPS Causes Worse Smoothness

Reset AutoFPS configuration.

Then test:

Non-Expert Mode.
IFR profile.
Auto Target FPS.
Performance Optimiser disabled.
Default airport.
No traffic.

Advanced values may be unsuitable for the system.

Student Practical Assignment

Install, Configure and Benchmark AutoFPS

Part 1 – Installation

AutoFPS version:

Download source verified: Yes / No

Security scan completed: Yes / No

Simulator: MSFS 2020 / MSFS 2024

Simulator detected correctly: Yes / No

Expert Mode initially disabled: Yes / No

Part 2 – Configuration

Flight type: IFR / VFR

Target mode: Manual / Auto / Fixed

Target FPS:

TLOD minimum:

TLOD maximum:

OLOD minimum:

OLOD maximum:

Frame Generation: On / Off

MSFS dynamic settings: On / Off

Performance Optimiser: On / Off

Part 3 – Test Flight

Use one complete benchmark route.

Record:

Departure airport.
Aircraft.
Weather.
Traffic.
Cruise altitude.
Arrival airport.

Part 4 – Performance Results

Measurement	AutoFPS Off	AutoFPS On
Average FPS
1% Low
0.1% Low
MainThread status
GPU utilisation
VRAM usage
Lowest TLOD
Highest TLOD
Lowest OLOD
Highest OLOD
Approach FPS
Touchdown FPS
Visual popping

Part 5 – Airport Comparison

Test:

Small airport.
Medium airport.
Premium hub.

Record

Airport	AutoFPS Off	AutoFPS On	Visual Quality
Small
Medium
Premium

Part 6 – Final Assessment

Answer:

Was the target realistic?
Did 1% lows improve?
Did MainThread performance improve?
Was visual popping acceptable?
Did Frame Generation behave correctly?
Did the app restore the original settings?
Did another performance utility conflict?
Is AutoFPS beneficial for this system?

Student Checklist

Official download source used.

Application scanned.

Correct simulator detected.

MSFS 2020 setup understood.

MSFS 2024 compatibility checked.

Update procedure understood.

Removal procedure understood.

IFR and VFR profiles understood.

Realistic target FPS selected.

Manual, Auto and Fixed modes understood.

Frame Generation considered.

TLOD minimum configured.

TLOD maximum configured.

OLOD behaviour tested.

Ground and cruise behaviour reviewed.

CPU limitation identified.

GPU limitation identified.

AutoFPS on/off comparison completed.

Average FPS recorded.

1% lows recorded.

MainThread monitored.

Visual popping reviewed.

Premium-airport test completed.

Dynamic-settings conflicts checked.

Other automation utilities disabled.

Original simulator settings restored.

Lesson Summary

You have now installed, configured and tested AutoFPS with Microsoft Flight Simulator 2020 or Microsoft Flight Simulator 2024.

Remember:

AutoFPS does not create free performance; it trades selected visual settings for more consistent smoothness.
Use only the official GitHub release.
The current unified application supports both MSFS 2020 and MSFS 2024.
Begin in Non-Expert Mode.
Choose IFR or VFR based on the type of flying.
Select a target the computer can realistically achieve.
Fixed Target FPS is only for a genuinely locked frame rate.
Frame Generation output is not the same as native FPS.
Terrain LOD mainly affects CPU and MainThread load.
Object LOD strongly affects airports and dense scenery.
A wider dynamic range may improve performance but increase visual popping.
The most important test is usually descent and approach into a demanding airport.
AutoFPS makes traditional benchmarking harder because graphics settings change during the run.
Record the minimum and maximum values used, not just FPS.
Do not run multiple dynamic-performance tools together.
Do not manually change controlled MSFS settings during an active AutoFPS flight.
Confirm that original simulator settings are restored after closing.

Knowledge Check

What is the main purpose of AutoFPS?
Where should the application be downloaded from?
Why may Windows warn about the installer?
Is AutoFPS installed in the Community Folder?
How does AutoFPS support both MSFS 2020 and MSFS 2024?
What is the difference between IFR and VFR profiles?
What makes a target FPS realistic?
What is Auto Target FPS?
When should Fixed Target FPS be used?
What is the difference between native and generated FPS?
Why does Terrain LOD strongly affect MainThread performance?
What does Object LOD influence?
Why can dynamic settings produce visual popping?
Why should the TLOD minimum not be set too low?
Why may AutoFPS provide limited benefit when strongly GPU limited?
Why is approach testing more valuable than cruise testing?
Why is benchmarking AutoFPS more difficult than benchmarking fixed settings?
Why should multiple dynamic-performance utilities not be used together?
What should be done if AutoFPS worsens smoothness?
What evidence confirms that AutoFPS is correctly configured?

1 2 3 4 5 6 7 ADD-ON Masterclass