Skip to content
FSX & FSX: Steam Edition 5 min read

How do I configure AIFP for AI aircraft on another drive?

Adam McEnroe
In short

Configure AIFP to find FSX AI aircraft on another drive, refresh its aircraft list, match aircraft.cfg titles and fix missing traffic.

To use AI aircraft stored on another drive, add their parent folder to FSX's active SimObjectPaths list, then select the correct FSX installation in AI Flight Planner and rebuild AIFP's aircraft list. AIFP references each aircraft by its aircraft.cfg title; it does not store the aircraft's drive path in the traffic BGL.

How do I add an external AI aircraft folder to FSX?

FSX must be able to load the external aircraft before AIFP can assign it to traffic. Close FSX and AIFP, then configure the active FSX profile rather than moving the aircraft back into the simulator folder.

  1. Create a clean parent folder. For example, use D:\FSX_AI\Airplanes. Each aircraft package should sit directly below it, such as D:\FSX_AI\Airplanes\AIA_B737, with its aircraft.cfg, model and texture folders inside that package.
  2. Find the active FSX configuration file. A Steam-only installation commonly uses %APPDATA%\Microsoft\FSX\fsx.cfg. A computer with boxed FSX and Steam Edition installed side by side commonly gives Steam Edition its own FSX-SE profile and fsx_se.cfg. Edit the file belonging to the edition AIFP will target.
  3. Back up the configuration file. In its [Main] section, add the external folder using the next unused consecutive number. The syntax is SimObjectPaths.N=D:\FSX_AI\Airplanes, replacing N with the appropriate number. Do not duplicate an existing index.
  4. Save and start FSX once. Close it again before asking AIFP to rebuild its aircraft data. Keep the external drive letter fixed; a changed or disconnected drive makes the whole path unavailable.

Our explanation of FSX AI aircraft folders and configuration titles covers the package structure in more detail.

How do I make AIFP scan the new drive?

AIFP must target the same FSX edition whose configuration file contains the external path, and its existing aircraft list must then be refreshed.

  1. Select the target simulator. In AIFP's simulator setup or target selection, choose the correct boxed FSX or FSX: Steam Edition installation. If automatic detection found the wrong copy, browse to the correct FSX root folder.
  2. Rebuild the aircraft list. Open AIFP's aircraft list or aircraft editor and run its scan, collect or rebuild command; the precise wording differs between AIFP releases.
  3. Include the external parent folder if prompted. Select D:\FSX_AI\Airplanes, not an individual aircraft package. This should be the same parent folder recorded in SimObjectPaths.
  4. Select the aircraft by title. AIFP uses the value after title= in each [fltsim.x] section. The folder name, ui_type and atc_model are not substitutes for that title.
  5. Validate and compile the plan. Resolve any missing-aircraft warning before producing the traffic BGL.

AIFP itself may be installed on either drive. Only its selected simulator, aircraft search data and output destination matter. See our guide to aircraft assignments and compiled AIFP traffic files for the remaining flight-plan workflow.

Which folder should FSX and AIFP scan?

The correct search path is the directory whose immediate subfolders are individual aircraft packages.

Selected pathExpected result
D:\FSX_AI\AirplanesCorrect when each aircraft package is directly inside this folder.
D:\FSX_AIUsually too high if it contains another Airplanes directory rather than aircraft packages.
D:\FSX_AI\Airplanes\AIA_B737Too low for a library scan and limits discovery to one package.

Every title= value should also be unique across the installed library. Duplicate titles can make AIFP validation ambiguous and cause FSX to load a different variation from the one intended.

Why is the aircraft still missing after the AIFP rescan?

A missing aircraft after rescanning normally indicates the wrong FSX profile, bad folder nesting, a stale AIFP list or an unmatched title= value.

SymptomLikely fix
The aircraft is absent from AIFP's listConfirm the external drive is available, the parent folder is in the active configuration file and AIFP is scanning the correct FSX edition. Then rebuild the list again.
AIFP reports a missing aircraft titleCompare the plan's aircraft assignment with the complete title= value in aircraft.cfg, including spaces and punctuation. Do not use the package folder name.
The plan compiles but no traffic appearsCheck that the BGL is in an active scenery area, the AI traffic slider is above zero, and the flight is scheduled for the airport, day and time being observed. Our FSX traffic visibility checks cover those simulator settings.
FSX-format traffic disappears globallyA legacy FS2004-format traffic BGL may be suppressing FSX-format traffic. Isolate or recompile the older traffic file rather than changing the aircraft path.
The aircraft loads without the expected model or textureCheck its model=, texture= and related package entries. AIFP can resolve a valid title even when the aircraft package itself is incomplete.

Where should AIFP save the traffic BGL?

The compiled traffic BGL belongs in an active FSX scenery folder, not in the external AI aircraft directory. AIFP source files may be stored anywhere; at run time, FSX reads the traffic BGL and resolves its aircraft titles through the configured SimObjectPaths.

If the external library is moved again, update its path before rebuilding AIFP's list. The same dependency applies when moving FSX add-ons while preserving their path references.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members