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.
GoFlight Modules Up and Running
I feel like I’ve won the lottery. After months of reading, configuring, trial and error and much frustration I believe I have my eight GoFlight modules up and running. Thought I would pass along some of what I experienced, what worked and what didn’t.
I was fortunate to have bought a PCI-E 5 port USB 2.0 expansion card in July 2017 when I began this GoFlight path. Made by Syba, I bought it off Amazon for $30.54, and am I glad I did. In the end it is now running two 166’s, my MPC PRO, EFIS and my GF 46. All appear to be working fine as far as I can tell. All I have now is dashes on the MCP panel but I do believe it is functioning. The GF46 is functioning in my default aircraft, CRS, Heading, both radios, ADF and DME all work as advertised. The two 166’s work in both default aircraft and the 737NGX. The Syba card is no longer available. I see some for PCI, but not PCI-E.
Of note, neither of the 166’s nor the GF46 would work, at all, on any hub I tried. I went through five, D-Link, Pluggable, Anker; none of them would power the 166’s nor the GF-46.
I installed one at a time, making sure it was recognized in GoFlight config software, then brought up both a default aircraft and then the 737NGX. Check for functionality. Power down; install next module, repeat. Nearly three full days of SLOWLY installing each module, one at a time, testing, swapping out, checking power management, etc.
The GF-T8-2 is plugged into one of the two USB 2.0 ports on the back of my Asus Hero IX MB. The two GF-P8’s are on the Plugable Hub which is plugged into the other USB 2.0 port.
I’m learning LINDA for my Thrustmaster Warthog HOTAS, Throttle and Crosswinds. Default aircraft all set up, will start next to assign axes and buttons for the 737NGX. I might have some more learning to do for the throttle setup but I believe I can begin the controls setup process now.
After that it’s back to rereading the GIT manuals for about the 6th time and starting to get my 737NGX airworthy and begin the slog up the never ending GIT and PDMG learning curve.
I’m sure I’ll be back here before it’s all over trying to get it all configured, but I do believe serious progress has been made. It is really nice to see eight functioning GoFlight modules all lit up and ready for the journey.
Cheers,
Bob
I was fortunate to have bought a PCI-E 5 port USB 2.0 expansion card in July 2017 when I began this GoFlight path. Made by Syba, I bought it off Amazon for $30.54, and am I glad I did. In the end it is now running two 166’s, my MPC PRO, EFIS and my GF 46. All appear to be working fine as far as I can tell. All I have now is dashes on the MCP panel but I do believe it is functioning. The GF46 is functioning in my default aircraft, CRS, Heading, both radios, ADF and DME all work as advertised. The two 166’s work in both default aircraft and the 737NGX. The Syba card is no longer available. I see some for PCI, but not PCI-E.
Of note, neither of the 166’s nor the GF46 would work, at all, on any hub I tried. I went through five, D-Link, Pluggable, Anker; none of them would power the 166’s nor the GF-46.
I installed one at a time, making sure it was recognized in GoFlight config software, then brought up both a default aircraft and then the 737NGX. Check for functionality. Power down; install next module, repeat. Nearly three full days of SLOWLY installing each module, one at a time, testing, swapping out, checking power management, etc.
The GF-T8-2 is plugged into one of the two USB 2.0 ports on the back of my Asus Hero IX MB. The two GF-P8’s are on the Plugable Hub which is plugged into the other USB 2.0 port.
I’m learning LINDA for my Thrustmaster Warthog HOTAS, Throttle and Crosswinds. Default aircraft all set up, will start next to assign axes and buttons for the 737NGX. I might have some more learning to do for the throttle setup but I believe I can begin the controls setup process now.
After that it’s back to rereading the GIT manuals for about the 6th time and starting to get my 737NGX airworthy and begin the slog up the never ending GIT and PDMG learning curve.
I’m sure I’ll be back here before it’s all over trying to get it all configured, but I do believe serious progress has been made. It is really nice to see eight functioning GoFlight modules all lit up and ready for the journey.
Cheers,
Bob
Comments
Got the same hassle with my 4 panels and programming several bespoke events for the ZIBO 738.
What i like to see in the tool is a better way of error tracing. So, increase logging levels within GIT can be from benefit with tracing down problems in connecting GF modules.
Cheers,
Andre