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 EFIS A320NEO or FWB MFS2020
I have an inquiry EFIS does not work for me
How do I activate
How do I activate
Comments
Best wishes
Steve
Steve G.
Even if it is paid by a third party
Even if it is paid by a third party
Even if it is paid by a third party
Best wishes
Steve
To my knowledge there are no videos specifically for the FBW A320. I had to learn the GIT and the Detective by watching the videos and looking at examples from other simmers. Once I had the knowledge of how to use Detective, I was able find the Lvars and events for the EFIS and MCPpro to build the custom Bespoke events required to interface the Goflight controls with the A320 sim.
Steve has done wonderful work in creating the GIT interface for Goflight controls. Its not difficult to learn and there are many people out there to help out if you have issues or questions.
Steve G.
But all the educational videos are very old in 2015
Please please please help me only in EFIS
All other buttons work for me without problems
just two buttons
In the attached picture
In the attached picture
First, these are knobs and not buttons. They require multiple selections, not simple on-off for buttons, so knobs are more complicated to make work. You have to assign each position on the selector.
The mode and the range knobs on the EFIS require custom bespoke events for each knob position. There are no direct Lvars from FBW that you can directly assign to a knob position in the GIT. It requires creating separate bespoke events in the Detective and then assigning each event you create to a position (Position 1, Position 2, etc.) on the mode and range EFIS knobs.
For the Range Selector, create in Detective:
1. an event “A32NX_EFIS_Range_10” and search for and assign “A320_Neo_MFD_Range_1=0”
2. an event “A32NX_EFIS_Range_20” and search for and assign “A320_Neo_MFD_Range_1=1”
3. an event “A32NX_EFIS_Range_40” and search for and assign “A320_Neo_MFD_Range_1=2”
4. an event “A32NX_EFIS_Range_80” and search for and assign “A320_Neo_MFD_Range_1=3”
5. an event “A32NX_EFIS_Range_160” and search for and assign “A320_Neo_MFD_Range_1=4”
6. an event “A32NX_EFIS_Range_320” and search for and assign “A320_Neo_MFD_Range_1=5”
For the Mode Selector, create in Detective:
1. an event “A32NX_EFIS_mode_plan” and search for and assign “A320_Neo_NAV_MODE_1=4”
2. an event “A32NX_EFIS_mode_arc” and search for and assign “A320_Neo_NAV_MODE_1=3”
3. an event “A32NX_EFIS_mode_vor” and search for and assign “A320_Neo_NAV_MODE_1=1”
4. an event “A32NX_EFIS_mode_ls” and search for and assign “A320_Neo_NAV_MODE_1=0”
Notes:
1. This is programmed for the FBW A320 Development version. I have not used it on the Stable or Experimental versions from FBW.
2. Remember that the EFIS is for a 737, not an A320. There are five positions for mode on an A320 and four mode positions on a 737, so one position on the A320 will not be selectable. You can decide which one to not use.
Steve G.
I will try it and let you know the results