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.

Developer Support for GIT for X-Plane

I'm currently mapping out all the functions for the MCP Pro for the Rotate MD-80 aircraft. It's actually coming along fairly well.

I spent about 5 hours yesterday and have about 80% full functionality. However I've found some strange inconsistencies. Specifically when it comes to lighting up some of the buttons (I.e. NAV button) it just doesn't behave.

In an effort to do a lot of the mapping I've been doing a side-by-side comparison between the default 737 XML file and the one that I'm editing (through the GIT). I constantly make sure to click "save settings" and export my module-specific XML files in an effort to not lose my work. I've had a good deal of success doing it this way.

The funny thing, there are just times when I'm feeling REALLY confident that I'm using the correct events/variables and not getting the expected results.

Do we have any access to the developer of the GIT? I'd like to share my XML files and get some feedback.
Chris - GoFlight and X-Plane 11.

Comments

  • Hi,

    GIT only updates the lights if the data changes, so when you are configuring GIT the value held by GIT needs to change for it to change on the GoFlight hardware. So you can have a situation where the light is on in the Sim but not on in the GoFlight hardware and vice versa. Triggering the light to go and off, thus changing the value will force GIT to synchronise. Its a quirk that only exists while configuring.

    If that doesn't help and you are certain of the correct variable, install the DataRef Tool plugin (its freely available) and monitor the variable in that to be absolutely sure it changes and stays changed. If it does, then we clearly have a bug that will need urgent attention.

    Best wishes
    Steve
  • edited December 2018
    Thanks Steve. I'll take a closer look tonight. I found the DataRef plugin. It looks like it's going to be an invaluable tool which should make the process of mapping events/variables between X-Plane and the GoFlight modules. Thanks.
    Chris - GoFlight and X-Plane 11.
  • Steve...you are the man. I’ve got about 95% of the MCP Pro finished, GF166 is already finished, and the useable features of the EFIS are complete for the Rotate MD-80. When I’m ready to submit to share my work for download how do I go about that? I certainly don’t want anyone to be forced to go thru all the same work. I’m also going to do the T8, I think that’s the switch panel I’ve purchased, and the transponder modules too. I get both of those tomorrow.
    Chris - GoFlight and X-Plane 11.
  • Just add it to this discussion, with your name and aircraft details and I will put it up on the website.

    Best wishes
    Steve
Sign In or Register to comment.