Update! MSFS2020 - Your Controls Shared Cockpit App - V.2.4.0 [1 Airplane 2 Pilot]

Shared Cockpit for Microsoft Flight Simulator 2020.


  • Frequent and smooth position updates through linear interpolation
  • Transferable controls
  • Configurable aircraft files to sync most switches/knobs
  • Synchronzied button presses on FMCs/GXXXXs

The following aircraft have config files:

  • FBW A32NX Stable + Dev
  • Cessna 152
  • Cessna 172 G1000
  • Diamond DA40
  • Diamond DA62
  • Pitts
  • TBM 930
  • XCub
  • Icon A5
  • DR400
A manual installation is not included with the releases anymore. Please use the latest installer to get this release. If it doesn't open, install the Webview Runtime.
It's recommended you tick the option for Clean Install when you install the new version, otherwise you'll have 3 files labelled A32NX.

An awesome release that adds an option to use Cloud Server instead of port forwarding/using a VPN client, and eliminates conflicts with other mods by default. Hoping to fix some autopilot issues and smoothen out position updates even more for the next update.

  • Mixture/Prop can now be controlled by both PM and PF in all aircraft
  • Yoke/Throttles will reset to the host's position when moved
  • H events are now received from JS via a websocket, which removes the need for defining H events manually (might support #34 automatically?)
  • Touch screen buttons in avionics are now automatically detected
  • Toe brakes synced
  • Ground speed synced (corrected for wind)
  • Sync elevator/aileron positions

  • Switch from TCP to UDP, implemented UDP hole punching for P2P connections
  • Switch from JSON to MessagePack
  • Fixed UPNP SSDP not broadcasting correctly, which should fix UPNP failing randomly
  • A client can no longer connect to a server that does not have the same version as they do

  • Active Aircraft is no longer saved to ensure that the correct aircraft gets selected
  • External IP now shown on the UI
  • Take Control button added for the host to force taking back control (#31)
  • Clients will now start as observers
  • WASM gauge moved to a standalone module (#57, #49)
  • The program will now look for files relative to its path rather than from the path where it was launched from

  • radios are value-synced on initial connection only now, relies on events for perfect synchronization
  • attempted to fix by removing sync of PLANE HEADING DEGREES GYRO
  • Fixed a bug where the batteries on the A32NX could get desynced

New Aircraft
  • Icon A5
  • DR400

Known Issues
  • AP flight director drifting off course
  • A32NX rattling sound in the air
    • Fixed white screen issue some computers were having by switching to MSHTML

    • Fixed Pitts/XCub not syncing position
    • Support new A32NX dev where most future A32NX updates will not be broken by YourControls
    • Download and run the installer.
    • If the installer does not open for you, you'll need to install Webview2.


    Ensure everybody has the same navdata, scenery, and weather installed.

    Launch MSFS, select the same aircraft and spawn location. Do NOT enable multiplayer unless you're on different servers.

    Once everyone has spawned in, start up the included .exe file. Do NOT run as administrator.

    In Settings, under the header Active Aircraft, select the .yaml file associated with the aircraft you're flying (both server/clients should do this).

    When a person connects, make sure to click the Observer button next to their name if you want them to be able to manipulate switches.

    Hoster (designate one person to run):

    Try all of these options in this order, until one works for you. Cloud Server does not have a 100% success rate. If you fail to connect using this method, try having another person host, but ultimately you'll have to fall back on the other methods.

    Cloud Server

    Click Start Server
    Give the provided session code to the joiners.

    Click Start Server
    Enter any port, or leave the default 7777 if unused.
    Give your External IP, and the port to the joiners. If an error occurs, your router may be incompatible with UPnP, or does not have it enabled. You'll need to login into your router to enable it. More information below.

    If you have a IPv6 address, you can simply give that along with the port to the joiners.
    UDP port forward either 7777 or the specified port in the application. If port forwarding is not an option, look into using Hamachi.
    Click start server.
    Joiners: If given a Session Code, click Cloud Server, paste code, and click Connect

    If given an IP, confirm with the hoster whether it is IPv4 or IPv6, enter port, and click Connect


    To transfer control, navigate to the Connections tab, find your partner's name and click Give Control.

    Example Method "Setup FlyByWire A32NX with Your Controls on VATSIM"
    1. Make sure both Captain and Co-pilot have the same A32NX version (DEV or STABLE) installed.
    2. MSFS Multiplayer settings should be the same as usual on VATSIM (Group Flight, no AI, Live Weather).
    3. Load your flights with the same plane, airport, and gate/ramp.
    4. Run Your Controls .exe file, one of you makes the server, and the others connects to it.
    5. The one who made the server is PILOT FLYING, controlling the aircraft by default.
    6. PILOT FLYING can give the aircraft control to the other pilot by choosing GIVE CONTROL.
    7. PILOT FLYING connects to VATSIM using callsign, for example here, AAL123, aircraft type A20N, and files a flight plan.
    8. PILOT MONITORING connects to VATSIM using callsign AAL123A, with same aircraft type A20N, and check that “shared cockpit mode (observer mode)” is on. Do NOT file a flight plan.
    9. A third pilot can join the jumpseat by connecting to VATSIM using callsign AAL123B, aircraft type A20N and checking “shared cockpit mode (observer mode)” on. Do NOT file a flight plan.
    10. Voice connection between the crew is not supported at the moment, so you will need a separate program for this.

    0/Post a Comment/Comments

    Previous Post Next Post