FLT Additional Information

On this page you can find additional information related to how certain FLT parameters work, as well as some tables containing values that are required by some FLT parameters.

Universal Screen Co-ordinates#

Universal screen coordinates is a system designed to make screen positions independent of screen resolution. The universal coordinates extend from (0, 0) in the top left hand corner to (8192, 6144) in the bottom right hand corner. So, for example: If the universal coordinates of a rectangle are (500, 400) and it has a width of 7192px and a height of 650px and the screen resolution is 1024x768px, then the actual screen coordinates and size of the rectangle would be calculated as follows:

• X = 500 * (1024/8192) = 62.5
• Y = 400 * (768/6144) = 50
• W = 7192 * (1024/8192) = 899
• H = 650 * (768/6144) = 81.25

So the pixel position of the top left hand corner of the rectangle is at position (62, 50) and will have with a width of 899px and a height of 81px.

Mission Order#

When creating missions, you can use the Difficulty parameter to set the order in which the missions are shown within the UI. The way this works is as follows:

• Missions that have the Difficulty parameter are going to be shown first in the UI list:

  • These missions will be sorted from the lowest difficulty to the highest, ie: A mission of difficulty 1 will be before a mission of difficulty 2, etc…

  • If two missions have the same difficulty then they will be sorted alphabetically using the translated name of the mission

Missions with no difficulty parameter will be at the end of the list and are going to be sorted alphabetically using the translated name of the mission

ATC Agent Signatures#

Air traffic control agents have signatures made up of four entries, for example:

AgentTracking=2,4,20287488,GREENLAKE

These four entries are made up of the following:

• The first number is always 2
• The second is the agent type (see the table below)
• The third number is a coding of the frequency
• The fourth entry is the call-sign.

In the example given above, the frequency coding is 20287477. To get this value we have taken the COM frequency of 135.9, multiplied it by 1000 to get 1359000. This value is considered as a hexadecimal and converted to decimal, which gives us 20287477.

The table below shows the values for agent type and what they correspond to:

Waypoint Format#

Failure Code Table#

The following table contains the various failure codes that can be used with the [SystemFailureN.i] option.

ATC Message ID#

The following is a list of all the possible ATC message IDs that can be used (and returned) by various parameters in the FLT file: