How do I install and use YourControls in MSFS?

To install YourControls in Microsoft Flight Simulator, download the official Windows release, extract the entire archive to a permanent folder, and run its executable alongside MSFS. Every crew member must use the same YourControls version and matching aircraft profile; one person hosts the session and the others join with the supplied connection details.

What do you need to use YourControls?

YourControls is an external Windows companion application that uses MSFS data to synchronise a shared cockpit. It is not ordinary Marketplace content, and normal Microsoft Flight Simulator multiplayer does not provide the same cockpit synchronisation.

• Every participant needs Microsoft Flight Simulator running on a Windows PC.
• Everyone needs the same YourControls release and the correct aircraft definition or profile.
• Each person must own and install the aircraft being flown. YourControls does not share aircraft licences or Marketplace purchases; our explanation of how Marketplace and externally installed PC content differ covers that distinction.
• The exact aircraft variant and add-on version should match. Using the same livery is safest, although a paint-only livery normally has no effect on cockpit systems.

A generic profile is not a substitute for one written for the aircraft. Two aeroplanes may share an airframe name yet expose completely different switches, avionics and autopilot variables.

How to install YourControls

Install YourControls by extracting the packaged release intact and keeping its executable, definitions and supporting files together.

1. Obtain the packaged Windows release. Do not download a source-code archive intended for developers; it may not contain a ready-to-run application.
2. Extract the complete archive. Use a permanent, user-owned folder and do not launch the executable from inside the compressed file. Moving only the executable will leave behind definitions and libraries it needs.
3. Keep it outside the Community folder. YourControls itself is normally a portable desktop application, not a standard MSFS package. If a particular release contains a separately labelled in-sim component, install only that component in Community. Our instructions for finding the active Community folder and avoiding double-nested packages explain the correct package structure.
4. Launch Microsoft Flight Simulator and YourControls. Load the simulator at least as far as the main menu, then open the YourControls executable. Loading the aircraft before connecting is more reliable.
5. Approve the Windows firewall prompt. Permit the application on the appropriate trusted network rather than disabling the firewall completely.
6. Repeat the installation on every crew member’s PC. All participants should confirm that the displayed YourControls versions match before troubleshooting anything else.

If Windows security removes or blocks the executable, verify that the archive came from the project’s official release source. Do not restore or whitelist a copy obtained from an unknown mirror.

How do I start a YourControls shared-cockpit session?

Start by loading the same aircraft and flight conditions on every computer, then let one person host while the other crew members join.

1. Match the flight setup. Use the same aircraft variant, airport position, panel state, fuel and payload, flight plan, weather and time. Matching airport scenery also reduces elevation or parking-position discrepancies.
2. Select the aircraft definition. Every participant must choose the profile intended for that exact aircraft or add-on. Do this before establishing the connection.
3. Create the session. The host starts a server or creates a shared session using the connection method offered by that YourControls release.
4. Join after loading the aircraft. Clients enter the host address, room information or other connection details shown by the application. Connect participants one at a time if the group is diagnosing a problem.
5. Test a harmless control. Try a battery switch, cockpit light or another visible control while parked. Confirm that it changes for everyone before starting engines.
6. Assign control clearly. Only one pilot should manipulate the flight controls, throttles, trim or autopilot at a time. Announce each handover and centre unused hardware where possible.

Normal MSFS multiplayer is not required. If another copy of the aircraft appears at exactly the same position, disable ordinary multiplayer or online traffic for the session.

Which connection method should I use?

Use a relay or room-code connection when the installed YourControls release provides one; use direct hosting when you need a host-controlled connection and understand router configuration.

A relay connection generally avoids port forwarding. With direct hosting, the host may need to permit the application through the firewall and forward the exact port and protocol specified by that release. Do not rely on port numbers copied from an old tutorial because application defaults can change.

If direct clients time out, check that they are using the host’s external address rather than its local network address. Carrier-grade NAT can prevent ordinary inbound port forwarding altogether, in which case a supported relay method is the practical choice.

Why are switches or controls not synchronising?

Partial synchronisation usually means the wrong aircraft profile is selected, the add-on versions differ, or the aircraft uses custom systems that its profile does not cover.

• Confirm the exact aircraft build. Update or roll back participants so everyone has the same add-on version.
• Check the selected definition. Do not choose a similarly named profile simply because the aircraft exterior looks identical.
• Expect aircraft-specific limits. Custom flight-management computers, EFBs, tablets, circuit breakers and proprietary avionics may not expose every state YourControls needs.
• Stop conflicting inputs. AI assistance, automated checklists, external hardware and duplicate bindings can repeatedly overwrite a synchronised value.
• Control noisy axes. A throttle or yoke that constantly sends small changes can fight the other pilot’s input. Add a sensible dead zone or use an observer/read-only mode if the installed release provides one.

Agreeing on bindings helps prevent accidental gear, flap or autopilot commands; our reference for MSFS keyboard and controller commands is useful when coordinating both cockpits.

If the cockpits have diverged badly, park the aircraft, disconnect every client, reload the same starting state and reconnect with the host first. Reloading is usually cleaner than trying to repair dozens of mismatched variables in flight.

Does YourControls work with MSFS 2024 and consoles?

YourControls requires its Windows companion application, while simulator and aircraft compatibility depends on the specific release and profile.

Successful connection alone does not prove aircraft compatibility. Position and basic flight controls can work while custom avionics remain unsynchronised, so test the important systems on the ground before committing to a long flight.