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.
How to ENABLE a device in "GoFlight Interface Tool" if you can't select it?
Hello together an good evening.
First I want to say thank you for that wonderful work you've done!!
I have a GoFlight MCP-Pro and want to use it under FSX with Aerosoft's AXE... The MCP works fine with default planes but if I set in GFConfig (2.23) the "mode of operation" either to FS default OR Compatible Add-On and start GoFlight Interface Tool (2-0-1129-0), I can't enable my devices (see attached pictures)... I got 3 green Lights, the Logfile looks good to me, my GoFlight Modules are recognized but no way to enable it. OS is Windows7 64bit - tested on 2 different systems - same result on both: no devices to select and unable to enable... Can please someone open my eyes and tell me, what's not ok?
Thanks in advance
Peter
First I want to say thank you for that wonderful work you've done!!
I have a GoFlight MCP-Pro and want to use it under FSX with Aerosoft's AXE... The MCP works fine with default planes but if I set in GFConfig (2.23) the "mode of operation" either to FS default OR Compatible Add-On and start GoFlight Interface Tool (2-0-1129-0), I can't enable my devices (see attached pictures)... I got 3 green Lights, the Logfile looks good to me, my GoFlight Modules are recognized but no way to enable it. OS is Windows7 64bit - tested on 2 different systems - same result on both: no devices to select and unable to enable... Can please someone open my eyes and tell me, what's not ok?
Thanks in advance
Peter
Answers
Hi Peter,
Just so I'm clear, when you click the combo box to the left of "DISABLED", no list appears for "Device 0"? If that's so, try moving GIT outside the FSX window as it sometimes corrupts the display and things don't appear.
Best wishes
Steve
Life can be so easy...
Thanx for your advise to put GIT outside! Absolutely correct and it works now - Great!!
So at the moment I'm able to change the MCPPro-displays with GIT loaded. Next step should be to bring the rotarys to work. But not so so easy as I thought - working and thinking a few hours now...
Here is, what I have done so far:
- FSX started
- GFConfig started to change mode to Compatible Add-On
- load a default plane (AirCreation Trike)
- load an Airbus 321 X
- starting GIT
- enable MCPPro and TQ6 tabs outside the FSX-Window
- assign DISPLAY_ALTITUDE and AB_AP_ALT_Select (works perfect)
- assign ROTARY_ALTITUDE / CLOC / AP_ALT_VAR_INC / ROTATE
and also ROTARY_ALTITUDE / ANTICLOC / AP_ALT_VAR_DEC / ROTATE
But nothing happens, if I turn the Altitude knob @-)
What am I doing wrong? Can you please give me only a short push in the right direction?
Best Regards
Peter
That all looks good. I would test the Bespoke events in Detective by selecting them and clicking Test to make sure you have built them correctly i.e. the VC updates.
Best wishes
Steve
short version:
Followed your advise - works now - thx (donated you).
long version:
Read a lot of docs - especially about Detective. For Airbus_X nothing appeard after using "Detected" button so tried a default Airbus... could see then the Variables to use. Also got an Airbus_X LUA-Script with the used Variables inside. Until now got 4 Rotary-Buttons work by creating Bespoke events and assign them to the matchingly ones. I don't know, if I do it the right way, but as a result for me Rotary & Display do their job as needed.
If you permit (and maybe comment it) - here my solution
(if not, feel free to delete the following entries):
Bespoke Event: Button used:
BE_ALT_INC "Add"
Send 65892 using AB_AP_ALT_Select (AP_ALT_VAR_INC) "Send Var"
AB_AP_ALT_Select += 100 "Set +"
BE_ALT_DEC "Add"
Send 65893 using AB_AP_ALT_Select (AP_ALT_VAR_DEC) "Send Var"
If AB_AP_ALT_Select > 0 Next Else NextSkip "If", Value
AB_AP_ALT_Select -= 100 "Set -"
BE_HDG_INC
Send 65879 using AB_AP_HDG_Select (HEADING_BUG_INC)
AB_AP_HDG_Select += 1
If AB_AP_HDG_Select = 360 Next Else NextSkip
AB_AP_HDG_Select = 0
BE_HDG_DEC
Send 65880 using AB_AP_HDG_Select (HEADING_BUG_DEC)
AB_AP_HDG_Select -= 1
If AB_AP_HDG_Select = -1 Next Else NextSkip
AB_AP_HDG_Select = 359
BE_SPD_INC
Send 65896 using AB_AP_SPEED_Select (AP_SPD_VAR_INC)
If AB_AP_SPEED_Select < 399 Next Else NextSkip
AB_AP_SPEED_Select += 1
BE_SPD_DEC
Send 65897 using AB_AP_SPEED_Select (AP_SPD_VAR_INC)
If AB_AP_SPEED_Select > 100 Next Else NextSkip
AB_AP_SPEED_Select -= 1
BE_VS_INC
Send 65894 using AB_AP_VS_Select2 (AP_VS_VAR_INC)
If AB_AP_VS_Select2 < 6000 Next Else NextSkip
AB_AP_VS_Select2 += 1
BE_VS_DEC
Send 65895 using AB_AP_VS_Select2 (AP_VS_VAR_DEC)
If AB_AP_VS_Select2 > -6000 Next Else NextSkip
AB_AP_VS_Select2 -= 1
Two annotations about the Lights-Operation when using it like I do:
- IAS/MACH has to be "rounded" 'cause the Display was telling me "100.00"
- V/S was multiplied by 100, otherwise no normal counting possible
What do you think?
This was only the beginning trying to bring the Hardware-Extensions alive using your tool.
Next will be buying and configuring an EFIS and a YOKE...
I donated your fantastic tool because it's worth it.
Keep going on with your work and good luck.
Hope you get a more "dry" springtime - water can be downright nasty...
Best regards
Peter