Set up YourControls shared cockpit in Microsoft Flight Simulator, match aircraft profiles, connect both pilots, transfer control and fix desync.
To use YourControls for shared cockpit, both pilots install the same PC release, run its external app, select a compatible aircraft profile, and connect to one pilot’s hosted session. Load the same aircraft and configuration in Microsoft Flight Simulator, then assign one pilot as the active controller and verify cockpit synchronisation before departure.
What do both pilots need before connecting?
YourControls is a third-party synchronisation utility, not a built-in Microsoft Flight Simulator mode. It runs as an external Windows application, so it cannot be installed on Xbox or PlayStation consoles.
- The same Microsoft Flight Simulator edition and simulator build.
- The same YourControls release and matching aircraft profile.
- The exact same aircraft add-on, version and model variant. Matching liveries are safest, although the model and systems package matter more.
- Matching fuel, payload, failures, weather, flight model and assistance settings.
- Working control profiles without duplicated or noisy axes. Correct any problems using our guide to checking joystick assignments and response settings before starting the shared session.
Disable AI piloting, assisted checklists and other features that can issue local cockpit commands. Set simulation rate to normal and avoid pause or slew while establishing synchronisation.
How do I install and connect YourControls?
- Extract the complete release: Obtain the developer’s packaged release and extract every file into a normal writable folder. Do not run it from inside the downloaded archive or place the whole application in the MSFS
Communityfolder. - Start Microsoft Flight Simulator: Load into a flight with the required aircraft. Run the YourControls executable and confirm that it detects the simulator rather than remaining disconnected from SimConnect.
- Select the aircraft profile: Choose the definition made for the exact aircraft and variant being flown. Never substitute a similarly named profile; custom systems can use completely different variables and events.
- Match the starting state: Both pilots should use the same airport, parking position, aircraft state and flight plan. Starting cold and dark is usually easier because one pilot can perform the setup after connecting while the other checks each action.
- Create the session: One pilot starts or hosts a session in YourControls. Share the connection detail required by that release, normally a session code or host address.
- Join from the second PC: The other pilot selects the same profile, enters the supplied connection detail and waits until both the network and simulator connections are shown as active.
- Test before moving: Operate a light, move one flap detent, adjust a radio and make a small throttle movement. Confirm the same indications on both PCs, return everything to its starting position, then test the control-transfer function.
If Windows Firewall asks for access, permit the application on the appropriate trusted network rather than disabling the firewall. Direct-IP hosting may require a router rule; use only the port and protocol specified for the installed YourControls release because these details can differ between builds and connection modes.
How should pilots hand over control?
Only one pilot should own the flight controls at a time, even though either person may be able to operate supported switches. Treat the active controller as the pilot flying and the other person as the pilot monitoring.
- The pilot flying says that control is being transferred and releases pressure on the yoke, pedals and throttle.
- Use YourControls’ control-transfer command.
- The receiving pilot confirms control and checks the throttle, trim, autopilot and flight-director states before making an input.
- Make the transfer on the ground or in stable flight, not during rotation, flare or an autopilot mode change.
A mistake we see constantly is leaving two throttle quadrants or sets of pedals active. A slightly noisy axis can overwrite the synchronised value as soon as control changes hands, producing sudden power, brake or rudder movement.
What does YourControls actually synchronise?
YourControls synchronises variables and control events defined by the selected aircraft profile; it does not stream one simulator instance to the other PC. Basic controls, lights, radios and autopilot functions may work well when mapped, while custom avionics depend entirely on the aircraft definition.
Treat toolbar windows, ATC audio, weather processing and third-party EFB pages as local unless the profile explicitly supports them. Complex FMS or CDU pages may only partially match. If route entry does not synchronise, load the same flight plan on both computers or enter it separately and compare every waypoint before departure.
Why is YourControls out of sync?
| Symptom | Likely cause | Fix |
|---|---|---|
| The client cannot join | Different YourControls builds, firewall blocking or an unreachable direct host | Match releases, permit the app through the firewall and verify the connection mode. Configure router forwarding only when that mode requires it. |
| Connected, but switches do nothing | SimConnect is not attached or the wrong aircraft profile is selected | Load both pilots into a flight, select the exact profile and reconnect the session. |
| Some switches or FMS pages differ | The aircraft uses unsupported custom variables, or an aircraft update has outpaced its profile | Use a profile written for that aircraft version. If the control is not mapped, operate or configure it separately on both PCs. |
| The aircraft jerks or controls fight | Both pilots are sending axis inputs, or local AI assistance is operating controls | Assign one active controller, neutralise the other hardware and disable piloting assistance. |
| The aircraft gradually diverges | Different fuel, payload, weather, failures, flight model or simulation rate | Match those settings, return to normal simulation rate and reconnect from a stable state. |
| A second aircraft overlaps the cockpit | Ordinary MSFS multiplayer is displaying the other pilot’s local aircraft | Disable the partner’s multiplayer representation or turn multiplayer traffic off while diagnosing the session. |
When troubleshooting, start with a default aircraft and a simple panel action. If that works, the network connection is sound and the remaining problem is probably the chosen aircraft profile rather than latency.
Does YourControls work with MSFS 2024 and every aircraft?
No. Compatibility requires a three-way match between the simulator edition, the installed YourControls release and an aircraft-specific definition.
Do not assume that a profile made for Microsoft Flight Simulator 2020 will work in Microsoft Flight Simulator 2024. Use only a build and profile that explicitly support the edition and aircraft concerned; simulator and aircraft updates can also break previously working mappings. Our explanation of shared-cockpit requirements in MSFS 2024 covers the wider platform limitations.
Default aircraft usually make the best first test. Advanced third-party aircraft can have partial support because their avionics, electrical systems and EFBs may not expose every action YourControls needs. Selecting the nearest available aircraft profile is not a safe workaround.
Do we need normal MSFS multiplayer as well?
No. YourControls supplies the cockpit and aircraft-state synchronisation independently of standard multiplayer, which normally represents each participant as a separate aircraft. You can leave multiplayer enabled for surrounding traffic, but overlapping partner models are a reason to switch it off; our guide to how standard MSFS multiplayer differs from shared cockpit explains the distinction.