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.

Simconnect Issue with GIT for MSFS

bigmartybigmarty
in GoFlight Interface Tool - Technical Support
I have recently acquired MSFS 2020. I downloaded the GoFlight Interface Tool for MSFS but when I start it I get a yellow light in the Simconnect panel, but green light in the left and right panels. What is causing this and is there a fix? I have read the posted startup procedure and think I am doing it right. The MCP pro remains blank.
Thanks for any help.
Martin

Comments

  • admin_ppsadmin_pps
    It's most likely you have not got the GIT WASM Module in your Community folder. Manually install it (it's downloadable). If you still have problems, post your GIT Log so I can see what is happening.

    Best wishes
    Steve
  • bigmartybigmarty
    Thank you. I installed the WASM module and this has partially fixed the problem. The MCP Pro is now active except for the altitude rotary. When turned the numerical value in the MCP flickers but does not change the altitude number in the MCP or in the aircraft. When the dial on the aircraft console is turned, this changes the value in the MCP.

    Can you help with this?
    Thank you again.
    Martin
  • admin_ppsadmin_pps
    Asobo have recently changed how the autopilot works, and now have multiple variables for various display windows on the AP depending on the mode/state. Try changing the Data/Variable for the altitude window to AUTOPILOT_ALTITUDE_LOCK_VAR:1 on the MCP Pro tab in GIT.

    Best wishes
    Steve
  • bigmartybigmarty
    I appreciate your help. I spent some time trying to make the change suggested but was not successful. I cannot find AUTOPILOT_ALTITUDE_LOCK_VAR:1 under the MCP Pro tab. I tried uninstalling and reinstalling GIT and the module, but am now back to having a totally blank MCP.

    Attached is a screen shot of the MCP pro tab, and the GIT log.

    I guess I will need some further guidance.
    Thank you.
    Martin
  • admin_ppsadmin_pps
    Click Defaut FS to get the default settings back. Then select the Input for the altitude display and then change the Light/Disp Data variable to AUTOPILOT_ALTITUDE_LOCK_VAR:1

    Best wishes
    Steve
  • bigmartybigmarty
    OK, I am back to where I was before - MCP Pro working except for altitude rotary. Followed the changes you suggested but no success. I should mention that I also have a Bravo throttle quadrant and the altitude selector on the Bravo give the same result as the MCP; ie does not change the altitude value in the aircraft.

    Is there something else I can try?
    Thanks again for your help.
    Martin
  • admin_ppsadmin_pps
    There are a number of AUTOPILOT_ALTITUDE_LOCK_VAR's e.g. AUTOPILOT_ALTITUDE_LOCK_VAR:2, AUTOPILOT_ALTITUDE_LOCK_VAR:3 etc. Try at least the first few, one of them will probably work.

    Best wishes
    Steve
  • carversorelcarversorel
    admin_pps said:

    It's most likely you have not got the GIT WASM Module in your Community folder. Manually install it (it's downloadable). If you still have problems, post your GIT Log so I can see what is happening.

    Best wishes
    Steve

    Hi
    I have a same issue with my set up ( simconnect inbound). Could you send to me the link for to install Wasm module in community folder.

    Thank you

    Jean
  • admin_ppsadmin_pps
    It's available in your account, in the same place you downloaded GIT.

    Best wishes
    Steve
  • bigmartybigmarty
    I do have the WASM module in Community folder. I have tried all AUTOPILOT_ALTITUDE_LOCK_VAR options 0 thru 8 or 9 without change. Recent log is attached.
  • admin_ppsadmin_pps
    See if its stored in an lvar (use Detective).

    Best wishes
    Steve
Sign In or Register to comment.

© Vanilla Keystone Theme 2025