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 GF166 display blank - but only for PMDG737NGXu
Hi Steve, firstly, a happy new year to you and yours. I am loving your software with P3D v5.3HF2 but have recently encountered a strange problem I can't resolve.
I was flying the PMDG737-800 when the sim froze and I had to terminate the process. During this the display turned into a rainbow of strange colours but once closed the desktop colours were fine.
The next time I launched P3D with that aircraft the two GF166 units both display fine. But once the profile for the 737 has been loaded by GIT the COM unit was blank. The NAV one was fine.
If I press any of the buttons on the COM unit the display comes to life and is fine thereafter. I've looked through the various files GIT uses but I can't see anything different to both 166 unit settings.
This problem only happens with the PMDG. My other aircraft are fine.
Do you have any idea how this can be fixed please? Happy to provide files you require.
I was flying the PMDG737-800 when the sim froze and I had to terminate the process. During this the display turned into a rainbow of strange colours but once closed the desktop colours were fine.
The next time I launched P3D with that aircraft the two GF166 units both display fine. But once the profile for the 737 has been loaded by GIT the COM unit was blank. The NAV one was fine.
If I press any of the buttons on the COM unit the display comes to life and is fine thereafter. I've looked through the various files GIT uses but I can't see anything different to both 166 unit settings.
This problem only happens with the PMDG. My other aircraft are fine.
Do you have any idea how this can be fixed please? Happy to provide files you require.
Cheers,
Ray (Cheshire, England)
Ray (Cheshire, England)
Comments
When I pressed COM a message appeared saying to press OK to revert to default settings. Having done so I discovered I now had Com frequencies to 0.025. But these weren’t being displayed properly and changing frequencies was a nightmare.
I searched for an option to undo this action. Couldn’t find one. I had a backup from a few months back and checked what settings I had for GF166 in PMDG.xml. The entries were all blank and very different to the current PMDG.xml.
Having made a copy of the current file I copied and pasted the GF166 values from my backed up file into the current one.
That worked and I now have 0.05 frequency values and the GF166 COM display remains on when the PMDG737 has stabilised.
It would have been a lot easier with instructions or an option to toggle between 0.025 and 0.05.
Still no sign of Steve. I hope he’s okay.
Ray (Cheshire, England)
I'm OK. Took a long xmas break and then was sick for a while.
Best wishes
Steve
I do have one issue when starting things manually as opposed to using SimStarterNG. That program is just a way of launching multiple executables to ease the workload.
GIT connects fine and shows my current aircraft (so all programmed buttons and switches work) with SimStarterNG.
However, if I start P3D manually, wait until the aircraft is at a parking position and then launch GIT I get the three green LEDs but the aircraft name just says Default and doesn’t display its name.
The log just says Waiting for SimConnect…
But the SimConnect LED is lit. Can you reproduce this? I can’t understand why it’s fine via SimStarterNG but not manually.
Ray (Cheshire, England)
Thx
Steve
Ray (Cheshire, England)
Here's the log. I started P3D manually with the PMDG737-800 selected at the Scenario screen. Then with P3D fully loaded I manually launched GIT.
10:05:12 GoFlight Connection Starting.....
10:05:12 SimConnect Connection Starting.....
10:05:13 SimConnect Message Processing Started
10:05:13 GoFlight Connection Started
10:05:13 SimConnect Connection Started
10:05:13 Aircraft Connection Starting.....
10:05:16 WinSock: Connected To localhost On Port 27015!
10:05:16 LUA Processor: Started!
10:05:20 FSUIPC: Connection Failed: No connection could be made because the target machine actively refused it 127.0.0.1:8385
10:05:20 Aircraft Connection Started
10:05:20 Simconnect Version: 4.5.0.0
10:05:20 Aircraft FullName: Generic
10:05:20 Synchronising Switches & Selectors .....
10:05:20 Synchronising Switches & Selectors: Waiting for SimConnect .....
Then I launch SimStarterNG which loads P3D and other executables including GIT.
GIT is set to be launched only when P3D is fully established in the sim. Here's that log. I should explain that I don't have P3Dv4 installed. A Registry entry is present to fool the installer for the Vertx DA62 which requires v4 to install.
It's interesting there's no entry for the P3Dv5 SDK when launched manually. Sigificant?
10:11:12 GoFlight Connection Starting.....
10:11:12 SimConnect Connection Starting.....
10:11:13 SimConnect Message Processing Started
10:11:13 GoFlight Connection Started
10:11:13 SimConnect Connection Started
10:11:13 Aircraft Connection Starting.....
10:11:13 PMDG SDK option is OK in Prepar3D v4
10:11:13 PMDG SDK option is OK in Prepar3D v5
10:11:13 SimConnect: Event Received: Aircraft Type Changed
10:11:13 SimConnect: Event Received: SIM, 1
10:11:13 SimConnect: Event Received: PAUSE, 0
10:11:13 SimConnect: Event Received: VIEW, 2
10:11:13 SimConnect Message Processing Finished
10:11:13 GoFlight Connection Starting.....
10:11:14 SimConnect Connection Starting.....
10:11:14 Creating Bespoke Vars
10:11:14 Bespoke Vars Created
10:11:14 Importing Bespoke Variables
10:11:14 Bespoke Vars Assigned, Importing Bespoke Events
10:11:14 Bespoke Events Temp Imported
10:11:14 Bespoke Events Imported
10:11:15 GoFlight Connection Started
10:11:15 SimConnect Message Processing Started
10:11:15 SimConnect Connection Started
10:11:15 Aircraft Connection Starting.....
10:11:15 SimConnect: Event Received: Aircraft Loaded/Flight Loaded
10:11:15 SimConnect: Event Received: SIM, 1
10:11:15 SimConnect: Event Received: PAUSE, 0
10:11:15 SimConnect: Event Received: VIEW, 2
10:11:19 WinSock: Connected To localhost On Port 27015!
10:11:19 LUA Processor: Started!
10:11:19 Aircraft Connection Started
10:11:19 Simconnect Version: 4.5.0.0
10:11:19 Aircraft FullName: PMDG 737-800NGXu BW
10:11:19 SimConnect: Exception Received: NAME_UNRECOGNIZED
10:11:19 Synchronising Switches & Selectors .....
Ray (Cheshire, England)
Best wishes
Steve
Can you do a more detailed log showing why the aircraft is not being picked up? What's with the FSUIPC Connection Fail?
Here's a log including a restart of GIT...
15:33:23 GoFlight Connection Starting.....
15:33:23 SimConnect Connection Starting.....
15:33:24 SimConnect Message Processing Started
15:33:24 GoFlight Connection Started
15:33:24 SimConnect Connection Started
15:33:24 Aircraft Connection Starting.....
15:33:27 WinSock: Connected To localhost On Port 27015!
15:33:27 LUA Processor: Started!
15:33:31 FSUIPC: Connection Failed: No connection could be made because the target machine actively refused it 127.0.0.1:8385
15:33:31 Aircraft Connection Started
15:33:31 Simconnect Version: 4.5.0.0
15:33:31 Aircraft FullName: Generic
15:33:31 Synchronising Switches & Selectors .....
15:33:31 Synchronising Switches & Selectors: Waiting for SimConnect .....
15:33:59 SimConnect Message Processing Finished
15:33:59 GoFlight Connection Starting.....
15:34:00 SimConnect Connection Starting.....
15:34:00 GoFlight Connection Started
15:34:01 SimConnect Message Processing Started
15:34:01 SimConnect Connection Started
15:34:01 Aircraft Connection Starting.....
15:34:04 WinSock: Connected To localhost On Port 27015!
15:34:04 LUA Processor: Started!
15:34:09 FSUIPC: Connection Failed: No connection could be made because the target machine actively refused it 127.0.0.1:8385
15:34:09 Aircraft Connection Started
15:34:09 Simconnect Version: 4.5.0.0
15:34:09 Aircraft FullName: Generic
Ray (Cheshire, England)
I've now changed it back to 0 and launched P3D manually, waited until I was in the VC and then launched GIT.
It connected first time and as I changed to two different aircraft it updated GIT.
Looks like SimConnect doesn't agree with using that core 6.
Ray (Cheshire, England)
When I terminated P3D it hung so I had to terminate the process via Task Manager.
Ray (Cheshire, England)
I will check at my end and see if I can replicate the issue.
Best wishes
Steve
I couldn’t get SODE to show a successful test from within P3D add-on menu. Then I discovered it was v1.80 which can cause issues with GSX. So I uninstalled it and reverted to 1.7.1 which is fine.
Simconnect has always been a mystery to me. If ASP3D, ChasePlane both connect successfully it’s baffling why GIT won’t on a consistent level. Fine when launched by SimStarterNG but not when done manually.
Ray (Cheshire, England)
Ray (Cheshire, England)
It’s baffling why it fails to work when launched manually but is fine when launched via SimStarterNG.
Another issue is P3D won’t close cleanly when I exit it on a manual start. No such problems via SimStarterNG. It has to be terminated via Task Manager. The P3D.cfg is identical for both situations.
Ray (Cheshire, England)
I then hit OK and the sim continues loading and eventually is ready with my chosen aircraft on the runway.
During that time the entries in add-ons.xml, exe.xml and dll.xml are loaded. These include ChasePlane but crucially not GIT.
But the relevant GoFlight executable is loaded so my GF166s and MCP becomes alive. Frequencies are shown on both 166 units.
I do nothing for 20-30 seconds to emulate how SimStarterNG behaves. GIT and other executables have not been started.
I then launch GIT in admin mode and the three LEDs all turn to green. But crucially the aircraft name is not displayed so my switches are useless.
It’s like SimConnect isn’t ready but the three LEDs suggest it is. The log says “Waiting for SimConnect…”. Why? It’s loaded according to the LEDs.
There are three SimConnect versions. Which does GIT rely on?
Ray (Cheshire, England)
One thing that baffles me. If the green SimConnect LED is flashing green why does the log say "Waiting for SimConnect"?
I have other programs that require SimConnect. SODE, ASP3D and ChasePlane. All are working correctly but GIT is the only one that isn't.
Could you consider providing a facility to allow the user to manually select their aircraft rather than you detect it? Given all my GIT aircraft files are on the same computer I fail to understand why GIT cannot load the correct one.
Ray (Cheshire, England)
If GIT isn't running at the point, why are these lit up? The GIT module cannot do this that is loaded into P3D, so either GIT is running, or something else is driving them, like GoFlights own drivers maybe?
I will add it to my to do list to fix, but in the meantime, start GIT as above and all should be good.
Also, address the issue I posted above and this may cause issues if two instances of software are trying to update the same hardware.
Best wishes
Steve
GIT interface.dll and GoFlightP3Dv4.exe.
I’m guessing the first is yours to communicate between P3D and GIT and the second is by GoFlight to provide a link for their hardware.
It’s interesting you say to launch GIT before P3D. I will test that tomorrow and report back. Thanks for your ongoing support.
Because I have a mixture of commands via GIT and others that use standard GoFlight commands I presumably need both GIT and GoFlight drivers running.
Ray (Cheshire, England)
Here's the results of this morning's tests.
1) I started GIT first.
2) Then started P3D.
GIT went through various LED stages but when I selected the Learjet in the Scenario window GIT loaded the aircraft profile.
When P3D was fully running the engines were running and my switch settings weren't read. I checked SODE and no connection to SimConnect could be established. ChasePlane couldn't load my camera settings and ASP3D could not connect to P3D.
So that sequence was not successful. When I exited P3D it didn't close fully and had to be "end tasked" in Task Manager.
Next I started P3D and at the Scenario screen I started GIT. When I selected the Lear GIT immediately loaded the profile. When P3D was fully loaded SODE was okay and so was ChasePlane. ASP3D made the connection as well. When I exited P3D it closed correctly.
So the sequence seems to be to delay loading GIT until the scenario screen is present. Hopefully you can resolve the bug so GIT can be loaded at any time. As things stand I can't load it via SimStarterNG and will have to load it manually at the correct time.
Ray (Cheshire, England)
Ray (Cheshire, England)
Best wishes
Steve
I'll bide my time.
Ray (Cheshire, England)
Ray (Cheshire, England)
Best wishes
Steve
Ray (Cheshire, England)
Ray (Cheshire, England)
Ray (Cheshire, England)