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.

Prepar3d V3.2

terrydewterrydew
in GoFlight Interface Tool - Technical Support
Has anyone with GFIT updated to V3.2 yet. Any issues with GFIT. Terry

Comments

  • robainsrobains
    No issues with GIT AND V3.2.  

    See my other thread on MESM issue with GF 2.26.1 and Steve's latest GIT.

    Unrelated to GIT and P3D, but also found resolution to older GF modules under Win10 (like 166A units working but no display) ... this process solved it:




    Cheers, Rob.


    Cheers, Rob.
  • terrydewterrydew
    Thanks Rob I am still on win7 where you can turn off the power mgt in properties. Did they change win 10 where the only way to turn them off is by registery change? Bummer. Terry
  • robainsrobains
    Win10 is still "Beta" as far as I'm concerned, I've endured a lot of Win10 issues over these past few months ... don't know why I thought it would be any different at Redmond.

    Here's the deal with disabling Power Management, after you go thru Device Manager and do a properties on ALL your "Input Devices" and HUBs and select the Power Management tab and uncheck "allow this device to be turned off to save power". 

    You then also have to bring up the Registry (RegEdit - make sure you "run as admin") and locate the devices per MS KB 2900614.  Once you have the correct registry path for the device you need to set TWO entries to 0 (zero):

    "EnhancedPowerManagementEnabled"
    "DeviceSelectiveSuspended"

    Once that is done, older GF modules (like my older RP-48s, 166s, T8s) will light up  (LEDs and displays work) as "normal".

    I have "legacy" support selected in my BIOS, but that didn't do anything to help.  ONLY these registry adjustments got my older GF modules working correctly.  This probably should be addressed by GF (they could handle via GF software install, add the registry changes since they'll know the device IDs), but I've not heard back from GF on my inquiries ... I still get occasional power cycles on a couple of my modules and wish GF would tell me why as I've exhausted all my diagnostics.

    Cheers, Rob.

  • terrydewterrydew
    I had extreme issues with getting all my goflight modules to consistently come on. I bought all kinds of hubs cables trying to solve. Then one day (knock on wood) the problem went away and they have been stable since? That is why I haven't tried the disconnect MESM solution to the 2.26 issue plus the fact that I have zero problems with the 2.52 set. If you see any pluses to the 2.26 set, please post and I will try. You mentioned MacPro. The only thing I use my Windows machines for is flight simulation. For everything else I am Apple based. It is a totally different and better IMHO world. Terry
  • admin_ppsadmin_pps

    I'm pretty sure running GFWindows8Fixer.cmd as administrator does the registry fixes mentioned.

    Best wishes

    Steve

  • robainsrobains
    Hi Steve, 

    I did notice GFWindows8Fixer, but was hesitant to run that on Windows 10 ... probably should be part of the GF 2.26.x installer.

    Cheers, Rob.


  • robainsrobains
    Just a quick update, it does look like GFWindows8Fixer was executed as part of the GF 2.26.1 install ... I found a GFWindows8Fixer.log file with entries and since I had not run GFWindows8Fixer, I can only assume it was part of the GF install ... unless the log file with entries was accidentally added to the installer package?

    Anyway, as a test I reverted one of my 166A entries back to default 1 values and re-ran GFWindows8Fixer (as admin) and re-checked, it didn't actually change the registry entries for my 166A (stayed at 1, should have been changed to 0). So it doesn't appear GFWindows8Fixer is working for Windows 10 unless there is something I'm missing?

    Unfortunately my devices are back to power cycling randomly, the odd thing is they don't power cycle when in P3D or XP nor when GFConfig is "active" ... they only power cycle when I'm working on other non-FS stuff on my main FS PC.

    Cheers, Rob.
  • admin_ppsadmin_pps
    edited March 2016

    Looks like GoFlight drivers need some Win10 tweaks. I'll let John know if you don't.

    Thx

    Steve

  • robainsrobains
    edited March 2016
    Hey Steve,

    I was able to reach John via phone today ... we discussed a few things on the Power Cycle issue, I'll try some hub re-arrangements my side and see what happens ... John believes it's a HUB power issue ... I've tried just about every HUB made (D-Link, Belkin, Rosewell, Sabrent, etc. etc.) so I'm not sure, just experiment some more and see.

    There is a BIOS setting that might help but I'm not using motherboard USB ports (so BIOS setting should make no difference), I use a separate PCIe USB 2.0 card (with dedicated power connection) ... I'll keep messing with it and see if I can't resolve the power cycle.  My HUBS are rated upto 2500ma which as I understand it is well above USB spec. 

    I did inform John about Win10 and GFWindow8Fixer.

    Cheers, Rob.
  • terrydewterrydew
    Hello Rob After I posted how stable my go-flights have been, a couple dropped out today. It took two or three unplug plug reboot cycles to get them back. I am with you, it is not the hubs it is in the units themselves. I am also using a pice card and have tried many different hubs. Terry
Sign In or Register to comment.

© Vanilla Keystone Theme 2025