Fix slow aircraft selection in FSX: Steam Edition by isolating bad add-ons, checking aircraft.cfg, gauges and textures, and resetting FSX safely.
Slow aircraft selection in FSX: Steam Edition is usually caused by a large add-on catalogue, malformed aircraft.cfg entries, damaged thumbnails, or an aircraft whose textures, panel gauges or aliases cannot load. Test a default aircraft, quarantine add-ons in batches, repair the culprit, then reset FSX’s configuration only if every aircraft remains slow.
Where is FSX spending the time?
The point at which FSX pauses identifies which files you need to investigate.
| Where the delay occurs | Most likely cause | First test |
|---|---|---|
| Opening the aircraft selection window | Too many aircraft or liveries, malformed configuration entries, or troublesome thumbnails | Temporarily remove third-party aircraft in batches |
| Changing the highlighted aircraft | Damaged or excessively large thumbnail.jpg files | Remove or replace the thumbnail in the affected variation |
| After pressing OK | Large textures, a bad model, missing panel or sound aliases, blocked gauges, or missing dependencies | Load a default FSX aircraft from the same airport |
| Every flight and aircraft loads slowly | Storage, security scanning, scenery, AI traffic, configuration damage or memory pressure | Test a simple default flight after restarting FSX |
If the aircraft eventually loads but the whole flight then becomes unstable or sluggish, check the wider flight-loading causes involving scenery, AI traffic and FSX’s 32-bit memory limit. Those are different from a slow aircraft catalogue.
How do I find the add-on causing slow aircraft selection?
The quickest reliable method is to isolate third-party aircraft by moving them outside every folder FSX scans.
- Back up the relevant files. Copy the aircraft folders and any
aircraft.cfgfiles before changing them. Do not edit the only copy of a payware or freeware package. - Close FSX completely. Find the active
SimObjects\Airplanesdirectory and any additional aircraft locations listed asSimObjectPathsin the active FSX configuration file. - Move half of the third-party aircraft elsewhere. Use a temporary folder outside the FSX installation and outside every configured SimObject path. Renaming a folder while leaving it under
SimObjects\Airplanesmay not stop FSX from scanning it. - Restart FSX and repeat the same test. If selection becomes fast, the culprit is in the removed group. If it remains slow, test the group still installed.
- Continue halving the suspect group. This finds one bad package much faster than testing a large collection individually.
- Retest from a cold start. Close and reopen FSX between meaningful tests so cached files do not disguise the result.
Keep the stock aircraft installed while testing because some add-ons alias their panels, sounds or other files. If selection stops responding completely or ends in a crash, use our checks for faulty gauges, missing dependencies and damaged add-on aircraft files.
What should I check inside the problem aircraft?
A problem aircraft should be checked for configuration references that point to missing, invalid or unreadable files.
- Variation entries: Each
[fltsim.x]section should have a uniquetitle. Keep the section numbering consecutive, beginning with[fltsim.0]. - Aircraft model: The
sim=value must match the aircraft’s AIR file name, whilemodel=must correspond to an existing model folder. - Panel, sound and texture folders: Values such as
panel=,sound=andtexture=refer to folder suffixes. A spelling error or missing folder can leave FSX searching for content that is not there. - Aliases and fallbacks: Panel, sound and texture configuration files may point to another installed aircraft. Confirm that the target aircraft and folder still exist.
- Thumbnails: Temporarily rename a suspect
thumbnail.jpg. FSX can display a placeholder when no thumbnail exists, so a damaged image need not be retained. - Panel gauges: A delay after pressing OK often comes from a legacy DLL gauge, a blocked module or a missing SimConnect dependency. Follow the FSX: Steam Edition SimConnect installation and repair procedure rather than downloading replacement DLL files from an unknown source.
- Textures: Very large or uncompressed texture sets increase loading time and memory use. Restore the package’s original texture files before attempting conversions, because unsuitable formats or missing alpha channels can create new faults.
Do not delete gauges merely to make the aircraft load faster; that commonly produces an empty or unusable virtual cockpit. If an edit makes a variation disappear, restore the backup and recheck its [fltsim.x] entry, folder suffixes and required files.
Can too many aircraft and liveries slow FSX down?
Yes, a large aircraft library can make FSX: Steam Edition spend noticeably longer enumerating variations and reading their configuration files and thumbnails.
Archive aircraft you rarely use outside the active SimObject paths. Removing complete packages is safer than deleting individual texture folders, especially where several aircraft share panels, sounds or gauges. The aircraft menu’s option to hide variations reduces visual clutter, but FSX may still have to parse the installed entries first, so it is not a substitute for reducing an oversized catalogue.
Why is every aircraft slow, including the default aircraft?
If default aircraft are also slow, test FSX’s global configuration, storage and security environment rather than repairing individual add-ons.
- Separate start-up delay from aircraft delay. If FSX is slow before reaching the main menu, use our diagnostic steps for slow FSX start-up.
- Generate a clean FSX configuration. Close FSX, back up and rename the active configuration file under
%APPDATA%\Microsoft\, then launch the simulator so it creates a new one. A standalone Steam installation and a system containing both boxed FSX and Steam Edition may use differently named FSX folders, so identify the active file by its modification time. - Test before restoring settings. A new configuration removes custom graphics options and SimObject paths. If it fixes the delay, reapply changes gradually rather than copying the old file over the new one.
- Verify the stock installation through Steam. File verification can restore damaged default FSX files, but it does not repair third-party aircraft or remove extra add-on files. Back up deliberate modifications to stock aircraft first.
- Check storage and antivirus activity. Thousands of small aircraft, gauge and texture files are slow to read from a struggling drive and may be scanned individually by security software. Keep FSX on healthy local storage; only exclude trusted, already-scanned simulator folders rather than disabling protection.
Restarting FSX temporarily clearing the problem after a long session points to memory pressure, especially with complex aircraft, dense scenery and heavy AI traffic. Graphics sliders, shader-cache deletion and scenery-index rebuilding rarely fix a delay confined to the aircraft selection window.