Install XPFW A320 AI traffic in FS2004 correctly, including aircraft folders, repaint entries, traffic BGL placement and missing-aircraft fixes.
To install XPFW A320 AI traffic in FS2004, place the complete A320 aircraft folder in FS2004\Aircraft, add any supplied repaint entry to aircraft.cfg, and put the traffic .bgl in an active scenery folder—normally Scenery\World\scenery. If no traffic BGL is included, you must create and compile AI flight plans.
What is actually in the XPFW download?
XPFW A320 downloads do not all contain the same components, so inspect the extracted archive before copying anything. The included files determine which installation steps you need.
| Files in the archive | What they mean |
|---|---|
aircraft.cfg, an .air file, and model/texture folders | A complete aircraft package that belongs in the FS2004 Aircraft folder. |
A texture folder and a [fltsim.x] entry | A repaint only. The matching XPFW A320 base model must already be installed. |
A traffic .bgl | A compiled AI schedule that belongs in an active scenery folder. |
Aircraft.txt, Airports.txt and FlightPlans.txt | Source files that must be compiled before FS2004 can use the schedules. |
An all-in-one package may contain both the aircraft and a compiled traffic file. Our complete FS2004 AI traffic installation checklist explains how those two parts work together.
How do I install the aircraft and traffic files?
- Extract the archive outside FS2004. Read its supplied documentation and keep the original archive as a backup. Copying directly from a compressed folder makes nested directories and missed files harder to spot.
- Install the complete aircraft. Copy the folder containing
aircraft.cfgintoFS2004\Aircraft. The finished structure should resembleFS2004\Aircraft\XPFW_A320\aircraft.cfg, notFS2004\Aircraft\XPFW_A320\XPFW_A320\aircraft.cfg. - Add the repaint if it is livery-only. Copy its texture folder into the existing XPFW A320 folder, back up
aircraft.cfg, and append the supplied[fltsim.x]block. Changexto the next consecutive number without leaving a gap. Do not replace the complete configuration with a small repaint text file. - Check the configuration references. The
sim=value must match the base name of the installed.airfile. Themodel=andtexture=values must point to the corresponding suffixed folders, while eachtitle=value must be unique. - Install the compiled schedule. Copy the supplied traffic
.bgltoFS2004\Scenery\World\scenery, or another scenery folder already enabled in the Scenery Library. Restart FS2004 after adding or replacing a traffic file. - Compile source schedules when necessary. Plain-text aircraft, airport and flight-plan lists are not loaded directly by FS2004. Use a Traffic Tools-compatible compiler; our guide to building and compiling FS2004 AI schedules covers the required structure.
- Enable airline traffic. Set FS2004's airline traffic density above zero, load an airport used by the schedule, and choose a time close to a listed departure or arrival.
A traffic BGL is not a normal saved flight plan and should not be placed with personal .PLN files. See the difference between a saved FS2004 flight plan and an AI traffic file if the package contains both types.
Why does the XPFW A320 not appear in FS2004?
The most common cause is installing only the aircraft model without a compiled schedule that calls it. AI aircraft do not generate their own flights merely because their folders are present.
- Repaint without the base model: a texture-only download cannot supply the required model or
.airfile. Install the exact XPFW A320 variant named by the repaint documentation. - Incorrect aircraft title: the aircraft name referenced by the traffic plan must match the relevant
title=line inaircraft.cfgexactly. - Broken folder structure: FS2004 must find
aircraft.cfgdirectly inside the aircraft's main folder, not beneath an extra wrapper directory. - Inactive or misplaced BGL: confirm that the file is inside an enabled scenery area's
scenerysubfolder and was compiled for FS2004. - Traffic density set to zero: raise airline traffic density temporarily while testing.
- No suitable parking: the scheduled airport may lack a large enough free gate, causing the aircraft not to spawn or to disappear after landing.
- White or missing textures: compare
texture=with the texture folder's suffix and confirm that the repaint was made for that exact XPFW model.
Test with one known airport, route and scheduled time rather than searching randomly. If it still fails, follow our diagnostic checks for missing FS2004 AI aircraft to isolate title, schedule, BGL and parking faults.
Does the A320 need to appear in Select Aircraft?
No. An AI-only XPFW A320 may be omitted from FS2004's aircraft selection menu yet still work correctly as traffic.
AI models also may not include a usable panel, sound set or player-aircraft flight dynamics. Those components are unnecessary for scheduled traffic. If the package uses a detailed flyable model rather than an AI-optimised one, large numbers of A320s can reduce performance at busy airports; lower traffic density or reduce the number of scheduled examples if that occurs.