Set up GSX Pro with the FlyByWire A32NX in MSFS, including aircraft profiles, flyPad sync, doors, boarding, fuelling and common fixes.
Yes. GSX Pro works with the FlyByWire A32NX in Microsoft Flight Simulator 2020 and 2024 on PC. Use an A32NX-specific GSX aircraft profile, enable the required GSX synchronisation options in the flyPad, and let one system control boarding, loading and fuelling. GSX cannot run on Xbox or PlayStation.
Which MSFS versions support GSX and the A32NX?
| Platform | Compatibility | What to check |
|---|---|---|
| MSFS 2020 on PC | Supported | Keep GSX Pro, Couatl and the A32NX updated. |
| MSFS 2024 on PC | Supported | Use builds intended for MSFS 2024 rather than manually copying old packages. |
| Xbox Series X|S | Not supported | GSX depends on external Windows software. |
| PlayStation 5 | Not supported | Console installations cannot run GSX or Couatl. |
How do I set up GSX Pro for the FlyByWire A32NX?
- Install or update the A32NX. Confirm the aircraft loads and its flyPad works before adding GSX to the equation. Our FlyByWire A32NX package information covers the aircraft and its installation context.
- Install and update GSX Pro. Its simulator packages must be linked to the active Community folder, and the Couatl engine must start alongside the simulator. Follow our full GSX installation and base-configuration procedure if the toolbar menu or Couatl is missing.
- Load the A32NX at a parking stand. Start at a gate rather than on the runway, then set the parking brake, shut down the engines and switch off the beacon before requesting ground services.
- Check the active aircraft profile. Open GSX's aircraft customisation interface and confirm that it recognises the FlyByWire aircraft, not the stock A320neo. Inspect the passenger doors, cargo doors, catering points, fuel connection and pushback reference position.
- Install a suitable profile if necessary. An additional profile is not required when GSX's supplied configuration already aligns everything correctly. If vehicles stop in the wrong places or GSX requests the wrong doors, use an A32NX-specific profile and follow the correct GSX aircraft-profile installation and selection process.
- Configure flyPad synchronisation. In the flyPad settings, locate the options containing GSX; their exact position can change between A32NX builds. Enable payload or fuel synchronisation only when GSX is going to control that operation.
- Request services through GSX. Use its toolbar menu for boarding, baggage, catering, refuelling and pushback. Set the planned passenger, cargo and fuel figures before boarding begins rather than changing targets midway through the process.
Should GSX or the flyPad control loading?
Choose one system as the authority for each operation; starting the same job in both is the most common cause of stuck boarding, mismatched weights and duplicate ground equipment.
| Desired result | Recommended control method |
|---|---|
| GSX boarding changes the aircraft payload | Enable GSX payload synchronisation and start boarding from GSX. |
| GSX passengers are visual only | Disable payload synchronisation and manage the actual load through the flyPad. |
| GSX refuelling changes fuel quantity | Enable the available GSX fuel-sync option and request fuel through GSX. |
| Fuel is preloaded or managed in the flyPad | Leave GSX fuel sync off and do not request a second refuelling process. |
The flyPad can also control doors, payload, fuel, external power and native ground equipment. Our guide to the A32NX flyPad ground-service controls explains those functions; avoid spawning its stairs, catering vehicles or ground-power unit when GSX is providing the same equipment.
Does GSX automatically open the A32NX doors?
Door behaviour depends on the GSX profile, its automation settings and the A32NX build. Some combinations operate mapped doors automatically; others display a request such as Open Exit 1. In that case, open the corresponding passenger or cargo door from the flyPad.
If GSX asks for an implausible door or a catering truck drives to the wrong side of the aircraft, correct the aircraft profile rather than moving every service point manually. A profile made for the stock A320neo is not interchangeable with one made for the FlyByWire A32NX.
Why is GSX boarding stuck or positioned incorrectly?
- GSX has selected the wrong aircraft profile: verify the aircraft name shown in its customisation page. A repaint package can occasionally affect profile matching.
- Boarding is waiting for a door: connect the jetway or stairs and open the mapped forward passenger door. Cargo loading may also wait for the appropriate hold door.
- Payload never changes: enable GSX payload synchronisation, then restart boarding. Do not run the flyPad loader simultaneously.
- Vehicles are misaligned: remove an obsolete duplicate profile and load the configuration intended specifically for the A32NX variant being flown.
- Services are unavailable: park fully on the stand, apply the parking brake, stop the engines and turn off the beacon. Some operations also require chocks or a suitable service point.
- Two jetways or sets of stairs appear: do not call the same equipment through GSX, the simulator's default ground-services menu and the flyPad. Static scenery jetways cannot be animated by GSX.
- The GSX menu is absent: confirm Couatl is running and that the GSX packages are linked to the Community folder used by that particular MSFS installation.