Learn what X-Plane 12 shared cockpit supports, how two pilots connect, what software they need, and how to fix sync and control conflicts.
X-Plane 12 can let two pilots fly together, but it does not include a complete, universal shared-cockpit system for every aircraft. For one cockpit, both pilots need a compatible synchronisation add-on and matching aircraft installations. To fly separate aircraft together, use X-Plane networking or an online network such as VATSIM.
What does X-Plane 12 support natively?
X-Plane 12's built-in networking supports separate multiplayer aircraft, external visuals and instructor-station functions, but these are not substitutes for a synchronised two-pilot cockpit.
An external-visual computer can display the aircraft flown by the master computer, but it does not turn the second installation into an independent co-pilot station. Likewise, ordinary multiplayer lets each person fly an aircraft; it does not synchronise the same switches, autopilot, radios or flight-management system between them.
| What you want to do | Method | Main limitation |
|---|---|---|
| Operate the same aircraft and cockpit | Compatible shared-cockpit plug-in or aircraft-specific multicrew system | Support varies by aircraft and version |
| Fly separate aircraft privately | X-Plane's built-in multiplayer networking | No shared controls or cockpit systems |
| Fly together with online ATC | VATSIM pilot client | VATSIM does not synchronise the cockpit |
How do two pilots share the same cockpit?
Both pilots must run compatible copies of X-Plane 12, the same aircraft and a shared-cockpit solution designed to synchronise that aircraft's controls and datarefs.
- Choose the aircraft first. Confirm that the shared-cockpit add-on has an X-Plane 12 configuration or profile for the exact aircraft release. A profile made for X-Plane 11 or an older aircraft version may connect while leaving major systems unsynchronised.
- Match both installations. Use the same X-Plane update, aircraft version, shared-cockpit plug-in and configuration file. Each pilot will normally need a properly licensed local installation. Matching navigation data is also advisable when both pilots will operate the FMS.
- Load the same starting conditions. Select the same airport, parking position and aircraft state. Align weather, time and fuel where the add-on does not copy them automatically. Different scenery can place a stand or ground surface at a different position or elevation.
- Create the connection. One pilot hosts and the other joins using the method provided by the plug-in. Permit the relevant program through each computer's firewall. Depending on the product and network arrangement, internet hosting may require router configuration or a private network connection.
- Set control ownership. Decide who is pilot flying and use the add-on's control-transfer function. Centre unused axes and check for duplicate throttle, mixture, tiller or brake assignments before moving.
- Test systems at the gate. Operate the battery, lights, radios, flight controls, autopilot and FMS from each side. Do not begin a flight until both pilots see the same indications and can transfer control cleanly.
Dataref-based tools such as SmartCopilot can provide this synchronisation when a suitable aircraft profile exists. Some complex aircraft use custom systems that need aircraft-specific support; installing a generic plug-in alone does not guarantee that every switch or display will work.
Why do shared-cockpit controls or instruments disagree?
Partial synchronisation usually means the aircraft versions, plug-in profiles or control assignments do not match.
- The aircraft moves, but switches do not: the profile is missing the aircraft's custom datarefs or was written for another release. Use the exact supported combination rather than trying to force an older profile.
- Controls fight or snap back: both pilots are sending joystick or throttle input. Transfer control through the plug-in and eliminate noisy or duplicate axis assignments.
- The FMS routes differ: match navigation data and aircraft options, then initialise the route from the designated master side. Some systems do not reliably copy scratchpad entries or partially completed pages.
- The pilots see different aircraft states: load the same cold-and-dark or engines-running state before connecting. Saved-flight states can contain values that the synchronisation profile does not overwrite.
- The connection fails: check host addresses, firewall permissions and matching plug-in versions. A successful voice call does not prove that the simulator's network traffic can pass through the router.
- One aircraft appears above the ground: use matching airport scenery or move to a stand represented consistently on both computers.
Can we fly together without sharing one cockpit?
Yes. For two separate aircraft, X-Plane 12's normal multiplayer networking is the simpler choice, particularly on the same local network.
Each pilot loads an aircraft, exchanges the required network details and appears as traffic in the other simulator. Internet play may need additional firewall or router work. Our X-Plane 12 multiplayer setup guide covers that method without confusing it with shared cockpit.
Can VATSIM be used with shared cockpit?
VATSIM can provide online traffic, controllers and voice communications, but it does not copy cockpit controls or aircraft systems between two computers.
For separate aircraft, both pilots can connect normally after following our practical VATSIM setup steps for X-Plane 12. For one shared aircraft, use a separate cockpit-synchronisation add-on and follow the pilot client's documented shared-cockpit or observer procedure. Do not connect two ordinary clients at the same position as if they were separate aircraft, because that can create duplicate network targets.