Introduction
The GoFlight Interface Tool (GIT) is a very powerful tool that enables the interfacing of all types of default and complex aircraft to GoFlight hardware. It is not a plug and play type tool - it is an interfacing tool which means it can appear complex.
However, you do not necessarily need to do any interfacing work yourself and thus avoid having to understand all the details of GIT. There are a number of pre-built configurations for various aircraft, that can be downloaded and imported into GIT via a few simple steps.
Also, PMDG aircraft (NGX, NGXu, NGXu BBJ, 777, 747) and iFly aircraft (737, 747) are automatically configured for the MCP, MCP PRO, EFIS, LGT, SECM, MESM, GF45/46 and the TQ6 (buttons only). All you need to do is enable the devices in the relevant GIT hardware tabs.
Why Can't GIT Be "Plug & Play"?
The answer is simple. There are no enforced standards for the creation of aircraft in FSX/P3D. Although Simconnect is a standard which most built-in aircraft adopt, the more modern and complex aircraft use custom gauges with their own internal controls. What this means is that an Event that works in one aircraft; lets say activates the WXR button on an EFIS, may not work in another aircraft as the aircraft designer has created their own custom Event for the WXR button.
So its next to impossible to build software that comes pre-configured to interface hardware to all aircraft built for FSX/P3D. There is of course the option to hard code support for every aircraft into the software as aircraft are released or updated, like GIT does for PMDG support; but this would be very costly to develop and maintain; and would increase the price of GIT to unaffordable levels.
There are some exceptions however. For example, generally COM, NAV, and ADF functions tend to stick to standard Events which is why GIT has the option to automatically configure a GF166 as a COM, NAV or ADF unit.
So GIT cannot be "Plug & Play" like GoFlights GFConfig software because by doing so it would be limited to default aircraft only and would behave inconsistently because even the default aircraft do not always use the standard Events.
Microsoft Flight Simulator (MSFS) Users
Take a look at the following for an overview on using GIT with MSFS before reading further: FS2020 Feature Status and Usage — PollyPot Software
Where Should You Start?
It is highly recommended that you use some pre-built configurations from the Downloads section of the website before delving into GIT any deeper. By using pre-built configurations you will start to get a high-level overview of how GIT works. You will also be able to reference the work done in the pre-built configurations when reading the manual which should help your understanding.
Note that PMDG and iFly aircraft do not have any pre-built configurations. These aircraft have built in support (hard coded into GIT) for most of the major hardware. These aircraft have their Software Developments Kits (SDK's) built into GIT so Detective is disabled when these aircraft are used as its irrelevant when support for the aircraft is built into GIT. See the PMDG and iFly sections further down in this article for more information.
So being a new user to GIT, it is highly recommended to follow these steps carefully:
1) Make sure you install GIT correctly by following the steps in either this article https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/16-installation/14-installation.html or for FS2020 version, follow this article: Installation FS2020 (pollypotsoftware.org.uk)
2) Identify a plane that you have from the Downloads section of the website and download the pre-built configuration from here: https://www.pollypotsoftware.org.uk/downloads.html (make sure you click the GIT Aircraft Configs FSX/SE/P3D tab!)
3) Install the pre-built configuration by following the first section of the following article: https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/16-installation/99-how-to-load-downloaded-aircraft-configuration-files.html
Automatically Configure Devices
On some tabs within GIT you will see buttons that enable that particular type of GoFlight hardware to be automatically configured using default FSX/P3D Events and Variables. The MCP PRO, MCP, LGT, GF166 have these options. There is no guarantee that devices automatically configured will work with all aircraft as explained previously.
To use automatic configuration do the following:
1) Load the relevant aircraft and get the Virtual Cockpit visible.
2) Click on the relevant hardware tab in GIT.
3) Pick a device from the dropdown list.
4) Click the button that will automatically configure the device.
5) Enable the device.
6) Its usually best to now quit GIT and restart GIT.
PMDG Aircraft
Read this additional installation note for the 777: https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/16-installation/40-setup-for-the-pmdg-777.html
The MCP, MCP PRO, EFIS, LGT, SECM, MESM, GF45/46 and the TQ6 (buttons only) are automatically configured. To use, do the following:
1) Load the relevant aircraft and get the Virtual Cockpit visible.
2) Click on the relevant hardware tab in GIT.
3) Select a device from the dropdown device list.
4) Enable the device.
5) Its usually best to now quit GIT and restart GIT.
IMPORTANT: Detective does not work with PMDG aircraft as the PMDG SDK is built into GIT making Detective irrelevant. See https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/17-concepts/35-pmdg-ngx-77x-747x-events-variables.html
For video tutorials on configuring the GoFlight Interface Tool and the NGX, (which can also be used to guide configuration on the PMDG 777 and 774) see the Documentation & Tutorials section below.
iFly Aircraft
Read this additional installation note: https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/16-installation/120-setup-for-the-ifly-737-747.html
The MCP, MCP PRO, EFIS, LGT, SECM, MESM, GF45/46 and the TQ6 (buttons only) are automatically configured. To use, do the following:
1) Load the relevant aircraft and get the Virtual Cockpit visible.
2) Click on the relevant hardware tab in GIT.
3) Select a device from the dropdown device list.
4) Enable the device.
5) Its usually best to now quit GIT and restart GIT.
IMPORTANT: Detective does not work with iFly aircraft as the iFly SDK is built into GIT making Detective irrelevant. See https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/17-concepts/119-ifly-737-747-events-variables.html
Technical Support
If you have any issues or questions about using GIT, technical support is provided Monday to Friday 10am to 6pm GMT on the support forum. The support forum can be found here: https://www.pollypotsoftware.org.uk/support/forum.html. Note that you need to register to join the forum as its a separate account from the Shop. VERY IMPORTANT: Please post in the Discussions section and not in the Activity section as we are only notified of posts in the Discussions section.
If you have problems registering the software, please use the general enquires form found here: https://www.pollypotsoftware.org.uk/contact-us.html
Documentation & Tutorials
Rob Ainscough from Avsim has kindly produced the following video tutorials.
Part 1 is here: Quick Tutorial on using GoFlight Interface Tool Part I (of III) [ FSX, SE and P3D only! ] — PollyPot Software
Part II is here: GoFlight Interface Tool Tutorial Part II of III — PollyPot Software
GoFlight collaborated with Jason from Angle Of Attack to create 3 tutorials about using the GoFlight Interface Tool with the PMDG NGX. They are also relevant for configuring the PMDG 777 and 774:
Part 1 is here: https://youtu.be/uqM0ZfGgS1M
Part II is here: https://youtu.be/nUgOO2S88bg
Part III is here: https://youtu.be/42jZ7xgKOa0
There is a Frequently Asked Questions (FAQ) article here: https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/41-faq/70-faq.html
Full online documentation can be found here: https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git.html