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.
GIT MCP PRO Install Issues
I have had my GF modules up and running now for about 10 days. All seem to operate as they should. However, I cannot get my MCP Pro to display anything when I have the PDMG 737NGX loaded and running. Perhaps I am misinterpreting the manuals or making errors unknown to me.
Some details:
I’m running PD3V4.4 under Win10. I have a MCP Pro, EFIS, (2)166’s, (2)GFP8’s, a GF46 and a T82. I have run them under half a dozen default aircraft and all work fine, including the MCP Pro.
GoFlight software is installed in C:\Program Files (X86). GoFlight Config recognizes all modules. I have the MCP Pro and EFIS set for Compatible AddOn (when not using a default aircraft). I downloaded GIT P3D4_64, extracted and installed it into the same directory as the GF software. I went into my P3D dll.xml file and indeed did find the correct new Launch Addon lines added to the bottom of the dll.xml file.
I load the 737, I then load GIT. I get two steady green buttons and one blinking. All the modules are recognized by GIT. Detective IS grayed out which is what I would expect.
OF NOTE: I did NOT get a warning message from P3D when first loading GIT. I’m not sure if the manual is just outdated or not. But again, the dll.xml file contains the correct entry. I also can see GIT in the AddOn drop down menu in P3D.
The MCP Pro displays dash lines in the middle of each LED display. It is unresponsive.
Again, I have spent much time switching back and forth between default aircraft and the 737. I’m confident the MCP Pro works as each time I load a different default aircraft I get control of autopilot buttons and correct display info. I can configure my virtual cockpits using the MCP Pro buttons and dials and the display LED’s provided correct info.
Being a new user I realize I may be doing something wrong. I have read and reread the manual.
As I understand the PDMG 737NGX is hard coded into GIT, I went no further in the manual such as downloading modules or using Detective. All in good time.
One last item that may be pertinent. I do use LINDA to set up my default controls, TM HOTAS, Throttle and Crosswind rudder. I did ensure there was no conflicts in LINDA for any MCP Pro settings. I also DO NOT load LINDA when using GIT.
Any suggestions would be most appreciated. Thanks!
Bob
Some details:
I’m running PD3V4.4 under Win10. I have a MCP Pro, EFIS, (2)166’s, (2)GFP8’s, a GF46 and a T82. I have run them under half a dozen default aircraft and all work fine, including the MCP Pro.
GoFlight software is installed in C:\Program Files (X86). GoFlight Config recognizes all modules. I have the MCP Pro and EFIS set for Compatible AddOn (when not using a default aircraft). I downloaded GIT P3D4_64, extracted and installed it into the same directory as the GF software. I went into my P3D dll.xml file and indeed did find the correct new Launch Addon lines added to the bottom of the dll.xml file.
I load the 737, I then load GIT. I get two steady green buttons and one blinking. All the modules are recognized by GIT. Detective IS grayed out which is what I would expect.
OF NOTE: I did NOT get a warning message from P3D when first loading GIT. I’m not sure if the manual is just outdated or not. But again, the dll.xml file contains the correct entry. I also can see GIT in the AddOn drop down menu in P3D.
The MCP Pro displays dash lines in the middle of each LED display. It is unresponsive.
Again, I have spent much time switching back and forth between default aircraft and the 737. I’m confident the MCP Pro works as each time I load a different default aircraft I get control of autopilot buttons and correct display info. I can configure my virtual cockpits using the MCP Pro buttons and dials and the display LED’s provided correct info.
Being a new user I realize I may be doing something wrong. I have read and reread the manual.
As I understand the PDMG 737NGX is hard coded into GIT, I went no further in the manual such as downloading modules or using Detective. All in good time.
One last item that may be pertinent. I do use LINDA to set up my default controls, TM HOTAS, Throttle and Crosswind rudder. I did ensure there was no conflicts in LINDA for any MCP Pro settings. I also DO NOT load LINDA when using GIT.
Any suggestions would be most appreciated. Thanks!
Bob
Comments
Please make sure you have enabled the MCP PRO in GIT when the NGX is loaded. If you have, then please read the FAQ entry "My MCP PRO or MCP Advanced is not updating its display (just showing zeroes or dashes)" here: https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/16-installation/70-faq-goflight-interface-tool.html
Best wishes
Steve
Thank you for the quick response. I looked in GIT under the MCP Pro tab. I changed it to 0 enabled. When I did that the panel went dark. I shut down GIT and P3D. Reloaded P3D and my 737. However, this time I ran GIT FIRST as Admin prior to loading P3d and the 737. Both the MCP Pro and my EFIS appear to be functional now. I say that as Heading, Course, FD, CMD, AT Arm all seem to function. I also have control of the EFIS buttons in the VC. My Vert Speed is dark, but that may be because I don't know what I'm doing yet and it is not suppose to become functional until takeoff.
I'm not sure, nor can I read in the manual, what each Device setting and various other settings should be for each tab. I'm going to make an assumption that much of that is in the Detective and module configuration manuals. Given I'm just interested, at this point, in a functional MCP Pro and EFIS for the 737NGX, I have not read any of those.
Anyway... I think I'm a Happy Camper. Much to keep me busy for quite some time. "I'll be back" if anything pops up. THANK YOU for lighting up my GoFlight modules. Very much appreciated!!
Bob