Fix GSX Pro with the Fenix A320 or PMDG 777 in MSFS by checking Couatl, aircraft profiles, variants, door control and parking state.
In Microsoft Flight Simulator, GSX Pro usually fails with the Fenix A320 or PMDG 777 because a stale profile overrides supplied integration, the wrong variant is matched, Couatl is disconnected, or the aeroplane is not ready for servicing. Update both add-ons, remove custom profiles, restart Couatl, and retest cold and dark at a gate.
GSX Pro requires its external Couatl program, so it is a PC add-on. It cannot run on the Xbox or PlayStation versions of Microsoft Flight Simulator.
How do I tell whether GSX, the aircraft or a profile is at fault?
The scope of the failure usually identifies the cause faster than reinstalling anything.
| Symptom | Likely cause | First check |
|---|---|---|
| GSX toolbar panel is missing with every aircraft | Couatl, installation, activation or package problem | Confirm Couatl is running and GSX is enabled for the correct simulator |
| GSX works with other aircraft but not the Fenix or PMDG | Aircraft profile, variant or aircraft integration mismatch | Remove custom aircraft profiles and update the aircraft |
| Vehicles use the wrong doors at every airport | Incorrect aircraft profile | Restore the GSX-supplied configuration for that aircraft |
| The problem occurs at only one gate or airport | Airport profile or scenery mismatch | Test at a default airport and another parking stand |
| GSX remains on “waiting for doors” or “waiting for parking brake” | Aircraft state or competing door control | Follow the prompt and stop the EFB, FMC or another add-on changing the same state |
| Only one livery fails | Poorly packaged livery or aircraft identity mismatch | Retest with a livery supplied with the aircraft |
How do I fix GSX with the Fenix A320 or PMDG 777?
- Establish the scope. Load a default airport and check whether the GSX toolbar menu opens with another supported aircraft. If it does not, this is a general GSX or Couatl fault rather than a Fenix or PMDG profile problem.
- Update GSX and the aircraft. Close Microsoft Flight Simulator, run the GSX installer or update tool, and verify that its packages target the simulator version you actually use. Update the Fenix A320 or PMDG 777 through its own manager as well, then restart the simulator.
- Disable downloaded aircraft profiles. Back up and temporarily remove the custom profile for the affected aircraft. A profile made before an aircraft update can override GSX’s newer supplied integration while retaining obsolete door names or positions. Our aircraft-versus-airport GSX profile instructions explain which type of profile controls each feature.
- Test the exact aircraft variant. A profile for one Fenix engine variant or one PMDG 777 model should not be assumed to match another. Use a livery included with that exact model for the first test; this eliminates repaints that alter package information incorrectly.
- Start from a valid ground state. Place the aircraft at a recognised gate with engines off, the parking brake or chocks set as requested, and electrical power available. If the Fenix displays are dead or the aircraft has not finished initialising, complete the Fenix A320 cold-and-dark power sequence before testing GSX.
- Restart Couatl. Use the available Couatl restart command, then reopen the GSX menu. After changing aircraft packages or profiles, a complete simulator restart is safer because some aircraft data is read only when the session loads.
- Remove competing ground-service add-ons. Temporarily disable other pushback, jetway or door-control tools. Test with no built-in tug already attached and no second program issuing door commands.
Which GSX profile should I remove?
Remove the aircraft profile when doors, cargo loaders, stairs or refuelling points are wrong at multiple airports. Remove or disable the airport profile only when the fault is confined to one airport, stand, jetway or pushback route.
A mistake we see constantly is deleting an airport profile to fix misplaced doors on the aeroplane. Airport profiles define stands and ground routes; aircraft profiles define service points on the airframe. Back up the file or package before removing it, and let GSX load its supplied configuration for the first clean test.
Why is GSX stuck waiting for doors or pushback?
GSX becomes stuck when its expected aircraft state does not match the state reported by the Fenix or PMDG systems. Read the exact GSX status line: a request for a door, parking brake, engine shutdown or tug release is a state problem, not a vehicle-position problem.
- Do not command the same doors from GSX and the aircraft’s EFB or FMC at the same time.
- If an automatic-door option is available, use one control method consistently rather than changing doors manually during boarding.
- Allow the aircraft to finish loading its panel state before requesting services.
- Cancel any active simulator pushback or other tug before starting GSX pushback.
- Do not edit door coordinates to fix a door-state detection failure; coordinates affect placement, not whether GSX reads a door as open.
For pushback, begin parked with the engines and brake in the state shown by the GSX prompt. Release the parking brake only when instructed; releasing it early can leave the sequence waiting or cause the tug to disconnect.
Does the fix differ between MSFS 2020 and MSFS 2024?
The simulator generation, GSX installation and aircraft build must agree. Do not assume that a Community-folder link, profile or aircraft package prepared for MSFS 2020 can simply be copied into MSFS 2024.
Our GSX compatibility breakdown for both simulator generations explains the package differences. If GSX fails across every aircraft in MSFS 2024, use the MSFS 2024 Couatl and package checklist instead of changing Fenix or PMDG profiles.
If a clean default-airport test works, restore custom liveries, aircraft profiles and airport profiles one at a time. If it still fails only with one aircraft after its custom profile has been removed, repair or update that aircraft’s integration; if it fails everywhere, repair GSX, its package links and Couatl rather than reinstalling the entire simulator.