Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.
FS2020 Feature Status and Usage
Please monitor this forum thread for the latest information on GIT FS2020!
The following GoFlight hardware works with GIT for FS2020 in exactly the same way as with FSX, FSX SE, P3D and X-Plane:
MCPPRO, MCP, EFIS, P8, T8, RP48, LGT, LGT II, GF45, GF46, GF166, WP6, MESM, SECM, DIO, TQ6
Installation
See this link: https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/16-installation/263-installation-fs2020.html
Starting GIT
Due to the current bugs in the Microsoft FS2020 SDK, start GIT after FS2020 has loaded and the menu has appeared, otherwise the aircraft currently loaded will not be identified (see the status tab to check). It's fine if you change the aircraft, but attempting to fly the current aircraft loaded on start-up causes the issue.
Using the MCP PRO and MCP
Whenever you use an aircraft for the first time, go to the MCP PRO or MCP tab, click the Default FS button, then select Device 0 from the drop down and then select ENABLE from the drop down next to it. It will now work, once you move the rotaries, or you can quit GIT and restart it and all the displays will light up.
You only need to do this once, you will never need to do it again for that aircraft.
Using the EFIS, WP6, T8, P8, RP48, GF45, TQ6
These need to be configured manually.
Using the LGT or LGT II
Whenever you use an aircraft for the first time, go to the LGT tab, click the Default FS button, then select Device 0 from the drop down and then select ENABLE from the drop down next to it. It will now work but LED's won't light up unless the gear state changes, or you can quit GIT and restart it and all the LED's will light up.
You only need to do this once, you will never need to do it again for that particular aircraft.
Using the GF46
You can configure this manually or have it automatically configured as the auto pilot or the instrument panel, just like GoFlights GFConfig does.
Whenever you use an aircraft for the first time, go to the 46R tab, click the INST or AP button. Now go to the 46O tab, then select Device 0 from the drop down and then select ENABLE from the drop down next to it. It will now work but LED's won't light up unless the gear state changes, or you can quit GIT and restart it and all the displays will light up.
You only need to do this once, you will never need to do it again for that particular aircraft.
Using the GF166
You can configure this manually or have it automatically configured for COM, NAV or ADF radios, just like GoFlights GFConfig does.
Whenever you use an aircraft for the first time, go to the GF166 tab, click the COM or NAV or ADF button, then select Device 0 from the drop down and then select ENABLE from the drop down next to it. It will now work but LED's and displays won't light up unless you click the buttons and use the rotaries. You can also just quit GIT and restart it and all the displays will light up.
You only need to do this once, you will never need to do it again for that particular aircraft.
Using the SECM
Whenever you use an aircraft for the first time, go to the SECM tab, click the Default FS button, then select Device 0 from the drop down and then select ENABLE. It will now work, or you can quit GIT and restart it and all the displays will light up.
You only need to do this once, you will never need to do it again for that aircraft.
Import Wizard
Once you have a completely configured a set of GoFlight devices for one aircraft. You can export the configs for each device and zip them up to make it Import Wizard compatible. Now, when ever you start using a different aircraft for the first time, run the import wizard, selecting the file you have created and all your GoFlight hardware will be configured for the new aircraft. See Importing & Exporting Device Configurations and Sharing Your Work in the on-line user guide.
Lua support
This is now available from release 4.3 onwards.
Detective including Bespoke Events & Variables and Lvar support
This is now working from version 4.4.0.0.
PMDG/iFly/Q400 Support
PMDG 737 support is now available. iFly & Q400 support is obviously not present at the moment because they haven't ported their aircraft yet. GIT will be updated (if necessary) to support these aircraft.
GoFlight Drivers
Any reference to GoFlight drivers or GFConfig in the end user documentation can be ignored for GIT FS2020 as they are not needed. I will update it asap.
Support
Please use the support forum for questions and technical issues.
The following GoFlight hardware works with GIT for FS2020 in exactly the same way as with FSX, FSX SE, P3D and X-Plane:
MCPPRO, MCP, EFIS, P8, T8, RP48, LGT, LGT II, GF45, GF46, GF166, WP6, MESM, SECM, DIO, TQ6
Installation
See this link: https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/16-installation/263-installation-fs2020.html
Starting GIT
Due to the current bugs in the Microsoft FS2020 SDK, start GIT after FS2020 has loaded and the menu has appeared, otherwise the aircraft currently loaded will not be identified (see the status tab to check). It's fine if you change the aircraft, but attempting to fly the current aircraft loaded on start-up causes the issue.
Using the MCP PRO and MCP
Whenever you use an aircraft for the first time, go to the MCP PRO or MCP tab, click the Default FS button, then select Device 0 from the drop down and then select ENABLE from the drop down next to it. It will now work, once you move the rotaries, or you can quit GIT and restart it and all the displays will light up.
You only need to do this once, you will never need to do it again for that aircraft.
Using the EFIS, WP6, T8, P8, RP48, GF45, TQ6
These need to be configured manually.
Using the LGT or LGT II
Whenever you use an aircraft for the first time, go to the LGT tab, click the Default FS button, then select Device 0 from the drop down and then select ENABLE from the drop down next to it. It will now work but LED's won't light up unless the gear state changes, or you can quit GIT and restart it and all the LED's will light up.
You only need to do this once, you will never need to do it again for that particular aircraft.
Using the GF46
You can configure this manually or have it automatically configured as the auto pilot or the instrument panel, just like GoFlights GFConfig does.
Whenever you use an aircraft for the first time, go to the 46R tab, click the INST or AP button. Now go to the 46O tab, then select Device 0 from the drop down and then select ENABLE from the drop down next to it. It will now work but LED's won't light up unless the gear state changes, or you can quit GIT and restart it and all the displays will light up.
You only need to do this once, you will never need to do it again for that particular aircraft.
Using the GF166
You can configure this manually or have it automatically configured for COM, NAV or ADF radios, just like GoFlights GFConfig does.
Whenever you use an aircraft for the first time, go to the GF166 tab, click the COM or NAV or ADF button, then select Device 0 from the drop down and then select ENABLE from the drop down next to it. It will now work but LED's and displays won't light up unless you click the buttons and use the rotaries. You can also just quit GIT and restart it and all the displays will light up.
You only need to do this once, you will never need to do it again for that particular aircraft.
Using the SECM
Whenever you use an aircraft for the first time, go to the SECM tab, click the Default FS button, then select Device 0 from the drop down and then select ENABLE. It will now work, or you can quit GIT and restart it and all the displays will light up.
You only need to do this once, you will never need to do it again for that aircraft.
Import Wizard
Once you have a completely configured a set of GoFlight devices for one aircraft. You can export the configs for each device and zip them up to make it Import Wizard compatible. Now, when ever you start using a different aircraft for the first time, run the import wizard, selecting the file you have created and all your GoFlight hardware will be configured for the new aircraft. See Importing & Exporting Device Configurations and Sharing Your Work in the on-line user guide.
Lua support
This is now available from release 4.3 onwards.
Detective including Bespoke Events & Variables and Lvar support
This is now working from version 4.4.0.0.
PMDG/iFly/Q400 Support
PMDG 737 support is now available. iFly & Q400 support is obviously not present at the moment because they haven't ported their aircraft yet. GIT will be updated (if necessary) to support these aircraft.
GoFlight Drivers
Any reference to GoFlight drivers or GFConfig in the end user documentation can be ignored for GIT FS2020 as they are not needed. I will update it asap.
Support
Please use the support forum for questions and technical issues.
This discussion has been closed.
Comments
Thanks!
Roberto
The device is cheap $18.99 from Amazon: https://www.amazon.com/gp/product/B07X3HST7V/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1
It will show you voltage drops, current load, resistance ... it was very helpful in identifying a few high load GFModules and controllers and problematic power from hubs and/or cables/connections.
Cheers, Rob.
I did have some issues with the GF46 and setting Transponder Inc/Dec Carry, it stop working after hitting about 47 increments.
Unfortunately MSFS updates are coming fast and furious, some bugs fixed, new bugs created so it can be unpredictable at times when using GIT.
Cheers, Rob.
"I updated to version 4.3 from 4.2, however, while opening it, it tries to show the control panel and then closes, but hangs on the task administrator. Could you help me. Thanks."
Best regards
Peter
Can you check the Settings.xml file in Documents\GoFlight Interface Tool and confirm they have actually gone?
Also, each aircraft has to be configured separately, config is not global. See first post in this thread for help on importing and exporting.
Thx
Steve
Best wishes
Steve
Pressing Alt and Enter keys together will toggle the sim from full screen to a resizable window which you can then use the mouse to make smaller.
Best wishes
Steve
(( These need to be configured manually.))
how can I do that
Is there an explanation?
Thank you so much
Best wishes
Steve
I now have Detective, Bespoke Events/Variables and Lvar support working in GIT. It needs a little more work, so look out for it shortly.
Best wishes
Steve
Best wishes
Steve
NB: My MCP pro work for ASOBO TBM, Cessna Caravan, C-172, SR22 but unable to make it work for the Beech Baron and Bonanza