How do I fix AutoFPS not connecting or starting in MSFS?

AutoFPS usually fails to start or connect to Microsoft Flight Simulator because the wrong simulator version is selected, it was launched from an incomplete archive, Windows blocked a file, SimConnect is unavailable, or another tuning utility is interfering. Extract a fresh copy, select the correct MSFS version, start the simulator first, then test SimConnect.

What does the AutoFPS symptom mean?

The point at which AutoFPS fails usually identifies the cause.

How do I fix AutoFPS not connecting to MSFS?

A clean, correctly matched installation fixes most AutoFPS startup and connection failures.

1. Confirm that you are using the PC version. AutoFPS is an external Windows utility and cannot run alongside Microsoft Flight Simulator on Xbox Series X|S, PlayStation 5 or PS5 Pro.
2. Close every related process. Exit MSFS, AutoFPS and any other dynamic LOD or automatic graphics-setting utility. Check Task Manager for an AutoFPS process left running in the background, then restart Windows if necessary.
3. Use a compatible AutoFPS build. The release must explicitly support your simulator generation and installed simulator update. An older MSFS 2020 build may not recognise MSFS 2024, while a simulator update can temporarily require a revised AutoFPS release.
4. Extract the complete archive. Do not run AutoFPS from inside a ZIP file or copy only its executable. Extract every supplied file into a simple, writable local folder rather than a protected system or synchronised location.
5. Check Windows security. Open the downloaded archive's Properties and use Unblock if that option appears before extracting it again. Check Windows Security protection history for quarantined AutoFPS components, but restore or allow a file only when the archive came from the project's trusted distribution source. Do not disable security protection globally.
6. Install the required runtime. If AutoFPS reports a missing framework or closes immediately, install or repair the Windows desktop runtime specified in that AutoFPS release's documentation. Avoid guessing the runtime version or copying DLL files from unrelated downloads.
7. Use the correct launch sequence. Start MSFS and wait until it reaches the main menu. For a decisive test, load a default aircraft into a simple flight and wait until the cockpit is fully active before starting AutoFPS. Where AutoFPS offers a simulator selector, choose MSFS 2020 or MSFS 2024 correctly; where it detects the simulator automatically, confirm the detected version in its status or log.
8. Match permission levels. Run both MSFS and AutoFPS normally first. If one has been forced to run as administrator, either remove that setting or test both at the same privilege level. Running AutoFPS permanently as administrator should not be necessary.
9. Reset AutoFPS without deleting your backup. Use its reset-to-default option if the window opens. If it does not, back up and rename its configuration file or settings folder, which may sit beside the executable or in the Windows user profile depending on the build, then let AutoFPS create clean settings.
10. Test with no competing tuner. Do not run AutoFPS beside another tool that changes terrain LOD, object LOD, clouds or the same simulator memory values. Two tuners can fight over settings, produce oscillation or make a successful connection appear ineffective.

Once it connects, apply conservative targets before changing every limit. Our AutoFPS configuration and launch-timing guidance covers simulator selection, sensible targets and the settings that commonly prevent the utility from behaving as expected.

How do I tell whether SimConnect is the problem?

SimConnect is the likely fault when AutoFPS opens normally but remains disconnected after a flight has loaded, especially if other local companion tools also cannot see MSFS.

MSFS supplies SimConnect, so installing random legacy DLL files is not the first fix. Restart the simulator and Windows, remove conflicting utilities, then test another known SimConnect-based tool if one is already installed. If every tool fails, follow our SimConnect installation and repair checks.

If other SimConnect tools work but AutoFPS does not, SimConnect itself is probably healthy. Concentrate on the AutoFPS build, selected simulator, blocked files and configuration. Router port forwarding is not required for a local AutoFPS connection; only investigate firewall or security rules when their logs show that the executable was blocked.

Why does AutoFPS connect but not improve frame rate?

A connected AutoFPS cannot create performance that the underlying PC and simulator workload cannot supply.

• Set a target frame rate your system can approach without AutoFPS, rather than a target far above its normal performance.
• Confirm that automatic adjustment is enabled and that minimum and maximum values are not pinning terrain LOD, object LOD or clouds at one value.
• Load into an active flight before judging the displayed values; menus and loading screens are not a useful test.
• Reduce heavy AI traffic, airport detail or demanding add-ons when the simulator is limited by the main thread.
• Lower resolution or GPU-heavy settings when GPU utilisation or VRAM is the constraint. AutoFPS cannot compensate for every graphics bottleneck.

Establish a stable baseline using our MSFS 2024 performance troubleshooting steps, then enable AutoFPS and compare the same aircraft, airport, weather and camera view. If performance only deteriorates after several hours, investigate the long-flight workload rather than treating it as an AutoFPS startup fault.

Can AutoFPS run on Xbox or PlayStation?

AutoFPS works only as a companion application on a Windows PC; consoles cannot install or run its executable.

This applies to MSFS 2020 on Xbox and MSFS 2024 on Xbox Series X|S, PlayStation 5 and PS5 Pro. Console users must tune the simulator's available settings and traffic options instead.