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.
Changing Device assignments (Device 0, Device 1, etc.)
Hi Steve (and others in this Forum),
I have been enjoying a stable 13-device setup for many months, with the one well-known issue that my 166 GF radio units were not working. I decided to try the fixes suggested in other threads - specifically I installed a USB 2.0 internal card, unchecked the power management checkboxes in Windows, and ran the Windows8 fixer exe thingy.
The good news - it worked. My 166s have come back to life and I reinstalled one I had detached from the setup.
The bad news is that my device assignments (Device 0, Device 1, Device 2) for toggle switches, buttons, and rotating devices have changed. And they appear to change each flight although I have a small sample size of just 2 flights. So obviously I caused the issue to occur with something I did.
My questions:
1) Will the assignments (which hardware is assigned to which Device #) be stable as long as I don't make more changes? If so I will just spend a bit of time to reprogram them to match my labels.
2) Or is there something about the 166s or other GF devices (I have just about all of them), or a mixed USB 3.0 and 2.0 environment that will continue to cause devices to be reassigned in GIT? If so I can yank the 166s or make whatever adjustments necessary to get back to a stable setup.
Thanks guys!
Mike
I have been enjoying a stable 13-device setup for many months, with the one well-known issue that my 166 GF radio units were not working. I decided to try the fixes suggested in other threads - specifically I installed a USB 2.0 internal card, unchecked the power management checkboxes in Windows, and ran the Windows8 fixer exe thingy.
The good news - it worked. My 166s have come back to life and I reinstalled one I had detached from the setup.
The bad news is that my device assignments (Device 0, Device 1, Device 2) for toggle switches, buttons, and rotating devices have changed. And they appear to change each flight although I have a small sample size of just 2 flights. So obviously I caused the issue to occur with something I did.
My questions:
1) Will the assignments (which hardware is assigned to which Device #) be stable as long as I don't make more changes? If so I will just spend a bit of time to reprogram them to match my labels.
2) Or is there something about the 166s or other GF devices (I have just about all of them), or a mixed USB 3.0 and 2.0 environment that will continue to cause devices to be reassigned in GIT? If so I can yank the 166s or make whatever adjustments necessary to get back to a stable setup.
Thanks guys!
Mike
Comments
Best wishes
Steve