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.
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.

GIT 64-bit blanks GF166 displays on startup

RayProudfootRayProudfoot
in GoFlight Interface Tool - Technical Support
Hi Steve,

I had a big Windows 10 update a few days ago. Ever since then when I launch P3Dv4.5 and the 64-bit GIT program launches the two GF166 displays are blanked. I can press a button on each and the display then shows again. But it never did this before the windows update. I tried reinstalling GIT 64-bit but it made no difference. I've also run GFWindows8 Fixer, again no resolution.

Looking at the log I wonder if that NAME_UNRECOGNIZED entry near the end could be the problem. Any ideas what it might be referring to? There's been no change in hardware.

10:54:04 GoFlight Connection Starting.....
10:54:04 SimConnect Connection Starting.....
10:54:04 SimConnect Message Processing Started
10:54:05 GoFlight Connection Started
10:54:05 SimConnect Connection Started
10:54:05 Aircraft Connection Starting.....
10:54:05 PMDG SDK option is OK in Prepar3D v4
10:54:05 SimConnect: Event Received: Aircraft Type Changed
10:54:05 SimConnect: Event Received: SIM, 0
10:54:05 SimConnect: Event Received: PAUSE, 1
10:54:05 SimConnect Message Processing Finished
10:54:05 GoFlight Connection Starting.....
10:54:06 SimConnect Connection Starting.....
10:54:06 Creating Bespoke Vars
10:54:06 Bespoke Vars Created
10:54:06 Importing Bespoke Variables
10:54:06 Bespoke Vars Assigned, Importing Bespoke Events
10:54:06 Bespoke Events Temp Imported
10:54:06 Bespoke Events Imported
10:54:08 SimConnect Message Processing Started
10:54:08 GoFlight Connection Started
10:54:08 SimConnect Connection Started
10:54:08 Aircraft Connection Starting.....
10:54:08 SimConnect: Event Received: Aircraft Loaded/Flight Loaded
10:54:08 SimConnect: Event Received: SIM, 1
10:54:08 SimConnect: Event Received: PAUSE, 0
10:54:11 WinSock: Connected To localhost On Port 27015!
10:54:12 LUA Processor: Started!
10:54:12 Aircraft Connection Started
10:54:12 Simconnect Version: 4.3.0.0
10:54:12 Aircraft FullName: PMDG 737-800NGX WL
10:54:12 Synchronising Switches & Selectors .....
10:54:12 SimConnect: Exception Received: NAME_UNRECOGNIZED
10:54:27 Global LUA Event Running
10:54:27 Global Aircraft LUA Event Running
10:54:27 Synchronising Switches & Selectors Complete
Cheers,
Ray (Cheshire, England)

Comments

  • admin_ppsadmin_pps
    Have you checked that Windows has not put power management back on your hubs and devices?

    Best wishes
    Steve
  • RayProudfootRayProudfoot
    admin_pps said:

    Have you checked that Windows has not put power management back on your hubs and devices?

    Best wishes
    Steve

    Yep. First thing I check. The GF166s work fine after I press a button to bring back the display. And they are illuminated when P3D starts. It's just when GIT64 starts they both go blank. What's that NANE UNRECOGNIZED entry referring to?
    Cheers,
    Ray (Cheshire, England)
  • admin_ppsadmin_pps
    Very odd. Can you try starting GIT before P3D.

    Best wishes
    Steve
  • RayProudfootRayProudfoot
    Hi Steve,

    If I start GIT before P3D when the Scenario Menu appears GIT has three greens which suggests all is well. I then select a saved Scenario to load and as soon as I do that the LEDs on the 166 go off. They previously showed 100.00 on both sides for the two 166s.

    After selecting a scenario to load it places me back at the Scenario screen so times / dates can be changed if required. The SimConnect LED in GIT is now showing yellow. The other two are green.

    As soon as I press OK to load that scenario the 166s return to life showing frequencies and the SimConnect LED in GIT is green as are the other two.

    I still have that NAME:UNRECOGNIZED entry in the log. Maybe it's a timing issue. I normally load GIT via SimStarterNG in the Run section. Temporarily disabled and I'll try to remember to run it first although the advantages aren't huge. It just means when it runs automatically I have to press the centre button on each module to brng it back to life.
    Cheers,
    Ray (Cheshire, England)
  • RayProudfootRayProudfoot
    edited June 2020
    Hi Steve,

    I thought sight of my simconnect.xml may help. Everything that needs it connects fine. What appears to have caused this little issue is a windows update which resulted in the IP address changing on my main FS PC.

    <?xml version="1.0" encoding="Windows-1252"?>


    SimConnect
    SimConnect.xml
    False


    False
    Auto
    local
    64

    4096
    False



    False
    IPv4
    global
    192.168.1.115
    64
    500
    4096
    False


    Cheers,
    Ray (Cheshire, England)
  • RayProudfootRayProudfoot
    Hi Steve,

    Bit more info which may help. I loaded the Carenado PC12 for which I have several custom commands assigned to the T8 switches. That is fine and the 166s stay illuminated. So it points to something with the PMDG737 configuration. The log is clean too. No NAME:UNRECOGNIZED entry in the log.
    Cheers,
    Ray (Cheshire, England)
  • admin_ppsadmin_pps
    That's even odder because its the same code for PMDG and generic aircraft that drives the GF166 - just gets the data from different places. So, it's suggesting that data is not initially coming down from the PMDG SDK, but why a Windows update would cause this?!

    It would be worth double checking you don't have have any config loaded in GFConfig.

    Perhaps try renaming PMDG.XML in Documents\GoFlight Interface Tool to something else so GIT starts clean. Then start GIT, re-enable the GF166 and click the COM button. Quit GIT, and reload GIT and see if the behaviour is the same.

    Best wishes
    Steve
  • RayProudfootRayProudfoot
    Steve,

    Attached is a zip with two configurations. PMDG.xml is the one giving me trouble. Temp_PMDG.xml was generated by GIT as PMDG.xml after renaming my original PMDG.xml to another name temporarily.

    When starting with my original PMDG.xml the two 166s blank when GIT starts.

    When starting with TEMP_PMDG.xml (named as PMDG.xml for the test) the two 166s stay illuminated. I thought you might be able to spot any issues quicker than me.

    Just to confirm I have no custom commands assigned to either 166. Just the standard GoFlight Nav and Com commands.
    Cheers,
    Ray (Cheshire, England)
  • RayProudfootRayProudfoot
    UPDATE: FIXED!!

    I compared the two xml files for the one that didn't blank the 166s against the one that did. The DEVICE_STATE in the one that worked was DISABLED but in the one giving me the trouble it was set to ENABLED.

    I replaced ENABLED with DISABLED and it's sorted the problem. The 166s now stay alive when GIT starts.

    Bloody computers eh? :D
    Cheers,
    Ray (Cheshire, England)
  • admin_ppsadmin_pps
    I know what has happened. Windows has changed the device ID's of the gf166 hardware so the GoFlight SDK has swapped the devices around.

    Best wishes
    Steve
  • RayProudfootRayProudfoot
    Thanks Steve. At least we have a reason why it happened. Something to be aware of for future Windows updates.
    Cheers,
    Ray (Cheshire, England)
Sign In or Register to comment.

© Vanilla Keystone Theme 2025