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.
The GF-166A has nearly reduced me to tears.
Steve -
I own two GF-166A’s. I purchased them from GoFlight about 5 years ago and am just now trying to use them as I’ve finally built a simulator in earnest. I’ve got $6k into everything and it all works but the #@##$& GF-166A. I have the latest drivers of everything and nothing in Program Files or Program Files (86). I have plugged them into a 2.0 hub as well as direct into 2.0 and 1.0 inputs on the back of my computer. Sometimes they show on the GF configuration, sometimes don’t. Sometimes one will show but the other won’t. I’ve gone through all the standard stuff (device manager, usb power management etc etc etc) with no success. They show on the GIT but won’t do a thing. Fsuipc wont even acknowledge their existence.
I have never in my 64 years dealt with an issue so frustrating. They have made me feel absolutely incapable and incompetent. The GF166A has beaten me into a nearly inconsolable pile of tears. I have spent hours upon hours upon hours trying to figure things out.
I tried running GFWindows8fixer but the log file comes back with multiple lines of Device Parameters: Unable to open.
I don’t know what to try next. I am wide open to suggestions. Anything. I want to take a hammer and beat them into tiny bits. In the end I do believe there is a simple and elegant solution (other than throwing them in the garbage where they belong), I just don’t know what it is or where to turn. Today I wrote an email to Tony at GoFlight but I have no expectations of a response. This is a simply ridiculous problem.
I apologize for the rant. I am frustrated to the boiling point
Bruce
I own two GF-166A’s. I purchased them from GoFlight about 5 years ago and am just now trying to use them as I’ve finally built a simulator in earnest. I’ve got $6k into everything and it all works but the #@##$& GF-166A. I have the latest drivers of everything and nothing in Program Files or Program Files (86). I have plugged them into a 2.0 hub as well as direct into 2.0 and 1.0 inputs on the back of my computer. Sometimes they show on the GF configuration, sometimes don’t. Sometimes one will show but the other won’t. I’ve gone through all the standard stuff (device manager, usb power management etc etc etc) with no success. They show on the GIT but won’t do a thing. Fsuipc wont even acknowledge their existence.
I have never in my 64 years dealt with an issue so frustrating. They have made me feel absolutely incapable and incompetent. The GF166A has beaten me into a nearly inconsolable pile of tears. I have spent hours upon hours upon hours trying to figure things out.
I tried running GFWindows8fixer but the log file comes back with multiple lines of Device Parameters: Unable to open.
I don’t know what to try next. I am wide open to suggestions. Anything. I want to take a hammer and beat them into tiny bits. In the end I do believe there is a simple and elegant solution (other than throwing them in the garbage where they belong), I just don’t know what it is or where to turn. Today I wrote an email to Tony at GoFlight but I have no expectations of a response. This is a simply ridiculous problem.
I apologize for the rant. I am frustrated to the boiling point
Bruce
Comments
I ran windows8fixer.
I plugged a GF166A into a 2.0 plug on the computer and reran w8fixer. I left all knobs and buttons unassigned.
I started the GIT and P3D and got a 166 tab. I selected device0 and enabled Com.
All of a sudden it woke up and started working perfectly in both frequency selection and transfer as well as the lower com1 left button and the com2 right button. The virtual cockpit radios were right in sync too.
I exited P3D, plugged in the second GF166, closed gfconfig and reran w8fixer. Reopened gf config and started P3D and GIT. The GF1, the one I had first assigned to com simply went dead. GF2, which I assigned to nav, worked perfectly. GF1 showed in GoFlight config but it was unresponsive. When I clicked on GF2 in GoFlight Config the lights would come on the NAV GF166. When I click on GF1 in GFC the lights will turn off on the previously selected NAV GF2 but they do not turn on on the GF1.
The GF1 just goes dead to the fs and git even though it shows in GFC. To verify, I tried to recreate the same install later in the day and it did not go well. NAV worked for a while then stuck. After a computer reboot the frequencies would change via the rotary knob and in the virtual cockpit but they wouln’t display display on the GF2
I don’t think I am far from a solution, I just don’t know how to get there. Any help is really appreciated. I’m at wits end.
Bruce
You may already know, but any time you run Windows8Fixer be sure to reboot your PC before using the modules.
When initially setting up all the GF modules, I recommend you add ONE device at a time, run Windows8Fixer, reboot ... repeat the process for each GF module.
Anyway, see my response at AVSIM.
Cheers, Rob.
Is this issue resolved now?
Best wishes
Steve
Bruce tried valiantly to resolve, but he ultimately called it quits and I think he sent the unit(s) back to GoFlight?
Cheers, Rob.
I was unable to get the 166A's working after days and days of ridiculous frustration. I finally just bought a Logitech last week and while it's not ideal it works perfectly. I am going to send the units back to GoFlight, crushed to bits, one in a plastic bag marked C and the second in a plastic bag marked N. As a side note, the GIT makes my MCP Pro a dream to use! For some reason I'm not getting 3 greens on the LGT when the gear is down, but I can live it unless there is an easy fix?
Bruce
I'm not aware of a problem with the LGT and the PMDG. I will test and come back to you.
Best wishes
Steve