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.

Clean Win10 install still no go for GIT 2.1.18.2 and GF 2.26.1

robainsrobains
in GoFlight Interface Tool - Technical Support
Hi Steve,

Just wanted to update so thought would be good to start a new thread.  Since you are running Win10 and GIT 2.1.18.2 and GF 2.26.1 without issues I was hoping a new fresh install of Win10, GF, and GIT would solve the lockup problem.  Unfortunately the issue remains.  Tested with all those Beta variants and still no go, the only working combination is GF 2.25.2 and GIT 2.1.18.2 (under Win7 or Win10).

I've reverted back to GF 2.25.2 and GIT 2.1.18.2.

Hope you're having a good holiday season.

Cheers, Rob.

Comments

  • robainsrobains
    FYI:

    Forgot to mention that GF 2.26.1 drivers would NOT illuminate each device when selected via GFConfig ... so with multiple devices of the same type it was impossible for me to determine which one I was actually setting until I was in P3D testing them.

    With GF 2.25.2 drivers I do not have this problem, all devices identify (with LED illumination) when selected.

    Hopefully the GF developer can get Win10 sorted out ... I would leave a message on their forums but they don't appear to respond to any questions/issues there.

    Cheers, Rob.


  • robainsrobains
    The issue with 2.25.2 seems to be any key sequences sent (i.e. S to cycle views) will repeat ... i.e. hit the an P8 button once and it will generate 4 or 5  "S" key sequences in P3D and hence I'll cycle 5 views rather than just one.

    Another issue is 2.25.2 must be loaded manually first prior to running P3D ... it seems the EXE.XML entry for GFDevP3D.exe is not being loaded when P3D starts.  I have everything set to "Run As Administrator" so not sure why ... any hints, did you run into this issue with Win10?

    Cheers, Rob.
  • robainsrobains
    UPDATE:

    Resolved GFDevP3D not loading ... the magical reboot or moving entries to the ProgramData versions of DLL.XML and EXE.XML ... and now it's working (not sure which solved it).  So GF 2.25.2 and GIT 2.1.18.2 are good to go in Win10 E.

    Also to note in P3D V3.x, I'd recommend you do NOT use the DLL.XML and EXE.XML located in the Roaming path, use the DLL.XML and EXE.XML located in the ProgramData path.  If any older products add entries in the Roaming version simply cut/paste the into the appropriate ProgramData pathing DLL.XML and EXE.XML.  This will also likely solve any permission issues.

    Cheers, Rob.
  • admin_ppsadmin_pps

    Hi Rob,

    The drivers need the PC to be rebooted as it sets admin rights in the registry for the data bridges that don't kick in until a reboot. This will stop GFDevP3D from loading.

    I've never had to mess with ProgramData xml files.

    I'll feedback to GoFlight regards the drivers.

    Best wishes

    Steve

  • robainsrobains
    edited December 2015
    Thanks Steve, I probably just got distracted when testing all the versions to see what works and doesn't and forgot my next step on return.

    It would be nice if GF could provide some drivers that work with GIT and/or visa versa.  But just curious what GF change for the 2.26.1 drivers that makes them P3D V3 compatible?  Anything "fixed" in 2.26.1 vs. 2.25.2?  The 2.26.1 still appears to use the EXE.XML from the "Roaming" path and not the new recommended "ProgramData" path.

    Cheers, Rob.


  • robainsrobains
    edited December 2015
    UPDATE:

    The problem returned again GFDevP3D will not load when P3D starts, permissions are set ... this one has me baffled and why is it not consistent?

    And now I'm running into issues with my Saitek throttle quadrants, my two USB Throttle Quadrants keep showing up with different names each time I reboot Win10 ... causing P3D to get confused about what axis to assign.  It's almost as if the device is being given a different GUID each time I reboot Win10.

    I'll keep banging on this a little more and see where I can get with Win10 ... but this issue is a show stopper for Win10, may have to revert back to Win7 sadly.

    Cheers, Rob.
  • robainsrobains
    edited December 2015
    SOLVED:

    Probably should stop posting updates ... but in case anyone reads this and makes the same Win10 mistake I did ...

    Source of the problem was checking "Run as administrator" in the "All users settings".

    image

    This is fine, however when I click on the "Change settings for all users"

    image

    I had also checked "Run this program as administrator" (for all users context) ... P3D V3.x did NOT like this and would trigger an error in the ContentError.log with Failed to load ... DLL and would NOT load anything from the EXE.XML.

    My Win10 lesson learned.

    Cheers, Rob.

  • terrydewterrydew
    Hi Rob Thanks for info on Win 10. I am still holding off. Do you see any net benefit from moving to 10? Thanks Terry
  • robainsrobains
    Hmmm ... that's a loaded question.

    Benefits:
    1.  LM are developing on Win10 boxes
    2.  Microsoft care more about Win10 than Win7 (think Windows updates)
    3.  DX12 (not much using that API yet, a few early access) will be big benefit for future graphics based apps
    4.  The User Interface is really very much like Win7 now with a few improvements, I like the spacing between X (close) minimize and maximize (less accuracy issues)
    5.  I/O performance seems better but no major FPS improvements (maybe 1-2 fps)
    6.  When copying files that take time, expand the detail button, get a new cool speed history graph (I like stuff like that)

    Headaches:
    1.  Security and user accounts issues
    2.  Explorer shows external USB drives twice (registry hack but it will get reset on every Win update)
    3.  USB issues ... multiple Saitek throttles for example, Win10 switches them around on every reboot which confuses P3D
    4.  Strange mouse delay (like taking time to register mouse over window has the focus) when trying to drag/move Explorer windows around quickly ... have pause while click hold ... then finally drag
    5.  Microsoft IS moving to a subscription based OS, Win10 is the bait ... I don't have an issue with that myself, but I know many do so listed under headaches.

    Most of the other features I don't use ... Cortina, One Drive, Virtual desktops ... so if those are important to you then add them to the benefits side.

    1151 build is certainly better than some of the earlier builds I worked with (for my real world work), but still has a list of issues that need fixing.  Win10 market share is currently around 10% but is showing steady growth even if slow growth.  A little disappointing considering it was Free for most, but unlike Win8.x I do think Win10 will eventually take the market share lead.

    Cheers, Rob.
  • terrydewterrydew
    Hi Rob Thank you for a very clear response! LM developing on 10 is a real plus as I only use my computer for P3D. The USB issues concern me as I had a miserable time getting all my goflight units to consistently stay online. Is the moving around problem just with Saitek or also with goflight? I am sure you already know about it but Spad.Next for Saitek gear development is coming along very well. If you haven't, check it out at http://www.fsgs.com/ Thanks Terry
  • robainsrobains
    So far the issue is specific to Saitek Throttle Quadrants ONLY (my other Saitek Yoke and Rudder Pedals work fine) - I suspect because I have two of them and Win10 gets confused so just picks the first it polls as #1 and the other as #2.

    I've heard of SPAD, will take a look.

    Cheers, Rob.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025