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.
FSLabs A320 Radios
Hi,
I have quite a bit of experience with GIT for XPlane and can find my way out of most technical challenges with configuring GF hardware for that sim. On the other hand, I have almost no experience with GIT for P3D and recently sat down to try to configure my GF166 to emulate the behaviour of the FSLabs A320 COM1.
This turned out to be more difficult than I thought. For example, I was able to find the correct event and lvar to change the COM1 standby frequency and testing that Bespoke event changed the value of the standby frequency on the GF166 display, but no corresponding changes were observed on the VC.
It seems that interacting with the VC with the mouse executes additional code to change the VC standby frequency which cannot be replicated by listening with GIT Detective alone. Detective did not detect any "Mse Clks" during this process.
I have read somewhere that devs may choose to implement certain features outside the P3D SDK in which case a separate SDK would need to be provided by FSLabs and GIT would then have to be built with new support for that custom SDK. As far as I know there is no SDK currently available for FSLabs A320 (in contrast to PMDG) and as a consequence trying to configure GF hardware for the A320 with the current version of GIT for P3D may be very limited and frustrating. Is that a correct assumption?
regards,
Martin
I have quite a bit of experience with GIT for XPlane and can find my way out of most technical challenges with configuring GF hardware for that sim. On the other hand, I have almost no experience with GIT for P3D and recently sat down to try to configure my GF166 to emulate the behaviour of the FSLabs A320 COM1.
This turned out to be more difficult than I thought. For example, I was able to find the correct event and lvar to change the COM1 standby frequency and testing that Bespoke event changed the value of the standby frequency on the GF166 display, but no corresponding changes were observed on the VC.
It seems that interacting with the VC with the mouse executes additional code to change the VC standby frequency which cannot be replicated by listening with GIT Detective alone. Detective did not detect any "Mse Clks" during this process.
I have read somewhere that devs may choose to implement certain features outside the P3D SDK in which case a separate SDK would need to be provided by FSLabs and GIT would then have to be built with new support for that custom SDK. As far as I know there is no SDK currently available for FSLabs A320 (in contrast to PMDG) and as a consequence trying to configure GF hardware for the A320 with the current version of GIT for P3D may be very limited and frustrating. Is that a correct assumption?
regards,
Martin
Comments
I don't have the plane so cannot offer assistance. I assume you tried the default COM button on the GF166 tab which will configure the GF166 for radios for aircraft that comply with Simconnect standards?
Best wishes
Steve