Set up YourControls with the Fenix A320 in MSFS 2024, match both PCs, choose the right profile, divide crew roles and fix common sync problems.
To use YourControls with the Fenix A320 in Microsoft Flight Simulator 2024, both pilots need the PC version of MSFS 2024, matching Fenix and YourControls builds, and a compatible Fenix profile. Load the same flight, connect before touching the cockpit, place one pilot in control, then test control transfer and key systems before departure.
Does YourControls work with the Fenix A320 in MSFS 2024?
Yes, provided the installed YourControls profile explicitly supports the Fenix A320 build being used in MSFS 2024. Compatibility is profile-specific: seeing an A320 profile does not mean it supports every Fenix update, and a FlyByWire or unverified MSFS 2020 profile is not a safe substitute.
Both pilots need their own working Fenix installation and licence. Each PC must be able to load and operate the aircraft normally before YourControls is introduced; our Fenix installation and desktop-component checks cover that baseline.
Can Xbox or PlayStation pilots join?
No. YourControls requires a Windows application running alongside the simulator, so both shared-cockpit seats must use PCs. An Xbox Series X|S or PlayStation 5 session cannot form one side of the connection.
How do both pilots set up the Fenix shared cockpit?
Start with a normal YourControls connection, then apply the Fenix-specific matching and operating rules below. If hosting, joining or firewall configuration is unfamiliar, complete our YourControls network and shared-cockpit setup first.
- Match every important version. Both PCs should use the same MSFS 2024 update, Fenix aircraft build, YourControls release and Fenix profile. Select the same A320 engine and airframe variant; matching liveries are optional unless a livery changes the panel configuration.
- Use the same aircraft state. Choose the same airport, stand, time, weather preset and cold-and-dark state. Turn off assistance features that manipulate throttles, flight controls, checklists or aircraft systems.
- Remove likely conflicts. Temporarily disable cockpit modifications, hardware utilities or other tools that write to the same controls. Both pilots may keep their hardware connected, but only the pilot holding control should move flight axes.
- Load the cockpit on both PCs. Confirm the Fenix background components are running and the aircraft is fully loaded. Do not begin the electrical setup, import a route or change the EFB yet.
- Select the Fenix profile and connect. The host creates the YourControls session and the second pilot joins using the same profile. Connect while both aircraft are still in the same untouched state.
- Let the initial state settle. Give YourControls time to exchange the mapped variables. One pilot should then perform the first action, such as selecting the battery or external power, while the other watches for the same result.
- Test before doing the full setup. Check an overhead switch, FCU altitude, radio frequency, flap selection and control handover. Verify that the sidestick, rudder, thrust levers and autopilot do not jump when control changes.
- Build one agreed flight. Use the same route, AIRAC cycle, weights and fuel on both computers. Where the EFB remains local, enter or import matching data separately; our Fenix SimBrief setup instructions explain the aircraft-side import process.
If no compatible Fenix profile is available for the installed aircraft build, stop there. Renaming or forcing an unrelated profile may connect the pilots, but important FCU, MCDU, autoflight and overhead functions can remain unsynchronised.
How should the pilots divide Fenix A320 crew roles?
A clear pilot-flying and pilot-monitoring split prevents most control conflicts. The host does not have to be the pilot flying, although keeping the host in control during the first test session makes faults easier to isolate.
| Role | Primary duties | What to avoid |
|---|---|---|
| Pilot flying | Sidestick, rudder, thrust, take-off, landing and final authority over FCU changes | Handing over during rotation, flare or an unstable manual-flight phase |
| Pilot monitoring | Overhead panel, radios, checklists, route verification and agreed MCDU work | Moving flight axes or operating the same switch at the same time |
For a control transfer, stabilise the aircraft first, preferably with the autopilot engaged. Both pilots should centre their controls and place physical throttles in matching detents, then use the YourControls handover command. The receiving pilot confirms control and makes a small, deliberate input before the flight continues.
What does YourControls synchronise in the Fenix?
YourControls synchronises only the events and variables covered by its active Fenix profile. Treat anything outside that profile as local to each computer rather than assuming the complete aircraft state is shared.
| System | Practical expectation |
|---|---|
| Flight controls and FCU | Normally shared when mapped by the profile, but noisy axes or mismatched throttle detents can cause jumps. |
| Overhead switches and radios | Commonly shared, though newly added or changed Fenix controls may be missing after an aircraft update. |
| MCDU and flight plan | Key presses may synchronise, but the underlying FMGC state can still diverge if AIRAC cycles, routes or starting states differ. |
| EFB and Fenix settings | Assume these are local unless the selected profile specifically covers them. Confirm fuel, payload and performance data on both PCs. |
| Weather, traffic and ATC | Not made identical by YourControls. Both pilots should select matching simulator conditions and manage any separate ATC sessions carefully. |
Why are the two Fenix cockpits out of sync?
Most desynchronisation comes from mismatched builds, an unsuitable profile, different starting states or both pilots sending inputs at once. Diagnose the first visible disagreement rather than continuing the cockpit setup and multiplying the differences.
- The Fenix profile is missing: YourControls does not recognise that aircraft build or the required profile is not installed. Do not substitute a generic A320 profile.
- Switches move and then snap back: Both pilots, an assistance feature or duplicate hardware bindings are writing to the same control. Leave one pilot in control and disable the conflicting input.
- The sidestick or throttle jumps after handover: Centre both sets of controls and match the Airbus throttle detents before transferring control. Calibrate the Fenix detents locally on each PC.
- The MCDUs show different routes: Check that both pilots use the same AIRAC, route and flight-plan revision. Avoid simultaneous imports or MCDU entries.
- Displays are blank or the aircraft is unresponsive: Verify the Fenix background application, authentication and installation before blaming YourControls. Our Fenix A320 fault checklist covers these aircraft-specific failures.
- The disagreement keeps spreading: Disconnect, reload the same cold-and-dark flight on both PCs and reconnect before touching any controls. A badly divided FMGC or electrical state is usually quicker to reset than repair in flight.