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.
AUTOPILOT_MACH_HOLD_VAR issue
Hello!
I tryed to make 'C/O' button on GF MCPpro work with default FSX Autopilot as expected.
bespoke event for it:
<Task ID="2" Type="SetInc" Var="Bespoke Var 0" Data="1" />
<Task ID="3" Type="If" Var="Bespoke Var 0" Operator="GREATER_THAN" Value="1" />
<Task ID="4" Type="Set" Var="Bespoke Var 0" Data="0" />
<Task ID="6" Type="If" Var="Bespoke Var 10" Operator="EQUALS" Value="1" />
<Task ID="10" Type="Goto" LabelID="7" />
<Task ID="12" Type="SetEquiv" Var="Bespoke Var 10" Data="AUTOPILOT_AIRSPEED_HOLD_VAR" />
<Task ID="14" Type="Goto" LabelID="8" />
<Task ID="7" Type="Label" Name="a" />
<Task ID="16" Type="SetEquiv" Var="Bespoke Var 10" Data="AUTOPILOT_MACH_HOLD_VAR" />
<Task ID="8" Type="Label" Name="b" />
Display source for IAS/MACH display setted to "Bespoke Var 10"
There are two issues found:
1) AUTOPILOT_MACH_HOLD_VAR is always truncated, I tryed use it as source for display also, display shows 0.00 while mach number less than '1' and 1.00 when greater
2) I hadn't find a way to set display format from bespoke event, so it seems impossible to have for example '266' for IAS and '0.55' for mach without every time correcting field format settings by hand. And absolutely impossible to have '0.551' for mach.
Answers
Is any solution of second issue possible?
It will happen automatically when I fix the data type bug.
Best wishes
Steve