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.
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.

Go Flight MCP Pro works?

curtplattcurtplatt
in GoFlight Interface Tool - Technical Support
Hello and thank you for having this forum. I am a very low skilled tech guy and the GIT appears to have a pretty high learning curve. I purchased it because my MCP Pro from Go Flight was only 50% functioning. Animations not working in XPlane when the physical GO Flight MCP switches are pressed. Some of many include AT switch would not animate or light on the software MCP. Pressing a software buttons causes the wrong physical button to light, etc. When I activated the GIT and got a good three green connection on the main page (Software, Plane, GIT) most of my problems with the MCP are gone. Can someone explain that? Thank you for your help!

Comments

  • admin_ppsadmin_pps
    Hi,

    What problems remain? What aircraft are you using? What profile are you using?

    Best wishes
    Steve
  • curtplattcurtplatt
    OK. Sorry for the following complicated explanation: I talked to the GoFlight people who are really nice but admit their products don't work with XPlane. (even though they say so on the website). They relied on a plug-in that was 5 years old or so and the guy who wrote it Sandy Barbour is long gone. So for a GoFlight MCPPro only about half of the functions works and 100% of the EFIS work with Sandy's outdated plug in. This is why I bought the GIT to try and fix the old broken plug-in GoFlight still recommends. By accident I found that if I run the GIT and leave it running in the background, the MCP Pro runs superb in XPlane...Yeah!!!! But...the EFIS does work. If I run the GIT and still use the old plug-in somehow the MCP Pro is using the GIT as a plug-in and then using the outdated plug-in for the EFIS and everything works AOK. Did I miss somehow programming the EFIS correctly with the GIT? Can anyone explain to me the basics of what is happening and what I should do? Thank you so much!!!
  • curtplattcurtplatt
    I am using 738 xplane version 11.35 with the 3rd party profile.
  • admin_ppsadmin_pps
    You can't run GIT and the plugin together. Yes GIT needs to be running in the background. If its the default 738 there is a profile in the Downloads section of the website. Just use the GIT wizard to install the file and all should be good.

    Best wishes
    Steve
  • curtplattcurtplatt
    edited August 2019
    Sorry to be trouble, the GIT is awesome. It looks like a lot of hard work went into it. I am sure it is user error. If I run the GIT with MEMS' 738 XP profile correctly installed, just the MCP Pro works perfectly. The EFIS does not. With the 738 XP profile by Polly Pot the MCP kinda works and no EFIS. If I run the old plug in by Sandy Barbour the EFIS works and the MCP Pro kinda doesn't. If I do what I am not supposed to do and run MEM"S profile in the GIT and the Sandy plug-in at the same time all works correctly. Maybe you have some suggestions to why I am not getting the EFIS to work right with the GIT??? Thank you so much!
  • DavidWilliams5620DavidWilliams5620
    Hi,
    Looking at the MCPPro and EFIS profile, in the b738.XML file which contains the Bespoke Events, it has a reference to D: drive for the .../Documents/GoFlight Interface Tool directory. Is that the drive on your system? I'd fix that and re-import the profile.
    Let us know how you get on.

    David
  • curtplattcurtplatt
    edited August 2019
    Wilco...cheers!!!!
  • admin_ppsadmin_pps
    Well spotted David. That is clearly a bug that must have been around for ages. I'll fix it! :)
  • curtplattcurtplatt
    edited August 2019
    Ok we are close!!! Changing the drive to the correct one for LUA in b738.xml made the mcp work great. I had two EGIS plugged in and recognized. Unplugged one and ran the import wizard and all works great!!!!! Thank you thank you!!! There must be a jumper in the EFIS to set it from EFIS(0) and EFIS(1) right???? Then re run the import wizard to get both to work???? Cheers.
  • DavidWilliams5620DavidWilliams5620
    Fantastic that things are working.

    In terms of the two EFIS, one will be device 0 and the other device 1. The difference between the two is that device 0 will use the capt datarefs while device 1 will use FO datarefs. Example is TERR button. Captain side is "laminar/B738/EFIS_control/capt/push_button/terr_press" while the FO is "laminar/B738/EFIS_control/fo/push_button/terr_press".

    David
  • DavidWilliams5620DavidWilliams5620
    Sorry but these are commands not datarefs.

    David
  • curtplattcurtplatt
    Thank you for everything David! Will they both be assigned device 0 and device 1 correctly by GIT? How does it know which is which?
  • DavidWilliams5620DavidWilliams5620
    Hi,
    Download the attachment. As you previously posted, GIT recognises the two EFIS. That's a good start and you can check that on the status tab.
    Click on the EFIS tab. Click on the device dropdown and it should show device 0 and device 1. If you select device 0 and ENABLE you should see the commands for each of the controls.
    Click on device 1 and then click on import. Select the XML file that you downloaded from the attachment. Device 0 and device 1should now be setup for that aircraft profile.

    The MAP and RANGE rotaries are connected for the default B738 (that's just the way the aircraft works) but the buttons should be independent between the two EFIS devices.

    Let us know how you get on.

    David
Sign In or Register to comment.

© Vanilla Keystone Theme 2025