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.
GF166 - Comm frequency dec digi7 to 8
Another little quirk I have noticed is that when trying to tune any decimal frequency on any GF166, anytime you get to .7 or .17 or .27 etc etc, the GF166 will show a 8 whereas in the cockpit, your aircraft com panel will show an 7..
So tuning to 110.27 will require you to tune to 110.28 on the GF166, so that when you look in the VC, you will see its on .27.
It seems borderline impossible to get the GF166 to hit a .7 of anything in the decimal tunings...
Whole number tuning is fine, no problems there, but decimal tuning seems far to sensitive, with numbers being hit between dial increments, meaning as soon as you let go of the knob, it settles back a touch or forward, and the value changes.
Is there anything I can change to adjust the sensitivity of the decimal tuning values so that 1 click on the knock = 1 step on the decimal frequency?
So tuning to 110.27 will require you to tune to 110.28 on the GF166, so that when you look in the VC, you will see its on .27.
It seems borderline impossible to get the GF166 to hit a .7 of anything in the decimal tunings...
Whole number tuning is fine, no problems there, but decimal tuning seems far to sensitive, with numbers being hit between dial increments, meaning as soon as you let go of the knob, it settles back a touch or forward, and the value changes.
Is there anything I can change to adjust the sensitivity of the decimal tuning values so that 1 click on the knock = 1 step on the decimal frequency?
Answers
The latest version fixes that bug.
Best wishes
Steve