Integrate FSHud with AIG Traffic Controller in MSFS using the right launch order, traffic settings and fixes for duplicate or unmanaged AI aircraft.
To integrate FSHud with AIG Traffic Controller in Microsoft Flight Simulator, install AIG aircraft through AI Manager, connect AIGTC to the running simulator, enable its third-party/API access if your build exposes that option, then start FSHud and select AIG as the traffic source. Disable every other traffic injector and the simulator’s own ATC.
This is a PC-only arrangement for supported editions of MSFS 2020 and MSFS 2024. FSHud and AIGTC are external Windows applications, so they cannot be used with the Xbox or PlayStation console releases.
What does each application do?
AIG and FSHud perform different jobs: AIG supplies and injects the aircraft, while FSHud provides ATC instructions and traffic sequencing.
| Component | Job |
|---|---|
| AIG AI Manager | Installs airline flight plans, aircraft models and liveries, normally through the OCI system. |
| AIG Traffic Controller | Connects to MSFS and injects the installed AIG traffic. |
| FSHud | Provides ATC for your flight and manages compatible AI movements, clearances and sequencing. |
| MSFS | Renders the aircraft and supplies the airport’s parking, runway and taxiway network. |
FSHud does not replace missing AIG models, liveries or schedules. Complete our AIG installation and connection checks before trying to join the two applications.
How do I connect FSHud to AIGTC?
- Install and verify the AIG content. Open AI Manager and confirm that the required airlines, flight plans and aircraft have been installed. Run AIGTC by itself once and check that it can read the OCI database.
- Remove competing traffic sources. Turn off MSFS live and offline AI traffic, set static ground-aircraft density to zero, and close every other injector. A mistake we see constantly is running two injectors because only one appears to be producing aircraft at first.
- Load into MSFS. Start a flight at the gate and wait until the aircraft and scenery are fully loaded. Starting external utilities from the main menu can leave them waiting for a simulator session that does not yet exist.
- Connect AIG Traffic Controller. Start AIGTC and wait for its simulator-connected indication. Leave traffic injection stopped for the moment. If that AIGTC release includes an API or third-party application option, enable it; some releases expose the interface automatically and have no separate switch.
- Start FSHud. Select MSFS and choose AIG or AIGTC as the external traffic provider where a provider selector is available. Enable FSHud’s AI traffic management option. Builds that detect AIGTC automatically should show both the simulator and traffic provider as connected.
- Load the same route into FSHud. The route used by FSHud should match the route in the aircraft’s flight-management system. This controls ATC handling of your aircraft; it does not install or generate AIG airline schedules.
- Begin traffic injection once. Start AIG traffic only after FSHud is connected, initially at a modest density. In integrations where FSHud starts AIG traffic through the API, use that control instead of also pressing AIGTC’s injection button. There must be one injection command, not two.
Keep FSHud as the only ATC application issuing instructions. Our comparison of MSFS ATC systems explains why combining native ATC, FSHud and another ATC utility leads to contradictory runway and altitude instructions.
Which MSFS traffic settings should I use?
Native traffic should be disabled because AIGTC is supplying the aircraft externally.
| Setting or application | Recommended arrangement |
|---|---|
| MSFS live traffic | Off |
| MSFS offline AI traffic | Off |
| Ground aircraft density | Zero, to prevent untracked static aircraft occupying AIG parking stands |
| Traffic injector | AIGTC only |
| ATC system | FSHud only |
| AIG traffic density | Start low, then raise it after confirming stable sequencing and performance |
Setting native traffic to off does not normally block aircraft injected through the external connection. Multiplayer aircraft are separate: FSHud cannot command another human pilot, even when that aircraft appears near its controlled AI traffic. If you are still choosing a source, our comparison of compatible MSFS traffic injectors covers why injectors should never be stacked.
How do I know the integration is working?
The integration is working when AIGTC reports a simulator connection, FSHud recognises the AIG traffic source, and injected aircraft receive FSHud sequencing rather than merely appearing at gates.
- Only one copy of each scheduled aircraft appears.
- FSHud lists or recognises nearby AIG flights with plausible airline callsigns.
- Departures hold, taxi and enter the runway according to FSHud’s traffic flow.
- Arrivals are sequenced or instructed to hold rather than landing independently through other traffic.
- Your own clearance follows the route loaded into FSHud.
Correct liveries alone do not prove that FSHud is connected; they only prove that model matching found AIG content.
Why is AIG traffic visible but FSHud not controlling it?
Visible but unmanaged traffic usually means AIGTC injected the aircraft before FSHud established its traffic-provider connection.
- Wrong launch order: remove the injected traffic, connect AIGTC and FSHud, then inject again. Restarting all three components in the order MSFS, AIGTC, FSHud is often quicker than trying to recover a stale connection.
- API connection unavailable: check the AIGTC third-party or API option if that build provides one. Confirm that the installed FSHud and AIGTC releases support the same simulator edition.
- Different permission levels: run both utilities under the same Windows privilege level. Running one normally and the other as administrator can interfere with communication.
- Security software blocking local communication: allow both applications through the relevant Windows security prompts. Do not disable security software wholesale.
- Duplicate aircraft: disable native live traffic, offline traffic, static ground aircraft and any second injector. Closing a second injector may not remove aircraft it already created, so restart the flight or clear existing traffic.
- Generic or missing models: repair the relevant OCI packages and confirm AIGTC can see the model library. Our MSFS model-matching and airline-livery checks cover this side of the setup.
- Aircraft stuck on the ground: lower traffic density first. Broken taxi links, unsuitable parking stands or runway data in an airport add-on can also trap AI traffic; neither FSHud nor AIGTC can fully repair a faulty airport ground network.
- Poor frame rate or delayed instructions: reduce AIGTC’s aircraft count or injection radius. Lowering graphics settings alone does not remove the simulation load created by large numbers of AI aircraft.
Does FSHud replace AIG Traffic Controller?
No. In this integration, AIGTC remains the traffic source and injector, while FSHud supplies ATC and sequencing. Keep AI Manager as the content manager, AIGTC as the single injector and FSHud as the single ATC system; that division avoids most duplicate, silent and unmanaged-traffic problems.