Learn how to download and install AIG AI aircraft, liveries and flight plans for MSFS, FSX or Prepar3D, plus Traffic Controller setup and fixes.
To install AIG AI traffic on PC, download AIG AI Manager and Traffic Controller from the project’s official source, extract each tool to a writable folder, select your simulator, then use AI Manager’s One Click Installer to add airlines, aircraft models, liveries and schedules. In MSFS, run Traffic Controller to inject them.
What does an AIG traffic installation contain?
AIG traffic is a linked set of components rather than one aircraft pack. Installing a livery without its model and flight plan will not make an aircraft appear.
| Component | Purpose |
|---|---|
| AIG AI Manager | Downloads, installs, updates and checks flight plans, models and liveries. |
| One Click Installer (OCI) | Resolves the aircraft and repaint dependencies required by each selected airline. |
| AI aircraft and liveries | Provide the visible traffic models and airline colours. |
| Flight plans | Define routes, airports, days and departure times. |
| AIG Traffic Controller | Connects to Microsoft Flight Simulator and injects the installed schedules. |
Our explanation of how schedules, injectors and real-airline model libraries work together covers why all three content layers must be present. If you are still choosing a system, our comparison of Microsoft Flight Simulator AI traffic options explains why AIG offers detailed control but needs more preparation than simpler products.
How do I download and install AIG AI traffic?
Set up one airline as a test before attempting a large regional or worldwide installation.
- Confirm simulator support. AIG’s tools are Windows applications. Select the exact Microsoft Flight Simulator, FSX or Prepar3D profile offered by the installed tool version; do not force a different simulator profile if yours is absent.
- Download the official tools. Obtain AIG AI Manager and, for an injected MSFS installation, AIG Traffic Controller from the project’s official distribution source. Avoid repackaged copies because an outdated manager may request the wrong dependencies.
- Extract both downloads. Do not run either program from inside its ZIP archive. Use short, writable folders such as
C:\AIGTech\AIManagerandC:\AIGTech\TrafficController, rather thanProgram Filesor a cloud-synchronised folder. - Configure AI Manager. Start it normally, choose the correct simulator and review the detected simulator and OCI content paths. Microsoft Store and Steam installations can use different content locations, so correct a path that points to an old or unused Community folder.
- Install a test airline through OCI. Open the online flight-plan list, select an airline serving a familiar major airport and choose the OCI installation action. AI Manager should obtain the flight plan and resolve its required aircraft models and liveries.
- Complete manual dependency prompts. Some model or repaint authors do not permit fully automatic redistribution. If AI Manager requests an archive, download the exact package it identifies and select or place it where the prompt instructs. Do not rename, unpack or substitute the archive unless AI Manager specifically asks.
- Check the installation report. Resolve entries marked as missing, failed or outdated before opening the simulator. A flight plan marked as installed is not enough if one of its assigned aircraft models is absent.
- Configure MSFS traffic injection. Point Traffic Controller at the same OCI installation if it is not detected automatically. In MSFS, disable built-in live or offline AI traffic and set the ground-aircraft density to zero if you want AIG to be the only traffic source.
- Load and inject the traffic. Start MSFS, load fully into a flight, then open Traffic Controller. Wait for its simulator connection to be confirmed before starting injection. Do not run a second injector using the same schedules.
- Use compiled traffic in FSX or Prepar3D. In a legacy BGL-based setup, AI Manager installs the models and compiles or places the traffic schedules for the simulator to load at startup. Traffic Controller is not required for every such installation. Our guide to manual FSX model, repaint and traffic-BGL checks is useful when verifying those folders.
Do I need AIG Traffic Controller?
Traffic Controller is normally required for AIG’s injected schedules in Microsoft Flight Simulator, but it may be optional when FSX or Prepar3D loads compiled traffic BGL files directly.
| Installation | Traffic Controller requirement |
|---|---|
| MSFS injected AIG traffic | Normally required to connect and inject the OCI schedules. |
| FSX or Prepar3D BGL traffic | Usually not required; the simulator reads compiled schedules at startup. |
| Aircraft and liveries only | Not required, although no scheduled traffic appears without flight plans or another traffic source. |
Do not combine an injected copy and a compiled copy of the same schedule. That creates duplicate registrations, overlapping aircraft and competition for the same parking stands.
Why is AIG traffic not showing?
Missing traffic is usually caused by an incomplete dependency, the wrong content path, a controller that is not connected, or a second traffic system interfering with AIG.
- No simulator connection: load completely into the flight before injecting, then verify that Traffic Controller identifies the correct simulator session.
- Wrong OCI folder: confirm that AI Manager and Traffic Controller reference the same content library. An old installation on another drive can be detected instead.
- Incomplete aircraft package: repair or reinstall any model, livery or flight plan marked as failed. Blank, untextured or substituted aircraft usually indicate a missing model or texture dependency.
- No scheduled movement: AIG traffic follows installed timetables. Test at a major hub served by the airline and allow time for aircraft within the controller’s injection range to appear.
- Duplicate or static traffic: turn off MSFS live and offline AI sources and reduce its stock ground-aircraft setting to zero. Parked stock aircraft are not controlled by AIG and will never depart as part of its schedule.
- Traffic slider at zero: in FSX or Prepar3D, make sure the relevant airline traffic setting is above zero and that the compiled BGL is active.
- Legacy FSX traffic file: an old FS2004-format traffic BGL can suppress newer-format FSX schedules. Temporarily isolate older traffic files and restart the simulator.
- Insufficient parking: airports with too few compatible gates may reject or remove injected aircraft. Test the same airline at a larger default airport before blaming its model package.
Installing every available airline is not the best first step. Installed libraries mainly consume storage, while the number of active injected aircraft, the controller’s range and dense hub operations have the greater performance impact. Build the collection by region and increase active traffic gradually.
Can I install AIG AI traffic on Xbox or PlayStation?
No. AIG AI Manager and Traffic Controller are Windows desktop tools, so this installation method is PC-only. Xbox and PlayStation editions of Microsoft Flight Simulator cannot run the controller or accept ordinary PC Community-folder packages, even when the simulator itself is available on those consoles.