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.

Upgrading from GoFlight Drivers v2.26.4

Hi Steve,

I am currently running P3D v3.4 with GIT 2.6.0.0 and the above GF drivers.

I would like to upgrade to GIT 3.0.0.0, but still continue to use P3D v3.4 for now.

What is the recommended version of GoFlight Drivers to use as of today? GF has released v2.28, but do you recommend upgrading to that version, or staying with an earlier version?

If you recommend upgrading from v2.26.4, should I first uninstall that version via Win 10 control panel, before installing a newer version of the GoFlight drivers?

Thank you.

regards
Martin

Comments

  • Hi Martin,

    The later version of the GoFlight drivers will make no difference to GIT. If I recall the later drivers only add support for P3Dv4 so they are of no real value to you.

    Best wishes
    Steve
  • Unfortunately installing GIT 3.0.0.0 seems to have broken something as P3D now starts but is unresponsive after loading the Majestic Q400 Pro which I did have a working config for in GIT 2.6.0.0.

    I notice that in app data I have:
    DLL.XML

    GoFlight Module Interface
    False
    F:\GoFlight Interface Tool\GoFlight Interface Module.dll


    EXE.XML

    False
    False
    GoFlight Hardware Interface
    F:\GoFlight\GFDevP3D.exe




    Should I have the entry for GFDevP3D.exe in EXE.XML?
    EXE.XML timestamp was touched as part of GIT 3.0.0.0 install.
  • Going back to GIT 2.6.0.0 has not helped resolve the issue.
  • Is the problem only with the Q400. What about other aircraft?
  • edited July 2017
    I tested the default Raptor and the FSLabs A320. No problems. Looks like the Q400 at this stage. I tried unzipping a full GIT backup from yesterday and this did not help. Basically the issue is, the Q400 loads and sits on the runway but does not revert to cold and dark state (but is configured to start cold and dark). Then P3D hangs on shutdown and the process needs to be killed in task manager. Once killed the gear lights on the LGTII stay on (which is also unusual).

    I have a feeling there might be something in my 2.6.0.0 GIT Q400 config which when loaded with the new GIT 3.0.0.0 causes some issue.
  • When did you last try GIT with the Q400?
  • 2 days ago. What is the best way to "temporarily" stop P3D from autoloading GIT? Win10 did some large developers update in the last 2 days. Perhaps that broke the Q400. I just want to start the Q400 without P3D loading GIT to help isolate the problem.
  • GIT is never installed to autoload. GFDevp3D.exe is GoFlight's software.
  • I just temporarily removed GFDevp3D.exe and GoFlight Interface Module.dll from DLL.XML and EXE.XML and the issue with the Q400 persists. So this has nothing to do with GIT at all. Its probably the large developers update that Win 10 did over the weekend that affected the Q400. It was just a unlucky coincidence that I noticed all this after upgrading GIT. Thank you for all your help.
  • A full reinstall as recommended by the above link fixed my Q400 problem. Apologies for jumping to the wrong conclusion. I'm still relatively new to P3D. Thanks again for the support Steve.
Sign In or Register to comment.