Learn how Fenix A320 shared cockpit works in MSFS 2020, what both pilots need, how to set up YourControls, and how to fix sync problems.
The Fenix A320 does not include native shared-cockpit support in Microsoft Flight Simulator 2020. On PC, two pilots can use the third-party YourControls utility with a compatible Fenix profile, matching software versions and identical aircraft states. This is an unofficial workaround, so complete system synchronisation is not guaranteed.
What do both pilots need?
Both pilots need separate PC installations of MSFS 2020, the Fenix A320 and the same YourControls release and aircraft profile. This method does not work on Xbox because the Fenix aircraft and external shared-cockpit utility require PC software.
- The same MSFS 2020 build
- The same Fenix A320 build, airframe variant and engine option
- A YourControls profile compatible with that Fenix build
- The same navigation-data cycle where possible
- A network connection that permits the host and guest to communicate
- A separate voice channel for crew coordination
Each participant must have a valid, working Fenix installation. If either pilot has not installed the aircraft yet, follow our Fenix installation and desktop-component checklist before attempting shared cockpit.
How do you set up Fenix A320 shared cockpit?
The most reliable method is to match both installations first, load identical aircraft states and connect before either pilot begins the cockpit setup.
- Compare software versions. Confirm that MSFS 2020, the Fenix A320, YourControls and the selected Fenix profile match on both computers. A profile made for an older aircraft build can lose access to switches or system variables after an update.
- Load the same aircraft configuration. Select the Fenix A320 with the same engine option and spawn at the same airport and stand. Match the panel state, fuel, payload, weather, time and failures. A matching livery is normally optional unless it changes the aircraft configuration.
- Check the Fenix desktop component. Make sure the aircraft has fully initialised on both computers before connecting. Do not continue if either pilot has blank displays, missing systems or an aircraft that has not finished loading.
- Select the same YourControls profile. The host creates a session using the compatible Fenix profile, and the second pilot joins with the supplied connection details. Our complete YourControls hosting and joining procedure covers the general network and control setup.
- Assign control authority. Decide who is pilot flying and who is pilot monitoring. Only the pilot with control should provide active pitch, roll, yaw and throttle inputs; duplicate hardware inputs can make controls flicker or snap back.
- Run a cockpit sync check. Test the battery, an exterior light, an FCU selector and a flight-control input. Both pilots should confirm every change before programming the MCDU or starting the engines.
Do you need the same MSFS multiplayer session?
No. YourControls supplies the cockpit connection; ordinary MSFS multiplayer places each participant in a separate aircraft rather than one shared Fenix cockpit.
Normal multiplayer can remain disabled. If it is enabled while both pilots occupy the same stand, overlapping aircraft or collision effects may appear. Our explanation of how standard MSFS multiplayer differs from shared cockpit covers that distinction.
Which Fenix systems synchronise?
Synchronisation depends on the selected profile rather than the Fenix aircraft alone. Basic flight controls, many panel switches, lights and FCU actions can be shared when the profile maps their variables correctly, but the entire aircraft state should not be assumed to match automatically.
The EFB, simulator menus, ground services, failures and some MCDU or externally calculated states may remain local. We recommend that one pilot performs MCDU programming and aircraft setup while the other verifies each page. Both pilots should independently confirm the route, fuel, performance data and active autopilot modes before departure.
Why is the Fenix A320 not synchronising?
Most Fenix shared-cockpit faults come from mismatched versions, different starting states or both pilots sending hardware inputs at once.
| Problem | Likely cause | Fix |
|---|---|---|
| Controls move on only one computer | Different profile or software version | Compare exact versions, reload the same profile and reconnect both pilots. |
| Switches flicker or snap back | Conflicting controller bindings | Centre unused axes, disable duplicate toggle assignments and give one pilot control authority. |
| Engines or displays disagree | Different initial states or connection made too late | Reload both aircraft into the same panel state and connect before cockpit preparation. |
| The guest cannot connect | Firewall, router or addressing problem | Permit the utility through the firewall and verify the host details using the documented connection method. |
| MCDU or EFB pages differ | The relevant state is not covered by the profile | Use one pilot for data entry and manually match any local pages or values. |
| Fenix systems are blank or unresponsive | Aircraft installation or desktop-component fault | Resolve the underlying aircraft problem before reconnecting. |
If the aircraft itself will not initialise, work through our Fenix loading, update and desktop-component checks. A Fenix update can also break an older YourControls profile even when the aircraft works normally in solo flight; in that case, use a profile explicitly compatible with the installed build.
What crew workflow works best?
A disciplined division of duties reduces desynchronisation and makes faults easier to identify.
- Let one pilot perform the initial cockpit and MCDU setup.
- Keep only the pilot flying's primary flight controls active.
- Use verbal call-outs before changing the FCU, radios or system panels.
- Test control transfer on the ground and again at a safe altitude.
- Avoid transferring control during take-off, landing or while correcting a sync fault.