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.
Moving to Windows 10 from Windows 7
Hello everyone,
My GIT works well with WIN 7 and my older build.....however, I am upgrading the video card and processor so WIN 10 is my only option. I am hoping I can install the GIT on my new rig. Does anyone have any advice and are there many using the GIT on WIN 10 and XP 11?
Thanks,
Scott
My GIT works well with WIN 7 and my older build.....however, I am upgrading the video card and processor so WIN 10 is my only option. I am hoping I can install the GIT on my new rig. Does anyone have any advice and are there many using the GIT on WIN 10 and XP 11?
Thanks,
Scott
Comments
Been using Win10 and GIT 1.9.1.0 now for quite a while and works well. I see 1.9.2.1 is now out for x-plane. I'll have to download it and try it out.
David
The only issue is non functioning LED's which can be easily fixed. Read the updated installation instructions for GIT as the fix is listed there.
Best wishes
Steve
Thanks,
Scott
Read the IMPORTANT section of the installation instructions here: https://www.pollypotsoftware.org.uk/support/user-guide/goflight-interface-tool-x-plane/33-installation/78-installation.html
Best wishes
Steve
2 - New, (Yellow LED's), GF166's
1 - Older version, (red LED's), GF166 - funny I cannot even get the GIT to turn this
unit on when clicking on the "IDENTIFY" button.
1 - GF-46
I have all but given up....as an Aeronautical Engineer, when I run into a problem troubleshooting, I develop a flow chart to weed out other casual effects. As the designer of theis fabulous GIT, Can you help me by giving me a checklist to use? One that I can go down list to absolutely make sure I am doing this right?
I have read on the worldwide web others who are just as frustrated.... I don't want to give up as it is not in my nature to do so.....
Questions:
1. Does the version of GIT make a difference on WIN 10? On my WIN 7 machine I believe I was using version 1.6. I couldn't find that version anywhere so I found version 1.8 and I am using that one.
At this point, I believe I should just start with a clean slate. So please, let's start there. Sorry for this winded message....I have invested much time and money in the cockpit build and without the radio stack it is non functioning.....
Regards and thanks Steve,
Scott
Hardware:
- The GF166's are notorious for locking up. To solve this, purchase separate powered USB 2 hubs and distribute a GF166 on each hub. Do not buy USB3 hubs.
- Has your new motherboard given you USB3 ports. You must use USB 2 or USB 1 for Goflight hardware, otherwise problems occur.
Windows:
- Download the GoFlight Drivers from GoFlight's website and install them. You don't need them for X-Plane, but they are useful for testing.
- Run GFConfig from the GoFlight Drivers and click on each device in turn. They hardware should light up. If it doesn't, you have the LED issue that has existing since Windows 8. Go back to the GIT installation guide and read the first part about getting LED's to work properly in Windows 10.
GIT:
- Once the Hardware and Software stuff is OK. Try GIT again and if issues remain, copy and paste the GIT log here for me to look at.
Best wishes
Steve
19:49:12 GoFlight Connection Starting.....
19:49:12 X-Plane Connection Starting.....
19:49:13 GoFlight Connection Started
19:49:15 GIP: Pipe Connect Failed!
19:49:18 GIP: Pipe Connect Failed!
19:49:21 GIP: Pipe Connect Failed!
19:49:24 GIP: Pipe Connect Failed!
19:49:27 GIP: Pipe Connect Failed!
19:49:28 X-Plane Connection Started
19:49:28 Aircraft Connection Starting.....
19:49:29 Aircraft Connection Started
19:49:29 Synchronising Switches & Selectors .....
19:49:29 Synchronising Switches & Selectors: Waiting for X-Plane .....
19:49:55 X-Plane: Event Received: Aircraft Loaded/Flight Loaded
19:50:41 X-Plane: Event Received: Aircraft Loaded/Flight Loaded
19:50:42 LvarNamesUpdated!
19:50:42 Creating Bespoke Vars
19:50:42 Bespoke Vars Created
19:50:42 Importing Bespoke Variables
19:50:42 Bespoke Vars Assigned, Importing Bespoke Events
19:50:42 Bespoke Events Temp Imported
19:50:42 Bespoke Events Imported
19:50:42 Loading Aircraft Settings
19:50:42 GetXMLConfigData
19:50:42 GotXMLConfigData
19:50:42 Loading Power
19:50:42 Loading MCPPRO
19:50:42 Loading MCP
19:50:42 Loading EFIS
19:50:42 Loading P8
19:50:42 Loading T8
19:50:42 Loading RP48
19:50:42 Loading MESM
19:50:42 Loading WP6
19:50:42 Loading LGT
19:50:42 Loading LGT II
19:50:42 Loading GF46
19:50:42 Loading GF45
19:50:42 Loading TQ6
19:50:42 Loading DIO
19:50:42 Loading GF166
19:50:42 Loading SECM
19:50:42 Loading Joysticks
19:50:42 Clearing Displays
19:50:42 Reset Data
19:50:42 Aircraft Settings Loaded
19:50:42 Calling Aircraft Changed
19:50:42 Aircraft Changed
19:50:42 XPlane: Event Received: Sim State 1
19:51:10 Synchronising Switches & Selectors Complete
What do you think?
I can't thank you enough for your help.....as this build right now is useless unless I we fix this issue and I have look for an alternate way for my radio stack.....
Scott
There is nothing in the log to indicate an issue. Have you done the Windows and Hardware steps I recommended? What is happening now to GIT and the GoFlight modules? Does the Detective button become enabled?
Best wishes
Steve
Any ideas on the GF-46?
I will check out the Detective button...
Thanks again Steve - you are awesome!
Scott
Also make sure the "chain" from the hubs back to the PC is all USB2 including the port into the PC itself.
Whilst you wait for the hubs, have you tried just having one of the units connected?
Best wishes
Steve
Hubs arrived today...I'll plug all units into separate powered hubs when I get home from work ; )
Say do you think it matters what version of GIT I use? Been using 1.8....thought that might have been causing my issues....if not I will go to the latest version...what is that now 1.9?
Thanks again,
Scott
The latest version is 1.9.2.1. I would strongly recommend that you upgrade as lots of bug fixes in the later releases.
Best wishes
Steve
I have disappointing news...just spent 60 bucks on USB 2.0 powered hubs and things went from bad to worse. Nothing works at all.... or intermittent at best. Goflight has not responded either - very poor customer service. I am thinking I will try one last thing that being the most recent GIT version. Very disappointed.....spent close to $800 USD on all this and nothing works and Goflight doesn't even care to help..... do you know anything about Sandy Barbour's interface for Goflight? I am desperate to solve this...
Scott
We must be missing something here. Can you start off with just one GF166 connected directly to your PC. Delete Documents\GoFlight Interface Tool. Start GIT and configure the GF166 for COM functions. Now test it with a default aircraft and tell me what happens on the hardware, in X-Plane and in the GIT log.
Best wishes
Steve
Scott
Understand how frustrating this is. From my experience GIT has been way ahead of other tools for programming and setting up the GoFlight hardware.
GoFlightInc hasn't been all that responsive by the look at their Community Forums. Either that or nobody posts anything on the forums.
I don't have half the equipment you do but I've attached a picture of what the Win10 settings should look like if Win10 is recognising the devices. What does yours look like?
You mentioned a new processor. Did this include a new motherboard as well, and if so which one? When I upgraded, the new motherboards are limited in USB 2.0 ports. 2 on the front and 2 on the back, in my case. Everything else USB 3.0 ports.
Any chance you can do a screen shot of your status page and attach a zip file of your ../Documents/GoFlight Interface Tool files.
Hope I can help.
David
If you are not going to follow my instructions so I can help you, then the best thing to do is to phone GoFlight (don't bother with their forum) and ask them how to get their hardware stable on your PC.
This is not a GIT issue, its hardware!
Best wishes
Steve
I have followed your instructions to the tee and tried to do so many times as to not make a mistake...I do not understand why all is not working. Sometimes it all seems to work then the next time I launch XP? Nothing....or just a few LED's will light up....or the radio stack partially lights but is non-functioning as far as it won't accept any inputs like turning a knob to change frequencies for example. I called Goflight and got the runaround. Their official statement is they do not support X-Plane but for $60USD/hr they would trouble shoot. Tony there did send me a "test program" but that program didn't even open and I haven't had time to follow up on that.
Dave thanks for chiming in....I will look and get back to you.
Frustrating....this just shouldn't be this difficult.
Scott
If you can get FSX up and running and use GoFlight's own drivers, the problem will still exist and they will have to support you then!
Unfortunately you have the two of the most finicky GoFlight units. I had the same problem you are having when I first bought them back in 2008 running Windows 7 and FSX using GoFlight's drivers (way before GIT was built or thought off). They constantly locked up or partially displayed. Rob Ainscough from Avsim and others have had the same issue.
The solution that has always worked for people, is no USB 3 ports in use anywhere in the chain. Try one device at a time, adding the others when the first is working OK and distribute across different powered USB2 hubs. With a bit of fiddling it settles down eventually.
Perhaps your new hubs are not up to scratch? It may be worth contacting Rob to find out what hubs he bought or the chap in this thread who had the same problem as you but fixed it: https://www.pollypotsoftware.org.uk/vanillaforums/discussion/715/problem-with-duel-gf166s#latest
Best wishes
Steve
Scott
I am returning the 3 previous USB 2.0 powered hubs I purchased and purchased the hubs that were recommended in your last email by klosurdo - that is the Plugable brand hubs. They will be here Thursday.
Scott
Scott
They are in the GIT Settings tab. See https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/19-operating/23-the-settings-tab.html
Best wishes
Steve
Here is the official word from Tony at Goflight:
"Hello Scott,
Apologies for the late reply. For the test software, to interpret it – if the test software shows that signals are being sent, then we know that the modules themselves are fine and the problems lie within the software of the computer. To see if the test software is working, when you run the .exe file, the program should read DETECTED for the GF-166 or GF-46. The lights should respond when you turn the dial.
If they are doing this, then the software you are using is creating the issues. The Windows10 upgrade would most likely be to blame. If that’s the case, there isn’t must we can do at this time."
The test program he sent checks out fine....looks like I will never get the goflight units to work....bummer...I have tried everything. I received three "PLUGABLE" 2.o USB powered hubs like the ones mentioned in the other forum thread....no deal this made no difference. I am out of options.
Hopefully Flight Illusion will work. Very expensive but at this point I don't have any other options...
Thank you for you help during this troubling test period.
Scott
Did you change your motherboard for your new build?
Thx
Steve
I'm trying to understand everything that has changed, because you did have all this working before the upgrade. So the two key things are Windows 10 and the motherboard (USB changes).
I don't think its Windows 10, most of my customers are now using Windows 10, as do I. I have had this very same issue on Windows 7 with FSX and GoFlight supplied USB hubs along time ago.
I'm wondering whether all your USB ports on your new motherboard are USB3 or there is some setting in the motherboard BIOS to turn off or enable so they are more compatible.
I find it odd that the test program works - I'm suspecting it doesn't use the GoFlight SDK that dev's have to use to interface to their gear. I would love to see the result of the GoFlight gear running FSX and their drivers to see if the lockup still occurs.
If I was you, I would check the motherboard BIOS settings related to USB and see if anything springs out at you and triple check you have plugged the hubs into USB2 ports.
Best wishes
Steve
Thanks Steve.....