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.
Gf rack Combo, functions are programmable when connected but connections die out
Hi,
I have a small rack with the following GF units : GF-MCP, GF-166A VRP, GF-LGT II , GF-MESM and GF-46.
Units are connected through a powered usb-hub to my pc.
My Pc only has usb-3 ports but the hub itself is usb 2.0 and I think I read somewhere that it could be a workaround for that problem, please let me know if otherwise.
When a unit successfully connects, it is fully programmable via your plugin , for example no problems assigning GF-46 to be switched between Transponder and barometer, or the GF- 166A VRP to alternate between Nav & Com radios, it works like a charm when it works.
However, all 5 units will not get detected simultaneously, and connection is either completely dropped or they start being less and less responsive until they either freeze up or go all blackout.
I have tinkered around with different hubs and made sure a lack of power is not the problem.
The interface tool also causes X-plane to freeze or crash quite a lot and I´ve looked around the forums here and other sites as well hoping to find some solution..
Please advise if there is something Im not seeing here, thanks
I have a small rack with the following GF units : GF-MCP, GF-166A VRP, GF-LGT II , GF-MESM and GF-46.
Units are connected through a powered usb-hub to my pc.
My Pc only has usb-3 ports but the hub itself is usb 2.0 and I think I read somewhere that it could be a workaround for that problem, please let me know if otherwise.
When a unit successfully connects, it is fully programmable via your plugin , for example no problems assigning GF-46 to be switched between Transponder and barometer, or the GF- 166A VRP to alternate between Nav & Com radios, it works like a charm when it works.
However, all 5 units will not get detected simultaneously, and connection is either completely dropped or they start being less and less responsive until they either freeze up or go all blackout.
I have tinkered around with different hubs and made sure a lack of power is not the problem.
The interface tool also causes X-plane to freeze or crash quite a lot and I´ve looked around the forums here and other sites as well hoping to find some solution..
Please advise if there is something Im not seeing here, thanks
Comments
In Power Options, edit your current plan and ensure USB selective suspend setting is Disabled.
The GF166 units are notorious for locking up. It is not a GoFlight Interface Tool issue as they still lock up if you use GoFlights own driver software. I suspect these units needed a firmware upgrade, just like MCP Pro had, which when running the A22 firmware would lock up just like the GF166's. You will need to find a solution that works best for your individual setup. You can search this forum for all the various ways users have found a work around to stopping the GF166's locking up. E.g. Some found tweaking BIOS usb settings helped, using specific USB 3 hubs only, spreading the GF166's across different hubs on different ports or going fully USB 1 which is what GoFlight recommended for all their hardware. Its trial and error for each system.
You can also try increasing the Write Delay and Cmd Delay sliders on the settings tab which in some cases has reduced the amount of data going to the GF166's and reduced the risk of lock ups.
The software crashes could be down to your GoFlight hardware/windows setup currently being unstable or you are running an addon that may need some GIT tweaks to work with it correctly. Whilst your PC/hardware needs some tweaking, I would suggest disabling all addon's except for GIT and its plugin to simplify getting your setup stable, then reintroduce the addons and see if the instability continues.
Best wishes
Steve
PS For changing the USB settings use Control Panel, and not Devices from Windows Settings.
I bought a new Chillblast PC in October and with 6 GoFlight units plus the MCPPro and EICAS unit I needed to ensure they would be recognised by Windows with zero issues.
The Asus motherboard has no USB2 ports but does have USB2 headers. So I asked Chillblast to get one of these and install it. They bought it from Amazon. The link is very long so copy and paste the text below to find it.
Xiatiaosann 2 Pack 2 Port USB 2.0 Rear Panel Expansion Bracket
It guarantees you two or four genuine USB2 ports. I plugged my powered USB2 hub into it and all GoFlight units are recognised by Windows 11.
I have no issues with my 2 GF166 units or the 2 GFT8, P8 or GF-LGT. The MCP Pro and EICAS work fine too with the PMDG737NGXu.
So I would recommend that £9 unit to resolve your issues.
Ray (Cheshire, England)
Ok , I will try that expansion bracket as a last resort, otherwise I´m probably gonna get ready to say goodbye to my GF Setup.
But if it works I will be really glad as the GF units give a quality feel indeed.
Will get back to you guys when I have got the stuff ready to try.
Brgrds // Jens
Ray (Cheshire, England)
So I´m making progress ,but are running in to new issues this time...
First, All GF units connected via powered usb adapter to computers usb 2.0 socket ( There was a factory cover plastic bit hiding it.)
Last time I could get the units to show up in the Interface tool for a while and I even got some units to work for a moment also.
Win 10 recognizes all units and they show up with correct names under devices, so connection seem solid.
Usb selective suspend is disabled, and each usb port has been configured so that the computer will not shut down to save power ( After connecting GF units this option became available for those also, so that too is configured likewise.)
The Interface tool starts and when in sim mode,it starts to scan for files and there it freezes .. according to the FAQ I should install the latest Goflight Drivers but the link to those get me to dropbox where it says the file is deleted.. I have looked around on the net but could only find the Goflight config program and not the actual drivers .
I am running Xplane 12 without any other plugins , tried restarting the interface tool but it is very unstable andpoints out that last config was not saved.. last time I could get the settings for the units to be customizable but this time I couldn´t even make it that far... Is there something I´m clearly missing here? Computer seem to register all units fine but the interface tool seems to be doing worse than last time I attempted this?
The interface tool became unresponsive after a few attempts and I could not get out of it without having to force shutdown programs via the task manager as it made xplane unresponsive as well.
And I had wiped my harddrive, reinstalled win10 and xplane fresh, so there should not be any addons or plugins causing compatibility issues either.
I will probably look to sell my GF gear if this cannot be resolved...kinda getting to my wits end here X-(
Yes , it was , but I decided to move on to other hardware solutions since I love to solder & tinker anyway, my units will be sold and shipped to anyone for a very fair price if you know anyone interested, let me know .
Brgrds// Jens
However, I did notice that when the GF modules are connected to FSX using the original GoFlight DLL, the connection seems to remain solid, even when connected through a USB3 port, and there is less noticeable lag than using GIT with MSFS. And when one of the modules (particularly my MCP) decides to go dark, it will remain dark until the module is unplugged and plugged back into the system.
With only GoFlight software I seem to have less issues, so that does point to some interaction between the Windows USB/HID subsystem and GIT that is specific to it, which causes the modules to either go into some kind of sleep mode or freeze.
Even with USB power management completely turned off it appears that the modules somehow still get into some kind of disconnected/sleep state.
Stabilising GoFlight hardware has always been a major issue. I had the same problems with my GoFlight airliner setup with supplied usb hubs from GoFlight using FSX (before GIT event existed). There are many posts in the forums on how people have managed to get a stable setup.
Best wishes
Steve