Use the FlyByWire A32NX with YourControls in MSFS: match builds and profiles, connect both pilots, transfer control and fix cockpit sync problems.
To fly the FlyByWire A32NX with YourControls in Microsoft Flight Simulator, both pilots need the same simulator generation, A32NX build, YourControls release and aircraft profile. Load the same parking stand and aircraft state, connect before programming the MCDU, give one pilot control, then verify overhead, FCU and flight-plan synchronisation before pushback.
How do you set up an A32NX shared cockpit?
Set up both PCs as matching copies before either pilot starts cockpit preparation. YourControls is an external shared-cockpit utility rather than MSFS multiplayer, so each pilot needs it running on Windows; our full PC installation, hosting and joining instructions cover the general network setup.
- Confirm the A32NX works alone: Load it in Microsoft Flight Simulator on each PC and check that its displays and systems initialise without errors. MSFS 2020 users can consult the A32NX package and Community-folder notes; for the newer simulator, use the correct A32NX installation route for MSFS 2024.
- Match both installations: Use the same MSFS generation, A32NX branch and build, YourControls release, aircraft definition and navigation-data set. Do not mix stable, development or experimental A32NX builds.
- Choose the same starting situation: Select the same airport, parking stand and aircraft state, preferably cold and dark. Match the time and weather, and consider disabling MSFS multiplayer traffic so that neither pilot sees an overlapping duplicate aircraft.
- Load the aircraft: Let the A32NX finish initialising on both PCs, but do not configure fuel, payload, the EFB or the MCDU yet. State loaded before the connection may not be transferred completely.
- Connect YourControls: One pilot hosts and the other joins. Load or confirm the A32NX-specific aircraft profile on both sides rather than relying on a generic airliner definition.
- Build one shared state: Have one pilot perform the initial cockpit setup while the other watches for matching changes. Compare battery and external-power indications, overhead switches, FCU values, trim, flap position and an MCDU page.
- Assign control: Decide who owns the flight-control and thrust axes. Use the YourControls hand-off when changing pilot flying, and do not begin pushback until the cockpit remains synchronised.
Which A32NX build and YourControls profile should you use?
Use an aircraft-specific profile that matches the exact A32NX branch installed on both computers. YourControls profiles depend on aircraft variables and events, which can change when FlyByWire updates the custom systems.
| Choice | When to use it | Main concern |
|---|---|---|
| Matching stable A32NX builds | Best choice when shared-cockpit reliability matters most | Both installations must still be on the same release |
| Matching development or experimental builds | Only when the available YourControls profile supports that build | Aircraft changes can break switch, display or system-variable synchronisation |
| Generic Airbus or default profile | Useful only for basic troubleshooting | It will not cover many A32NX-specific systems |
A common mistake we see is matching the branch name but not the actual aircraft build. If one pilot updated after the other, update both installations and restart MSFS before diagnosing the profile.
Does everything in the A32NX cockpit synchronise?
No. YourControls exchanges the events and variables defined by its aircraft profile; it does not stream one pilot’s entire simulator state or screen to the other.
With a compatible profile, the flight controls, FCU selections, autopilot modes, many overhead controls, flaps, landing gear and numerous MCDU key presses should be shared. Exact coverage depends on the aircraft and profile builds.
These items are more likely to remain local or require manual matching:
- EFB pages, preferences and some EFB-triggered actions
- Fuel, payload, chocks, doors and ground-service state
- Toolbar windows, cameras, audio and assistance settings
- Flight plans imported before the YourControls connection
- Weather, traffic and controller calibration
Nominate one pilot to manage the EFB, payload and ground services. If an action does not appear on the other PC, match it manually rather than repeatedly operating the control from both sides.
Why do the controls snap back or cockpit states disagree?
Persistent disagreement usually comes from mismatched builds, different starting states or two hardware devices sending competing inputs. Correct the cause before taxi rather than hoping the aircraft will resynchronise in flight.
| Symptom | Likely cause | Fix |
|---|---|---|
| A switch or lever immediately snaps back | The other pilot’s hardware, a duplicate binding or an assistance feature is sending the opposite input | Assign one control owner, remove conflicting bindings from the non-flying station and disable automated piloting assistance |
| Overhead or ECAM indications differ immediately | Different A32NX builds, profiles or initial aircraft states | Disconnect, reload the same state on both PCs and connect before cockpit setup |
| Thrust levers or autothrust behave differently | Throttle detents are calibrated locally and do not match | Apply the A32NX throttle-detent calibration procedure on each computer before swapping pilot flying |
| MCDU routes or ND displays disagree | The route was loaded before connection, or the navigation-data sets differ | Match the data, clear the route on both sides and have one pilot enter or import it after connecting |
| EFB, doors or chocks do not match | The function is local or absent from the selected profile | Let one nominated pilot command it, then reproduce the state manually on the other PC |
| The connection drops or never completes | Firewall permission, incorrect host details or different YourControls releases | Permit the application through the host firewall and recheck the release and connection details on both PCs |
How should two pilots divide A32NX duties?
Treat the session like a two-crew cockpit: one person owns the flight-control and thrust axes at a time, while the other handles agreed system tasks. Simultaneous commands are the quickest way to create a control fight.
- Brief who is pilot flying and who is pilot monitoring before engine start.
- Let one pilot initialise the MCDU and EFB instead of importing the route independently on both PCs.
- State FCU changes aloud and avoid turning the same knob simultaneously.
- Use a clear verbal hand-off before transferring control in YourControls.
- After every hand-off, confirm thrust, sidestick, rudder and autopilot status before continuing.
Can you use YourControls with the A32NX on console?
No. YourControls relies on a Windows desktop application and aircraft-profile files, so it cannot run on Xbox Series X|S, PlayStation 5 or PS5 Pro. Both crew stations must use compatible PC installations even though Microsoft Flight Simulator itself is available on those consoles.