How do I set up MSFS shared cockpit with YourControls?

To set up a YourControls shared cockpit in Microsoft Flight Simulator, every pilot installs the same Windows release, selects an exact matching aircraft profile, and loads the same flight state. One pilot hosts, the others join, then the crew verifies synchronisation and assigns a single active controller before departure.

What do both pilots need before connecting?

YourControls is an external Windows application, not a built-in Microsoft Flight Simulator mode, so every crew member needs a PC capable of running it alongside the simulator. It cannot be installed on Xbox or PlayStation consoles.

• The same simulator generation and build: MSFS 2020 or MSFS 2024, not a mixture of both.
• The same YourControls release and matching definition files.
• The exact same aircraft add-on, version, engine and model variant. A matching livery is safest, although the underlying model and systems package matter more.
• A locally installed copy and valid licence for any paid aircraft. YourControls does not distribute aircraft files or share Marketplace purchases.
• Matching airport, aircraft state, flight plan, fuel, payload, failures, weather, time, flight model, assistance settings and simulation rate. If stand positions or elevations differ, match the installed airport scenery as well.
• Control profiles without duplicated commands or noisy axes. Our advice on setting up yokes, throttles and pedals without conflicting inputs covers the hardware side.

Disable AI piloting, assisted checklists and anything else that can issue local cockpit commands. Keep simulation rate at normal, and avoid pause or slew while establishing the initial state.

How do I install YourControls?

Install YourControls by extracting the developer’s complete packaged Windows release to a permanent, writable folder.

1. Obtain the packaged application: Use the ready-to-run release rather than a source-code archive intended for developers.
2. Extract every file: Keep the executable, aircraft definitions and supporting files together. Do not run the program from inside the compressed archive or move only its executable.
3. Keep the application outside Community: YourControls is a desktop companion program, not a normal MSFS package. If a particular build includes a separately labelled bridge or in-sim component, place only that component in the active Community folder as its instructions specify.
4. Repeat the installation on every PC: Compare the displayed versions before investigating network or aircraft-profile problems.

If Windows security blocks or removes the executable, verify the origin of the archive. Do not restore or whitelist an unknown copy obtained through a mirror.

How do I start a YourControls shared-cockpit session?

A dependable session starts with both simulators fully loaded into matching aircraft and flight states before anyone connects.

1. Load the same starting situation: Use the same airport, parking position, aircraft state and flight plan. A cold-and-dark stand is easier than an active runway because one pilot can prepare the cockpit after connecting while the other checks each action.
2. Run YourControls: Start the application after loading into the aircraft and confirm that it detects Microsoft Flight Simulator. Permit its Windows Firewall rule on the appropriate trusted network rather than disabling the firewall.
3. Select the exact aircraft profile: Every pilot must choose the definition written for that aircraft and variant. A similarly named or generic profile is not a safe substitute because custom systems use different variables and events.
4. Create the session: One pilot starts the host, server or room function provided by the installed release. The host must leave YourControls running throughout the flight.
5. Join from the other PCs: Enter the supplied room code, host address or relay details, then wait until both the simulator and network connections show as active. Connect one client at a time when diagnosing a fault.
6. Let the initial state settle: Before touching anything, compare the battery, avionics, lights, radios, engines, flight controls and throttle positions.
7. Test representative systems: While parked, operate a light, change a radio setting, move one flap detent, make a small control and throttle input, and select an autopilot mode. Confirm each result on every PC, then restore the starting state.
8. Assign cockpit roles: Agree who is pilot flying and pilot monitoring, then give one pilot control of the yoke or stick, pedals, throttles, trim and autopilot.

How do you connect YourControls over the internet?

Use a relay or room-code connection when the installed release offers one; choose direct hosting only when the host can configure the network correctly.

Local-network clients normally use the host PC’s local address and configured port. Direct internet hosting can require the host’s public address, a firewall allowance and router port forwarding. Use only the port and protocol specified for that YourControls build, never values copied from an old tutorial, and do not publish the host address openly.

If local clients connect but internet clients time out, check the public address, firewall rule and router forwarding. Carrier-grade NAT can prevent inbound direct connections entirely, making a supported relay connection the practical option.

How should pilots hand over control?

Only one pilot should send flight-control inputs at a time, even when both crew members can operate supported switches.

1. The pilot flying announces the transfer and releases pressure on the controls, pedals and throttle.
2. Use YourControls’ control-transfer command.
3. The receiving pilot confirms control and checks throttle, trim, autopilot and flight-director states before making an input.
4. Transfer on the ground or in stable flight, not during rotation, flare or an autopilot mode change.

Different controller types are acceptable because bindings remain local to each PC. The common failure is leaving two throttle quadrants or sets of pedals active: a slightly noisy axis can overwrite the synchronised value and cause an abrupt power, brake or rudder movement. Centre unused hardware, add a sensible dead zone, and use an observer or read-only mode if the release provides one.

What does YourControls synchronise?

YourControls synchronises only the simulator variables and control events covered by the selected aircraft definition.

It does not stream the host’s simulator, install aircraft for other pilots or guarantee that every custom system will match. Basic controls, lights, radios and autopilot functions may work well, while proprietary avionics, tablets and circuit breakers can have limited coverage.

Treat toolbar windows, ATC audio, weather processing and third-party EFB pages as local unless the profile explicitly supports them. If the FMS or CDU route does not synchronise, load the same flight plan on both computers or enter it separately and compare every waypoint before departure.

Why is YourControls connected but not synchronising?

A network connection can succeed while the cockpit remains out of sync because simulator detection, aircraft-profile coverage and networking are separate parts of the setup.

For a first diagnostic test, use a default aircraft and one simple panel action. If that works, the network and simulator connection are sound; the remaining fault is probably the selected aircraft profile or add-on version rather than latency.

How do you recover from cockpit desynchronisation?

Recover by leaving one pilot in control, stopping all other inputs and returning both simulators to a stable, matching state.

Compare autopilot modes, gear, flaps, engines, electrical power and radios first. Use the resynchronisation function if the installed release provides one. If the disagreement remains, park or stabilise the aircraft, disconnect the client and reconnect after matching the states; a complete reload is usually cleaner than correcting dozens of variables in flight.

Before take-off and approach, agree who retains control after a connection loss. The other pilot should make no inputs until synchronisation has been restored.

Does YourControls work with MSFS 2024 and every aircraft?

YourControls works only where the simulator version, Windows application and aircraft-specific profile are compatible.

Simulator and aircraft updates can break previously working mappings. A successful connection also does not prove complete compatibility: position and basic controls may synchronise while custom avionics remain independent. Our explanation of the shared-cockpit limits in MSFS 2024 covers the wider platform and aircraft restrictions.

Default aircraft are usually the best first test. Advanced add-ons require profiles written for their custom systems, and selecting the nearest available definition is not a safe workaround. For one common complex-aircraft example, see our FlyByWire A32NX session setup and pre-flight checks.

Do we need normal MSFS multiplayer as well?

No. YourControls handles cockpit and aircraft-state synchronisation independently of standard MSFS multiplayer, which represents each participant as a separate aircraft.

You can leave multiplayer enabled for surrounding traffic, but the other pilot’s model may appear in the same position as your aircraft. Disable that representation or turn multiplayer traffic off if it overlaps the cockpit or complicates troubleshooting.