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.

A2A trainer & MCPPro

Hi Steve

I have the latest version of GIT and have added MCPPro via detective and the A2A .xml file. However nothing works. The display is lit but no response from the rotaries. I have selected "compatible add-on" in the GF software.

If I set there GF software to "FS Default" and disable in GIT it works fine except the altitude increments in 1000's rather than 100's?

Any pointers please.

Paul Gardner

Answers

  • edited November -1
    Hi Paul,

    Did you complete both steps. Import the bespoke events in detective and then import the config via the MCP PRO tab?

    Thx
    Steve
  • edited November -1
    Steve,
    1. imported A2A.xml file
    2. enabled MCPPRO and then imported MCPPRO.xml file.
    Got message "event monitoring stopped", "Lvar monitoring stopped"

    MCPPro displays all alight but rotaries do nothing, neither on the displays or on the acct.?
    Just rechecked the Aerosoft Twotter with the GIT and that works perfect!

    Paul
  • edited November -1
    Hi Paul,

    Can you attach your settings.xml file for me to try.

    Thx
    Steve
  • edited November -1
    Hi Steve

    Won't let me upload says "upload file type is not allowed"
    Paul
  • edited November -1
    Hi Paul,

    Put them in a zip file and it should be OK.

    Thx
    Steve
  • edited November -1
    Hi Steve

    Have saved as a .txt file. 

    Paul
  • edited November -1
    Hi Steve

    zip file as well

    Paul
  • edited November -1
    Hi Paul,

    There is no config data for the A2A in your settings file. You need to go into the MCPPRO tab, click the Import button and load the file A2A_C172_GFMCPPRO.XML.

    If you are doing this and it still doesn't work, can you please check the log and see if any errors have appeared.

    Thx
    Steve
  • edited November -1
    Hi Steve

    Solved thanks.  I was importing both .xml files via the detective. Didn't realise about the import facility on the MCPPro tab.

    Paul
  • edited November -1
    I hate to bring up an old thread, but I have an issue related to the A2A C172 and didn't want to start a new one.

    I just purchased the A2A C172 and am trying to get my GF-MCP pro working.  However, when I downloaded the GIT version (2.0.1131.0) which is on the download page and try to install it, I'm prompted that I have a newer version already installed on my system.  This is true as I have 2.1.2.0 installed for the PMDG 777.

    However, in 2.1.2.0 the Detective button is greyed out as is the GF-MCP Pro tab.  

    I have not attempted to uninstall the newer version and go back to the old version.  I suppose I can try this, but I also don't want to have to uninstall and install back and forth if I can avoid it.  

    Any ideas what I'm doing wrong?

    Jerry
  • edited November -1
    Hello???  Anyone around???

    Just an update, I did install the older version and get the exact same issue where the detective and MCP-Pro tab are grayed out.  I have the GF-Config software set to compatible Add-On and I have the A2A C172 loaded in the VC.  The GIT even recognizes the A2A C172.  But the buttons are still grayed out.

    Any help would be appreciated.  I will apologize in advance, as I must be blind I do not see a search feature to search the forums.  
  • edited November -1
    Hi Jerry,

    Sorry I missed your first post. I suspect you haven't configured the dll.xml file. See here for instructions:


    Best wishes
    Steve
  • edited November -1
    Hi Steve,  

    Thank you.  Yes...that was my issue.

    However, in order to make this work with my A2A C172, I had to uninstall the beta version of GIT which I use for my PMDG T7 and install GIT version 2.0.1131.0.

    I received an error when I tried importing the A2A_C172 xml doc into the Detective.  

    Are you aware of this?  

    Is there any way to have both versions installed?  Or will I need to uninstall and revert back when I want to fly the A2A and use the beta version when I want to fly the T7?

    Jerry
  • edited November -1
    Hi Jerry,

    I'll need to check as you may have found a bug with the Beta version. I'll come back to you asap.

    Best wishes
    Steve
  • edited November -1
    Thank you Steve.  I'll stand by.

    Jerry
  • edited November -1
    Hi Jerry,

    Just tested it out and everything worked fine for me. Make sure you import the correct file into Detective called A2A_C172.XML.

    If you still have the same problem it might be worth renaming the Goflight Interface Tool in My Documents and trying again.

    Let me know.

    Thanks
    Steve
  • edited November -1
    Steve,

    I'm importing the correct file as that is what I did in the older version of GIT.

    I'm not sure what you mean by "Renaming the GIT in My Documents".  Can you shed more light on what  you mean by this please?

    Jerry
  • edited November -1

    Its the directory that contains all your config information. By renaming it, you can keep your old files whilst new ones will be created. I want to see if its a bug related to your config files.

    Thanks

    Steve

  • edited November -1
    Hi Steve,

    My apologies for the delay.  I renamed the folder I found under My Docs, then uninstalled the beta version of the GIT, then reinstalled it.  I tested the A2A C172 and my PMDG T7.  All work as they should.  I'm a happy camper.  

    Thanks for your help and thanks for developing these tools.  

    Jerry
  • edited November -1

    Hi Jerry,

    Can you email or attach the files from your renamed directory so I can detect the bug and fix it.

    Thanks

    Steve

Sign In or Register to comment.