Shared Cockpit Guide

64bit edition
Fly the Maddog X 64bit edition
DC 9/80
SHARED COCKPIT GUIDE 1/6 17/04/20 Rev 6

INTRODUCTION
Shared Cockpit is a new feature added in Fly the Maddog X 64bit edition that allows for a much more
realistic flying experience: the main concept is sharing the panel with a friend over an IP connection (via
LAN or WAN), adding the ability to use Multi Crew Coordination procedures (MCC), positioning one of
the pilots as the CM1 (left seat) in the cockpit, and the other one as the CM2 (right seat).
Each pilot has his own flows, duties and tasks to accomplish, and the workload this way is balanced among
the different roles that a pilot can have - regardless the physical position he occupies - being the PF (Pilot
Flying) or the PM (Pilot Monitoring).
In a nutshell, Shared Cockpit will give you the opportunity to fly in a completely immersive way, simulating
the real cockpit workload and dealing with this complex add-on as it is though in real life: managed by
two people in close coordination, sharing their experience to solve problems and take accurate decisions
when needed.

Leonardo SH has been the very first developer, back in 2006, introducing this new concept of “sharing
the cockpit” with the legacy Maddog PRO series; many developers have followed after, with noticeable
results: that’s why Shared Cockpit actually doesn’t need any further presentation.
We have always wanted to bring this feature back in Fly the Maddog X, and finally all our efforts have
reached the end point of almost a year of work, bringing back the old MultiCrew interface (as it was
originally named), coding it to this new version and improving it to current standards.

NOTE: Shared Cockpit might not be available in some regions because of ports limitation for restricting
specific network services.

HOW SHARED COCKPIT WORKS

Two computers, each one running separate installations of Fly the Maddog X 64bit edition, can connect
via a Local Area Network (LAN), or to a Wide Area Network (WAN) via internet.
Two network parameters are needed for Shared Cockpit to correctly work: the remote IP address of the
other side you’re connecting to, and the TCP port trough which data is sent/received (26867 is default).
Each respective remote IP address must be known by both participants, and TCP port used must be
negotiated between both sides prior to connect.

LAN connections: the easiest case. If your network is properly set up, Shared Cockpit is capable to find
the other side remote IP automatically through a network broadcast search. You will only need to specify
the TCP port you’re going to use in the Shared Cockpit fields in Load Manager. Default port setting is TCP
26867 and should work for most network configurations.

Anyhow, if the auto-discovery feature doesn’t work and you have two PCs connected to a local network,
probably you know their remote IP addresses if you already assigned your PCs a static one when setting
up the network.

However, when IP assignment is automatically managed by a DHCP server integrated in your

modem/router (Dynamic Host Configuration Protocol), you can retrieve the IP address just opening the
Command Prompt by clicking Start, searching CMD and clicking on cmd.exe.

After the window opens, type ipconfig /all. Find the Local Area Connection listing. Find your network
adapter, useful information is listed and on the IPv4 Address line you can see your currently assigned IP
address.
Fly the Maddog X 64bit edition
DC 9/80
SHARED COCKPIT GUIDE 2/6 17/04/20 Rev 6

WAN connections: this is the case when the PC you’re connecting to is not physically in the same place
of yours; Shared Cockpit connection is carried out by sending/receiving data trough Internet and, in most
cases, your is PC isn’t exposed directly to the network but you connect via a modem/router that has its
own remote IP address (which is usually dynamic and can change over time), while it also has another IP
address for the local network interface in order to correctly manage it.
The modem/router therefore acts as a “bridge” between the internal world of the local network and the
external one of the Internet.

To successfully establish a Shared Cockpit connection, you will have to set up the modem/router in such
a way that Shared Cockpit data, which pass through a TCP port, is correctly forwarded to the PC where
the simulator actually runs and the Shared Cockpit data is exchanged.

There are some thousands different network devices on the market, each one with its own settings: for
the purpose of this guide it is impossible to cover every single one, but at this link you can access general
information on how to successfully carry out port forwarding.

Default port setting is TCP 26867, but any other TCP port can be used provided it has access granted for
your country/provider. I.e. port 3074, which is the Xbox Live network, is usually a good port to try if the
default one is restricted.

Getting the remote IP address of the other participant is extremely easy: ask him to visit
https://www.whatismyip.com/ to discover his IPv4 remote address, communicate yours found in the
same way and vice-versa.
Fly the Maddog X 64bit edition
DC 9/80
SHARED COCKPIT GUIDE 3/6 17/04/20 Rev 6

LOAD MANAGER CONFIGURATION

Once the port forward rule in your router/modem is set, ports in use and remote IP addresses are shared,
open the Load Manager and configure the Shared Cockpit data fields with the corresponding data.

USAGE
Consistency is the key for the perfect experience: for this reason, you and the other side have to check
some settings to avoid experiencing discrepancies during the flight.

Prepar3D Settings
Options Category Field Value
General
➢ Application ➢ General Pause on task switch OFF
➢ International All values in category SYNCED

➢ Information ➢ Information text Message text ON*

➢ Traffic ➢ Aviation traffic All values in category SYNCED

➢ Realism ➢ All categories All values in categories SYNCED

*= Shared Cockpit will display connection status information in the green P3D message field and we
suggest to keep them on.

The ideal condition is when both parties have PCs with the same software installed and the same add-
ons settings.
Fly the Maddog X 64bit edition
DC 9/80
SHARED COCKPIT GUIDE 4/6 17/04/20 Rev 6
Fly the Maddog X Settings
Category Option Value
Airline Options All options SYNCED *

Simulator Options All options SYNCED **

*= this can be easily done by just sending to the other party the .mda file corresponding to the airframe
you’re going to fly from the folder %Documents%\Maddog X Files\Prepar3D v4\Aircrafts, pasting and
overwriting it in the same location.

**= saving your settings using the Save button and sharing your config file with the other party, he can
use the Load button to import them. When using Shared Cockpit, the PNF calls and the CM1/CM” sync
options will be disabled upon connection, as well as all failures.

Following the same principle, when you plan your route and generate the .mdr route file and the OFP file,
share it with the other side to ensure identical fuel and weights figures.
To avoid discrepancies, remember also to check you have same AIRAC cycle installed.
Any other 3d party add-on that may alter the flight should be installed and configured the same way in
both systems, or completely disabled before connecting (i.e. wx engines).
GSX Level 2 can be used, provided services are called in sync in both sides of the connection (refueling,
boarding, etc. while Pushback service must be requested by PF only). In case of different boarding density
settings, boarding is considered “completed” when the slower finishes. This is also to keep ACARS
messaging sync’d.

All of the flight deck and animations are synchronized between both sides, but panels must be in the
same state before connecting: the easiest way is loading the aircraft then selecting a predefined panel
state before connecting from the P3D Add-ons menu, i.e. Add-ons -> Maddog X -> Cold and dark.

The whole Shared Cockpit idea develops around the concept of MCC procedures: CM1 and CM2 have
their own duties and tasks as well as the PF and the PM. They are detailed in the OM vol. 2 ch. 8 - Checklists
- Procedures Guide, which are based on real MD-82 procedures for a major operator. However other
operators can have different procedures, the ones described must therefore be understood as guidelines.
To avoid control interferences and better integrate the MCC concept, the following axis are inhibited as
shown. However, joystick buttons or key assignments will still work for both sides.

Axis Control Monitor

Flight Controls and Throttles PF PM
Flap and slat PM PF
Speedbrakes and brakes PF + PM
Tiller CM1 No tiller*

*= in the real aircraft the tiller is located on the CM1 side only. If you have assigned an axis for tiller control,
and you are connected as CM2, it’s not possible to disable it due P3D limitations. To avoid discrepancies
please do not operate tiller axis on CM2 position.

Fly the Maddog X uses custom code to manage axis (including throttle slope filtering with a logarithmic
curve to enhance power management at low regimes) and is not fully compatible with FSUIPC direct axis
assignment method; if you can use FSUIPC direct method only, and have the “FSUIPC compatibility mode”
option in load manager - Simulator Options enabled, be advised your throttle axis movement can’t be
forwarded to the other party of the connection.
Fly the Maddog X 64bit edition
DC 9/80
SHARED COCKPIT GUIDE 5/6 17/04/20 Rev 6

You are now ready to connect: create a new scenario using the same airframe, same scenery and parking,
same date and time and once negotiated who’s sitting in which side, select from the P3D Add-ons menu,
in the same time (or the connection will timeout), Maddog X -> Shared Cockpit connection as Host (CM1)
(or Client (CM2) as appropriate). Connection will establish, a confirm message will display inside the
simulator and for the next 30 seconds you will be able to swap position between CM1 or CM2 (this is
useful in case one of tho sides can only connect to Shared Cocpkit as Client (CM2) but wants to seat on
CM1 side).
By default, the designated PF is CM1 while the CM2 will be PM; but what if you want to pass control to
the other side? There are three ways of doing it:

1) Autopilot guidance switch: slide the knob to the side that will fly as PF: a message inside the
simulator will confirm the transfer of control. For coordination purposes between the PF and PM,
it is recommended that the CM assuming control is also the one to operate the AP guidance
switch. Bear in mind switching the AP guidance transfers also navigation systems priority.

Slide the switch from 1 to 2 for passing control to CM2 and vice-versa

2) Autopilot reset: disengage Autopilot with the yoke AP disengage button (or with the default Z
key assignment) and press it a second time, resetting the red AP light annunciator in the FMA: a
message will confirm the transfer of control.

Autopilot disengage button

3) Operating tiller: tiller is located on CM1 side only. When CM2 is PF, operating the axis by CM1
will set CM1 as PF and CM2 as PM: a message will confirm the transfer of control.

Once the CM1/CM2 swap PF/PM roles, axis control priority change accordingly at the moment of the
transfer or control. This can lead to discrepancies for the flaps axis if not synced before changing role.
Fly the Maddog X 64bit edition
DC 9/80
SHARED COCKPIT GUIDE 6/6 17/04/20 Rev 6

CONNECTION STATUS MESSAGES

Connection status messages are displayed in the green P3D message field, including errors.

Connection failure: Shared Cockpit connection is lost. You can try to connect again but do not operate
any switch meanwhile or discrepancies will occur. You can also disconnect Shared Cockpit to gain full
control of the aircraft again and continue flying alone.

Dead reckoning: shown ON PM side only when the position data streaming is temporarily interrupted.
Simulation won’t be affected and the message disappears as soon as data streaming starts again.

Shared Cockpit custom commands: custom commands can be set to manage shared cockpit connection
and enable connection status messages in the simulator bar.
To enable it open the load manager - custom events tab and add the command
SHARED_COCKPIT_STATUS, set command parameter 0 and associate your key combo or joystick button.

DISCONNECT
To disconnect from Shared Cockpit, select from the P3D Add-ons -> Maddog X menu Disconnect Shared
Cockpit.

VPN AND HAMACHI

Provided you set correctly the remote IP address and the TCP port, Shared Cockpit should work also when
connected via VPN.
Hamachi is a VPN client. It creates a Virtual Private Network over a public network like the Internet. When
this client runs, it implements a virtual network adapter, and you’re given an additional IP address that
identifies you on any virtual network you join. More information can be found here:
https://www.howtogeek.com/77164/beginner-how-to-use-logmein-hamachi-to-access-your-files-
anywhere/