CustomDraw Map Guidebook v1.0

8/9/2019 CustomDraw Map Guidebook v1.0

http://slidepdf.com/reader/full/customdraw-map-guidebook-v10 1/175



i

Table of Contents

FS9 FSX

Introduction 1

Map Projections 2

Flight Planner and World Maps 2CustomDraw fs9gps:Map 4

CustomDraw Map variables

Name, X, Y, and Bright 6

Zoom 6

Latitude and Longitude 8

Heading 8

TrackUp 10

CenterX and CenterY 10

SelectedVehicle 10

TagPosition 11 BackgroundColor 12

IceColor 12

WaterColor 12

ElevationXXColor 13

TerrainShadow 14

PanVertical and Horizontal 15

PanReset 18

Priority 18

MapLoading 18

UpdateAlways 18

LayerTerrain

LayerTerrain 19

DetailLayerTerrain 19

Example Elevation Colors 19

TextDetailLayerTerrain 23

ObjectDetailLayerTerrain 23

ColorLayerTerrain 24

TextColorLayerTerrain 24

Elevation Color Palettes 24

Color Feathering 25

Redundant

Non-Functional

Redundant

Non-Functional



ii

FS9 FSX LayerBorders

LayerBorders 26

DetailLayerBorders 26

TextDetailLayerBorders 26

ObjectDetailLayerBorders 26

ColorLayerBorders 29 TextColorLayerBorders 29

Borders Example - FSX 29

Borders Example – FS9 30

LayerGridLines 31

LayerRangeRings

LayerRangeRings 32

DetailLayerRangeRings 32

TextDetailLayerRangeRings 32

ObjectDetailLayerRangeRings 32

Range Ring Center 33

Projection Change at 500,000 Meter Range 33

TrackUp=0 only 34

ColorLayerRangeRings 34

LayerAirports

LayerAirports 35

DetailLayerAirports 35

Airport Symbol Orientation 36

TextDetailLayerAirports 37

TextDetailLayerAirports Example 38 ObjectDetailLayerAirports 38

ObjectDetailLayerAirports Rules 39

TextColorLayerAirports 40

ColorLayerAirports 41

ColorLayerAirportsTowered 41

ColorLayerAirportsUntowered 42

LayerVORs

LayerVORs 43

DetailLayerVORs 43

TextDetailLayerVORs 44 ObjectDetailLayerVORs 45

ColorLayerVORs 46

TextColorLayerVORs 46



iii

FS9 FSX LayerNDBs

LayerNDBs 47

DetailLayerNDBs 47

TextDetailLayerNDBs 48

ObjectDetailLayerNDBs 48

ColorLayerNDBs 49 TextColorLayerNDBs 49

NDB Color Example 49

LayerILSs

LayerILSs 50

DetailLayerILSs 50

TextDetailLayerILSs 50

ObjectDetailLayerILSs 50

Localizer Cone Symbol Dimensions 51

Localizer Course Line Symbol Dimensions 52

Localizer Orientation 52 ColorLayerILSs 53

TextColorLayerILSs 53

LayerIntersections

LayerIntersections 54

DetailLayerIntersections 54

TextDetailLayerIntersections 54

ObjectDetailLayerIntersections 55

ColorLayerIntersections 55

ColorLayerIntersectionsEnroute 55

ColorLayerIntersectionsTerminal 55 TextColorLayerIntersections 55

Additional points 57

LayerAirspaces

LayerAirspaces 58

DetailLayerAirspaces 58

TextDetailLayerAirspaces 58

ObjectDetailLayerAirspaces 58

Airspace Definitions 59

Center Airspace 59

Air Traffic Control-Based Airspace Classes 60Special Use Airspaces 60

LayerAirspaces Line Format 61

Examples of LayerAirspaces in FSX 62

ColorLayerAirspaces 64

TextColorLayerAirspaces 64



iv

FS9 FSX LayerFlightPlan

LayerFlightPlan 65

DetailLayerFlightPlan 65

TextDetailLayerFlightPlan 66

ObjectDetailLayerFlightPlan 66

ColorLayerFlightPlan 67 TextColorLayerFlightPlan 68

FlightPlanLineWidth 68

ActiveColorLayerFlightPlan 69

PastColorLayerFlightPlan 69

LayerApproach

LayerApproach 70

DetailLayerApproach 70

TextDetailLayerApproach 72

ObjectDetailLayerApproach 72

ColorLayerApproach Crashes the Sim 72 TextColorLayerApproach 72

LayerApproachAirport 72

LayerApproachApproach 72

LayerApproachTransition 72

LayerApproachLeg 73

LayerApproachAircraftSpeed 73

LayerApproachLineActiveColor 74

LayerApproachLineColor Crashes the Sim 75

LayerApproachLineWidth 75

Other LayerApproach Observations 75

LayerVehicles

LayerVehicles 76

DetailLayerVehicles 76

TextDetailLayerVehicles 78

ObjectDetailLayerVehicles 78

ColorLayerVehicles 80

ColorLayerVehiclesSelected 80

TextColorLayerVehicles 80

LayerAirways

LayerAirways 81 DetailLayerAirways 81

TextDetailLayerAirways 81

ObjectDetailLayerAirways 82

ColorLayerAirwaysVictor 82

ColorLayerAirwaysJet 82

TextColorLayerAirways 82



v

FS9 FSX LayerRacePoints 84

LayerRacePoints

DetailLayerRacePoints

TextDetailLayerRacePoints

ObjectDetailLayerRacePoints

ColorLayerRacePointsGate ColorLayerRacePointsPylon

ColorLayerRacePointsVolume

TextColorLayerRacePoints

CustomDraw: Rose

Heading 85

CenterX and CenterY 85

Radius 85

Color 85

BackgroundColor 85

LineWidth 86 Font 86

FontSize 86

BigFontSize 86

FullCircle 86

LabelAllTicks 86

Force3Digits 86

ITrafficInfo: Nearest Traffic Group

Introduction 88

ITrafficInfo:Latitude 89

ITrafficInfo:Longitude 89 ITrafficInfo:MaxVehicles 89

ITrafficInfo:Radius 89

ITrafficInfo:Filter 89

Designating the Filter Value 91

Sleep State 91

Nearest Traffic Search Example 92

ITrafficInfo:SortOrder 96

ITrafficInfo:CurrentVehicle 96

ITrafficInfo:SelectedVehicle 96

ITrafficInfo:SelectedVehicleID 97

ITrafficInfo:ListSize 97 ITrafficInfo:CurrentDistance 98

A Note on Update Frequency 98

ITrafficInfo:SelectedFlightPlan 98

ITrafficInfo XML Script Examples 99

Example 1. Displaying a List of AI Aircraft Information 99

Example 2. Displaying the Selected Aircraft on the Map 102



vi

FS9 FSX

ITrafficInfo:CurrentPlayerName 103

ITrafficInfo:SelectedPlayerName 103

Combining XML Objects with CustomDraw Map 104

Screen Pixels vs. Gauge Units 105

Three examples of Panel Background Image stretch 107

Map Scale Calibration for Overlays

Scale Calibration – FSX 110

Scale Calibration – FS9 113

Manual Calibration Summary Points 115

Transforming Lat/Lon Coordinates to Gauge Units

Lat Lon to Gauge Units: Creating Overlays 116

TrackUp = 1 118Euclidean Coordinate Rotation 118

Vector Rotation given Distance and Bearing 120

TCAS Overlay Example (FSX) 122

Transforming Gauge Units to Lat/Lon Coordinates 125

Distance, Bearing, Lat and Lon from a Mouse Click

Accuracy 129

Key Equations 130

TAWS

TAWS = GPWS + FLTA 131

Terrain Awareness Map 132

Elevation Color Selection 132

Yellow Band Must be 1000’ (or Multiples of 1000’) 134

Color Feathering 134

Radar Altimeter ElevationXColor Adjustment 136

Terrain Refresh 137

LayerTerrain Refresh 137

Example <Mouse> section – turn TAWS Mode On and Off 138

Example <Update> section – Terrain Refresh 140

Example <Update> section – Timing of Terrain Refresh 141



vii

FS9 FSX

TCAS

Acknowledgements 142

XML TCAS in FSX 142

An approach to XML TCAS in FSX 143

FAA TCAS II Protocol 144Range Tau and Vertical Tau 145

DMOD and ZTHR 147

Display Variables and Arrays 147

XMLVars 148

TCAS Overlay Display Example 149

References 153

Other Applications

Click Distance, Bearing, Latitude and Longitude 154

Nearest Search Centered on a Mouse Click 154

Add Waypoint to a Flight Plan 154

Stationary Map rather than Moving Map 154

Example XML Map Gauges

Gauge Setup 155

XMLVars 156

ExampleMovingMap1.xml 156

ExampleStationaryMap1.xml 156

Description of Features 156

LayerAirports Additional Information

Airport Symbol Size – A Function of Rwy Length and Zoom 162

TextDetailLayerAirports – A Function of Zoom 163

Airport Symbol Type Overrides Text Index Selection 164

Font Type, Font Size and Label Offset 165

Default De-cluttering scheme 166



1

Introduction

This is a guide for working with Flight Simulator’s CustomDraw map function – theprogram that draws the map in the stock gps500 gauge. The purpose of the guidebookis to epand on !icrosoft’s SD" !o#ing !ap documentation which is #er$ brief so that

ineperienced gauge programmers can get up and running more %uickl$.

The guidebook is written primaril$ with FS& in mind because it contains importantadditional mapping capabilities and related #ariables that are absent in FS'. (owe#er)an attempt has been made to note ke$ differences between the two sims) for eample)map pro*ection scheme differences.

+ll of the map #ariables are documented although there remain %uestions about a fewand those are noted in the tet. +dditionall$) as , ha#e ne#er used FS& race missions)there is no -a$erace/oints chapter $et.

,n addition to the CustomDraw map #ariables) the following topics and map applicationsare discussed

&!- gauge units #s. ph$sical screen piels Calibrating &!- and CustomDraw map scales Transforming mouse & and 1 into longitude and latitude Creating map o#erla$s and coordinate rotation for Track2p34 T+S map TC+S o#erla$ using ,Traffic,nfo #ariables !ouse click distance) bearing) latitude and longitude 6earest search centered on a mouse click point rather than aircraft position +dding a flight plan wa$point b$ mouse click Stationar$ !ap #s. !o#ing !ap

,n m$ opinion) some interesting applications can be imagined when $ou calibrate &!-and CustomDraw map scales and transform mouse & and 1 into longitude and latitude.

, need to acknowledge the assistance of a few people7 Tom +guilo) and obbie !c8lrath.Tom is the author of &!-9ars) a #ariable handling module that , use to d$namicall$create &!- #ariable arra$s without which m$ rendition of TC+S is reall$ not possible.obbie is the author of :lack:o and -ogger) both of which were indispensable in thepreparation of this guidebook. (e also pro#ided feedback on application of +ffinetransforms needed for coordinate rotation.

Finall$) two full$ functional &!- gauges for use in FS& are a#ailable as download fromthe :lack:o website that demonstrate the applications mentioned abo#e.

:ob !c8lrath:angkok) Thailand;anuar$) <04=



2

Map Projections

Flight Simulator pro#ides two different map s$stems ha#ing different pro*ection schemes.

4. Flight Planner Map and World Map: FS' and FS& Flight /lanner and orld

maps both use the 8%uidistant C$lindrical) Plate Carrée pro*ection >Flights Flight /lanner Find oute and orld !ap?

<. CustomDraw fs9gps:Map: FS' – Sinusoidal 8%ual +rea) /seudoc$lindricalpro*ection. FS& – :oth Sinusoidal 8%ual +rea and Plate Carrée pro*ections.CustomDraw is the map engine for the mo#ing map displa$ used in the stockgps@500 and radar gauges and is the sub*ect of this guidebook.

Flight Planner and World Maps

Flight /lanner and orld maps of both FS' and FS& incorporate an 8%uidistant

C$lindrical) Plate Carrée pro*ection. This pro*ection is characteriAed b$ straight andorthogonal meridians >lines of constant longitude? and parallels >lines of constantlatitude? producing s%uare graticules >the latBlon grid? and simple) computationall$friendl$ e%uations. ,t is well suited for the eas$ panning around the globe and flightplan editing7 6orth is 2p) 8ast is ight) and latBlon position is simple to interpolate.

,ts drawback is that eastBwest distances are progressi#el$ distorted as latitude increasestoward the poles to the point where &Bais map scale becomes infinite at the poles. +sshown on the net page) the high latitude distortion is #er$ ob#ious when the map isAoomed out. +lthough useful and intuiti#e for general map reference) this pro*ections$stem is poorl$ suited for na#igation purposes re%uired b$ a gps instrument because of

the significant distance and angle distortions.

The images that follow are composite screen captures from the FS' and FS& Flight/lanner and orld maps



3



4

CustomDraw fs9gps:Map

CustomDraw fs'gps!ap is Flight Simulators programmable map engine used in thestock gps gauges and in FS& radar applications. ,t is part of the gps.dll module. !ap#ariables discussed in the SD" and this guide appl$ to the fs'gps!ap s$stem.

,n FS9) fs'gps!ap uses a Sinusoidal /ro*ection scheme >a.k.a. SansomBFlamsteed)8%ualB+rea /seudoc$clindrical) or !ercator 8%ualB+rea /ro*ection?. ,mportantl$) theSinusoidal /ro*ection is characteriAed b$ e%ual northBsouth and eastBwest map scales atall points on the globe. n the map as in realit$) the length of each parallel isproportional to the cosine of the latitude) so real distance between meridians decreasestoward the poles. The resulting shape of the earth is the region between two s$mmetricrotated cosine cur#es.

Sinusoidal /ro*ections displa$ shape correctl$ onl$ along the central meridian and distortshape awa$ from it. To mitigate this) the map can be interruptedE b$ shifting thelongitude of the central meridian and redrawing the map around the new central

meridian. Flight Simulator incorporates interruption b$ continuously shifting the centralmeridian as the aircraft flies. The continuous shift is enabled when the -ongitudeG #ariable is set to the aircraft longitude

<Longitude> (A:PLANE LONGITUDE, radians) </Longitude>

This produces a #er$ accurate map especiall$ when Aoomed in to the most common gpsgauge operational ranges ><00 6!iles or less?.

Figure A) on the following page) is a composite screen shot of FS'’s CustomDrawfs'gps!ap Aoomed out to maimum Hoom. ,n this eample) the central meridian is'0I est.

,n FSX ) the fs'gps!ap is a h$brid of 8%ual +rea Sinusoidal and 8%uidistant C$lindricalpro*ections that is a function of Hoom. +t anges below <J0 6! >Hoom less than500)000 meters?) FS& uses the Sinusoidal /ro*ection like FS'. (owe#er) at Hoom G3500)000 meters) it switches to the 8%uidistant C$lindrical pro*ection as shown in thecomposite FS& fs'gps!ap screen capture in Figure B. + conse%uence of this switch isthat the &Bais scale must be multiplied b$ the cosine of the latitude to $ield correcteastBwest distances.

Distance distortion becomes so se#ere at high latitudes in this pro*ection scheme thatFS& re#erts back to sinusoidal pro*ection at latitudes greater than J0I 6orth and South.

n 8%uidistant C$lindrical /ro*ections) ange ings are actuall$ ellipses >ecept at thee%uator? because of the different & and 1 ais scales. n Sinusoidal /ro*ections) the$are circles. Conse%uentl$) ange ings >-a$erangeingsG? should ne#er bedispla$ed in FS& at Hoom Factors of <J0 6! and abo#e.



5



6

CustomDraw Map variables

CustomDraw Map Variales

!ame) X ) " ) and Bright must be placed in the CustomDraw start tag) the$ cannot be

scripted as child elements like the rest of the fs'gps!ap #ariables. 6ame) &) and 1 aremandator$. :right is optional.

<CustomDraw Name="fs9gps:1:Map" X="275" Y="230" Bright="1">

!ame#$fs9gps:%:Map&' fs'gps!ap refers to the code that generates the mapdispla$. From the SD" the K4K is unnecessar$ if the panel in which the map is toappear has onl$ one map. therwise use K4K) K<K and so on to distinguish thedifferent maps.

X#()*+( "#$),-&' & and 1 are the horiAontal and #ertical dimensions of the mapdispla$) measured in gauge units >gauge pielsE? not in monitor or screen piels.

+s an eample) the dimensions of the map displa$ of the stock FS' and FS&[email protected] gauges are <J5 <=0 gauge units. efer to line J5' of the FS&[email protected] gauge.

Bright#$%&' Set to 4E) 1esE) or TrueE if the map remains at its normalbrightness at dawn) dusk and night times of the da$) otherwise it will be darkened.

The remaining fs9gps:Map variables discussed below as well as the -a$er #ariablesco#ered in subse%uent chapters can all be scripted as child elements of theCustomDraw element.

.oom /meters0

Hoom changes the apparent distance of the obser#er >pilot? to the ground surfaceshown in the map b$ changing map scales and area displa$ed as Hoom changes. ,t is astandard Aoom definition B Aoom in >smaller Hoom #alues? to see more detail) Aoom out

>larger Hoom #alues? to see more area.

Hoom limits are L0 to 5)000)000 meters in FS& and 400 to 5)000)000 meters in FS'.

The terms Hoom and ange are sometimes used interchangeabl$) but the fs'gps!ap#ariable is Hoom and its units are meters.



7

Hoom or ange is the radius of the biggest complete circle that can be drawn within theboundaries of the map. n the map) Hoom or ange represents oneBhalf the distanceof the short side of the map displa$.

Flight Simulator automati1all2 draws the map to fit ) times 3ange or .oominto the short side of the map displa2' Technicall$) this is the shortest side asmeasured in screen pixels, not gauge units.

The term HoomFactor is defined in the stock gps@500 gauge to represent 6!iles insteadof the default units) meters. ,f the user wants a ange of 45 6!iles) then the following&!- can be used

<Zoom> 27780 </Zoom> or

<Zoom> 15 1852.0 * </Zoom> or

<Zoom> (L:ZoomFactor, number) 1852.0 * </Zoom> or

<Zoom> (@g:map_ZoomFactor) 1852.0 * </Zoom>

where >-HoomFactor) number? and >Mgmap@HoomFactor? #alues e%ual 45. Theconstant) 4L5<.0) is the number of meters per 6autical !ile) and pro#ides thecon#ersion to 6!iles. Hoom >m? 3 HoomFactor >6!? 4L5< >mN6!?.



8

4atitude 4ongitude /radians0

-atitude and longitude of the center of the map) in radians. 2suall$) this is the aircraftposition which can be defined as

<Latitude> (A:PLANE LATITUDE, radians) </Latitude>

<Longitude> (A:PLANE LONGITUDE, radians) </Longitude> or

<Latitude> (A:GPS POSITION LAT, radians) </Latitude>

<Longitude> (A:GPS POSITION LON, radians) </Longitude>

+O/S /S,T,6 -+T and -6 ma$ be a good choice as far as s$stem workload isconcerned because those #ariables are updated e#er$ one second. (owe#er) in someapplications such as a TC+S s$stem) +/-+68 -+T,T2D8 and -6O,T2D8 are preferredbecause these are updated e#er$ gauge update c$cle.

,n an +TC Controller session) the map can be centered on a fied location. +s aneample) for the control tower at ;ohannesburg ,nternational +irport >F+;S?) epublic ofSouth +frica >-at S<PI L.=40'=E) -on 80<LI 45.0L440E?) the &!- would be

<Latitude> -26.138516 dgrd </Latitude>

<Longitude> 28.251352 dgrd </Longitude> or

<Latitude> -0.4562032 </Latitude>

<Longitude> 0.4930791 </Longitude>

5eading /radians0

(eading determines the orientation and direction of mo#ement of the map when theaircraft is in flight) and when Track2p 3 4.

hether True or !agnetic (eading or e#en a fied orientation is specified is a matter of

preference. ,n actual Oarmin O/SNO6S Q00 and 500 Series and O4000 units) setupconfigurations accommodate True or !agnetic tracks or 2ser defined orientation. ,n thestock Flight Simulator [email protected] gauge and O4000 !FD ml gauges) (eading isprescribed as 6378) which is the usual preference) but could be changed if desired.efer to line JPQ in the [email protected] gauge or line <J0P in the !FD@:aron.ml gauge.

<Heading> (A:GPS GROUND TRUE TRACK, radians) </Heading>



9

(A:PLANE HEADING DEGREES TRUE, radians) is not an ideal choice for (eading

because in a crosswind) the aircraft heading and ground track differ) but ground track iswhat is needed.

5eading 8amples

The figures abo#e depict an aircraft fl$ing northeast along the coast after departurefrom Deputado -uRs 8duardo !agalhes ,nternational +irport >S:S9?) Sal#ador da :ahia):raAil. !ap siAe is 50 P<.5 6!.

,n Figure A) (eading is set to the True ground track) and Track2p is 4. The groundtrack that the aircraft is making alwa$s points up) to the top of the map. This is thenormal configuration. !ap mo#ement is alwa$s 4L0 degrees from the ground track.

,n Figure B) (eading is set to a constant 440 degrees

<Heading> 110 dgrd </Heading>

,n Figure C) Track2p is not set to 4. ,n this e#ent) the map is alwa$s oriented with thetop) or up) towards true 6orth regardless of the (eading #alue.

Fig A (eading 3>+O/S O26D T28 T+C") radians?Track2p 3 4

Fig B (eading 3 440 dgrd >constant?Track2p 3 4

Fig C (eading 3

>+O/S O26D T28 T+C") radians?Track2p 3 0

A B

C



10

The compass rose of all three maps is oriented to magnetic 6orth) consistent with theaircraft’s DO or (S, compass.

+lso note that with CustomDraw map) the map surface mo#es and the aircraft s$mbolremains fied. There is no capabilit$ using fs'gps!ap #ariables for the aircraft to mo#eacross a stationar$ map #iew) howe#er) this can be accomplished with the aircraft as ano#erla$ ob*ect and result is #er$ interesting. This feature is included in the8ampleStationar2Map%'ml file downloadable from the :lack:o website.

6ra17p /ool0

Track2p determines whether (eading >the aircraft ground track or other specifieddirection? or true 6orth points up) toward the top of the map.

Track2p 3 0. The top of the map) up) points toward true 6orth

Track2p 3 an$ #alue other than Aero. The direction determined b$(eading points up) to the top of the map

CenterX Center" /gauge units; float0

Center& and Center1 define the position on the map displa$ where the map centerE islocated. The map center ser#es as the position of the aircraft or of the control tower ina +TC Controller session. Center& and Center1 are gauge units measured from theupper left corner of the map.

Sele1tedVehi1le /inde enum0 FSX <nl2

Selected9ehicle is a #ariable in the ,Traffic,nfo group that is useful when fs'gps!ap isset up as an +TC radar screen. ,t is the inde pointer used to select a specific aircraftfrom the ,Traffic,nfo list in order to highlight its mo#ement in contrast to all otheraircraft on the radar screen) or to keep specific record of an$ flight #ariables associatedwith this aircraft. The aircraft must be included in the ,Traffic,nfo search results inorder to be selectedNhighlighted. nl$ one aircraft can be Selected at a time.

efer to the ,Traffic,nfo group chapter for further detail.



11

6agPosition /integer inde0 FSX <nl2

Tag/osition is an inde associated with the -a$er9ehicles group that controls placementof the aircraft flight status information label >TetDetail-a$er9ehicles? for the Selectedaircraft on the radar screen. ,ts purpose is to help make the Selected aircraftinformation tag easier to see b$ mo#ing its position relati#e to all the other aircraftinformation tags.

Tag placement relati#e to the aircraft s$mbol is as follows

0 3 2//8@,O(T >Default? Q 3 -8@-8FT

4 3 ,O(T 5 3 -8FT

< 3 -8@,O(T P 3 2//8@-8FT

= 3 :TT! J 3 T/

+n aircraft must first be Selected and then a new Tag/osition can be set if desired.

+s an eample) the radar screen images below show airborne +, traffic with flightinformation labels >TetDetail-a$er9ehicles 3 <? displa$ed in the default 2pper ightposition >Tag/osition 3 0. See Fig A?.

The table shows ,Traffic,nfo search results and 65P4L) a #er$ fast :eech "ing +ir =50)has been Selected. 8#en though the Selected aircraft label alwa$s turns red) it is still alittle difficult to read. Subse%uentl$) its Tag/osition was set to < 3 -ower ight) asshown in Figure B; and can be read more clearl$ in that position.

Tag/osition 3 0

Tag/osition 3 <

A B



12

The ke$ &!- for this se%uence is

2 (>C:ITrafficInfo:SelectedVehicle)

<TagPosition> 2 </TagPosition>

(C:ITrafficInfo:SelectedVehicleID) (>C:fs9gps:SelectedVehicle)

Further discussion of the &!- in#ol#ed can be found in the ,Traffic,nfo group chapter.

Ba1groundColor /B=3 heade1imal0 FSX <nl2

:ackgroundColor is the background color of the map when -a$erTerrain 3 0. ,t is alsothe color of land when Detail-a$erTerrain 3 4 >ater nl$?.

,f :ackgroundColor is omitted from the script) the default color is black.

,n FS') the background color cannot be selected. hene#er -a$erTerrain 3 0) thebackground color is alwa$s black in FS'.

>1eColor /B=3 heade1imal0 FSX <nl2

,ceColor is the color of the land surface when it is ice.

,f ,ceColor is omitted from the script) the default color is a light gra$

ed 222 Oreen 222 :lue 222 :O (e 0xDEDEDE

,n FS') ,ceColor is the same light gra$ and cannot be changed.

WaterColor /B=3 heade1imal0 FSX <nl2

aterColor is the color of water surfaces oceans) lakes) and ri#ers.

,f aterColor is omitted from the script) the default color is a light blue

ed 132 Oreen 222 :lue 247 :O (e 0xF7DE84

,n FS') aterColor is the same light blue and cannot be changed.



13

8le?ationXColor /B=3 heade1imal0 FSX <nl2

8le#ation&Color determines the terrain color applied between specified ele#ations.

The number in the #ariable name defines the top ele#ation on which the color will beapplied. The units are feet and are not changed e#en if FS settings are set to metric>ptions G Settings G Oeneral G 2nit of measure G !etric?.

For eample) the ml

<Elevation3000Color> 0x73C3C8 </Elevation3000Color>

produces a tan ele#ation color -*,C,C@ between <000 ft and =000 ft ele#ation.

The 8le#ation&Color #ariables

8le#ation0Color 3 Color between B4000 and 0 feet ele#ation

8le#ation4000Color 3 Color between 0 and 4000 feet ele#ation

8le#ation<000Color 3 Color between 4000 and <000 feet ele#ation

8le#ation=000Color 3 Color between <000 and =000 feet ele#ation

8le#ationQ000Color 3 Color between =000 and Q000 feet ele#ation

8le#ation5000Color 3 Color between Q000 and 5000 feet ele#ation

8le#ationP000Color 3 Color between 5000 and P000 feet ele#ation

8le#ationJ000Color 3 Color between P000 and J000 feet ele#ation

8le#ationL000Color 3 Color between J000 and L000 feet ele#ation

8le#ation'000Color 3 Color between L000 and '000 feet ele#ation

8le#ation40000Color 3 Color between '000 and 40000 feet ele#ation

8le#ation44000Color 3 Color between 40000 and 44000 feet ele#ation

8le#ation4<000Color 3 Color between 44000 and 4<000 feet ele#ation

8le#ation4=000Color 3 Color between 4<000 and 4=000 feet ele#ation

8le#ation4Q000Color 3 Color between 4=000 and 4Q000 feet ele#ation

8le#ation45000Color 3 Color between 4Q000 and 45000 feet ele#ation

8le#ation4P000Color 3 Color between 45000 and 4P000 feet ele#ation

8le#ation4J000Color 3 Color 4P000 feet and greater





15

The second pair of maps demonstrates TerrainShadow when the O4000 color palette isused with 8le#ation&Color #ariables. 6ote the color feathering >blending? effect whenTerrainShadow 3 0.

TerrainShadow is a#ailable throughout all Hoom ranges in FS&.

,n FS') terrain shadowing is enabled b$ default for Hoom le#els between 400 and<P=)40J meters. +t Hoom 3 <P=)40L meters and higher) terrain shadow is disabled.

PanVerti1al Pan5oriontal /s1reen piels0 FSX <nl2

/an9ertical and /an(oriAontal mo#e the center of the map and are analogous toCenter& and Center1 ecept that the /an #ariables are measured in screen piels whileCenter& and 1 are measured in gauge piels.

The screen captures on the net page show the pan effect. ,n Figure A) (ong "ong,nternational +irport >9(((? is at the center of the map) but the center has beenad*usted using Center& to cause the airport to be positioned at the horiAontal mid pointof the screen. The screen resolution is 4P00 4<00 piels) so 9((( is at the L00 pielposition as shown b$ the red cross hairs.

Figure B is a screen shot after a pan to the left of Q00 has been applied. :ecause thereference point >the red cross hairs? is fied) panning to the left causes the map to

mo#e to the right. 6ow) 9((( has mo#ed Q00 screen piels to the right as marked b$the blue cross hair) and the red cross hair is centered on a location that was out of map#iew to the left before the pan.

8#er$thing is shifted Terrain) 2ser’s +ircraft) ange ings) Traffic) etc.

errainShadow 3 0 TerrainShadow 3 4



16

The &!- re%uires CustomDraw and !ouse entries. ithin the CustomDraw element

<PanVertical> (L:Pan_V) </PanVertical>

<PanHorizontal> (L:Pan_H) </PanHorizontal>

<PanReset> (L:Pan_Reset) </PanReset>

The /an9ertical) (oriAontal and eset -9ars can ha#e an$ name and can be unitless.

A

VHHH

4P00 screen piels

B

VHHH



17

Click spots are usuall$ established to enable mouse control of panning. These computethe -/an@9) -/an@() and -/an@eset #alues. The !ouse &!- below is associated

with the pan controls and of the gauge in the screen captures.

<Area Name="PanLEFT" Left="10" Top="275" Width="20" Height="30"><Cursor Type="LeftArrow"/><Click Kind="LeftSingle">

(L:Pan_H) (L:Pan_Pix, enum) - (>L:Pan_H)</Click>

</Area>

<Area Name="PanRIGHT" Left="60" Top="275" Width="20" Height="30"><Cursor Type="RightArrow"/><Click Kind="LeftSingle">

(L:Pan_H) (L:Pan_Pix, enum) + (>L:Pan_H)</Click>

</Area>

<Area Name="PanUP" Left="30" Top="255" Width="30" Height="20"><Cursor Type="DownArrow"/><Click Kind="LeftSingle">

(L:Pan_V) (L:Pan_Pix, enum) - (>L:Pan_V)</Click>

</Area>

<Area Name="PanDOWN" Left="30" Top="304" Width="30" Height="20"><Cursor Type="UpArrow"/><Click Kind="LeftSingle">

(L:Pan_V) (L:Pan_Pix, enum) + (>L:Pan_V)

</Click></Area>

<Area Name="PanRESET" Left="37" Top="282" Width="15" Height="15"><Cursor Type="Hand"/><Click Kind="LeftSingle">

(L:Pan_Reset) ! (>L:Pan_Reset)</Click>

</Area>

,n this eample) the magnitude of the pan >number of screen piels? is a #ariable)>-/an@/i)@enum?) that was pre#iousl$ set with a #alue of Q00

400 (>L:Pan_Pix, enum)



18

Pan3eset /unitless0 FSX <nl2

Toggling /aneset will reset the map to its center position prior to the application of/an9ertical andNor /an(oriAontal. efer to the &!- eample abo#e.

Priorit2 /ool0

From SD" Set to True to draw the map as a priority.

Map4oading /ool0 FSX <nl2

From SD" : Set to True if the map is currently being loaded. This is a S8T) not O8T#ariable

7pdateAlwa2s /ool0 FSX <nl2

From SD" Set to True if the map should be updated every frame. Set to False if themap is only to be updated when positions have changed enough.

2nfortunatel$) it is difficult to be sure what these last = #ariables do. , ha#e onl$ a fewobser#ations

2pdate+lwa$s will not b$ itself cause terrain to be refreshed >see T+S chapter?

-a$er9ehicles +, traffic positions do not update when 2pdate+lwa$s30 and user

aircraft is not mo#ing. Therefore) in an +TC simulation) 2pdate+lwa$s mustalwa$s be set to 4. 6ote that ,Traffic,nfo #ariables >other than,Traffic,nfoCurrentDistance? update e#er$ gauge c$cle regardless of2pdate+lwa$s setting.

The map is *itter$E when 2pdate+lwa$s 3 4.

/riorit$34 clearl$ speeds certain scripts such as the T+S refresh B the terraincolor refresh >see T+S chapter?

, welcome specific feedback on the purpose and actions of /riorit$) !ap-oading) and2pdate+lwa$s.



19

LayerTerrain

-a$erTerrain draws terrain ele#ation and water background colors.

4a2er6errain /ool0

-a$erTerrain controls whether or not the la$er is displa$ed. +n$ number other than 0will displa$ the la$er. + Aero results in no rendering. ,f -a$erTerrain is Aero) thebackground color of the map is determined b$ the :ackgroundColor #ariable in FS&. ,nFS') the background color is alwa$s black.

8ample &!-

<LayerTerrain> 1 </LayerTerrain>

Detail4a2er6errain /enum0

Detail-a$erTerrain controls whether or not terrain ele#ation colors are displa$ed.

Detail-a$erTerrain 3 B4. Terrain ele#ation colors are displa$ed. ,n FS') thedefault terrain ele#ation palette is applied to land and water. ,n FS&) the defaultterrain ele#ation palette is applied to land if no 8le#ation&Color #ariables aredefined. ater color can be set using aterColor.

Detail-a$erTerrain 3 0. 6o terrain ele#ation colors are displa$ed. This has thesame effect as -a$erTerrain 3 0. The map background color will be set b$

:ackgroundColor in FS) and will alwa$s be black in FS'. Detail-a$erTerrain 3 4. ater onl$. -and will show no ele#ation colors but will

be the same color as the map background color. ater is a default dark blue inFS') same in FS&) but can be reset using aterColor in FS&.

Detail-a$erTerrain 3 <U. Same as B4. Terrain ele#ation colors are displa$ed. ,nFS') the default terrain ele#ation palette is applied to land and water. ,n FS&)the default terrain ele#ation palette is applied to land if no 8le#ation&Color #ariables are defined. ater color can be set using aterColor.

8ample 8le?ation Colors

The following eamples demonstrate some of the options. The maps co#er Tok$o :a$and !t. Fu*i and are centered on +tsugi +ero :ase >;T+?) "anagawa /refecture) ;apan.!ap siAe LJ.5 J0 6!.



20

A VFR Sectional. US FAA Format

Figure A

9F Sectional chart) 2S F++format for comparison

B DetailLayerTerrain = -1 or 2+ Default FSX Terrain Palette

Figure B

Detail-a$erTerrain 3 B4

Default FS& terrain colorpalette. 6o 8le#ation&Color #ariables are in the &!- script

FSX

C DetailLayerTerrain = -1 or 2+ Default FSX Terrain Palette TerrainShadow = 1

Figure C


Default FS& colors with TerrainShadowing

Comparison with the 2S 9FSectional which is the basis offs'gps!ap format is apparent

FSX



21

D DetailLayerTerrain = -1 or 2+ Default FSX Terrain Palette TerrainShadow = 1 WaterColor = 0x783C30

Figure D


aterColor was changed toOarmin’s O4000 water color./ro#ides better contrast withland

FSX

E DetailLayerTerrain = -1 or 2+

G1000 Terrain Palette WaterColor = 0x783C30

Figure 8


Oarmin terrain color palette>from Oarmin O4000 !anual?was used with 8le#ation&Color #ariables

FSX

F DetailLayerTerrain = -1 or 2+ G1000 Terrain Palette TerainShadow = 1 WaterColor = 0x783C30

Figure F


Oarmin O4000 terrain colorpalette was used with8le#ation&Color #ariables

TerrainShadow 3 4

FSX



22

G DetailLayerTerrain = 1 WaterColor = 0x783C30 BackgroundColor= 0x99FFCC

Figure =

Detail-a$erTerrain 3 4.

ater onl$.

hen Detail-a$erTerrain is setto 4) ele#ation colors aredisabled) and :ackgroundColor is used as the land color. ,nthis eample light green)0''FFCC

FSX

H DetailLayerTerrain = 2 ElevationXXXXColor = 0xC0C0C0 WaterColor = 0x783C30 TerrainShadow = 1

Figure 5


TerrainShadow eample. Forthis #iew) all 8le#ationColor #ariables are 0C0C0C0 andTerrainShadow 3 4

FSX

IFigure >


6AWS !ap approimation.

+ll 8le#ation&Color #ariables foraltitudes abo#e aircraft are red)8le#ation&Color for the la$erbeneath aircraft is $ellow) andbelow that) are all black. FS&stock aterColor used to maskscreen refresh flicker

DetailLayerTerrain = -1 or 2+ ElevationXXXXColor = a/c alt dependent WaterColor = 0xF7DE84 TerrainShadow = 0

FSX

6errainShadow must edisaled in 6AWS Mode



23

6etDetail4a2er6errain

TetDetail-a$erTerrain is not functional. There is no tet in this la$er.

<e1tDetail4a2er6errain /ool0

b*ectDetail-a$erTerrain is redundant with -a$erTerrain and it is best to omit this#ariable from the &!- script altogether. ,f b*ectDetail-a$erTerrain is Aero) thenregardless of -a$erTerrain or Detail-a$erTerrain #alues) no ele#ation colors aredispla$ed and the map background is determined b$ :ackgroundColor in FS& or is blackin FS'. +n$ number other than Aero will enable Detail-a$erTerrain to control ele#ationcolor parameters. ,n all cases) -a$erTerrain is the parent #ariable and should be used tocontrol displa$ of terrain ele#ation colors.

J

FS9

Figure


FS' Terrain color. This is thedefault) and onl$) terrain colorscheme a#ailable.

,n FS') TerrainShadow is not a#ariable but is applied b$default in low Hoom ranges

DetailLayerTerrain = -1 or 2+

Figure

Detail-a$erTerrain 3 4

ater onl$.

,n FS') there is no land orwater color choice. -and coloris alwa$s black) and blackbackground is the onl$ FS'option. 9er$ dark image.

K DetailLayerTerrain = 1

FS9



24

Color4a2er6errain

Color-a$erTerrain is not functional in either FS' or FS&.

6etColor4a2er6errain

TetColor-a$erTerrain is not functional. There is no tet in this la$er.

8le?ation Color Palettes

8le#ation color palettes of FS') FS& and the real Oarmin 4000 !FD within the limits ofthe color fidelit$ of screen captures and /ilot Ouide pdf manuals are shown below.

The O: decimal #alues are in normal 3 = B order whereas the headecimal is standardFS :O headecimal.



25

Color Feathering

hen using either the default FS& color palette or custom 8le#ation&Color color#ariables without TerrainShadow) FS& feathers the colors. This is something to beaware of when de#eloping a terrain awareness map.

The maps below demonstrate the effect on 8le#ationQ000Color.

Figure A is a contour map of the ,sland of (awaii) 2S+. The <000’) =000’) and Q000’topographic contours from the FS& terrain data are displa$ed.

,n Figure B) 8le#ationQ000Color 3 0=J5'JD >a chocolate brown color? andTerrainShadow 3 4. The ele#ation color uniforml$ fills the inter#al from Q000 feet to=000 feet as epected) and no color feathering occurs.

Figure C is the same map but with TerrainShadow 3 0. This ob#iousl$ presents a fewissues to deal with for a terrain awareness displa$. The area outlined b$ the dashed line

is enlarged a little in Figure D.

Figure D shows that the brown color bandassociated with 8le#ationQ000Color is actuall$centered on the =000’ ele#ation contour and

feathers out in both directions for 4000 #erticalfeet.

2 0 0

0 ’

3

0 0 0 ’

4 0 0 0

’

8le#ationQ000Color3 0=J5'JD

TerrainShadow # -

D

2 0 0

0 ’

3

0 0 0 ’

4 0 0 0

’

8le#ationQ000Color3 0=J5'JD

TerrainShadow # -

D



26

LayerBorders

-a$er:orders adds geopolitical boundar$ lines. nshore) these are internationalboundaries as well as state boundaries in the 2nited States. ffshore in FS&) the$include coarsel$ digitiAed territorial water boundaries and large regional boundaries such

as those recogniAed in the South /acific. ffshore in FS') coastlines are drawn.:oundaries drawn b$ -a$er:orders do not correspond to ,C+ egions in all cases >e.g.)FS& South /acific) +ustralia?.

,n FS& onl$) -a$er:orders includes a few >#er$ few? disputed international boundaries.

4a2erBorders /ool0

-a$er:orders controls whether or not the la$er is displa$ed. +n$ number other than 0will displa$ the la$er. + Aero results in no rendering.

8ample &!-

<LayerBorders> 1 </LayerBorders>

Detail4a2erBorders /ool0

Detail-a$er:orders is redundant with -a$er:order. +n$ number other than 0 will displa$the la$er. + Aero results in no rendering. ,t is recommended to ecludeDetail-a$er:orders from the &!- script and to control displa$ of the la$er using

-a$er:orders.

6etDetail4a2erBorders

TetDetail-a$er:orders is not functional. 6o names are displa$ed b$ this la$er.

<e1tDetail4a2erBorders /de1imal or heade1imal0

FSX:

,n FSX onl$) b*ectDetail-a$er:orders controls whether disputed internationalboundaries) nonBdisputedE international and state boundaries) or both) are displa$ed.



27

b*ectDetail-a$er:orders 3 B4. Default. Disputed and 6onBDisputedE

b*ectDetail-a$er:orders 3 0. 6othing is drawn

b*ectDetail-a$er:orders 3 4. Disputed boundaries are drawn

b*ectDetail-a$er:orders 3 <. Disputed and 6onBDisputedE boundaries

Technicall$) FS& b*ectDetail-a$er:orders is a sort of binar$ construction that can berepresented b$ a headecimal number

< 4 B Decimal e%ui#alent

, 6

T 8 . 6 + T , 6 + -

+ 6

D . 8 O , 6 + -

:

2 6 D + . 1

D ,

S / 2 T 8 D

, 6

T 8 . 6 + T , 6 + -

:

2 6 D + . 1

4 0 B :it number >:it 0 and :it4?

% - B b*ectDetail-a$er:orders selections

(owe#er) :it 0 >disputed boundaries? is alwa$s li#e and conse%uentl$) alwa$s drawn.2sing the selection abo#e) -)) disputed boundaries are still displa$ed.

Thirteen disputed territories are depicted b$ Flight Simulator >FS&?

Disputants >alphabetic? Disputed Territor$

Ou$ana B 9eneAuela Hona en eclamatiVn Ou$ana 8se%uibaOu$ana B Suriname 6ew i#er Triangle

,srael B State of /alestine OaAa Strip

,srael B State of /alestine est :ank

,srael B 6orth District ecluding Oolan (eights

C$prus B 6. C$prus Turkish C$priot +rea >6orthern C$prus?

!orocco B SpainCeuta) !elilla) /eWVn de 9XleA de la Oomera)/eWVn de +lhucemas islands) ,slas Chafarinas),sla de +lborYn

+Aerbai*an B 6agorno "arabakh 6agornoB"arabakh territor$

,ndia B /akistan +Aad "ashmir,ndia B /akistan 6orthern +reas) Siachen Olacier

China B ,ndia +ksai Chin

China B TaiwanTaiwan) /enghu ,slands) Oreen and rchid,slands

!orocco B Sahrawi +rab Dem. ep. estern Sahara



28

Disputed boundaries are drawn using a dashed) one screen piel wide line. 6onBdisputed boundaries use a solid 4 piel line.

FS9:

,n FS9 onl$) b*ectDetail-a$er:orders controls whether coastlines) international borders>plus State borders in the 2S+? or both) are displa$ed. The FS' database does notinclude disputed territories.

+ Decimal or (eadecimal number is used that is in the form of a bit table filter similarto filters in 6earest searches >reference O/S Ouidebook page P<BP=?.

<e1tDetail4a2erBorders /FS90

Bit Name Bit Name

0 Coastlines 1 Borders


: . D 8 . S

C + S T - , 6 8

4 0 B :it number >:it 0 and :it 4?% - B b*ectDetail-a$er:orders selections

+s an eample) if borders but no coastline is desired) then :it 4 is selected which resultsin the :inar$ number 1 0. The decimal e%ui#alent is < and the headecimal is 0<.

The appropriate &!-

<ObjectDetailLayerBorders> 2 </ObjectDetailLayerBorders> or

<ObjectDetailLayerBorders> 0x2 </ObjectDetailLayerBorders>

:oundaries and Coastlines are drawn using a one screen piel wide long dash) shortdash line.



29

Color4a2erBorders /B=3 heade1imal0

Color-a$er:orders controls the color of the boundar$ line. The default is a dark gra$

ed132

Oreen132

:lue132

:O (e0x848484

6etColor4a2erBorders

TetColor-a$er:orders is not functional.

Borders 8ample E FSX

The maps below demonstrate FS& b*ectDetail-a$er:orders in the 9eneAuela – Ou$ana – Suriname – French Ouiana region of South +merica. The Ou$a$a 8se%uiba andSuriname 6ew i#er Triangle disputed territories are shown b$ the dotted lines. !apsiAe 4000 L00 6!.

b*ectDetail-a$er:orders 3 4 b*ectDetail-a$er:orders 3 <FSX FSX



30

Borders 8ample FS9

The maps below demonstrate FS' b*ectDetail-a$er:orders in the 9eneAuela – Ou$ana – Suriname – French Ouiana region of South +merica. !ap siAe 4000 L00 6!.

b*ectDetail-a$er:orders 3 04 b*ectDetail-a$er:orders 3 0<

b*ectDetail-a$er:orders 3 0=

FS9FS9

FS9



31

LayerGridLinesFSX Only

-a$erOrid-ines does not appear to be functional.



32

LayerRangeRings FSX Only

-a$erangeings adds range rings at prescribed inter#als centered on the aircraftposition +/-+68 -+T,T2D8 and +/-+68 -6O,T2D8. ange rings should bedispla$ed onl$ when Track2p 3 0 >top of the map is true 6orth? and when Hoom is lessthan 500 km ><J0 6!?.

4a2er3ange3ings /ool0

-a$erangeings controls whether or not the la$er is displa$ed. +n$ number other than0 will displa$ the la$er. + Aero results in no rendering.

8ample &!-

<LayerRangeRings> 1 </LayerRangeRings>

Detail4a2er3ange3ings

Detail-a$erangeings is not functional.

6etDetail4a2er3ange3ings

TetDetail-a$erangeings is not functional. Tet labels of the range) or radius) of thecircle are alwa$s drawn regardless of the #alue for TetDetail-a$erangeings. The tetlabel position) siAe) and units >6!? cannot be changed b$ the user. The label appearsinside the ring) and its position is a function of ring inter#al and Hoom factor. ,t canappear in all four %uadrants.

<e1tDetail4a2er3ange3ings /nmiles enum0

b*ectDetail-a$erangeings is the range increment between rings in 6autical !iles.nl$ integer #alues >enum? are accepted.

The default unit for range rings is 6autical !ile. ,t’s impractical to tr$ to achie#edifferent range ring units such as "! because the tet label alwa$s displa$s 6!E andfractional range #alues are not permitted. 8#en changing the measurement s$stem tometric in ptions G Settings G Oeneral will not change range ring units of 6!.



33

3ange 3ing Center

ange rings are centered on the users aircraft position) A:P4A!8 4A6>67D8 and A:P4A!8 4<!=>67D8) not +O/S /S,T,6 -+T and +O/S /S,T,6 -6 whichma$ be different from +/-+68 -+T,T2D8 and -6O,T2D8) and not CustomDraw-atitude and -ongitude which define the center of the map.

,n a multipla$er +ir Traffic Controller session) Flight Simulator places +/-+68 -+T,T2D8and -6O,T2D8 at the coordinates of the Tower 9iew >the latitude and longitude of theScener$b*ectG within TowerG? found in the airport bgl file.

6ote that the Tower 9iew latitude and longitude are not the same asa$point+irport-atitude and -ongitude. Tower 9iew coordinates are not gps.dll#ariables.

,f the map center is changed using Center& and Center1 or b$ panning with/an(oriAontal and /an9ertical) the range rings will still remain centered on +/-+68

-+T,T2D8 and -6O,T2D8.

Proe1tion Change at +--;--- Meter 3ange

FS& changes map pro*ections at 500)000 meter >Z<J0 6!iles? ange.

From L0 to Q'')''' meters ange) FS& uses a Sinusoidal /ro*ection that is characteriAedb$ e%ual northBsouth and eastBwest map scales at all points on the globe. This $ieldsrange rings that are circular as demonstrated in Figure A on the following page.

+t 500)000U meters ange) FS& uses the 8%uidistant C$lindrical /latte CarrXe pro*ection.,n this pro*ection) the northBsouth and eastBwest map scales are no longer e%ual eceptat the 8%uator and eastBwest map distances are progressi#el$ stretched as latitudeincreases. This results in the map #iew shown in Figure B >look at the width of theState of "ansas) 2S+?. -a$erangeings can onl$ draw circular rings) howe#er) so as aresult) rings drawn when Hoom is 500)000 meters or greater ><J0 6! or greater? areaccurate in the 6orthBSouth direction onl$) but #er$ inaccurate in the 8astBestdirection >Fig. B?. This gets worse as latitudes increase awa$ from the 8%uator.

The elliptical rings in Figure C are accurate) but these had to be drawn using FS& 8llipseb*ects) not -a$erangeings.

-a$erangeings should not be used when Hoom eceeds 500)000 meters >when HoomFactor is <J0 6! or greater?.



34

6ra17p#- onl2

ange rings reflect accurate distance onl$ when Track2p30 and Hoom is less than500km. ange ings are reall$ an +ir Traffic Controller radar gauge feature. +TC radaris normall$ configured with 6orth up >Track2p30?.

Color4a2er3ange3ings

Color-a$erangeings is the color applied to the range rings and associated tet labels.

The default color is a lime green shade

ed 0 Oreen 197 :lue 0 :O (e 0x00C500

ange Hoom Factor 3 <P'.'JLQ 6!Q'')''' !eters

A B

C

ange Hoom Factor 3 <P'.'JL5 6!500)000 !eters

ange Hoom Factor 3 <P'.'JL5 6!500)000 !eters

-a$erangeings alwa$s draws circularrings as shown in Figures A and B.

The rings drawn in Figure B are

inaccurate) howe#er) because of thechange to the Platte Carrée mappro*ection where 6BS and 8B mapscales are no longer e%ual.

The elliptical rings in Figure C areaccurate) but had to be drawn using FS&8llipse b*ects) not -a$erangeings.

Kansas Kansas

Kansas

Map Center Latitude 38.0655°NorthRing Interval 100 NM



100 NM

200 NM

300 NM

300 NM

200 NM

100 NM

100 NM

200 NM

300 NM

RANGE RING

DISTANCE NO LONGER ACCURATE

RANGE ELLIPSEDISTANCE IS ACCURATE

RANGE RINGDISTANCE IS ACCURATE



35

Layerirports

-a$er+irports renders airport s$mbols at the location specified b$a$point+irport-atitude and a$point+irport-ongitude. CustomDraw map replicatesthe s$mbols used on 2S 9F +eronautical Charts as shown below

The t$pe of airport) s$mbol) tet label) and colors can be controlled through specification

of parameters in the -a$er+irports group.

4a2erAirports /ool0

-a$er+irports controls displa$ of the la$er. +n$ number other than 0 will displa$ thela$er. + Aero results in no rendering.

8ample &!-

<LayerAirports> 1 </LayerAirports>

Detail4a2erAirports /integer inde0

Detail-a$er+irports controls the t$pe of s$mbol displa$ed. nl$ one inde #alue can beselected at a time.



36

DetailLayerAirports Index

-1 = Default 1 = Dot 3 = Circle Rwy 5 = Runways

0 = Draw nothing 2 = Circle 4 = Block Rwy

B4 3 Default. Flight Simulator automaticall$ chooses the airport s$mbol t$pedepending on Hoom setting as part of its default deBcluttering scheme

FSX Index Zoom range (m) ZoomFactor range (NM)

Runways 5 80 11,050 0.0432 5.9665

Block Rwy 4 11,051 55,250 5.9671 29.8326

Circle Rwy 3 55,251 110,500 29.8332 59.6652

Circle 2 110,501 552,500 59.6658 298.3261

Dot 1 552,501 2,965,000 298.3267 1600.9719

Nothing 0 2,965,001 5,000,000 1600.9725 2699.7840

0 3 Draw nothing

,nde 4 through 5. The user specifies t$pe of airport s$mbol to displa$

8ample &!-

<DetailLayerAirports> 3 </DetailLayerAirports>

Airport S2mol <rientation

+irport s$mbol inde =) Q) and 5 >Circle w$) :lock w$) and unwa$s? are orientedaccording to magnetic direction of the runwa$>s? as demonstrated abo#e. The 4 screenpiel siAe s$mbol ,nde 4 Dot is not discernable in this screen shot reproduction.



37

6etDetail4a2erAirports /integer inde0

TetDetail-a$er+irports controls the t$pe of tet labeling that is displa$ed. The tetdispla$ is cumulati#e such that ,nde < 3 ,nde 4 plus ,nde <) ,nde = 3 ,nde 4 plus,nde < plus ,nde =) and so forth.

TextDetailLayerAirports Index

-1 = Default 1 = Ident3 = Elevation &

Runway Length

5 = Runway

Numbers

0 = Draw

nothing2 = Name

4 = Control and

Advisory Freq

B4 3 Default. Flight Simulator automaticall$ chooses the airport tet labeldepending on Hoom setting as part of its default deBcluttering scheme. The#alues below represent Aoom ranges within which the corresponding tetinformation is displa$ed. The default is affected also b$ the screen resolution asshown in the FS& eamples. The numbers for one screen resolution comparedto another are proportional) but , don’t understand the details of wh$ the$ aredifferent.

D8FA746 68X6 D>SP4A" .<<M 3A!=8S

FS& 4P00 4<00 FS& 4P00 '00Zoom range (m) ZoomFactor range (NM) Zoom range (m) ZoomFactor range (NM)

Runway Numbers 80 to 4,447 0.043 to 2.401 80 to 3,316 0.043 to 1.790

Frequencies 80 to 10,970 0.043 to 5.923 80 to 8,177 0.043 to 4.415

Elevation & Length 80 to 14,825 0.043 to 8.005 80 to 11,050 0.043 to 5.967

Name 80 to 22,237 0.043 to 12.007 80 to 16,575 0.043 to 8.950

Ident 80 to 148,250 0.043 to 80.049 80 to 110,500 0.043 to 59.665

Nothing 148,251 to 5,000,000 80.049 to 2699.784 110,501 to 5,000,000 59.666 to 2699.784

FSX: Permissible Zoom range for fs9gps:Map is 80 to 5,000,000 meters

FS' 4P00 4<00Zoom range (m) ZoomFactor range (NM)

Runway Numbers 100 to 8,745 0.054 to 4.722

Frequencies 100 to 21,862 0.054 to 11.805

Elevation & Length 100 to 43,725 0.054 to 23.610

Name 100 to 145,750 0.054 to 78.699

Ident 100 to 291,500 0.054 to 157.397

Nothing 291,501 to 5,000,000 157.398 to 2699.784

FS9: Permissible Zoom range for fs9gps:Map is 100 to 5,000,000 meters

0 3 Draw nothing

4 3 ,D86T. The = to Q character a$point+irport,dent of the airport. The SD"refers to this as the ,C+.

< 3 +irport 6ame a$point+irport6ame plus ,dent in parentheses.



38

= 3 < plus airport ele#ation a$point+irport8le#ation and length of the longestrunwa$ a$point+irportunwa$-ength. 8le#ation and length are reported in 2.S.S$stem >ft? or !etric >m? depending upon Flight Simulator Settings >Settings –Oeneral – ,nternational – 2nits of !easure?.

Q 3 = plus Control and +d#isor$ fre%uencies. The control >Control Tower or

CT+F B Common Traffic +d#isor$ Fre%uenc$? and ad#isor$ >+T,S B +utomatedTerminal ,nformation Ser#ice) or +S B +utomated eather bser#ationS$stem? fre%uencies are listed if the$ are a#ailable. ,n the case of multiplecontrol or ad#isor$ fre%uencies a#ailable for an airport) the fre%uenc$ with thelowest a$point+irportFre%uenc$ ,nde is displa$ed.

5 3 Q plus unwa$ numbers displa$ed at the appropriate end of each runwa$.

6etDetail4a2erAirports 8ample

<e1tDetail4a2erAirports /de1imal or heade1imal0

b*ectDetail-a$er+irports controls the t$pes of airports that are displa$ed. + Decimal or(eadecimal number is used that is in the form of a bit table filter similar to filters in6earest searches >reference O/S Ouidebook 6earest,ntersectionCurrentFilter) page P<B

P=?.

Bit !ame Bit !ame Bit !ame Bit !ame

0 Towered < (ard Surface Q ater P /ri#ate4 6ot Towered = Soft Surface 5 (eliport

Combinations of airport t$pes can be selected according to the following rules



39

<e1tDetail4a2erAirports 3ules

4. :it 0 or 4) or both >Towered or 6ot Towered? must alwa$s be selected

<. :it < or =) or both >(ard or Soft Surface? must be selected for -+6D >nonBateror (eliport? airports

+s an eample) if all ater) (ard and Soft Surface) Towered and 6onBTowered airportsare to be displa$ed) then the selection in binar$ number format is

PQ =< 4P L Q < 4 B Decimal e%ui#alent

/ . , 9 + T

8

( 8 - , /

. T

5 + T 8 .

S F T S 2 . F + C 8

( + . D S

2 . F + C 8

6 T T

5 8 . 8 D

T 5 8 .

8 D

P 5 Q = < 4 0 B :it number >:it 0 thru :it P?

- - % % % % % B b*ectDetail-a$er+irports selections

The :inar$ number is 0 0 1 1 1 1 1. The Decimal e%ui#alent is =4 and the

(eadecimal is 4F. The appropriate &!- is therefore either

<ObjectDetailLayerAirports> 31 </ObjectDetailLayerAirports>

or)

<ObjectDetailLayerAirports> 0x1F </ObjectDetailLayerAirports>



40

b*ectDetail-a$er+irports for indi#idual airport t$pes) together with Detail-a$er+irports s$mbol options is shown in the diagram below.

6etColor4a2erAirports /B=3 heade1imal0

TetColor-a$er+irports controls color of the Towered airport tet label. The tet colorfor 2ntowered airports alwa$s matches the airport s$mbol color for 2ntowered airports.This is the same for both FS' and FS&. ,ts format is headecimal :lueBOreenBed.

Default Color

FS9 and FSX: The default TetColor-a$er+irports color is the same as the

airport s$mbol.



41

Color4a2erAirports /B=3 heade1imal0 /FS9 onl20

FS9 <!4": Color-a$er+irports controls color of Towered airport s$mbols onl$. ,t doesnot affect the default magenta color applied to 2ntowered airports. ,ts format isheadecimal edBOreenB:lue and with the he #alues concatenated from right to left >inother words) O:?.

8ample &!-

<ColorLayerAirports> 0xFF9400 </ColorLayerAirports>

FS9: The default color for Towered +irports is a blueBgreen shade

Decimal Hex

Red: 8 08

Green: 132 84

Blue: 173 AD

FS9: The default) and onl$ ) color for 2ntowered airports is a magenta shade

Decimal Hex

Red: 197 C5

Green: 0 00

Blue: 206 CE

Color4a2erAirports6owered /B=3 heade1imal0 /FSX onl20

FSX <!4": Color-a$er+irportsTowered controls color of Towered airport s$mbols. ,tsformat is headecimal edBOreenB:lue and with the he #alues concatenated from rightto left >in other words) O:?.

8ample &!-

<ColorLayerAirportsTowered> 0xFF9400 </ColorLayerAirportsTowered>



42

Default Color

FSX: The default Color-a$er+irportsTowered color is a blueBgreen shade

Decimal Hex

Red: 8 08

Green: 132 84

Blue: 173 AD

Color4a2erAirports7ntowered /B=3 heade1imal0 /FSX onl20

FSX <!4": Color-a$er+irports2ntowered controls color of 2ntowered airport s$mbols.,ts format is headecimal edBOreenB:lue and with the he #alues concatenated from

right to left >in other words) O:?.

8ample &!-

<ColorLayerAirportsUntowered> 0xCE00C5 </ColorLayerAirportsUntowered>

Default Color

FSX: The default Color-a$er+irports2ntowered color is a magenta shade

Decimal Hex

Red: 197 C5

Green: 0 00

Blue: 206 CE



43

Layer!"Rs

-a$er9s draws 9s and associated tet labels at locations defined in the gps.dlldatabase >a$point9or-atitude and a$poin$9or-ongitude?.

4a2erV<3s /ool0

-a$er9s controls whether or not the la$er is displa$ed. +n$ number other than 0 willdispla$ the la$er. + Aero results in no rendering.

8ample &!-

<LayerVors> 1 </LayerVors>

Detail4a2erV<3s /integer inde0

Detail-a$er9s controls the t$pe of 9 s$mbol displa$ed. There is not much of aselection7 it’s either a one piel dot or a 9 s$mbol. The particular s$mbol displa$eddepends upon the t$pe of 9 >a$point9orT$pe? as shown below. +lso for referenceare the e%ui#alent F++ s$mbols.

DetailLayerVors

1 = Dot 2 = Symbol

Detail4a2erV<3s % # Dot ) # S2mol

FS9 G FSX

fs9gps:Map

Wa2pointVor62pe % ) ) , ,

V<3 V<3HDM8 V<3HDM8 DM8 DM8

FAA 6N+

VFR SECTIONA L V FR SECTIONAL VFR SECTIONA L IFR ENROUTE VFR SECTIONA L

V<3 V<3EDM8 V<36AC 6ACA! !DBEDM8



44

The FS& SD" lists categories for the following 9 T$pes

Bit Name and Type # Bit Name and Type #

0 UNKNOWN = 0 4 TACAN = 4

1 VOR = 1 5 VORTAC = 5

2 VOR_DME = 2 6 ILS = 6

3 DME = 3 7 VOT = 7

http://msdn.microsoft.com/en-us/library/cc526954.aspx#VorType

(owe#er) not all categories are populated in the gps.dll database7 onl$ 9 T$pe 4) <)and = are found. The remaining 9 T$pes are grouped in with T$pe < and = 9s orare not founds in the database

T+C+6s >T$pe Q? are included in the T$pe = D!8 categor$

9T+Cs >T$pe 5? are included in the T$pe < 9@D!8 categor$

,-S >T$pe P? belong to the +irport Oroup

9T >T$pe J? are not populated because 9Ts are meaningless in Flightsimulator

Conse%uentl$) when fs'gps!ap displa$s 9s) it can either use a single piel dot) orone of three s$mbols that represent 5 different realBworld 9 t$pes.

The default >no entr$? Detail-a$er9s is <.

6etDetail4a2erV<3s /integer inde0

TetDetail-a$er9s is an integer inde representing the t$pe of tet label to displa$

B4 3 Default

0 3 6othing

4 3 ,dent

< 3 ,dent U Fre%uenc$

= 3 ,dent U Fre%uenc$ U ,dent !orse

The following is an eample of the -imoges 9ND!8) -imoges) France

The default TetDetail-a$er9s) B4 or no entr$) results in a 4 3 ,dent label.

4 < =



45

<e1tDetail4a2erV<3s /de1imal or heade1imal0

b*ectDetail-a$er9s has #er$ little meaning. The SD" indicates that a Decimal or(eadecimal number is used. This is in the form of a bit table filter similar to filters in6earest searches >reference O/S Ouidebook 6earest,ntersectionCurrentFilter) page P<BP=?. ,n this case) howe#er) there is onl$ one #alid selection) 9.

b*ectDetail-a$er9s

:it [ 6ame :it [ 6ame

B4 D8F+2-T 0 D+ 6T(,6O 0 9 4 9T

+lthough this is the simplest possible bit table case) to be thorough) the bit selectionprocess is still demonstrated below. To select 9) choose bit 0 as indicated


9 T

9 .

4 0 B :it number >:it 0 and :it 4?

- % B b*ectDetail-a$er9s selections

The decimal e%ui#alent of binar$ 0 1 is 4) and the headecimal is likewise e%ual to 4.

The &!-

<ObjectDetailLayerVORs> 1 </ObjectDetailLayerVORs>

or)

<ObjectDetailLayerVORs> 0x1 </ObjectDetailLayerVORs>

9T is not a #alid choice principall$ because 9Ts >9 test transmitters? are not foundin the gps database. Furthermore) because the$ are testing facilities for real aircraft

9 recei#ers) the$ are meaningless in Flight Simulator to begin with.

The default) B4 or no entr$) results in 9 selected.

ne other point) the T$pe of 9s displa$ed cannot be filtered inb*ectDetail-a$er9s as can be done in b*ectDetail-a$er+irspaces) for eample.

:ottom line) a Aero and an$ other e#en number) positi#e or negati#e) results in nodispla$. +n$ odd number) positi#e or negati#e) results in a displa$ of the 9 la$er.



46

Color4a2erV<3s /B=3 heade1imal0

Color-a$er9s controls the color of the s$mbol) Detail-a$er9s. The default >no

entr$? color is blue

Decimal Hex

Red: 0 00

Green: 0 00

Blue: 255 FF

6etColor4a2erV<3s /B=3 heade1imal0

TetColor-a$er9s controls the color of the s$mbol) TetDetail-a$er9s. S$nta for

this #ariable is the same as for Color-a$er9s.

,f this #ariable is not included in the script) then the no entr$ default color is the samecolor as the 9 s$mbol.





48

6etDetail4a2er!DBs /integer inde0

TetDetail-a$er6D:s determines which tet label to displa$. The label is displa$ed tothe left of the 6D: s$mbol and cannot be reBpositioned.

TetDetail-a$er6D:s 4) <) and = are independent of Hoom le#el. Tet displa$ed usingTetDetail-a$er6D:s 3 B4 is a function of Hoom) howe#er) as follows

<e1tDetail4a2er!DBs /ool0

b*ectDetail-a$er6D:s is redundant with -a$er6D:s. +n$ number other than 0 willdispla$ the la$er. + Aero results in no rendering. ,f b*ectDetail-a$er6D:s is omitted)

the default is to displa$ the la$er.

B4 or omitted. Default. Tet displa$ed is a function of Hoom

0 3 6o tet drawn

4 3 6D: ,dent onl$

< 3 6D: ,dent U Fre%uenc$ >!(A?

= 3 6D: ,dent U Fre%uenc$ >!(A? U ,dent !orse Code

,dent UFre% U!orse

L0

4Q)L<5

L.0

,dent UFre%

4Q)Lm?

Hoom !a >m?

Hoom !a >6!?

6o Tet-abel

<'P)504

5)000)000

<P''.'

TetDetail-a$er6D:s 3 B4



49

Color4a2er!DBs /B=3 heade1imal0

Color-a$er6D:s controls the color of the 6D: s$mbol and !orse Code. The defaultColor-a$er6D:s is a magenta shade

Decimal Hex

Red: 255 FF

Green: 0 00

Blue: 132 84

6etColor4a2er!DBs /B=3 heade1imal0

TetColor-a$er6D:s controls the color of the ,dent and Fre%uenc$ tet. The default

color is a magenta shade

Decimal Hex

Red: 255 FF

Green: 0 00

Blue: 132 84

!DB Color 8ample

+n eample demonstrating Color-a$er6D:s and TetColor-a$er6D:s

Color-a$er6D:s is 0FF0000 >blue?

TetColor-a$er6D:s is 000FF00 >lime?



50

LayerIL$s

-a$er,-Ss draws ,nstrument -anding S$stem components >localiAer cone or localiAercourse line? for approaches utiliAing a localiAer >-D+) -C) or ,-S approach t$pes?.These correspond to Flight/lan+pproachT$pe 3 40) 44) and 4=. !icrowa#e -anding

S$stem approaches) Flight/lan+pproachT$pe 3 4<) are absent in the stock gps databaseas far as , know) although there is limited !-S deplo$ment in the real world.

FS& offers two ,-S s$mbols >cone and course line? while FS' is limited to cone onl$.

4a2er>4Ss /ool0

-a$er,-Ss controls whether or not the la$er is displa$ed. +n$ number other than 0 willdispla$ the la$er. + Aero results in no rendering.

8ample &!-

<LayerILSs> 1 </LayerILSs>

Detail4a2er>4Ss /ool0

Detail-a$er,-Ss is redundant with -a$er,-Ss. +n$ number other than 0 will displa$ thela$er. + Aero results in no rendering.

6etDetail4a2er>4Ss /enum0

2nfortunatel$) TetDetail-a$er,-Ss is nonBfunctional.

<e1tDetail4a2er>4Ss /enum0

b*ectDetail-a$er,-Ss determines which ,-S s$mbol is used) a localiAer cone or a localiAercourse line.

b*ectDetail-a$er,-Ss 3 B4 or 4. -ocaliAer Cone. This represents the shape of thelocaliAer >horiAontal guidance? beams.

b*ectDetail-a$er,-Ss 3 <. -ocaliAer Course -ine. FS& onl$. +dded as part of the +TC radar feature.

The figures on the following page show FS' and FS& localiAer s$mbols associated with,-S and -C approaches at Cincinatti N 6orthern "entuck$ ,nternational +irport >"C9O?)2S+.



51

4o1alier Cone S2mol Dimensions

-ocaliAer cone width #aries with runwa$ length. ,n Flight Simulator as in the real world)localiAer beams are = to P degrees wide. -ocaliAer antennas are tuned for a beam widthof J00 feet at the landing threshold of the runwa$ the$ ser#e. +ntenna arra$s arepredominantl$ located about 4040 feet or more from the stop end of the runwa$. The4000U ft gap is re%uired to pro#ide a runwa$ safe area for aircraft takeoffs and landingsthat are a little too low. +s far as , know) the stock FS database has accuratecoordinates for localiAer arra$ locations.

,n the eample below) the landing threshold is about 40)000 feet from the antennaarra$) producing a beam angle of Q degrees. The longer the runwa$) the narrower the

beam. Flight Simulator’s localiAer cone s$mbol reflects this width as shown b$ thedifference between the s$mbols for "-2" ,-S w$ <4- >P404 foot runwa$? at Z 5.PI and"C9O ,-S w$ <J >4<)000 foot runwa$? which is Z =I.

-ength of the cone s$mbol drawn in fs'gps!ap is usuall$ around 44)L00 meters.



52

4o1alier Course 4ine S2mol Dimensions

The localiAer course line etends about 4=.5 6!iles outward from the antenna arra$which is roughl$ half of the distance at which the localiAer indicator becomes acti#e inthe aircraft in a straightBin approach.

4o1alier <rientation

8cept for irregular fs'gps database errors) course lines and cone orientation are coBlinear with the runwa$ centerline for ,-S and -C approaches and ha#e an offsetorientation for \ffset’ -C and -D+ approaches which) b$ definition) are at angles tothe runwa$ centerline.



53

Color4a2er>4Ss /B=3 heade1imal0

Color-a$er,-Ss controls color of the ,-S s$mbol. ,f Color-a$er,-Ss is omitted from the&!- script) the default color is lime

Decimal Hex

Red: 0 00

Green: 255 FF

Blue: 0 00

6etColor4a2er>4Ss /B=3 heade1imal0

TetColor-a$er,-Ss is nonBfunctional.



54

LayerIntersections

-a$er,ntersections draws 8nroute and Terminal intersections at locations defined in thea$point,ntersections group.

4a2er>nterse1tions /ool0

-a$er,ntersections controls whether or not the la$er is displa$ed. +n$ number otherthan 0 will displa$ the la$er. + Aero results in no rendering.

8ample &!-

<LayerIntersections> 1 </LayerIntersections>

Detail4a2er>nterse1tions /enum0

Detail-a$er,ntersections controls the st$le of intersection s$mbol) either a single pieldot or a triangle.

Detail-a$er,ntersections 3 B4 or omitted. Triangle

Detail-a$er,ntersections 3 0. Draw nothing

Detail-a$er,ntersections 3 4. Single piel dot

Detail-a$er,ntersections 3 +n$ number other than 0 or 4. Triangle

6etDetail4a2er>nterse1tions /ool0

TetDetail-a$er,ntersections controls the displa$ of the intersection ,dent. The tet ispositioned to the right of the intersection s$mbol at about the Q o’clock position andcannot be mo#ed. +n$ number other than Aero will displa$ the ,dent7 Aero will hide,dent.

Detail-a$er,ntersections 4 B4 or <





56



57

Additional points

Figure A shows intersections displa$ed b$ -a$er,ntersections in the #icinit$ of +chorage) +laska) 2S+.

8nroute intersections are colored the default magenta . These areintersections used for crossBcountr$ na#igation purposes and are often part of

9ictor and ;et +irwa$ routes. 8nroute wa$points often ser#e as approachtransition wa$points.

Terminal wa$points are displa$ed in green in this eample. Theseintersections are used b$ Terminal and approach procedures into and out ofairports.

Figure B shows the flight path for the ,-S w$ 4Q +pproach) ,9+66 Transition into +nchorage ,nternational +irport >/+6C?.

The ,dent tet color of terminal wa$points used b$ the approach >F-+6D) 1(66) C(+9,) C+DD) "+6S"1? is the same color >black in this eample? asthe approach flight path. Color-a$erFlight/lan color selections o#erride-a$er,ntersections color selections in displa$ of Flight /lan and +pproachelements) and the s$mbol color of terminal wa$points included in the approachre#ert to the default blue color.

The ,C+ of terminal intersections contains the ,dent of the owning airportE in,C+ character positions Q through J. ,n this eample) /+6C. The ,C+ ofenroute intersections does not contain the ,dent of an owning airportE >e.g.),9+66?.

+pproach a$point ,nde P is a unwa$ a$point used b$ Flight Simulator to

define the runwa$ location. +ll approaches include such a wa$point. ,t isdispla$ed when -a$erFlight/lan is enabled and an approach is loaded) but absentotherwise.





59

+,S/+C8 6+!8 T1/8 C26T D+6 +,S/+C8 6+!8 T1/8 C26T D+6

C86T8 4 Q4'P APPROACH 13 0

C-+SS@+ < =0J M<A %I K),

C4ASSHB , +*I 38S63>C68D %+ ,)@+

C4ASSHC I %K@* P3<5>B>68D %K @,,

C4ASSHD + )+*, WA3!>!= %* ,9% C4ASSH8 K %9)K A4836 %@ I+

C-+SS@F J ' DA!=83 %9 ))%%

C-+SS@O L JQ NATIONAL_PARK 20 0

TOWER 9 0 MODE_C 21 0

CLEARANCE 10 0 RADAR 22 0

GROUND 11 0 T+,6,6O <= 5<J

DEPARTURE 12 0 Total 4')<P4

Airspa1e Definitions

Flight Simulator incorporates airspace boundaries defined b$ the air traffic authorities of#arious countries around the world. !ost countries adopt the 4''0 ,C+ +irspaceclassification for the type of air traffic control) that is) the flight rules >,F) S9F) or 9F)

+TC communication) speed) and separation protocol? applied within each airspace class)howe#er) countr$Bb$Bcountr$ adaptation and boundar$ definitions for the airspaceclasses #ar$ widel$. Countries are free to select and appl$ onl$ those +irspace Classesthat are suitable to their needs and to de#elop their own chart s$mbol st$les as well.

+s an eample) some countries do not use Class B airspace. thers designate a blanketla$er between certain altitudes >therefore lacking geographic boundaries that can be

drawn on a map? as Class B) and $et others appl$ Class B to familiar \upside downwedding cake’ boundaries that are easil$ drawn on a map.

Flight Simulator’s line st$les and colors for each Class are consistent across all countries)but in the real world the$ are not.

Center Airspa1e

Center >+irspace T$pe 4? is not an +irspace) per se. Center airspace boundariesrepresent the areas of responsibilit$ of indi#idual enroute air traffic control centers >+iroute Traffic Control Centers B +TCCs in the 2S) +rea Control Centers in 8urope?. The

boundaries of Centers determine where the Flight Simulator +TC function handsBoffaircraft to the subse%uent Center. ,n FS) onl$ Center airspaces ha#e a fre%uenc$ and afre%uenc$ name) 6earest+irspaceCurrentFre%uenc$ and CurrentFre%uenc$6ame. TheCurrentFre%uenc$6ame is alwa$s CenterE. Center altitude boundaries are defined as6earest+irspaceCurrent!in+ltitude 3 0 >surface? and Current!a+ltitude 3 400000meters) or edge of space. Center +irspace boundaries are not drawn b$ -a$er+irspacesnor found on 2S Sectional >9F? charts which are the basis for the -a$er+irspaces format.



60

Air 6raffi1 ControlEBased Airspa1e Classes

+TCBbased +irspace Classes include Class A through Class =. These correspond toFlight Simulator +irspace T$pes < – L >6earest+irspaceCurrentT$pe?. The first fi#e)Classes A through 8) are Controlled +irspaces) and where geographic boundaries forthese airspaces eist in the database) Flight Simulator draws them.

(owe#er) geographic boundaries that can be drawn on a map do not alwa$s eist in FSor the real world. Class A +irspace is not used b$ all countries) but where it is used)such as in the 2nited States and ussia) it is a blanket airspace defined b$ altitude limitsbut not geographic boundaries. Conse%uentl$) Class A +irspaces cannot be drawn b$-a$er+irspaces e#en though Class A airspaces are found in the database.

+dditionall$) 2S Class 8 +irspace generall$ eists e#er$where below 4L)000 ft there isnot alread$ Class A) B) C) or D or = +irspace) and e#er$where abo#e F-P0.

8#er$whereE lacks boundaries that can be drawn) so instead) FS draws Class 8 boundaries onl$ where the$ etend to the ground surface.

Class F and = are 6onBControlled +irspaces and are not drawn in Flight Simulator.

Spe1ial 7se Airspa1es

Special 2se +irspace’s >S2+? purpose is to ad#ise pilots of acti#ities or areas that ha#especial flight rules or ma$ be haAardous at certain times. Se#en S2+ t$pes are found inthe gps database and si of these are drawn b$ -a$er+irspaces.

SUA Name

FS

Airspace

Type

FS

Drawn?

Controlled

Airspace?

MOA 14 Yes NoMilitary. USA. Purpose is to separate high-speed military

traffic from IFR traffic. VFR also permitted but with caution

RESTRICTED 15 Yes Yes

Not prohibited to fly, but unauthorized penetration not allowed

and possibly dangerous at certain times (eg, live military firing,

bombing ranges in US)

PROHIBITED 16 Yes No* Flight of aircraft is not permitted

WARNING 17 Yes NoAdvisory in nature. Airspace over domestic or international

waters that extends from three NM beyond shore

ALERT 18 Yes No

Training Area: US. No restrictions but use caution. Alert

areas may contain a high volume of pilot training or unusualactivity. All but 2 Alert areas are in US. Other 2 are in S Korea

DANGER 19 Yes No

Military usually. Non-US. Unauthorized penetration not

allowed and possibly dangerous at certain times. Most are

military operations areas (high speed a/c, live firing, etc)

TRAINING 23 No No Training Area: Non-US.



61

4a2erAirspa1es 4ine Format

-a$er+irspaces adopts the 2.S. F.+.+. Sectional Chart >9F? airspace s$mbol format.

+ comparison of ,C+ >most of the nonB2S world?) 2S F.+.+. Sectional) and FlightSimulator airspace boundar$ st$les is shown below. Some points

The basis for -a$er+irspaces line st$les is the 2S F.+.+. 9F Sectional Chart) not(igh and -ow +ltitude 8nroute charts which use different airspace s$mbol sets

2S F.+.+. Sectional charts depict Class 8 Surface) J00N4<00 foot +O- Transition)8 at =surface) and (igh +ltitude !S- >Aipper line? +reas. ithin 2S +irspace)-a$er+irspaces draws onl$ the Class 8 Surface +irspace at ground surface

F++ Sectionals use a magenta color for +-8T S2+ whereas FS uses blue

-a$er+irspaces pro#ides no tet labeling of airspace name or altitude limits

-a$er+irspaces applies 2S F++ Sectional format worldBwide) e#en in countries

that use ,C+ Standard s$mbol format or their own airspace boundar$ format The FS airspace database is not current. egular updates occur in the real world

ICAOAnnex 4 July 2009

FF

BB

CC

DD

EEE

AA

GG

PROHIBITEDRESTRICTED

WARNING

PROHIBITEDRESTRICTED

WARNING

MOAALERTMOA

ALERT

PROHIBITED

RESTRICTEDDANGER

PROHIBITED

RESTRICTEDDANGER

15- RESTRICTED16- PROHIBITED17- WARNING18- ALERT

19- DANGER

14- MOA

A

B

C

D

E

F

G

B

C

D

E

E

E

SUA SUA

US FAA VFRJanuary 2012

FS9 & FSXLayerAirspaces

E: Transition: Flr 700 ft AGL

E: Flr 1200+ ft AGL @ G:surface

3- B

4- C

5- D

6- EE: At Surface

E: High Alt (zipper line)E

No equivalent symbol in FS







62

-ine widths and colors >essentiall$? cannot be changed in -a$er+irspaces. +dditionall$)line widths are constant and are not scaled according to Hoom.

8amples of 4a2erAirspa1es in FSX

These figures show airspace below4Q)500’ !S- down to the base of Class 8

or Class = and points out differencesbetween FS and real charts. (owe#er)the lack of Class 8 detail has littlesignificance in FS e#en in multipla$ercontroller simulations.



63



64

Color4a2erAirspa1es /B=3 heade1imal0

Color-a$er+irspaces is not reall$ functional the wa$ one would epect. +lthough

Color-a$er+irspaces can be specified) it is applied to all airspace t$pes) and mostimportantl$) it has the effect of onl$ dulling) or dimming the default color onl$) but notchanging it to the specified color. Furthermore) all color choices for Color-a$er+irspacesdarken the default color) ne#er lighten) or brighten it.

mitting Color-a$er+irspaces or using it with -FFFFFF results in the default color)entering ------- produces black airspace boundar$ lines.

6etColor4a2erAirspa1es

TetColor-a$er+irspaces is not functional. ;ust as there is no TetDetail-a$er+irspaces)there is no color choice either.



65

Layer%lig&tPlan

-a$erFlight/lan draws a wa$pointBtoBwa$point path of the loaded Flight /lan. +pproachprocedures are also drawn after an +pproach has been loaded >the +pproach becomespart of the Flight /lan at that point?.

4a2erFlightPlan /ool0

-a$erFlight/lan controls whether or not the la$er is displa$ed. +n$ number other than 0will displa$ the la$er. + Aero results in no rendering.

8ample &!-

<LayerFlightPlan> 1 </LayerFlightPlan>

Detail4a2erFlightPlan /enum0

Detail-a$erFlight/lan determines the line st$le of the !issed +pproach path.

E% 3 Default. Dashed -ines for !issed +pproach >includes (olding /attern?.Solid lines for 8nroute and +pproach flight plan segments. nl$ !issed

+pproach and (olding /attern can be dashed lines.

- 3 Draw 6othing

%3 +ll Solid lines for !issed +pproach >includes (olding /attern?) 8nroute ) and +pproach flight plan segments

) 3 Same as Default. Dashed -ines for !issed +pproach >includes (oldingpattern?. Solid lines for 8nroute and +pproach flight plan segments



66

6etDetail4a2erFlightPlan /enum0

TetDetail-a$erFlight/lan is nonBfunctional.

<e1tDetail4a2erFlightPlan /de1imal or heade1imal0

b*ectDetail-a$erFlight/lan controls which Flight /lan and +pproach segments aredrawn. ,t is best thought of as a binar$ number that represents the choices asdemonstrated below.

L Q < 4 B Decimal e%ui#alent

5

+ 1 / , 6 T S

!

, S S 8 D

+

/ / . + C (

+

/ / . + C (

8 6 . 2 T 8

= < 4 0 B :it number >:it 0 thru :it =?

Fig' A - - - % B b*ectDetail-a$erFlight/lan selections

Fig' B - - % % B b*ectDetail-a$erFlight/lan selections

Fig' C - % % % B b*ectDetail-a$erFlight/lan selections

Fig' D % % % % B b*ectDetail-a$erFlight/lan selections

+s an eample) if the user wants to draw the 8nroute Flight /lan and +pproach/rocedure >Figure B?) the appropriate selection is bit 0 and bit 4. The resulting binar$



67

number is - - % % whose decimal e%ui#alent is =. The headecimal e%ui#alent islikewise =.

8ample &!-

<ObjectDetailLayerFlightPlan> 3 </ObjectDetailLayerFlightPlan>

or)

<ObjectDetailLayerFlightPlan> 0x3 </ObjectDetailLayerFlightPlan>

The !issed +pproach and (olding pattern is added in Figure C) and a$pointdesignations are added in Figure D.

Selecting a$points adds the wa$point’s >9F? +eronautical Chart s$mbol and thewa$point ,dent tet label to the right of the s$mbol. The tet cannot be reBpositioned.

There is no Hoom limit on the Flight /lan displa$ – it is drawn at all Hoom le#els) L0 to5)000)000 meters for FS&) 400 to 5)000)000 meters for FS'.

Color4a2erFlightPlan /B=3 heade1imal0

Color-a$erFlight/lan controls color of the nonB+cti#e Flight /lan leg. ,fb*ectDetail-a$erFlight/lan a$points bit is set) then Color-a$erFlight/lan also controlsthe color of the a$point ,dent tet. ,ts format is headecimal :lueBOreenBed.



68

,f Color-a$erFlight/lan is omitted from the &!- script) the default color is a #er$ paleblue shade which is suitable when terrain is showing

ed 215 Oreen 255 :lue 255 :O (e 0xFFFFD7

The stock [email protected] gauge uses a conditional statement within Color-a$erFlight/lanthat sets the color to a medium gra$) 0L0L0L0) when no terrain background is showing)and white when it is.

6etColor4a2erFlightPlan /B=3 heade1imal0

TetColor-a$erFlight/lan is nonBfunctional.

FlightPlan4ineWidth /numer0

Flight/lan-ineidth controls the width of the Flight /lan line. ,t is approimatel$ e%ualto screen piel width rendered but can #ar$ according to screen resolution and gaugeconfiguration settings as demonstrated in the chart below. ,f Flight/lan-ineidth isomitted from the &!- script or set e%ual to Aero) a 4 screen piel width line is drawn.



69

A1ti?eColor4a2erFlightPlan /B=3 heade1imal0

+cti#eColor-a$erFlight/lan is the color of the acti#e Flight /lan or +pproach segment.The default color if +cti#eColor-a$erFlight/lan is omitted from the &!- script is amagenta shade

ed 255 Oreen 49 :lue 255 :O (e 0xFF31FF

,f b*ectDetail-a$erFlight/lan a$points bit is set) then +cti#eColor-a$erFlight/lan alsocontrols the color of the acti#e wa$point ,dent tet. +cti#eColor-a$erFlight/lano#errides Color-a$erFlight/lan for the acti#e segment.

PastColor4a2erFlightPlan /B=3 heade1imal0

/astColor-a$erFlight/lan is the color of all past) or completed) Flight /lan segments. +sshown below) /astColor-a$erFlight/lan also controls the color of past wa$points ,denttet.



70

Layerpproac&

-a$er+pproach draws a map of approach procedures identified b$ a$point+irport,C+)a$point+irportCurrent+pproach and a$point+irportCurrentTransition selections. Thisla$er is limited to the approach procedure and does not include an$ of the enroute flight

plan legs.

The screen capture on the right showsthe FS' and FS& Oarmin O/S 500/rocedures /age after ",CT ,-S 4'

+pproach) ,CT Transition has beenselected. The insert map that displa$sthis approach procedure uses#ariables of the -a$er+pproach group.,n the stock gps@500 gauge) it is setup as a separate CustomDraw element

>refer to lines <J<0 through <J54 ofthe FS& [email protected]?7 it’s not part ofthe main CustomDraw fs'gps!apelement >lines J5P through JL= of theFS& [email protected]?.

+fter an approach has been loaded) it becomes part of the flight plan and will berendered in the main map as part of the -a$erFlight/lan group.

4a2erApproa1h /ool0

-a$er+pproach controls whether or not the la$er is displa$ed. +n$ number other than 0will displa$ the la$er. + Aero results in no rendering.

8ample &!-

<LayerApproach> 1 </LayerApproach>

Detail4a2erApproa1h /de1imal or heade1imal0

Detail-a$er+pproach controls the approach segments that are displa$ed. + Decimal or(eadecimal number is used that is in the form of a bit table filter similar to filters in

6earest searches >reference O/S Ouidebook 6earest,ntersectionCurrentFilter) page P<BP=?.

Bit # Name Bit # Name Bit # Name

0 Approach 1 Missed 2 Arrow Head



71

+s an eample) to draw the approach and missed approach segments) bits 0 and 4 areselected

Q < 4 B Decimal e%ui#alent

+ . . 5

( 8 + D

! , S S 8 D

+ / / .

+ C (

< 4 0 B :it number >:it 0 thru :it <?

- % % B Detail-a$er+pproach selections

The decimal e%ui#alent of binar$ - % % is =. The headecimal #alue is likewise =. The&!- instruction is

<DetailLayerApproach> 3 </DetailLayerApproach> or

<DetailLayerApproach> 0x3 </DetailLayerApproach>

The default Detail-a$er+pproach #alue is J) or 0J.

",CT ,-S 4' +pproach) ,CT Transition

Binary: 0 0 1; Hex: 0x1


Approach

Approachw/ Arrows



Missed

Missedw/ Arrows



Approach &Missed

Approach &Missedw/ Arrows



72

6etDetail4a2erApproa1h /enum0

2se of TetDetail-a$er+pproach has no effect in either FS' or FS&. There is no tetlabel associated with -a$er+pproach.

<e1tDetail4a2erApproa1h /ool0

+n$ number other than 0 will displa$ the approach segments selected b$Detail-a$er+pproach. + Aero results in no rendering of the approach segments. Thishas the same effect as Detail-a$er+pproach 3 0) and as such is of little use.

Color4a2erApproa1h /B=3 heade1imal0

2se of Color-a$er+pproach crashes the approach map in both FS' and FS&. This#ariable should not be used.

6etColor4a2erApproa1h /B=3 heade1imal0

2se of TetColor-a$er+pproach has no effect in either FS' or FS&. There is no tet labelassociated with -a$er+pproach.

4a2erApproa1hAirport /string0

-a$er+pproach+irport is the fs'gps ,C+ identit$ of the approach airport. ,t is the full

,C+) not the ,dent. 8%ui#alent to a$point+irport,C+.

4a2erApproa1hAproa1h /enum0

-a$er+pproach+irport is the inde pointer for the airport approach list. 8%ui#alent toa$point+irportCurrent+pproach. This inde pointer is used to select a specificapproach procedure to displa$.

4a2erApproa1h6ransition /enum0

-a$er+pproachTransition is the inde pointer for the approach transitions list. 8%ui#alentto a$point+irportCurrentTransition. This inde pointer is used to select a specificapproach transition to displa$.



73

4a2erApproa1h4eg /enum0

-a$er+pproach-eg is an inde pointer to the approach and missed approach segments.,t is e%ui#alent to Flight/lana$point+pproach,nde. The starting number for thisparticular inde is 4) not 0. Flight Simulator approach segments correspond to standardapproach nomenclature

4a2erApproa1h4eg

FS9

FSX Appr' Segment

FS9

FSX Appr' Segment

FS9

FSX Appr' Segment

FS9

FSX Appr' Segment

4 +pproach

Transition=

,ntermediate

+pproach5 Final +pproach J

!issed +pproach

Turn to (olding

< ,nitial +pproach Q,ntermediate

+pproachP

!issed +pproach

ClimbL (olding /attern

The default -a$er+pproach-eg #alue is 0) which will result in no leg being selected.

4a2erApproa1hAir1raftSpeed /numer; nots0

+n aircraft’s approach groundspeed affects the length of se#eral approach segmentsdepicted on the approach map. ,n the eample that follows) the length of the outboundleg of the ,nitial +pproach) entr$ into the Q5I /rocedure Turn >/T?) and length of the(olding /attern legs are all a functions of groundspeed and are rendered according to-a$er+pproach+ircraftSpeed. -a$er+pproach assumptions include

+ two minute Q5I straight segment prior to initiating the 4L0I turn. Thestandard for this timed subBsegment) howe#er) is 4 minute for Categor$ + and :

aircraft and 4.<5 min for Categor$ C) D) and 8) so Flight Simulator’s choice is abit ecessi#e.

Two minute legs in the (olding /attern

9ariable length outbound ,nitial +pproach leg segment. This leg must beshortened as speed increases in order complete the /T within the 45 6!manue#ering limit from the /T Fi >(98 intersection?. Flight Simulator comesclose) but does not %uite accomplish this. Distances of 4J.0) 4J.5 and 4L.= 6!for -a$er+pproach+ircraftSpeed 400) 450 and <00 knots are rendered. Theeagerated duration of the Q5I straight segment has a lot to do with this.

The default -a$er+pproach+ircraftSpeed is 4.= times Flaps@2p@Stall@Speed

found in the aircraft.cfg file. 4.= times Full@Flaps@Stall@Speed might ha#e been amore logical choice because reference approach speed is defined as 4.= 9so.





75

4a2erApproa1h4ineColor /B=3 heade1imal0

2se of -a$er+pproach-ineColor crashes the approach map in both FS' and FS&. This#ariable should not be used.

4a2erApproa1h4ineWidth /enum s1reen piels0

Screen piel line width of the approach and missed approach segments. The default is 4piel.

<ther 4a2erApproa1h <ser?ations

To replicate the approach select function of the O/S 500 gauge) the +pproach la$ershould be set up as a separate CustomDraw element apart from the main map. +ll#ariables needed to render a map such as :ackgroundColor) Hoom) -atitude and

-ongitude as well as other desired la$ers like 9s and 6D:s need to be included in thiselement.

There are a few uni%ue considerations for the +pproach map

:ackgroundColor must be dark. ther than -a$er+pproach-ine+cti#eColor)-a$er+pproach renders approach segments in a nearBwhite color onl$ >O: <QJ)<QJ) <QJ7 0FJFJFJ?. +lthough -a$er+pproach-ineColor seems to be the logicalcolor choice for the rest of the segments) its use crashes the map. (Note: Colorsof the approach maps in this section were edited to eliminate dark print images)

-atitude and -ongitude should be set appropriate for the approach rather than

the usual aircraft latNlon. The stock [email protected] pro#ides a good eample)a$point+irport+pproachTransition-atitude and -ongitude.

-a$erangeings should not be used because range rings are alwa$s centeredaround the user aircraft position >+/-+68 -+T,T2D8) radians? and >+/-+68-6O,T2D8) radians?) not +pproachTransition-atitude and -ongitude.

Track2p should be set to 0) that is) to 6orth.



76

Layer!e&icles FSX Only

-a$er9ehicles draws 2ser) +, and !ultipla$er onBground and airborne aircraft traffictargets. ,ts primar$ function is to replicate an +ir Traffic Control radar screen for usewith the Flight Simulator Tower feature a#ailable in FS& Delue.

,n -a$er9ehicles) \#ehicles’ means aircraft) not ground #ehicles like trucks or leisureboats) although it may be possible that -a$er9ehicles can draw commercial boat >Shipsand Ferries? targets7 the SD" indicates that 6raffi1 6ools can #iew and customiAe +,>artificial intelligenceE or computerBcontrolled? aircraft and Ships and Ferries boat traffic.:ut) , ha#e no knowledge about a connection between Traffic Tools and -a$er9ehicles nor ha#e , seen a Ship or Ferr$ boat target e#er painted b$ -a$er9ehicles.

+ re#iew of -a$er9ehicles itself is reasonabl$ simple and straightforward. The related,Traffic,nfo group) on the other hand) is of greater interest and pro#ides much more

insight into what can be done with traffic information.

4a2erVehi1les /ool0

-a$er#ehicles controls displa$ of the la$er. +n$ number other than 0 will displa$ thela$er. + Aero results in no rendering.

8ample &!-

<LayerVehicles> 1 </LayerVehicles>

Detail4a2erVehi1les /enum0

Detail-a$er9ehicles determines the st$le of aircraft s$mbol displa$ed.

% # A6C S2mol' Color can be changed

) # 6CAS S2mol' 6o color choice with thiss$mbol. +lwa$s a white diamond with black fill

, # 3ealisti1 S2mol' :ut not too realisticlooking. Color can be changed

E% # Default' 6o s$mbol is drawn

- # Draw !othing' 6o s$mbol is drawn



77

The figures below demonstrate Detail-a$er9ehicles st$les when displa$ed on the map.

+ few obser#ations

Figure A' Detail-a$er9ehicles 3 4. + good choice as it produces the cleanest

looking displa$. +lthough the Selected aircraft s$mbol in the lower left corner iscolored oli#e green >Color-a$er9ehiclesSelected?) the label color of the Selectedaircraft is alwa$s red. SiAe of the aircraft s$mbol cannot be changed.

Detail-a$er9ehicles 3 4 includes a (istor$ Trail as shown below. 8#er$ fewseconds) the aircraft lea#es \breadcrumbs’ showing where it has been.

(istor$ Trail is part of Detail-a$er9ehicles 3 4 and cannot be turned off.

Figure B' Detail-a$er9ehicles 3 <. +lwa$s a white diamond with black fill. Thiss$mbol appears best on a dark background. 6o (istor$ Trail) but Track -ine canbe displa$ed for this s$mbol. SiAe of the aircraft s$mbol cannot be changed.

Figure C' Detail-a$er9ehicles 3 =. Can produce a congested looking displa$.The color of the Selected aircraft remains the same color as the rest of theaircraft. 6o (istor$ Trail. SiAe of the aircraft s$mbol cannot be changed.

,f Detail-a$er9ehicles is not included in the &!- code) no aircraft s$mbol will be drawn.

(istor$ Trail (istor$ Trail

DetailLayerVehicles = 1 DetailLayerVehicles = 2 DetailLayerVehicles = 3

A B C



78

6etDetail4a2erVehi1les /enum0

TetDetail-a$er9ehicles controls the format of aircraft flight status information displa$edin the tet label for each aircraft.

% # 3ealisti1' Fi#e items of information are

displa$ed on two lines of tet that alternate backand forth about e#er$ two seconds.

) # Detailed' Fi#e items of information aredispla$ed on fi#e lines.

E% # Default' 6o tet label is drawn

- # Draw !othing' 6o tet label is drawn

Draw nothing

Draw nothing

The flight status information consists of

%' Air1raft Call Sign' ,n this eample) 6<PJL]

)' Air1raft Model' For eample) -;Q5

,' Destination Airport' This is the ,dent of the destination wa$point of the +, or!ultipla$er aircraft. ,n this eample) /+O) rangell +irport) rangell +laska.

I' Altitude' ,n ealistic Format) it is +ltitude >!S-? in 400s of feet. ,n thiseample) =4' 3 =4)'00 feet. utput is in 2S B ,mperial units >feet) knots? e#enif simulation settings are metric. ,n real life) this is the !ode C standardpressure altitude reported in hundreds of feet b$ the aircraft transponder.

+' 6rue Airspeed' ,n ealistic Format) True +irspeed is represented in 40s ofknots. ,n this eample) QQ 3 QQ0 knots. utput is in 2S B ,mperial units e#en ifthe sim settings are metric. ,n real life) this is =roundspeed of course. h$does FS use True +irspeed when ,Traffic,nfo can access +O26D 98-C,T1

,f TetDetail-a$er9ehicles is not included in the &!- code) no tet label will be drawn.

<e1tDetail4a2erVehi1les /de1imal or heade1imal0

b*ectDetail-a$er9ehicles controls what is drawn. 2suall$) this is +irborne’ and \Oround’#ehicles >aircraft on the ground?) and the bit selection is





80

Color4a2erVehi1les /B=3 heade1imal0

Color-a$er9ehicles controls color of the +TCE and ealisticE aircraft s$mbol>Detail-a$er9ehicles 4 and =?. ,ts format is headecimal edBOreenB:lue.

,n the e#ent that Color-a$er9ehicles is not included the &!- script) the default color is$ellow

ed 247 Oreen 247 :lue 0 :O (e 0x00F7F7

Color4a2erVehi1lesSele1ted /B=3 heade1imal0

Color-a$er9ehiclesSelected controls color of the Selected #ehicle. This applies onl$ tothe +TCE aircraft s$mbol >Detail-a$er9ehicles 4?. The TC+SE and ealisticE s$mbolsdo not change color if Selected. ,ts format is headecimal edBOreenB:lue.

,n the e#ent that Color-a$er9ehiclesSelected is not included the &!- script) the default

color is $ellow

ed 247 Oreen 247 :lue 0 :O (e 0x00F7F7

6etColor4a2erVehi1les /B=3 heade1imal0

TetColor-a$er9ehicles controls the color of the tet label for all three aircraft s$mbolt$pes. +pplies to nonBSelected aircraft onl$. ,ts format is headecimal edBOreenB:lue.

,n the e#ent that TetColor-a$er9ehicles is not included the &!- script) the default coloris magenta

ed 255 Oreen 0 :lue 255 :O (e 0xFF00FF

The tet color of the Selected aircraft label is alwa$s red) regardless of the color of the

Selected aircraft s$mbol itself.



81

Layerirways FSX Only

-a$er+irwa$s draws -ow +ltitude 9ictor and (igh +ltitude ;et +irwa$ centerlines.

4a2erAirwa2s /ool0

-a$er+irwa$s controls whether or not the la$er is displa$ed. +n$ number other than 0will displa$ the la$er. + Aero results in no rendering.

8ample &!-

<LayerAirways> 1 </LayerAirways>

Detail4a2erAirwa2s /enum0

Detail-a$er+irwa$s controls the line thickness.

Detail-a$er+irwa$s 3 B4. Default. + 4 screen piel wide line is drawn

Detail-a$er+irwa$s 3 0. 6othing is drawn

Detail-a$er+irwa$s 3 4. Thin -ines. + 4 screen piel wide line is drawn

Detail-a$er+irwa$s 3 <. Thick -ines. + = screen piel wide line is drawn

6etDetail4a2erAirwa2s /ool0

TetDetail-a$er+irwa$s controls labeling of the +irwa$ name. +n$ number other than 0will displa$ the name. +irwa$ names are often) but not alwa$s) placed between enroute

intersections that define airwa$ segments.

9,CT +,+1ST+--+ 9BD!8 >T-+?Olasgow) Scotland 2" ange 4< 6!



82

<e1tDetail4a2erAirwa2s /enum0

b*ectDetail-a$er+irwa$s determines whether 9ictor +irwa$s) ;et +irwa$s) or both aredispla$ed.

b*ectDetail-a$er+irwa$s 3 B4 or omitted. Default. :oth 9ictor and ;et

b*ectDetail-a$er+irwa$s 3 0. 6othing displa$ed

b*ectDetail-a$er+irwa$s 3 4. 9ictor +irwa$s displa$ed

b*ectDetail-a$er+irwa$s 3 <. ;et +irwa$s displa$ed

b*ectDetail-a$er+irwa$s 3 =. :oth 9ictor and ;et displa$ed

Color4a2erAirwa2sVi1tor /B=3 heade1imal0

Color-a$er+irwa$s9ictor is a :O (e number representing the color of 9ictor +irwa$s.

,f Color-a$er+irwa$s9ictor is omitted) the default color is a light blue shade

ed 140 Oreen 181 :lue 214 :O (e 0xD6B58C

Color4a2erAirwa2set /B=3 heade1imal0

Color-a$er+irwa$s;et is a :O (e number representing the color of 9ictor +irwa$s. ,f Color-a$er+irwa$s;et is omitted) the default color is a light magenta shade

ed 222 Oreen 164 :lue 222 :O (e 0xDEA4DE

6etColor4a2erAirwa2s /B=3 heade1imal0

TetColor-a$er+irwa$s is a :O (e number representing the color of the name label of 9ictor +irwa$s onl$. ,t is not applied to ;et +irwa$s. ,f TetColor-a$er+irwa$s isomitted) the default color is a c$an shade

ed 0 Oreen 255 :lue 255 :O (e 0xFFFF00



83

The default) and onl$ color a#ailable for the name label of ;et +irwa$s is a purple shade

ed 148 Oreen 90 :lue 148 :O (e 0x945A94



84

LayerRacePoints FSX Only

+s of the release date of this Ouidebook >;anuar$) <04=?) , ha#e not taken the time to

stud$ this la$er.

+ future update to the guidebook ma$ contain a discussion of this la$er.



85

CustomDraw' Rose

CustomDraw ose is a separate class that renders a compass rose o#erla$ for the

CustomDraw map. ,ts &!- must be placed below the map code in order to displa$ ontop of the map.

The start tag is similar to fs'gpsmap) as follows

<Element Name=”Compass Rose”><Position X="150" Y="10"/><CustomDraw Name="fs9gps:rose" X="500" Y="400" Bright="Yes">

/osition) & and 1 are normall$ the same as used for fs'gpsmap.

5eading /radians0

(eading is the direction to which the top of the rose points. , prefer

<Heading>(L:TrackUp, bool) 0 ==

if{ 0 }els{ (A:GPS GROUND MAGNETIC TRACK, radians) }

</Heading>

CenterX Center" /gauge units0

Center of the compass) normall$ the user’s aircraft position.

3adius /gauge units0

adius of the compass measured in gauge units along the short ais.

Color /B=3 heade1imal0

-ine color of the rose) tick marks) and degrees labels.

Ba1groundColor /B=3 heade1imal0

:ackground color of the degrees markings.



86

4ineWidth /s1reen piels0

-ine width of the rose) in screen piels.

Font /string0

Font used for the degrees markings) for eample) +rial.

FontSie /integer0

Font siAe of the degrees markings.

BigFontSie /integer0

SiAe of the 6E) SE) 8E) E labels in the -abel+llTicks30 case.

FullCir1le /ool0 FSX <nl2

FullCircle34 for a complete circle rose. FullCircle30 for a half rose.

4aelAll6i1s /ool0 FSX <nl2

-abel+llTicks 3 4 Ticks are drawn and annotated e#er$ 40 degrees.

-abel+llTicks 3 0 Ticks are drawn e#er$ 40 degrees but annotated e#er$ =0 degrees.

+dditionall$) the cardinal directions) 6E) SE) 8E) and E) are displa$ed using:igFontSiAe.

For1e,Digits /ool0 FSX <nl2

Three digits are used to annotate degrees. For eample) P0 degrees is displa$ed as 0P0.See diagram below.



87



88

ITra((icIn(o' #earest Tra((ic Group FSX Only

,Traffic,nfo is a 6earest search group analogous to other fs'gps 6earest groups such as6earest+irport. ,t returns +, or multipla$er aircraft traffic nearest the search origin thatis normall$ defined as the user’s aircraft or control tower position. ,t sorts data b$

ascending distance. -ike all 6earest searches) ,Traffic,nfo returns an indeed list and acurrent line number >or pointer) inde? must be supplied to obtain data about a specificaircraft. +s far as , can tell) an ,Traffic,nfo search returns aircraft onl$. 6o boats)trucks) etc.

The ,Traffic,nfo #ariables retrie#e flight and communication data of indi#idual +, ormultipla$er aircraft >i.e.) \9ehicles’?. +s referenced in the SD") b$ using &!- instructionsa large number of Simulation 9ariables >+9ars? can be retrie#ed each update c$cle fore#er$ aircraft without needing SimConnect. The table below is a sample) but some

ob#ious applications such as TC+S come to mind.

8!=>!8 DA6A62!:8 F 86O,68S

86O,68 T1/8

//4 /!T2: 86O4 64

P<S>6><! A!D SP88D DA6AO26D 98-C,T1

/-+68 +-T +:98 O26D

/-+68 -+T,T2D8/-+68 -6O,T2D8

/-+68 +-T,T2D8/-+68 /,TC( D8O88S

/-+68 :+6" D8O88S

/-+68 (8+D,6O D8O88S T28/-+68 (8+D,6O D8O88S !+O68T,C

F4>=56 >!S637M8!6A6><! DA6A +,S/88D T28

98T,C+- S/88D

+TT,T2D8 ,6D,C+T /,TC( D8O88S

+TT,T2D8 ,6D,C+T :+6" D8O88S

AV><!>CS DA6AC!4 T+6S!,T

C!4 +CT,98 F8]286C1C!4 ST+6D:1 F8]286C1

6+94 +CT,98 F8]286C1

6+94 +9+,-+:-8

+DF4 +CT,98 F8]286C1

T+6S/6D84 CD8

C<!63<4S DA6A2DD8 /S,T,6

8-89+T /S,T,6

+,-86 /S,T,6

,S O8+ 8T+CT+:-8 +,-86 -8FT D8F-8CT,6

+,-86 ,O(T D8F-8CT,6

M>SC844A!8<7S S"S68MS DA6A8-8CT,C+- !+ST8 :+TT81

C,C2,T +9,6,CS 6

M>SC844A!8<7S DA6AD8S,O6 S/88D 9S0

8!/T1 8,O(T

S,! 6 O26D

S63>!= DA6A +TC T1/8

+TC !D8-

+TC ,D

+TC +,-,68 +TC F-,O(T 62!:8

Some #ariables) howe#er) such as Fuel data >stock +, aircraft ne#er run out of fuel oreperience emergencies?) the +O/S #ariables) and +utopilot data are not retrie#ablefrom ,Traffic,nfo. 8periment to see which #ariables are retrie#able.



89

>6raffi1>nfo:4atitude >6raffi1>nfo:4ongitude /degrees or radians0 L=et; Set

-atitude and -ongitude of the reference point) usuall$ the aircraft or control tower.Default is +/-+68 -+T,T2D8 and -6O,T2D8.

>6raffi1>nfo:MaVehi1les /enum0 L=et; Set

The limit of the number of aircraft returned b$ the search. The larger the number) thelonger it takes for the ,Traffic,nfo search to complete. ,t’s good practice to keep

,Traffic,nfo!a9ehicles to an appropriate siAe for the application. +s an eample) in aTC+S gauge) a maimum of =0 is a proper choice for ,Traffic,nfo!a9ehicles. Defaultis <00 #ehicles. !aimum is approimatel$ <50 to <P0. +n$ #alue set larger than thiswill likel$ crash the simulation – a memor$ issue) , think.

>6raffi1>nfo:3adius /meters; !Miles0 L=et; Set

!aimum search radius. +, aircraft be$ond ,Traffic,nfoadius will still be displayed b$-a$er9ehicles on the map) but onl$ those aircraft returned in the ,Traffic,nfo nearestsearch will ha#e accessible information. Default is Q= 6!iles. +, aircraft are generatedup to a maimum distance of 400 6!) so when working with +, traffic) there is no need

to set adius larger than 400 6!.

>6raffi1>nfo:Filter /enum or heade1imal0 L=et; Set

,Traffic,nfoFilter filters the search according to traffic categories.

T+FF,C@F,-T8@++"8. +wake are acti#e ground or airborne aircraft.Setting this filter will include +wake aircraft in the search results. nl$ \+wake’aircraft can be displa$ed on the map >i.e.) radar screen?. Filters +, but not!ultipla$er searches.

T+FF,C@F,-T8@S-88/,6O. \Sleeping’ are ground +, aircraft that ha#e beengenerated b$ Flight Simulator but are not $et an acti#e participant in thesimulation. The$ ha#e an aircraft Call Sign consisting of +TC +irline and Flight

6umber or +TC ,D >e.g.) S+J4'<?) !odel >e.g.) +=<4?) a two wa$point Flight/lan >Departure and Destination airport? and a uni%ue 9ehicle,D. 9ariablesassociated with sleeping aircraft can be listed) but the aircraft s$mbol will not

displa$ on the map until it is awakened b$ Flight Simulator. Sleeping aircraft areinitiall$ positioned at airport gates and parking ramps as demonstrated in the

figures that follow.

6ote that this filter adds \Sleeping’ ground aircraft. The list of aircraft returnedalwa$s includes \+wake’ aircraft. Filters +, but not !ultipla$er searches.

T+FF,C@F,-T8@,6@+, . +irborne aircraft are included in the search results.:$ definition) these will also be +wake aircraft. The search condition is the same



90

as >+S,! 6 O26D) bool? 3 0. This filter operates in +, as well as!ultipla$er traffic searches.

T+FF,C@F,-T8@6@O26D. Oround aircraft will be included in the search.

The search condition is the same as >+S,! 6 O26D) bool? 3 4. This filteroperates in +, as well as !ultipla$er traffic searches.

T+FF,C@F,-T8@T8@C6T--8S. , am not sure of the function of thisbit. wing to its name) it appears to control inclusion of tower controller>s? in

the search. ,f so) it isn’t understood wh$ that would be useful other thanpro#iding the abilit$ to retrie#e Tower -at and -on information perhaps) or wh$the name is plural. 6e#ertheless) Tower Controller is a multipla$er option.

T+FF,C@F,-T8@O26D@98(,C-8S. , am not sure of the function of this bit.

,ts name suggests it could include +, #ehicles other than aircraft in the search)for eample) such as Ships and Ferries) but more likel$) this refers to groundaircraft. ,t’s also possible that it is not functional in FS&.

T+FF,C@F,-T8@+,C+FT. , am not sure of the function of this bit. ,t is set

in the FS& eample sessionHinfo'ml >-Filter 3 decimal <5 which is e%ui#alentto binar$ - - % % - - %?. [email protected] is part of the FS& traffic radareample which is a multipla$er feature.

,t’s tempting to propose that T8@C6T--8S) O26D@98(,C-8S and +,C+FT are !ultipla$er options. (owe#er) m$ eperience is that search results ofboth +, and !ultipla$er traffic are not affected when :it 0) :it 4) or :it< are selected) ornot selected.

/reliminar$ obser#ations regarding ,Traffic,nfoFilter

o Filters A> and Multipla2er 6raffi1 Sear1hes:

:it P T+FF,C@F,-T8@++"8

:it 5 T+FF,C@F,-T8@S-88/,6O

:it Q T+FF,C@F,-T8@,6@+,

:it = T+FF,C@F,-T8@6@O26D

o 7nsure fun1tion:

:it < T+FF,C@F,-T8@T8@C6T--8S

:it 4 T+FF,C@F,-T8@O26D@98(,C-8S

:it 0 T+FF,C@F,-T8@+,C+FT

,f ,Traffic,nfoFilter is not included in the ml script) the default is decimal L') e%ui#alentto binar$ % - % % - - % >\+wake’) \,n@+ir’) \n@Oround’) \+ircraft’?'

-astl$) note that +, traffic is not possible in !ultipla$er mode.



91

Designating the Filter Value

+s an eample) if +irborne traffic is to be included in the nearest search) an appropriateselection is bit P and Q) \+wake’ and \,n@+ir’ as follows


+ 5 + " 8

S - 8 8 / , 6 O

, 6@

+ , .

6@

O . 2 6 D

T 5 8 .

C 6 T . - - 8 . S

O . 2 6 D

9 8 ( , C - 8 S

+ , . C . + F T


% - % - - - - B ,Traffic,nfoFilter selections

The resulting binar$ number is % - % - - - - whose decimal e%ui#alent is L0 andheadecimal e%ui#alent is 50. The appropriate &!- is either

80 (>C:ITrafficInfo:Filter) or

0x50 (>C:ITrafficInfo:Filter)

Sleep State

Sleep state has no influence on \,n@+ir’ aircraft7 airborne #ehicles are all \+wake’ b$definition. Conse%uentl$) all of the following $ield the same search results


+ 5 + " 8

S - 8 8 / , 6 O

, 6@

+ , .

6@

O . 2 6 D

T 5 8 .

C 6 T . - - 8 . S

O . 2 6 D

9 8 ( , C - 8 S

+ , . C . + F T


- - % - - - - B ,Traffic,nfoFilter selections

- % % - - - - B ,Traffic,nfoFilter selections

% - % - - - - B ,Traffic,nfoFilter selections

% % % - - - - B ,Traffic,nfoFilter selections



92

Sleep state does affect the search of Oround aircraft) howe#er. ,f all \+wake’ \Oround’aircraft are to be included in the search) the selection would be


+ 5 + " 8

S - 8 8 / , 6 O

, 6@

+ , .

6@

O . 2 6 D

T 5 8 .

C 6 T . - - 8 . S

O . 2 6 D

9 8 ( , C - 8 S

+ , . C . + F T


% - - % - - - B ,Traffic,nfoFilter selections

8ample &!-

72 (>C:ITrafficInfo:Filter) or

0x48 (>C:ITrafficInfo:Filter)

Selecting \Sleep’ adds sleeping Oround aircraft to the search results. \+wake’ is thedefault sleep state and is alwa$s included for both \,n@+ir’ and \Oround’ searches. Thereis no wa$ to isolate *ust \Sleeping’ \n@Oround’ aircraft. :oth of the following $ield thesame search results) namel$) \+wake’ plus \Sleeping’ \n@Oround’ aircraft


+ 5 + " 8

S - 8 8 / , 6 O

, 6@

+ , .

6@

O . 2 6 D

T 5 8 .

C 6 T . - - 8 . S

O . 2 6 D

9 8 ( , C - 8 S

+ , . C . + F T


% % - % - - - B ,Traffic,nfoFilter selections

- % - % - - - B ,Traffic,nfoFilter selections

!earest 6raffi1 Sear1h 8ample

6et is an eample of a 6earest Traffic search result for +, aircraft at San Francisco,nternational +irport. ,t shows some of the t$pes of data that can be retrie#ed for e#er$aircraft during each gauge update c$cle. The search radius was two 6!iles so aircraftat nearb$ airports were not included. ,n this particular case) the search center is m$user aircraft) 6='PLO) 9ehicle ,D [4) a Cessna Q<4 parked at the center of the airportfacilit$. +lternati#el$) a Control Tower can be established as search center >the t$picalmultipla$er setup for a Traffic Controller?.



93

Cur ,d >Current ,nde?) Dist >Distance?) 9,D >9ehicle ,D?) and Flight /lan are SD" documentedE ,Traffic,nfo #ariables and are discussed later. +s well) the simple &!-

re%uired to retrie#e other #ariables such as -atitude) -ongitude) +ltitude) etc is alsoaddressed later.

Oround 9ehicle ,D PPQ is a little noteworth$. ,t’s an !DL0 from -as 9egas !cCarranthat *ust landed w$ <L and is alread$ on taiwa$ /apa) less than <J00’ from the touchdown Aone. +, aircraft land hard and stop %uickl$ in Flight Simulator.





95



96

>6raffi1>nfo:Sort<rder

This #ariable is not implemented according to the SD". (a#ing said that) howe#er),Traffic,nfo is a 6earest search and traffic returned b$ the search are ordered inascending distance from the search origin >,Traffic,nfo-atitude and -ongitude?.

>6raffi1>nfo:CurrentVehi1le /enum0 L=et; Set

,Traffic,nfoCurrent9ehicle is the inde pointer for the nearest traffic search list. The

first aircraft in the list is ,Traffic,nfoCurrent9ehicle 0. 8ample &!-

0 (>C:ITrafficInfo:CurrentVehicle)

>6raffi1>nfo:Sele1tedVehi1le /enum0 L=et; Set

,Traffic,nfoSelected9ehicle is an inde pointer used to select a specific aircraft from the,Traffic,nfo list in order to highlight its mo#ement in contrast to all other aircraft on theradar screen. The aircraft must be included in the ,Traffic,nfo search results in order tobe selectedNhighlighted. nl$ one aircraft can be Selected at a time.



97

Figure A abo#e is a traffic radar image around -ondon (eathrow +irport. The ange isL0 6!. + nearest traffic search was enabled with a Filter #alue of L0 >\+wake’ and \,n@+ir’?) a search radius of Q0 6!) and maimum #ehicle limit of 50. +dditionall$)-a$erangeings) -a$erTerrain and TerrrainShadow were enabled.

Figure B is a list of the <0 aircraft returned in the nearest Traffic search. ,fCurrent9ehicle ,nde P is subse%uentl$ chosen) then the \Selected’ aircraft) S<A*%9))can be highlighted in a different color as shown in Figure C. 2ntil a new selection ismade) S+J4'< will remain highlighted as its flight continues.

Figure D demonstrates that the radar screen will displa$ all +, or multipla$er aircraft

within the map boundar$. hich aircraft are displayed on the map is controlled b$b*ectDetail-a$er9ehicles >airborne andNor ground?) not b$ ,Traffic,nfoFilter. (owe#er)onl$ the <0 aircraft returned from the nearest traffic search) that is) the aircraft that arewithin the Q0 6! search radius) can be Selected or interrogated for #arious realBtimedata as shown in Table B.

,ncidentall$) a count of aircraft displa$ed on the map within the Q0 6! search radiusapparentl$ results in 4') but the ,Traffic,nfo list contains <0. 6ote that Current ,nde 4Qand 45 is essentiall$ a duplicate aircraft. + common +, gen bug.

>6raffi1>nfo:Sele1tedVehi1le>D /enum0 L=et

,Traffic,nfoSelected9ehicle,D is a uni%ue identification number automaticall$ assignedb$ the traffic module to +, or multipla$er aircraft in order to enable selectionNhighlight ofspecific aircraft. The Current9ehicle inde pointer is not suitable for this purpose

because it represents relati#e distances from the search origin at the point in time the

search was made. +s aircraft mo#e around) the relati#e distance order constantl$changes and the Current9ehicle inde of a particular aircraft ma$ be < now) but couldbe a different number the net update c$cle. n the other hand) Selected9ehicle,D remains with the aircraft regardless of relati#e distance position until it is retired fromthe simulation b$ the traffic module.

8ample &!- script at the end of this section demonstrates the #ehicle selection process.

>6raffi1>nfo:4istSie /enum0 L=et

,Traffic,nfo-istSiAe is the number of aircraft returned b$ the nearest aircraft search. ,t

is analogous to the ,tems number from other 6earest searches) for eample)6earest+irport,tems6umber.



98

>6raffi1>nfo:CurrentDistan1e /!Miles or m0 L=et

,Traffic,nfoCurrentDistance is the slant distance of each aircraft retrie#ed in the nearesttraffic search from the search origin. 6ote that this is slant distance) not horiAontaldistance like OeoCalcDistance. ,Traffic,nfoCurrentDistance incorporates the relati#ealtitude difference between the search origin which is usuall$ the user’s aircraft) and thetraffic aircraft.

A !ote on 7pdate FreNuen12

,Traffic,nfoCurrentDistance is updated e#er$ < seconds onl$ b$ Flight Simulator.

(owe#er) other +, or multipla$er s$stem #ariables are updated e#er$ gauge updatec$cle. For eample

C,Traffic,nfoC/-+68 -+T,T2D8

C,Traffic,nfoC/-+68 -6O,T2D8

C,Traffic,nfoC/-+68 +-T,T2D8

C,Traffic,nfoS/-+68 -+T,T2D8

C,Traffic,nfoS/-+68 -6O,T2D8

C,Traffic,nfoS/-+68 +-T,T2D8

C,Traffic,nfoC+,-86 -8FT D8F-8CT,6

C,Traffic,nfoC/-+68 +-T +:98 O26D) etc.

are all updated e#er$ gauge update c$cle.

>6raffi1>nfo:Sele1tedFlightPlan /String0 L=et

,Traffic,nfoSelectedFlight/lan is a list of a$point ,dents of the flight plan for the

selected aircraft. For +, aircraft) it consists onl$ of the departure airport ,dent >not,C+ as stated in the SD"? and the destination airport ,dent. The SD" states that flightplans longer than two wa$points will be listed in comma separated format) howe#er itappears that ,Traffic,nfoSelectedFlight/lan will return the ,dents of first two wa$pointsonl$ of an$ flight plan.



99

>6raffi1>nfo XM4 S1ript 8amples

8ample %' Displa2ing a 4ist of A> Air1raft >nformation

The first eample demonstrates the setBup of the 6earest Traffic search and an eampleof an 8lement displa$ for the list of aircraft retrie#ed in that search

1 <Macro Name="CurrentCallsign">

2 (C:ITrafficInfo:C:ATC AIRLINE, string) d slen 0 >

3 if{ 0 3 ssub uc (C:ITrafficInfo:C:ATC FLIGHT NUMBER, string) scat }

4 els{ (C:ITrafficInfo:C:ATC ID) d slen 0 == if{ (C:ITrafficInfo:CurrentPlayerName) } }

5 </Macro>

6

7 <Update>

8 (A:PLANE LATITUDE, radians) (>C:ITrafficInfo:Latitude, radians)

9 (A:PLANE LONGITUDE, radians) (>C:ITrafficInfo:Longitude, radians)

10 30 (>C:ItrafficInfo:MaxVehicles)

11 40 (>C:ItrafficInfo:Radius, nmiles)

12 0x50 (>C:ItrafficInfo:Filter) 

13 </Update>

14

15 <Element Name="ITrafficInfo Nearest Traffic Search Display">16 <Position X="10" Y="10"/>

17 <FormattedText X="500" Y="600" Font="courier new" FontSize="9" LineSpacing="9" Color="Blue"

18 BackgroundColor="white" Bright="Yes" Align="Right">

19 <Color Value="#111111"/>

20 <String>

21 \{clr2}

22 %CUR ON MAG GND\n

23 %IDX CALL MODEL DIST VID LATITUDE LONGITUDE ALT VSI GND HDG SPD FLIGHT PLAN\n

24 \{clr}

25 %((C:ItrafficInfo:ListSize) s2 0 !=)

26 %{if}

27 %(0 sp1)

28 %{loop}

29 %(l1 (>C:ITrafficInfo:CurrentVehicle))

30 %((C:ITrafficInfo:CurrentVehicle) (>C:ITrafficInfo:SelectedVehicle))

31 %((C:ITrafficInfo:CurrentVehicle))%!-5d!32 %( @CurrentCallsign )%!-10s!

33 %((C:ITrafficInfo:C:ATC MODEL, string))%!-8s!

34 %((C:ITrafficInfo:CurrentDistance, nmiles))%!4.1f!

35 %((C:ITrafficInfo:SelectedVehicleID))%!6d!

36 %((C:ITrafficInfo:C:PLANE LATITUDE, degrees))%!11.6f!

37 %((C:ITrafficInfo:C:PLANE LONGITUDE, degrees))%!12.6f!

38 %((C:ITrafficInfo:C:PLANE ALTITUDE, feet))%!7d!

39 %((C:ITrafficInfo:C:VERTICAL SPEED, feet per minute))%!7d!

40 %((C:ITrafficInfo:C:SIM ON GROUND, bool))%!4d!

41 %((C:ITrafficInfo:C:PLANE HEADING DEGREES MAGNETIC, degrees))%!5d!

42 %((C:ITrafficInfo:C:GROUND VELOCITY, knots))%!5d!

43 %((C:ITrafficInfo:SelectedFlightPlan))%!12s!\n

44 %(l1 ++ s1 l2 <)

45 %{next}

46 %{end}

47 </String>

48 </FormattedText>

49 </Element>

4ines % +: + macro that generates the aircraft Call Sign from the +, +TC

+irline 6ame plus Flight 6umber or Current/la$er6ame in the case of amultipla$er aircraft. The SD" eplanation of ssu is incorrect. Correcteddocumentation for the ssu operator can be found in the FSDe#eloper iki



100

http://www.fsdeveloper.com/wiki/index.php?title=XML:_Displaying_only_part_of_a_string

4ines @ E %): This is the standard 6earest Search setup – 4? search origin) <?maimum items) =? search radius) and Q? search filter. +s soon as thesestatements are eecuted) the default ,Traffic,nfo search setup will be reBset to

the new #alues in lines L through 4<. Default ,Traffic,nfo setup #alues areapplied whene#er the user does not include them >-atitude and -ongitide 3 +/-+68 -+T,T2D8 and -6O,T2D8) !a 9ehicles 3 <00) search radius 3 Q=6!) Filter 3 decimal L'?.

,n the eample abo#e) the setup instructions are eecuted e#er$ update c$cle)howe#er the$ need to be eecuted one time onl$ in order to reBset eisting setup#alues. Conse%uentl$) a better place for these lines of code might be within aClick section of a mouse area) or if left in the update section) limited to oneeecution c$cle onl$ b$ use of a conditional if_ ` statement.

4ine %@: 6ote the use of Ba1groundColor in the tet format. This will nicel$mitigate the ob*ectionable antiBaliasing applied to tet in FS&.

4ine )+: This statement will pre#ent the displa$ of the list until the nearesttraffic search is complete) as e#idenced b$ -istSiAe being greater than Aero. Thisis a standard approach for fs'gps nearest searches.

4ine )*: The #alue Aero is stored into egister [4. 0E is alwa$s the #alue ofthe first inde line.

4ine )@: The displa$ loop begins. 9ariables for an indi#idual traffic aircraft aredispla$ed one aircraft at a time) one line at a time based on the current ,ndepointer) the #alue in egister [4.

4ine )9: egister [4 is loaded into the Current9ehicle inde pointer.

4ine ,-: Two of the desired outputs for this particular list are the uni%ue 9ehicle ,D and +, Flight /lan for each traffic aircraft. 2nfortunatel$) these two

#ariables can be retrie#ed onl$ from the Selected aircraft. The &!- to Select anaircraft in#ol#es passing a pointer #alue >in this case) the Current9ehicle pointer#alue? to the Selected inde pointer. The &!- is straightforward

(C:ITrafficInfo:CurrentVehicle) (>C:ITrafficInfo:SelectedVehicle)

The result is that during each pass through the displa$ loop) -ine =0 causes theCurrent aircraft to also become the Selected aircraft) enabling retrie#al anddispla$ of Selected9ehicle,D and SelectedFlight/lan for each aircraft retrie#ed in

the search. 4ines ,K I): 6ote the special use s$nta. +s eplained in the SD") The C:

following ,Traffic,nfo stands for Current) and #alues retrie#ed e#er$ update c$cle

b$ these code lines are the respecti#e +9ar Simulation 9ariable #alues for theCurrent aircraft. Similarl$) an S: can be used and the #alues retrie#ed will be forthe Selected aircraft >although in this eample) -ine =0 alread$ made the Currentaircraft and the Selected aircraft one and the same?.



101

This is #er$ useful. +mong other things) it satisfies the traffic data re%uirementsto build a 6CAS gauge. /lotting intruder aircraft on a TC+S mo#ing map gaugeor as an o#erla$ to fs'gps!ap can be done in &!- using map scale methodsco#ered in the !ap /ro*ections chapter.

Two additional notes. First) the SD" states that to set the Current or Selected

aircraft) use a statement such as

>C:ITrafficInfo:CurrentVehicle N

where 6 is a #alue between 0 and -istSiAe B4. +pparentl$) this is a small t$poE)and the correct s$nta is

N (>C:ITrafficInfo:CurrentVehicle)

Secondl$) the SD" ad#ises that for the units) the Simulation 9ariables are alltreated as numer) ecept for certain string #ariables. This could be a littlemisleading) and the use of standard Flight Simulator units as shown in -ines =Pthru Q< is encouraged. +s alwa$s) FS will make internal con#ersions for an$ of itsstandard units.

4ine II: The incrementerE. +fter each line of traffic aircraft information isretrie#ed and displa$ed) egister [4 is incremented b$ 4 and egister [< ischecked to see if all of the aircraft ha#e been displa$ed.

The preceding code generated the following list of 4Q +, aircraft retrie#ed in the search.,t’s a realBtime displa$) with numbers and relati#e aircraft positions continuousl$changing.

,n this eample) the aircraft that is \Selected’ is also constantl$ changing >-ine =0? as thedispla$ loop progresses through the nearest traffic search results. ith this code itimpossible to Select a particular aircraft and watch its flight progress on the map) as inFigure C abo#e. Therefore) this script) specificall$) -ines =0) =5) and Q= cannot be usedif $ou want to be able to select a specific aircraft and follow its flight on the map orradar screen.



102

8ample )' Displa2ing the Sele1ted Air1raft on the Map

This eample shows code re%uired to highlight and displa$ the Selected aircraft on themap.

1 <ColorLayerVehiclesSelected> 0x0000FF </ColorLayerVehiclesSelected>

2 <TagPosition> 5 </TagPosition>

3

4 

5 3 (>C:ITrafficInfo:CurrentVehicle)

6 (C:ITrafficInfo:CurrentVehicle) (>C:ITrafficInfo:SelectedVehicle)

7

8 3 (>C:ITrafficInfo:SelectedVehicle)

9

10 (C:ITrafficInfo:SelectedVehicleID) (>C:fs9gps:SelectedVehicle)

4ine %: ,f it is to stand out) the Color-a$er9ehiclesSelected #ariable must be setto a different color than the other #ehicle s$mbols) Color-a$er9ehicles. ,n thiseample) the Selected aircraft will be displa$ed with a red s$mbol. :$ default)the Selected aircraft’s tet label will be red.

4ine ): +dditionall$) the position >Tag/osition? of the Selected aircraft’s labelcan be changed to help alle#iate label congestion. Tag/osition operates onl$ onthe Selected #ehicle) not all #ehicles) so its an aircraftBb$Baircraft process to

reposition all tags. The re#ised Tag/osition remains with the aircraft e#en whenanother is subse%uentl$ Selected. The default location >Tag/osition 0? is upperright. ,n this eample) the label) or tag position is set to 5) to the left of theSelected aircraft s$mbol.

4ine I through 9: The abilit$ to Select an aircraft re%uires that first) a nearesttraffic search has been completed. The nearest search returns an indeed list ofaircraft traffic) and the Selected aircraft is then chosen from that list. ,n order todo that) the desired inde pointer of the nearest traffic search list)Current9ehicle) needs to be identified b$ the user and passed to

Current9ehicleSelected. That thought process is reflected b$ -ines 5 and P) but itis more efficient to simpl$ code -ine '.

4ine %%: The last step. ,n order for CustomDraw to accept the Selected aircraftfor map displa$) this instruction must be included. 6ote also that it is notnecessar$ to pass the Selected9ehicle inde number to Selected9ehicle,D

That is) the following is not necessar$

(C:ITrafficInfo:SelectedVehicle) (>C:ITrafficInfo:SelectedVehicleID)



103

>6raffi1>nfo:CurrentPla2er!ame /string0 L=et; Set

The !ulti/la$er pla$er name.

>6raffi1>nfo:Sele1tedPla2er!ame /string0 L=et; Set

The selected !ulti/la$er aircraft.



104

Combining )ML "bjects wit& CustomDraw Map

,f a gauge programmer wants to combine their own map applications such as a custom

&!- mo#ing map o#erla$ on the CustomDraw !ap terrain base) or create the abilit$ toclick an$where on the map to retrie#e latitude and longitude) distance and bearing) then

the difference between screen piel and gauge measurement unit >gauge unit? aspectratios and the transform function between the two must be understood and applied.

CustomDraw !ap is measured in screen piels) &!- gauge applications are measured ingauge units) and the two are not the same.

The table below summariAes some of the things that can be accomplished using &!-script with standard gps and CustomDraw #ariables.

Mouse Cli1 >nformation XM4 <?erla2 <?erla2 !ot 8as2

-atitude and -ongitude S$mbols +irports +irspace

Distance and :earing 9s +pproach +dd Flight /lan a$points 6D:s :orders

,nitiate 6earest Searches ,-Ss Orid >sinusoidal pro*?

Fre%uencies ,ntersections +irwa$s

unwa$s 2ser +ircraft

Ser#ices 8nroute Flight /lan

Facilities TC+S !ap B +ir Traffic

etc. ange ings

2ser Defined points

Stationar$ !ap

,n general) mo#ing map o#erla$s of single point ob*ects such as facilities or air trafficcan be accomplished. Shapes like +irspace or line segments such as +irwa$s thatre%uire data base access not a#ailable from a %uer$ of Flight Simulator’s gps databaseare be$ond the scope of this discussion.

hile the applications abo#e ma$ be possible within the &!- world) in m$ opinion it’s

not practical to replace the CustomDraw !ap la$ers. + notable eception is Traffic. TheCustomDraw -a$er9ehicles was designed for an +TC Controller radar screen #iew) but itdoesn’t produce the best looking TC+S gauge displa$. (owe#er) e#en a TC+S ,, #J.4s$stem can be modeled using ,Traffic,nfo group #ariables) an o#erla$ with customs$mbols) &!- script to identif$ the Traffic +lerts) and &!- to replicate the #J.4

esolution +d#isories.



105

$creen Pi*els vs+ Gauge ,nits

!ap Scale is the ratio of real distance to map displa$ distance. For CustomDraw !ap)

the scale units are 6!iles or meters per ph$sical screen piel. n the other hand) the&!- !ouse parameters >!&? and >!1?) measure gauge units, not screen piels. +s

demonstrated below) when a gauge unit is used to measure distance between twoscreen piels) then

The number of gauge units will not necessaril$ e%ual the number of screen piels – usuall$ not) in fact) because the panel background image is usuall$ not at thesame aspect ratio as the screen. /anel background images of stock FS' and FS&aircraft are 40<Q & JPL piels >Q= ratio?) but monitor screens #ar$ 4P00 & 4<00>Q=?) 4P00 & '00 >Q<.<5?) 4'<0 & 40L0 >Q<.<5?) 4<L0 & 40<Q >Q=.<?) etc.

Panel Ba1ground >mage ma2 e distorted ut CustomDraw Map is not

,n the figures that follow) an FS& fs'gps!ap #iew of the San Francisco California) 2S+peninsula is shown as displa$ed on a 4P00 4<00 piel screen and on a 4P00 '00piel screen. ,n both cases) the panel background bitmap image is the stock FS' FS&40<Q JPL piels) and the CustomDraw map siAe is 500 Q00 gauge units. The Hoomis low >Hoom less than 500 km? so the Sinusoidal pro*ection is used

The relati#e distances) angles) areas and shapes of the two map imagesrendered b$ CustomDraw are identical. There is no distortion of map elementsbetween the two images. The 45 6! ange ing is perfectl$ circular on bothimages. The panel background image and the shape of the 500 & Q00 gaugeunit map area ma$ be stretched on different screens) but the map rendered b$fs'gps!ap is ne#er stretched or distorted.



106

,n other words) the fs'gps!ap engine is independent of both screen and panelbackground image resolutions) and it internall$ applies sinusoidal pro*ection>Aoom dependent in FS&? with e%ual & and 1 ais scales. +s rendered on thescreen) all sinusoidal pro*ection fs'gps!aps ha#e e%ual & and 1 scales asmeasured in screen pixels.

The onl$ difference is that more map image is displa$ed in the eastBwestdirection on the 4P00 '00 screen due to the different aspect ratio of thatmonitor.

,n each image) the short ais >1 ais? scale as measured in gauge units is the

same. :$ definition) it is =0 6!iles per Q00 gauge units >Hoom Factor 3 45?) or0.0J5 6! per gauge unitB1.

The long ais >& ais? scale) measured in gauge unitsB&) is different between thetwo images. The reason is the aspect ratio of the screens) and conse%uentl$)

the aspect ratios of the gauge units) are not the same.



107

6hree eamples of Panel Ba1ground >mage stret1h

The following = figures demonstrate stretch of the panel background image on different

monitors and in different #iew modes. 8ach produces a different gauge unit aspect ratiothat must be accounted for if using the mouse to measure distance on the CustomDrawmap or creating o#erla$s for the CustomDraw map where the latNlon of the point to bedispla$ed must be correctl$ translated into gauge units.

4. 4P00 4<00 screen and 40<Q JPL panel background

,n the figure abo#e) both the screen and the panel background image ha#e the sameaspect ratio so there is no distortion of gauge units when the background panel bitmapimage is enlarged to fill the screen.

,n this configuration) the short and long ais scales measured in gauge units areidentical and) in the cartoon eample) a mouse click at &3QE) 130E is at a ange #alueof = and a mouse click at &3JE) 13=E is also at a ange #alue of =. This is thesimplest situation.



108

<. 4P00 '00 screen and 40<Q JPL panel background

n the 4P00 '00 screen abo#e) the panel background bitmap image is stretched to fillthe screen and the gauge unit shape becomes elongated as demonstrated in the cartoon.

+ mouse click at &3QE) 130E is still at a ange #alue of =) but a mouse click at &3JE) 13=E is at a point on the map further than ange 3 =. The short and long ais scalesmeasured in gauge units are no longer e%ual7 now a mouse click at &3P.<5E) 13=E isat ange 3 =.

=. indowed #s. Full Screen 9iew mode

8#en the subtle change of switching from Full Screen 9iew to indowed 9iew >i.e.) nonBFull Screen 9iew? affects map scales measured in gauge units because the backgroundimage is compressed to make room for the FS !enu) the indows Task bar) and a one



109

screen piel black frame >in FS'?. This changes the gauge unit aspect ratio whichchanges the &!- map scales.

The following chapter) !ap Scale Calibration for #erla$s) discusses a techni%ue toderi#e & and 1 scale functions that translate CustomDraw screen piel coordinates into&!- gauge unit coordinates) and #ice #ersa. +pplication of these functions allows theuser to accuratel$ position &!- ob*ects on the CustomDraw map base.



110

Map $cale Calibration (or "verlays XML and Customra!

&!- o#erla$s and mouse mo#ements are measured in gauge units but CustomDraw !aprenders screen piels. The scales are not the same. To o#erla$ &!- gauge ob*ects atthe correct coordinates relati#e to the underl$ing CustomDraw map or to use the mouse

on it) map scale measured in gauge units must be determined first. :oth the &Bais and 1Bais scales >meters per gauge unit & and 1? are needed because the$ are oftendifferent. &!- o#erla$s and mouse use can add useful and #er$ cool functionalit$ toCustomDraw !ap) but calibrating the scales needs to be done accuratel$.

S1ale Caliration FSXS1ale # Meters O /∆∆∆∆=auge 7nits .oom Fa1tor0

Calibration can be achie#ed b$ clicking the map at locations with known earth

coordinates or distances) recording the mouse & and 1 gauge unit position) andcomputing the & and 1 scale functions that translate between the two.



111

The manual calibration techni%ue in FS& uses ange ings to establish distance andin#ol#es two mouse clicks on the long ais. The short ais is alwa$s calibrated becauseFlight Simulator alwa$s fills the short ais with < ange.

Calibration should be done at Hoom Factors >ange? less that <P' 6! >Hooms less than500 "!?. The calibration se%uence in#ol#es the following

Track2p 3 0

-a$erangeings 3 4 b*ectDetail-a$erangeings 3 H Factor >ange? +dd /ol$line 8lements through the map center) Center& and Center1 ) as shown

with the blue cursor lines on the map Click on the intersections of the range ring and the long ais pol$line as shown

abo#e.

Two mouse clicks determine range ring diameter measured in gauge units for the long

ais. The &!- map scale is a simple calculation for each ais after that. +dditionall$)thse scale functions can be permanentl$ stored as -9ars so that calibration is no longerre%uired unless the aspect ratio of the map changes.

The &!- map scale functions calculated from the calibration eample is shown below.6ote that cosine correction of the &Bais scale at Aooms below 500 "! is absent



112

+n eample of short ais 3 &Bais

8%uations for Scale #s. Hoom functions

A B C D E F

1 Short Ais 4ong Ais

2 H Factor >ange? 50.000 6autical !iles "nown Distance 3:< 6autical !iles

3 !ouse 4 =5.=4J Oauge 2nits

4 !ap SiAe =00 Oauge 2nits !ouse < =PQ.0=P Oauge 2nits

5 !ap Scale 3>:<4L5<? N>:Q N< ? !e te rs N Oauge 2. !ap Scale 38<4L5<<N+:S>8Q B8= ? !e te rs N Oauge 2.

6 >Scale? N >H Factor? #B+OB) Short +is B &!- !ap Scale as a function of H Factor > 4 N 4L5< Oauge 2nit?

7 >Scale? N >H Factor? #8+OB) -ong +is B &!- !ap Scale as a function of H Factor > 4 N 4L5< Oauge 2nit?

+ functional &!- eample of this calibration techni%ue is included in the downloadsection of the :lack:oNCustomDraw website.



113

S1ale Caliration FS9

The idea behind scale calibration in FS' is the same as for FS&) but range rings are nota#ailable so single point ob*ects from the gps data base >airports) 6D:s) or 9s? are

substituted for range rings and OeoCalcDistance is used to establish known distance onthe long ais.

2sing airports as an eample) the calibration se%uence in#ol#es the following

Track2p 3 0 Detail-a$er+irports 3 4. /oint s$mbol ,C+ or ,dent to access a$point+irport-atitude and -ongitude Click the airport s$mbol to determine gauge &) 1 coordinates OeoCalcDistance #ariable for distance between the two airports

Oeometric calculations to compute the & and 1 components of the distance

8%uations for Scale #s. Hoom functions



114

Hoom Factor J5 6! Hoom Factor 3 ange!ap SiAe & 500 Oauge 2nits!ap SiAe 1 Q00 Oauge 2nits

!ouse 4 & PJ.<J<J Oauge 2nits Calibration /oint 4 &!ouse 4 1 =0<.=50P Oauge 2nits Calibration /oint 4 1

!ouse < & Q40.PLQ0 Oauge 2nits Calibration /oint < &!ouse < 1 4<0.PPP0 Oauge 2nits Calibration /oint < 1 Delta !ouse & =Q=.Q44= Oauge 2nits /oint < B /oint 4 &Delta !ouse 1 4L4.PLQP Oauge 2nits /oint < B /oint 4 1

OeoCalc-atitude 4 4<.P=0= Degrees Calibration /oint 4 -atOeoCalc-ongitude 4 ''.'5== Degrees Calibration /oint 4 -on

OeoCalc-atitude < 4=.JPPJ Degrees Calibration /oint < -atOeoCalc-ongitude < 40<.=4PJ Degrees Calibration /oint < -on

OeoCalcDistance 45=.'LJP 6!Delta -atitude 4.4=PQ DegreesDelta -atitude PL.4L== 6! Component@1

-ong +is Distance 4=L.0P'J 6! Component@&-ong +is Distance <55J05.0 !eters Component@&Short +is &!- !ap Scale P'Q.5000 !eters per Oauge 2nit

-ong +is &!- !ap Scale JQQ.P0<' !eters per Oauge 2nit

>Scale? N >H Factor? 9')K-- Short +is Scale as function of H Factor

>Scale? N >H Factor? 9'9)@- -ong +is Scale as function of H Factor

A B C D

1 Hoom Factor J5 6! Hoom Factor 3 ange2 !ap SiAe & 500 Oauge 2nits3 !ap SiAe 1 Q00 Oauge 2nits4

5 !ouse 4 & PJ.<J<J Oauge 2nits Calibration /oint 4 &6 !ouse 4 1 =0<.=50P Oauge 2nits Calibration /oint 4 1 7 !ouse < & Q40.PLQ0 Oauge 2nits Calibration /oint < &8 !ouse < 1 4<0.PPP0 Oauge 2nits Calibration /oint < 1 9 Delta !ouse & 3+:S>:JB:5? Oauge 2nits /oint :LB:P? Oauge 2nits /oint < B /oint 4 1 11

12 OeoCalc-atitude 4 4<.P=0= Degrees Calibration /oint 4 -at13 OeoCalc-ongitude 4 ''.'5== Degrees Calibration /oint 4 -on14 OeoCalc-atitude < 4=.JPPJ Degrees Calibration /oint < -at15 OeoCalc-ongitude < 40<.=4PJ Degrees Calibration /oint < -on16

17 OeoCalcDistance 45=.'LJP 6!18 Delta -atitude 3:4QB:4< Degrees19 Delta -atitude 3:4LP0 6! Component@1 20 -ong +is Distance 3S]T>:4J<B:4'<? 6! Component@&21 -ong +is Distance 3:<04L5< !eters Component@&22 Short +is &!- !ap Scale 3<:44L5<N:= !eters per Oauge 2nit23 -ong +is &!- !ap Scale 3:<4N:' !eters per Oauge 2nit24

25 >Scale? N >H Factor? #B))OB% Short +is Scale as function of H Factor26 >Scale? N >H Factor? #B),OB% -ong +is Scale as function of H Factor



115

The &!- map scale – Hoom functions calculated from the FS' calibration eample isshown below

Manual Caliration Summar2 Points

+ccurac$ is impro#ed if two points are clicked for measurement b$ the mouse ratherthan using map Center& and Center1 as one of the points.

&!- eamples for all calibration techni%ues are included in the download section of the:lack:oNCustomDraw website.



116

Trans(orming Lat-Lon Coordinates to Gauge ,nits And "ice "ersa

!aking &!- o#erla$s for the CustomDraw map in#ol#es transforming latitude andlongitude of o#erla$ ob*ects $ou wish to displa$ into gauge units in order to accuratel$position them with respect to the underl$ing CustomDraw mo#ing map. 2sing the

mouse to identif$ coordinates or distances on the map in#ol#es the re#erse –transforming &!- gauge units into latitude and longitude. Se#eral #er$ cool applicationsare possible using these transforms.

The transform process is described b$ these simple relationships

!eters@& 3 Scale@& Oauge 2nits@& Hoom Factor

!eters@1 3 Scale@1 Oauge 2nits@1 Hoom Factor

where

!eters The real earth 8astBest >&E? and 6orthBSouth >1E? distance from thereference point) normall$ the users aircraft position) to the point of interest

Scale The Scale@& and Scale@1 functions deri#ed during map calibration

Oauge 2nits The gauge unit difference >DeltaO2@& and DeltaO2@1? betweenthe reference point and the point of interest

Hoom Factor The map Aoom setting where Hoom 3 Hoom Factor 4L5<

6ransforming 4atO4on Coordinates to =auge 7nits: Creating Map <?erla2s

This eample demonstrates the coordinate transform step for making a TC+S o#erla$from traffic coordinates returned b$ ,Traffic,nfo #ariables. The task is to determine thegauge unit position of the intruder aircraft gi#en its latitude and longitude so it can bedispla$ed using &!- gauge units. hen Track2p 3 0 >top of the map is True 6orth?) itis a straightforward twoBstep process of determining & and 1 distance from the latNlonpairs and then con#erting the &)1 distance into gauge units.

Distance calculation is separated into 6BS and 8B components using spherical

geometr$ assumptions shown on the following page. The 6orthBSouth 1E distance) or

arc length) is

+rc -ength@1 3 >-atitude< – -atitude4? 8arth adius where -atitude4 and < areepressed in radians) not degrees. , use 8arth adius 3 =QQ0.0P5 6! or P=J4000

meters.

The 8astBest &E component has a similar approach but +rc -ength@& must becorrected for latitude



117

+rc -ength@& 3 >-ongitude< – -ongitude4? >8arth adius cos>-at<?? where-ongitude4 and < are epressed in radians.

-at<

% 3adian: Ar1 4ength # 3adius

φ >radians? 3 -at< >radians? – -at4 >radians?

φ >radians? 3 +rc -ength@1 N 8arth adius

+rc -ength@1 3 >-at< – -at4? 8arth adius

-at4φ

8arth adius=QQ0.0P5 6!

P)=J4)000 meters

Determination of distance should also account for the special case where the useraircraft and intruder aircraft are on opposite sides of the e%uator andNor prime meridian.

The second step) con#erting +rc -ength@& and +rc -ength@1 into gauge units) in#ol#esapplication of the map scales deri#ed during calibration. The e%uations

DeltaO2@& 3 +rc -ength@& N >Scale@& Hoom Factor?

DeltaO2@1 3 +rc -ength@1 N >Scale@1 Hoom Factor?

$ield gauge units that are measured relati#e to the users aircraft position) Center& and Center1 . Therefore) the final displa$ location) Oauge@& and Oauge@1) is the sum of therelati#e gauge units plus aircraft position) i.e.) Oauge@& 3 DeltaO2@& U Center&.

8ample &!- for FS& used for air traffic in a TC+S displa$



118

-ines 4< applies a cos>-at<? correction to compensate for the pro*ection change.

,n FS') the line ' through 4< e%ui#alent would reduce to < lines

6ra17p # %

Track2p 3 4 is the normal map configuration for an aircraft gps or !FD displa$. ,n thismode) the ground track of the aircraft determines the direction to which the top of the

map points. The map continuousl$ rotates as the user aircraft changes ground pathdirection during flight. To displa$ o#erla$ ob*ects such as other air traffic in the correctposition with respect to the underl$ing CustomDraw map) the gauge units of the o#erla$ob*ect must also be rotated consistent with the base map.

There are two approaches to accomplish this. The first utiliAes a coordinate rotationtransform. For simplicit$) , prefer a 8uclidean transform applied to the real earth & and 1 distances of the o#erla$ ob*ect relati#e to user aircraft and subse%uentl$ con#ertingthe rotated &) 1 into rotatedE gauge units for the &!- displa$. The second is a #ectorsolution in which a rotated) pseudo -atN-on is computed gi#en distance and bearing. ,nthis case) distance is the distance to the o#erla$ ob*ect and bearing is the true bearingfrom user aircraft to the o#erla$ ob*ect minus the rotation angle) the aircraft groundtrack direction. Flight Sim’s built in OeoCalc #ariables are well suited for this solution.The gauge units of the pseudo -atN-on are then used to displa$ the o#erla$ ob*ect with&!-. f the two methods) , prefer 8uclidean coordinate rotation7 the code is simplerand the results are slightl$ more accurate.

8u1lidean Coordinate 3otation

+ twoBdimensional coordinate rotation ><Bd +ffine transform? applies the following matrimultiplication

where ><) $

<? are the coordinates of point >

4) $

4? after rotation of angle α around the

origin – normall$ the users aircraft. 8panding the matri produces

<

$<3

cosα Bsinα

sinα cosα

$4

4



119

< 3 4cos>α? B $4sin>α?

$< 3 4sin>α? U $4cos>α?

6ote that the rotation must be applied to real earth & and 1 distances) not the gaugeunits. Following rotation the new point) ><) $<?) is con#erted into gauge units for &!-

displa$.

The FS& &!-

where the coordinate rotation script for Track2p 3 4 starts at line 4L. +rc-en@&)

+rc-en@1 are >4) $4? and +rc-en@&<) +rc-en@1< are ><) $<?. The rotation angle) α) is

>+O/S O26D T28 T+C") radians?.



120

Ve1tor 3otation gi?en Distan1e and Bearing

The second approach creates rotated coordinates for the o#erla$ ob*ect b$ subtractingthe rotation angle from the true bearing to the o#erla$ ob*ect) then computing a pseudoE latitude and longitude gi#en distance and the ad*usted bearing. Subse%uentl$)the pseudo latitude and longitude are con#erted to gauge units for displa$ b$ &!-.efer to the diagram below.

Formulas for latitude and longitude gi#en distance and bearing can be found in theecellent reference) +#iation Formular$ #.4.QPE b$ 8d illiams) but the most con#enientwa$ to compute the pseudo latitude and longitude is to use the built in gps OeoCalc

#ariables) OeoCalc-ength) +Aimuth4) 8trapolation-atitude and 8trapolation-ongitude.



121

The FS& &!-

The #ector rotation script starts at line 4'. 8planation of the OeoCalc #ariables can befound in the FS'O/S !odule Ouidebook.

The Track2p34 rotations described abo#e are #alid in FS' at all Aoom le#els and in FS&at Aooms less than 500 km where sinusoidal pro*ection is used. 2nfortunatel$) FS&introduces an unepected incremental rotation at Aooms greater than or e%ual to 500km with the e%uidistant c$lindrical pro*ection and conse%uentl$) the rotation methods ,

use do not work. 2ntil , can determine how to predict this) , ha#e no solution forTrack2p34 for Aooms G3 500 km.

Hoom500 km G3500 km

FS' Track2p30 FS' Track2p34

FS& Track2p30 FS& Track2p34



122

6CAS <?erla2 8ample /FSX0

The maps below demonstrate a TC+S o#erla$ that can be scripted using &!-. Figure A is a Track2p 3 0 map showing all airborne traffic in the #icinit$ egan ashington6ational +irport using the +TC small black s%uare s$mbol. The small red circles inFigure B are the o#erla$ points whose gauge displa$ coordinates were generated withthe &!- pre#iousl$ described.

Figures C and D are the e%ui#alent maps but with Track2p 3 4.



123

+d#antages of a TC+S o#erla$ include

The TC+S search radius can be limited to Z<0 B =0 6! which is the

design specification for real TC+S s$stems. -a$er9ehicles displa$s allaircraft traffic in map #iew) e#en traffic in ecess of =0 6! that wouldne#er be seen b$ real TC+S.



124

+ccurate intruder alerts >/roimate Traffic) Traffic +d#isor$ andesolution +d#isor$? can be computed in real time from informationreturned b$ the ,Traffic,nfo search together with a Closest /oint of +pproach algorithm.

+n o#erla$ allows utiliAation of the CustomDraw map terrain base) if

desired. ealistic looking) alert status dependent) custom TC+S traffic s$mbols can

be displa$ed) all positioned accuratel$ with respect to the underl$ingCustomDraw mo#ing map >in TC+S mode) -a$er9ehicles would not bedispla$ed) onl$ the TC+S o#erla$ would be displa$ed?.

Some disBad#antages include 4? man$ 8lementG) <? interrogation

geometr$ that is circular rather than ellipsoidal frontBlooking.

The TC+S chapter discusses this in more detail.



125

6ransforming =auge 7nits /Mouse Cli10 to 4atO4on Coordinates:Determining Distan1e; Bearing; 4atitude and 4ongitude from a Mouse Cli1

This straight forward solution in#ol#es calculation of 6BS and 8B arc lengths >distances?

of the clicked point from the aircraft position using mouse coordinates) &!- map scalefunctions and Hoom Factor and then computing latitude and longitude from the resultingspherical angles. Distance and bearing to the mouse click point are calculated using gps#ariables after that.

,n the eample abo#e) the aircraft is holding on w$ 5 at +delaide ,nternational +irport)South +ustralia) and the airport s$mbol for Cle#e +irport) Cle#e South +ustralia >1C88?)is clicked.

!ouse functions !& and !1 return the gauge unit coordinates of the mouse click)which) in the eample) are & 5L.'Q=J<= and 1 454.05'J=0 gauge units.

The coordinate calculations that follow are #alid for Track2p30) or) top of the map isTrue 6orth. hen Track2p34) a rotation to re#erse out the aircraft ground track isre%uired for the correct latitude) longitude and bearing of the mouse click point. +fterclick -atitude and -ongitude are calculated) distance and bearing are easil$ determinedusing OeoCalc #ariables.



126

!ouse 1 >!1? %+%'-+9*,- gauge units

!ouse & >!&? +@'9I,*), gauge units

/-+68 -+T,T2D8 >-at4? E,I'9+@)%% degrees

/-+68 -6O,T2D8 >-on4? %,@'+%*K@- degrees

/lane 1 >Center1? ,-- gauge units

/lane & >Center&? )+- gauge units&!- !ap Scale 1 9')K---- 4N>4L5< gauge units?

&!- !ap Scale & 9'*9@*%* 4N>4L5< gauge units?

H Factor %-- 6!

+#erage 8arth adius ,II-'-K+ 6!

Flight Simulator & % 4 3 FS&7 0 3 FS'!ouse Delta 1 B4QL.'Q0<J0 gauge units!ouse Delta & B4'4.05P<JJ gauge units

Hoom 4L5<00 meters +rc -ength@1 >6BS? BJQ.QJ04=5 6!

Delta -atitude adians B0.0<4PQL radians

Click /oint -atitude E,,'*%*@*@ degreesCosine +#erage -atitude 0.L<5J<Q unitless

Sinusoidal /ro*ection +d*ust 4 unitless +rc -ength@& >8B? B404.0L5P5L 6!

Delta -ongitude adians B0.0=55LJ radiansClick /oint -ongitude %,K'I*@*%% degrees

A B C

1 !ouse 1 >!1? %+%'-+9*,- gauge units2 !ouse & >!&? +@'9I,*), gauge units3 /-+68 -+T,T2D8 >-at4? E,I'9+@)%% degrees

4 /-+68 -6O,T2D8 >-on4? %,@'+%*K@- degrees5 /lane 1 >Center1? ,-- gauge units6 /lane & >Center&? )+- gauge units7 &!- !ap Scale 1 9')K---- 4N>4L5< gauge units?8 &!- !ap Scale & 9'*9@*%* 4N>4L5< gauge units?9 H Factor %-- 6!10 +#erage 8arth adius ,II-'-K+ 6!11 Flight Simulator & % 4 3 FS&7 0 3 FS'12 !ouse Delta 1 3:4B:5 gauge units13 !ouse Delta & 3:<B:P gauge units14 Hoom 3:'4L5< meters15 +rc -ength@1 >6BS? 3:4<:J:'N4L5< 6!16 Delta -atitude adians 3:45N:40 radians17 Click /oint -atitude #B,ED8=388S/B%K0 degrees18 Cosine +#erage -atitude 3CS>+D,+6S>>:=U:4J?N<?? unitless19 Sinusoidal /ro*ection +d*ust 3,F>:4QG3500000):4L)4? unitless20 +rc -ength@& >8B? 3:4=:L:':4'N4L5< 6!21 Delta -ongitude adians 3:<0N>:40:4L? radians22 Click /oint -ongitude #BIJD8=388S/B)%0 degrees



127

The $ellow #ariables are the mouse click coordinates returned b$ the !& and !1functions) the #ariables in red are knowns) or gi#ens) and the rest are simplecalculations. The green #ariables are the #alues initiall$ being sought7 latitude andlongitude of the mouse click.

The e%ui#alent &!- is shown below. This should be placed within an 2pdateG sectionof the code.

-ines = B 4J The click latitude and longitude calculations.

-ines 4L B <Q The distance and bearing calculations using OeoCalc #ariables.

-ines <L – =5 -atitude) longitude and bearing calculation for the Track2p 3 4case.



128

The mouse code

-ine 4 The upper left corner of the CustomDraw map displa$ is located atgauge unit &3450) 1340. The map displa$ is 500 gauge units wide b$ Q00gauge units high. Conse%uentl$) this line establishes the entire map displa$ as aclickable area

-ine P + left mouse click enables displa$ of -atitude and -ongitude informationon the screen – a readout of the lat) lon) dist) brg calculations

-ine J + toggle that allows the calculation code to be eecuted

-ine 4< + right click disables displa$ of the lat) lon) dist) brg readout

These calculations fail to $ield accurate latitude) longitude and bearing information inthe FS& case where Aoom eceeds 500 km.

Hoom

500 km G3500 km

FS' Track2p30 FS' Track2p34

FS& Track2p30 FS& Track2p34



129

A11ura12

+ssuming the &!- !ap has been calibrated carefull$) accurac$ of coordinates calculatedfrom a mouse click is %uite acceptable , belie#e.

The crossBplots abo#e show the percent error for coordinates and distances measuredusing mouse clicks. -atitude and -ongitude errors relati#e to gps #ariables

OeoCalc-atitude and -ongitude rise with increasing Hoom Factor) but are less than about0.4 percent error through L00 6! range. Distance and :earing errors calculated usingthe Click -atitude and -ongitude are also #er$ low) a#eraging less than 0.5 percent.

To put those errors in perspecti#e) the plot below translates the errors into ph$sicalscreen piels. +t Hoom Factors less than <00 6!) accurac$ is within one ph$sical piel)or) in practical terms) essentiall$ no error. 8rrors reach up to about = ph$sical piels at

the L00 6! ange le#el.

Distan1e 8rror

0.0

0.5

4.0

4.5

<.0

<.5

=.0

=.5

Q.0

0 400 <00 =00 Q00 500 P00 J00 L00 '00

.oom Fa1tor # 3ange /!M0

! u m

e r o f P i e l s



130

e2 8Nuations

Oauge 2nits 3 !eters N >Scale Hoom Factor?

Scale 3 !eters N >Oauge 2nits Hoom Factor?

ffset -at -on gi#en 6BS and 8B arc lengths

-at< 3 -at4 U +rc-en1 N 8arthadius

-on< 3 -on4 U +rc-en& N >8arthadius cos>-at<??

-at8arthadius cos>-at<??

+rc-en1 3 >-at-on8arthadius cos>-at<??

Coordinate rotation

&4 3 0cos>a? – $0sin>a?

1 4 3 0sin>a? U $0cos>a?



131

T.$#errain A!areness Map in FSX

6AWS # =PWS J F46A

Terrain +#oidance arning S$stems are a combination of a Oround /roimit$ arningS$stem and Forward -ooking Terrain +#oidance. FS' and FS& pro#ide capabilit$ tomodel O/S !odes 4 through P) but not F-T+ – that is) FS has no &!- gauge capacit$to measure terrain ahead of the aircraft and issue F-T+ alerts as appropriate. The tablebelow summariAes terrain a#oidance modeling capabilit$ in Flight Simulator using stock

FS #ariables and &!-. +ural alerts re%uire a third part$ sound module and sound files

6AWS S"S68M 387>38M8!6S6AWS

Class A

6AWS

Class B e2 Flight Simulator Variales

adar +ltimeter e%ui red 6ot e%uired 1es FS' and FS& ++D, (8,O(T

+irdata and Computer e%uired 6ot e%uired 1es FS' and FS& 9arious s$stem #ariables >+9ars?

Oear S tate ,nput e%ui red 6ot e%uired 1es FS' and FS& +O8+ (+6D-8 /S,T,6

Flaps S tate ,nput e%uired e%uired 1es FS ' and FS & +F-+/S (+6D-8 /8C86T

Supplemental T$pe Certification e%uired 6ot e%uired 6N+ 6ot +pplicable 6ot +pplicable

Terra in +wareness !ap e%uired 6ot e%uired +ppro FS& onl$8le#ation&Color #ariablesand +/-+68 +-T,T2D8

Full $ +utonomous O/S e%ui red 6ot e%uired 1es FS' and FS& +9ars plus O/S module #ariables pro#ides

redundanc$

=PWS A4836S =PWS Mode A1ron2m e2 Flight Simulator Variales

8cessi#e ate of Descent !ode 4 8D 1es FS ' and FS & +/-+68 +-T,T2D8 and ++D, (8,O(T

8cessi#e Terrain Closure ate !ode < 8CT 1es FS' and FS& ++D, (8,O(T

6egati#e Climb ate +fter Takeoff !ode = 6C+T 1es FS' and FS& +/-+68 +-T,T2D8) ++D, (8,O(T and

+98T,C+- S/88D

Flight ,nto Terrain 6ot ,n -anding Configuration !ode Q F,T6- 1es FS ' and FS & ++D, (8,O(T) +O8+ (+6D-8 /S,T,6)and +F-+/S (+6D-8 /8C86T

8cessi#e De#iation :elow Ol ideslope !ode 5 8DOSD 1es FS' and FS& ++D, (8,O(T) +6+94 OS,

8cessi#e :ank +ngle !ode P 8:+ 1es FS' and FS& ++TT,T2D8 ,6D,C+T :+6" D8O88S

+ltitude Callout !ode P 9C 1es FS' and FS& ++D, (8,O(T

indshear /rotection !ode J S Doubtful FS' and FS& ++!:,86T ,6D & and H) but #ertical wind

speed >+!:,86T ,6D 1? not a#ailable

F46A A4836S A1ron2m e2 Flight Simulator Variales

Forward -ooking Terrain +#oidance F-T+ 6o 6one :e$ond the capabilit$ of the O/S !odule.

/remature Descent +lert /D+ 1es FS' and FS& +/-+68 +-T,T2D8 and O/S !odule #ariables

Can Be Modeled B2

Flight SimulatorQ

Can Be Modeled B2

Flight SimulatorQ

Can Be Modeled B2

Flight SimulatorQ



132

Oi#en the F-T+ limitation) howe#er) a crude Class + T+S s$stem can be built for FS&using &!- script because CustomDraw !ap can be configured to produce a Terrain +wareness !ap facsimile. This chapter focuses on the Terrain +wareness !ap.

6errain Awareness Map

2sing 8le#ation&Color #ariables and aircraft altitude) it is possible to create anapproimate T+S terrain awareness displa$. ,t is approimateE at best because thecoarse 4000 foot 8le#ation&Color inter#al combined with significant color feathering

produces an inaccurate terrain awareness map.

Two issues must be addressed for the T+S terrain awareness displa$ in FS&

8le?ation 1olor sele1tion that is a function of aircraft height abo#e terrain

6errain 3efresh needed due to aircraft altitude change

8le?ation Color Sele1tion

The chart below shows Terrain +wareness !ap colors used in a few T+S s$stems thatcan be researched online. f these) the Oarmin 500 Series B O4000 T+S color

scheme is the simplest and makes the most sense for an FS& implementation that isonl$ approimate an$wa$. The fewer colors the better in an FS& T+S map.



133

The &!- approach is to incorporate +/-+68 +-T,T2D8 conditions into the8le#ation&Color epression. The following is an eample of the 8le#ationQ000Color >=000 ft to Q000 ft ele#ation la$er? epression

4 <Elevation4000Color>

< (L:TAWS_Mode, bool) 0 == (A:SIM ON GROUND, bool) or

= if{

Q 0x6EB5C7 

5 }

P els{

J (A:PLANE ALTITUDE, feet) 5000 >

L if{

' 0x101010 

40 }

44 els{

4< (A:PLANE ALTITUDE, feet) 4000 >

4= if{ 4Q 0x00F6FF 

45 }

4P els{

4J 0x0202E3 

4L }

4' }

<0 }

<4 </Elevation4000Color>

4ines ) *' ,f the T+S switch is FF or the aircraft is on the ground) thenthe standard nonBT+S ele#ation color is used. ,n this case) it is -K8B+C* which is from the O4000 manual.

4ine K' T+S !ode. The T+S switch is 6 and the aircraft is in the air.

4ines * %-' ,f the aircraft is at an altitude greater than 5000 feet >line J?)then the top of the 8le#ationQ000Color la$er) which is Q000 feet) is more than

4000 feet below the aircraft) and according to the T+S color palette the la$ershould be colored B4AC >line '?.

4ine %%' ,f the aircraft altitude is not greater than 5000 feet) then

4ines %) %+' ,f the aircraft is at an altitude greater than Q000 feet >line 4<?)

then the top of the 8le#ationQ000Color la$er is between 0 feet and 4000 feetbelow the aircraft) and according to the T+S color palette the la$er should becolored "844<W >line 4Q?.

4ine %K' ,f the aircraft altitude is not greater than Q000 feet) then

4ine %*' The top of the terrain la$er >Q000 feet? is at or abo#e the aircraft) andaccording to the T+S color palette) the la$er should be colored 38D.



134

"ellow Band Must e %---R /or Multiples of %---R0

:ecause of the 4000 foot 8le#ation&Color inter#al) the difference between altitudes inline J and 4< must be 4000 feet) or multiples of 4000 feet. ,f not) then as the aircraft

climbs or descends past each thousand foot altitude le#el) the $ellow band will eitherdisappear or double its width for a while.

,f) for eample) line J has 5000’ but line 4< has Q<00’ instead of Q000’) then the $ellowband will disappear when +/-+68 +-T,T2D8 is between Q000’ and Q<00’. This will

repeat for the other 8le#ation&Color la$ers if the line J) line 4< ele#ations are epressedin a similar manner >i.e.) not multiples of 4000’ difference?.

Color Feathering

TerrainShadow must be disabled in T+S mode or the T+S colors will not displa$ in asatisfactor$ manner. (owe#er) when TerrainShadow 3 0) significant color feathering

occurs o#er a <000 foot ele#ation inter#al) and as well) the central color band iscentered 4000 feet below the #alue epressed in the 8le#ation&Color #ariable name.

The maps below demonstrate the effect on 8le#ationQ000Color.

Figure A is a contour map of the ,sland of (awaii) 2S+. The <000’) =000’) and Q000’

topographic contours from the FS& terrain data are displa$ed >a /hotoshop manipulationfrom 8le#ation&Color) not a direct etraction from the terrain database?.

,n Figure B) 8le#ationQ000Color 3 0=J5'JD >a chocolate brown color? andTerrainShadow 3 4. The ele#ation color uniforml$ fills the inter#al from Q000 feet to=000 feet as epected.

Figure C is the same map but with TerrainShadow 3 0 as re%uired for T+S !ode.This ob#iousl$ presents a few issues to deal with for a terrain awareness displa$. Thearea outlined b$ the dashed line is enlarged in Figure D.



135

Figure D shows that the brown color band associated with 8le#ationQ000Color is actuall$centered on the =000’ ele#ation contour and feathers out in both directions for 4000#ertical feet. Figure 8 is a crossBsectional #iew.

For an aircraft fl$ing at =000’ altitude) the bottom of the $ellow band should be at <000’ele#ation) as shown in Figure F. :ut 8le#ation&Color #ariables are a#ailable onl$ at4000’ inter#als) so the same color band applies for an aircraft fl$ing at ='''’ altitude –

the T+S map colors cannot change until the aircraft reaches Q000’ altitude.



136

+s a conse%uence of the coarse 4000’ color inter#al) a 500 foot altitude compromisebetween the two 8le#ation&Color epressions in Figure F is

The T+S map displa$ is therefore onl$ approimateE. The coarse 4000’ color inter#allimits accurac$ of the displa$ and the color edges >i.e.) black to $ellow? are featheredrather than crisp) but $ellow pro#ides such a contrast to black that the bottom of the$ellow color band is still %uite apparent.

3adar Altimeter 8le?ationXColor Adustment

+bout half of the time when close to terrain) the altitude compromise ends up being tooliberal and the terrain awareness map shows the aircraft to be in the :lack when radioaltitude is less than 4000’. To help mitigate this) , prefer to incorporate the followingradar altimeter condition as a final ad*ustment of the T+S displa$ colors

G >+/-+68 +-T,T2D8) feet?

3 =000

,sland of(awaii)2S+

>++D, (8,O(T) feet?

3 44QJ

Figure = shows the terrain awarenessmap displa$ using corresponding8le#ation&Color epressions for all theele#ation color #ariables. The aircraft is

fl$ing in a S direction at =000’altitude. ,ts radar altimeter reads 44QJfeet meaning that terrain clearance is inthe :lack T+S color band. 44QJ feetis close to the 4000 foot threshold for

1ellow T+S color and on the map) the

aircraft is close to the bottom of the 1ellow band. So in this particularsnapshot) the terrain awareness mapseems to be reasonabl$ accurate.

Detail-a$erTerrain 3 B4TerrainShadow 3 0



137

<Elevation4000Color>(L:TAWS_Mode, bool) 0 == (A:SIM ON GROUND,bool) or

if{ 0x6eb5c7 } // NON-TAWS ELEVATION COLOR els{ (A:RADIO HEIGHT, feet) 1000 <

if{(A:PLANE ALTITUDE,feet) 4000 >=

if{ 0x101010 } // BLACK els{ (A:PLANE ALTITUDE, feet) 3000 >=

if{ 0x00f6ff } // YELLOWels{ 0x0202e3 } // __ RED __

}}els{

(A:PLANE ALTITUDE,feet) 3500 >=if{ 0x101010 } // BLACK els{ (A:PLANE ALTITUDE, feet) 2500 >=

if{ 0x00f6ff } // YELLOWels{ 0x0202e3 } // __ RED __

}}}

</Elevation4000Color>

The download &!- gauges contain a complete list of 8le#ation&Color epressions.

6errain 3efresh

+fter the terrain la$er is rendered) CustomDraw !ap will not regularl$ reBe#aluate8le#ation&Color epressions and reBdraw the map as aircraft altitude changes wouldotherwise dictate. This is true e#en when 2pdate+lwa$s 3 4) or TrueE. Therefore) inT+S mode) the user must force terrain reBfresh.

This T+S map refresh approach consists of two parts

efreshing the terrain ele#ation colors Timing of the reBfresh

4a2er6errain 3efresh

efreshing the terrain ele#ation colors re%uires initiating the computation of a new)different) terrain displa$. ne wa$ to trigger this is to briefl$ change Detail-a$erTerrain to 4 >ater nl$?. The other wa$) which , recommend) is to momentaril$ change Hoom.efreshing an$ other la$er or e#en toggling -a$erTerrain) will not trigger the reBe#aluation of terrain ele#ation colors needed for the T+S displa$.



138

The new terrain does not need to be full$ displa$ed) *ust initiated) before reBsettingHoom. There is an una#oidable but momentar$ dropout of the map displa$ while thishappens.

8ample XM4 MouseT se1tion turn 6AWS Mode <n and <ff:

1 <Area Name="TAWS MODE" Left="110" Top="430" Width="35" Height="13">

2 <Cursor Type="Hand" />

3 <Click Kind="LeftSingle">

4 (L:TAWS_Mode, bool) ! (>L:TAWS_Mode, bool)

5 (L:TAWS_Mode, bool)

6 if{

7 (L:ZFactor, number) (>L:ZFactorOrig, number)

8 (L:Background_Color, enum) (>L:BkgdColorOrig, enum)

9 (L:Terrain_Shadow, bool) (>L:Terrain_ShadowOrig, bool)

10 0 (>L:Terrain_Shadow, bool)

11 0 (>L:Update_Always, bool)

12 1 (>L:Map_Priority, bool)

13 1 (>L:Map_Loading, bool)

14 65973 (>L:Background_Color, enum)

15 1 (>L:AC_Cursor_Lime, bool)

16 1 (>L:Terrain_Refresh, bool)

17 0 (>L:TCAS_Mode, bool)

18 }

19 (L:TAWS_Mode, bool) !

20 if{

21 @TAWSClose

22 }

23 0 (>L:TAWS_Counter, enum)24 </Click>

25 </Area>

4ine I' T+S !ode toggle 6 and FF.

4ine + E %@' ,nit se%uence when T+S mode is turned 6

4ine * E 9' The original settings of ke$ displa$ #ariables are stored for referencewhen T+S is turned FF and the terrain displa$ returns to normal.

4ine %-' TerrainShadow must be 0 for T+S !ode. Certain colors displa$etremel$ poorl$ when terrain shadow is enabled) among them) unfortunatel$)

red and $ellow) and black.

4ine %%' 2pdate+lwa$s 3 0. +ctuall$) this is *ust a preference) , prefer it toalwa$s be 0 otherwise the map noticeabl$ dancesE.

4ine %)' /riorit$ 3 4. /riorit$ 3 4 will significantl$ speed up terrain ele#ationcolor refresh.

4ine %I' :ackgroundColor 3 P5'J=. This is the decimal e%ui#alent of 0040404):lack. hen terrain ele#ation colors refresh) the terrain will usuall$ disappear



139

momentaril$ and onl$ the :ackgroundColor will remain. ,t is preferable to ha#ea flashE of :lack than sa$) :ackgroundColor 3 4PJ44'=5 3 0FF00FF 3!agenta.

4ine %+' The aircraft cursor s$mbol color is changed to lime. To be seen inT+S !ode) the cursor needs to be a color that contrasts with :lack) 1ellow)

ed and water :lue. -ime or white are good a choices. 2ser preference. 4ine %K' Terrain@efresh is enabled. Terrain@efresh is the code that

momentaril$ changes Hoom which causes FS& to refresh terrain.

4ine %*' ,n this eample gauge) T+S and TC+S share the same screen) soTC+S mode is disabled when T+S map is showing. 6ot a realBworld condition.

4ine %9' ,nit se%uence when T+S mode is turned FF. See T+SClosemacro below

4ine ),' The c$cle skip counter re%uired during the terrain refresh step is set toAero.

6AWSClose ma1ro

1 <Macro Name="TAWSClose">

2 (L:ZFactorOrig, number) (>L:ZFactor, number)

3 (L:Terrain_ShadowOrig, bool) (>L:Terrain_Shadow, bool)

4 (L:BkgdColorOrig, enum) (>L:Background_Color, enum)

5 0 (>L:AC_Cursor_Lime, bool)

6 0 (>L:TAWS_Mode, bool)


8 </Macro>

4ine ) E +' riginal #alues of ke$ displa$ settings are returned to preBT+Smode state

4ine K' T+S@!ode is turned off

4ine *' +n additional terrain refresh is performed. T+S@!ode30) so thestandard terrain palette will be used.



140

8ample XM4 7pdateT se1tion 6errain 3efresh:

The following is the terrain ele#ation color refresh script) placed in the 2pdate section

1 (L:Terrain_Refresh, bool)

2 if{

3 (L:ZFactor, number) (>L:ZFactorTemp, number)

4 2699 (>L:ZFactor, number)

5 (L:TAWS_Counter, enum) ++ (>L:TAWS_Counter, enum)

6 (L:TAWS_Counter, enum) 3 ==

7 if{

8 (L:ZFactorTemp, number) (>L:ZFactor, number)


10 0 (>L:TAWS_Counter, enum)

11 }

12 }

4ine ,' The current Hoom factor is stored as -HFactorTemp

4ine I' Hoom factor is set to <P'' 6!) the largest allowable Hoom. This willtrigger a reBcomputation of the 8le#ation&Color #ariables which is the goal.

4ine + K' C$cle Skipping. Terrain color calculation appears to be a multiBc$cle process. -ines 5 and P create a dela$ to allow sufficient time for theprocess to sufficientl$ progress before resetting Aoom back to normal >line L?. ,nm$ eperience) onl$ a one c$cle dela$ has been re%uired) but eperimentationwith line P ma$ be needed if the T+S !ode colors do not appear >i.e.) set the

#alue to = or more?. 4ine @' The preBrefresh Aoom factor is restored. ,n a similar manner with line Q)

this triggers a reBcomputation of the terrain but this time with 8le#ation&Color #alues that are updated b$ current aircraft altitude.

4ines 9 E %-' Terrain@efresh flag is reBset to Aero) as is the c$cle skip counter.



141

8ample XM4 7pdateT se1tion 6iming of the 6errain 3efresh:

The refresh timing script) also in the 2pdate section

1 (L:Alt500, enum) (>L:Alt500_Old, enum)

2 (A:PLANE ALTITUDE, feet) 100 + (A:RADIO HEIGHT, feet) 1000 <

3 if{ 500 } els{ 1000 } / int (>L:Alt500, enum)

4 (L:Alt500_Old, enum) (L:Alt500, enum) != (L:TAWS_Mode, bool) and

5 if{


7 0 (>L:TAWS_Counter, enum)

8 }

4ine %' The #alue of -+lt500 is stored into -+tl500@ld.

4ine ) E ,' This creates an aircraft altitude inde so that with e#er$ 500 footchange in aircraft altitude) a terrain refresh can be initiated.

o /A:3AD>< 58>=56; feet0 %--- GltU if +-- els %--- O int creates an altitude inde at 500’ or 4000’ inter#als depending upon radaraltitude. 8#en though 8le#ation&Color #ariables are limited to 4000’

inter#als and a 4000’ altitude change inde might at first seem sufficient)a 500’ inde is necessar$ at low radar altitude because m$8le#ation&Color #ariables change ele#ation color on the 4000 foot mark if+D, (8,O(T is less than 4000’ or on the 500 foot mark if it is not >thisis the adar +ltimeter 8le#ation&Color +d*ustment?.

o %-- J is used to pre#ent the inde from triggering a refresh right at the500’ or 4000’ altitude increments) where aircraft t$picall$ le#el off. ,f thisis omitted) constant minor changes in cruise altitude will force new T+S

colors. The 400 is added >U? which will create altitude inde marks >andterrain refreshes? at the Q00’ and '00’ le#el so that T+S colors will berefreshed *ust before the aircraft reaches normal cruising altitudes.

4ine I' ,f the altitude inde has changed and T+S !ode is enabled) then aterrain refresh will be triggered.

4ine K E *' The c$cle skip counter re%uired during the terrain refresh step is set

to Aero and the Terrain efresh flag is set to 4.



142

TC$ #ra$$ic Alert and Collision A%oidance System in FSX

A1nowledgements

+ discussion of Flight Simulator TC+S must begin with acknowledgement of the originalFS' TC+S de#eloped b$ +rne :artels in <00P and Doug Dawson’s reBpackaging of it forFS& use in <04<. +rne’s FS' Trafficadar module can be downloaded free of charge at

httpNNlibrar$.a#sim.netNinde.phpCat,D3fs<00Qgau >logBin) then search for DLL for

XML traffic radar / TCAS” ?

Doug’s work is also in the public domain and can be downloaded from the +9S,! -ibrar$abo#e) or from the FSDe#eloper Downloads site

httpNNfsde#eloper.comNforumNdownloads.phpdo3fileid340Q

or here >Doug’s web site?

httpNNwww.douglassdawson.caN

+rne and Doug’s work remains the standardBbearer of flight sim TC+S and use of thesemodules is highl$ recommended when de#eloping $our own TC+S gauge.

-astl$) acknowledgement is owed to !icrosoft for making ,Traffic,nfo #ariables a#ailablein FS&.

XM4 6CAS in FSX

The discussion of TC+S that follows ties together pre#ious topics such as scalecalibration) latNlon transforms) #ector rotations and ,Traffic,nfo #ariables. ,t shows themath behind simple threat identification and demonstrates one approach forde#elopment of a &!-Bbased TC+S o#erla$ that can be superimposed on CustomDraw!ap or used in a standBalone gauge.

The ,Traffic,nfo group #ariables in FS& enable interrogation and tracking of +, and

multipla$er aircraft traffic. This is the platform of an &!-Bbased TC+S s$stem for FS&.

+ll realBworld TC+S s$stems contain a traffic displa$ and some le#el of traffic threat alertcapabilit$ /roimate Traffic) Traffic +d#isor$ >T+? and esolution +d#isor$ >+?. TC+Ss$stems in use toda$ are di#ided into two groups) TC+S , and TC+S ,,. For FlightSimulator purposes) TC+S , and TC+S ,, differ in the sophistication of the alertingcapabilit$ and collision a#oidance maneu#er instructions.



143

6CAS S"S68M C<MP<!8!6S6CAS

>

6CAS

>> e2 Flight Simulator Variales

Traffic Displa$ e%uired e%uired 1es FS& ,Traffic,nfo #ariables and +/-+68 #ariables

/roimate Traffic Threshold e%uired e%uired 1es FS & ,Traffic,nfo #ariables and +/-+68 #ariables

Traffic +d#isor$ Threshold e%uired e%uired 1es FS&,Traffic,nfo and +/-+68 #ariables and Closes t

/oint of +pproach algorithm

esolution +d#isor$ Threshold 6N+ e%uired 1es FS&,Traffic,nfo and +/-+68 #ariables and Closes t

/oint of +pproach algorithm

esolution +d#isor$ !aneu#ers and Displa$ 6N+ e%uired 1es FS & ,Traffic,nfo #ariables and +/-+68 #ariables

Can Be Modeled B2

Flight SimulatorQ

,n Flight Simulator &) the TC+S Traffic displa$ o#erla$) TC+S , and TC+S ,, /roimateTraffic and Traffic +d#isor$ Status) and man$ features of TC+S ,, esolution +d#isoriescan be modeled with &!-. esolution +d#isor$ !aneu#ers and a esolution +d#isor$Displa$ are be$ond the scope of this guidebook7 howe#er) references listed at the end ofthis chapter will be useful guidance to those that want to replicate this capabilit$.

Complementar$ +s >mutual a#oidance maneu#ers or TC+SNTC+S coordination? with +,traffic are not possible in Flight Simulator because +, traffic ha#e no collision a#oidancecapabilit$.

An approa1h to XM4 6CAS in FSX

ne approach for a FS& &!-Bbased TC+S ,, s$stem is to construct it from three parts

6earest traffic search using ,Traffic,nfo #ariables

Search interrogation loop. ealBtime) continuous assessment of /roimateaircraft) Traffic +d#isor$ and esolution +d#isor$ status based on 2S F++ or,C+ TC+S ,, protocol) and computation of Oauge@&) Oauge@1 map position foreach intruder aircraft

Traffic displa$ o#erla$ for the CustomDraw map which enables the use of customtraffic bitmaps or pol$gons >i.e.) realistic looking s$mbols that change accordingto alert status? instead of the stock FS& CustomDraw traffic s$mbol.

+ general logic flow is shown on the net page. ,n m$ application) the ,Traffic searchinstructions and the interrogation loop are contained within the 2pdateG section and

the traffic displa$ o#erla$ in 8lementG.



144

,Traffic,nfo 6earest Traffic Search /arameters

C,T raffic,nfoFilter L0 >+wake and ,n +ir?

C,Traffic,nfoadius <0 6autical !iles >4Q to =0) user preference?

C,Traffic,nfo!a9ehicles =0

C,Traffic,nfo-atitude +/-+68 -6O,T2D8

C,Traffic,nfo-ongitude +/-+68 -+T,T2D8

-oop through ,ntruder +ircraft returned b$ the ,Traffic Search

,ntruder +ircraft 4 through C,Traffic,nfo-istSiAe

,nterrogate

CTraffic,nfoC/-+68 -+T,T2D8

CTraffic,nfoC/-+68 -6O,T2D8

CTraffic,nfoC/-+68 +-T,T2D8

CTraffic,nfoC98T,C+- S/88D

CTraffic,nfoCO26D 98-C,T1

Calculate

Time of Closest /oint of +pproach >ange Tau?

Time of CoB+ltitude >9ertical Tau?

+ssess

/roimate) T+ or + Status) elati#e +ltitude) 9S, +rrow

Compute

Oauge@& and Oauge@1 map position

Store

/roimate) T+ or + Status) elati#e +ltitude) 9S, +rrow

Oauge@&) Oauge@1 into -9+s or &!-9+S

6et

TC+S !ap Displa$

Displa$ 8lement

/roimate) T+ and + +ircraft S$mbol as appropriate

Displa$ using

ShiftG9alueG,ntruder@4@Oauge&N9alueGScale &3K4KNGNShiftG

ShiftG9alueG,ntruder@4@Oauge1N9alueGScale 13K4KNGNShiftG

6 e a r e s t T r a f f i c

S e a r c h

, T r a f f i c , n f o S e a r c h . e s u l t s , n t e r r o g a t i o n - o o p

T r a f f i c D i s p l a $

# e r l a $

FAA 6CAS >> Proto1ol

8ample code written for this guidebook incorporates TC+S ,, protocol described in the

following 2S F.+.+. reference) ,ntroduction to TC+S ,, 9ersion J.4E >Februar$) <044?

httpNNwww.faa.go#Ndocument-ibrar$NmediaN+d#isor$@CircularN

TC+S^<0,,^<09J.4^<0,ntro^<0booklet.pdf



145

&!- design elements include >page number refers to the F.+.+. reference?

/age 4= /roimate Traffic definition P 6! and UNB 4<00 feet

/age 4=B4Q Traffic Displa$ S$mbolog$

/age 4J Simultaneousl$ track up to =0 transponder e%uipped aircraft within anominal range of =0 nmi.

/age << TC+S Control panel switch Stand:$) T+Bnl$) and T+B+

/age <<B<= TC+S Sensiti#it$ -e#els >S-? based on TC+S control panel switchposition and altitude

/age <= Tau. TimeBtoBgo to Closest /oint of +pproach and CoB+ltitude. angeTau and 9ertical Tau alarm thresholds as indicated in Table <

Table 2. Sensitivity Level Definition and Alarm Thresholds

Own Altitude (feet) SL Tau (Seconds) DMOD (nmi) ALIM

(feet)TA RA TA RA TA RA RA

< 1000 (AGL) 2 20 N/A 0.30 N/A 850 N/A N/A

1000 - 2350 (AGL) 3 25 15 0.33 0.20 850 600 300

2350 - 5000 4 30 20 0.48 0.35 850 600 300

5000 - 10000 5 40 25 0.75 0.55 850 600 350

10000 - 20000 6 45 30 1.00 0.80 850 600 400

20000 - 42000 7 48 35 1.30 1.10 850 700 600

> 42000 7 48 35 1.30 1.10 1200 800 700

Introduction to TCAS II Version 7.1, US Department of Transportation, Federal Aviation Administration, Feb 28, 2011

ZTHR (feet)

Altitude Threshold

/age <=B<5 Distance !odification >D!D? and +ltitude Threshold >HT(? alarmthreshold modifications

/age <L Target on ground determination. +d#isor$ ,nhibit if intruder adio(eight >simplif$ing assumption? is less that =P0 feet

/age <' ,nhibit threat declaration against intruder aircraft with #ertical rates inecess of 40)000 fpm

3ange 6au and Verti1al 6au

TC+S computers primaril$ incorporate time separation calculations rather than distance

separation to determine traffic alerts. +lert criteria) or thresholds) are di#ided into#ertical and slant time components. ,n the #ertical dimension) the time to coBaltitude iscalled 9ertical Tau and in the slant >range? dimension) the time to closest point ofapproach is called ange Tau. + T+ or an + is issued onl$ when both the range tauand #ertical tau are less than certain threshold #alues that are a function of altitude>Sensiti#it$ -e#els) see Table <?.



146

ange tau is e%ual to the slant range di#ided b$ the relati#e closing speed between ownaircraft and the intruder. ,t can be calculated b$ comparing changes in slant distancefrom one ,Traffic interrogation c$cle to the net as follows

Slant@Distance4 >6!? 3 Slant Distance pre#ious interrogation c$cle

Slant@Distance0 >6!? 3 Slant Distance current interrogation c$cle

Time4 3 Time of pre#ious interrogation c$cle

Time0 3 Current time

Delta@Distance >6!? 3 Slant@Distance4 B Slant@Distance0

Delta@Time >seconds? 3 Time0 B Time4

Closing@Speed >6! per sec? 3 Delta@Distance N Delta@Time

ange Tau0 >seconds? 3 Slant@Distance0 N Closing@Speed

,Traffic,nfoCurrentDistance is a slant range distance that would appear well suited forthis calculation. (owe#er) Flight Simulator updates this #ariable e#er$ two seconds onl$)so it is not ideal for a TC+S application. Conse%uentl$) , prefer to deri#e slant distanceusing OeoCalc and s$stem #ariables as follows

Slant@Distance0 3 >OeoCalcDistance0C,Traffic,nfoC/-+68 +-T,T2D8) feet?

>+/-+68 +-T,T2D8) feet?

>+/-+68 -+T,T2D8) degrees?

>+/-+68 -6O,T2D8) degrees?

>C,Traffic,nfoC/-+68 -+T,T2D8) degrees?

>C,Traffic,nfoC/-+68 -6O,T2D8) degrees?

>Cfs'gpsOeoCalcDistance) nmiles?

9ertical tau can be sol#ed b$ an intersection of two lines method



147

DM<D and .653

T+ and + thresholds are further modified for low closure rate situations where anintruder can come #er$ close while range and #ertical tau remain abo#e standardthresholds. These modifications are discussed in the F++ TC+S ,, #J.4 reference.

Displa2 Variales and Arra2s

+t the conclusion of e#er$ ,Traffic,nfo interrogation c$cle) fi#e #alues must be calculated

and stored for each intruder aircraft to pro#ide information for a TC+S o#erla$.

4. TC+S displa$ s$mbol code >-TC+S@S$mbol) enum?) a function of alert status>ther) /roimate) T+) or +?. +n eample



148

The displa$ s$mbol code determines which TC+S s$mbol is used for the displa$.6ote that most real TC+S s$stems displa$ intruder aircraft on a black background)not superimposed on a color terrain base. ,f this is the users’ preference) then inTC+S mode) set -a$erTerrain 3 0 and :ackgroundColor 3 0040404) or create a

standBalone TC+S gauge that is not an o#erla$ for the CustomDraw map.

<. elati#e +ltitude measured in hundreds of feet=. elati#e altitude label position shift. hen the intruder is abo#e user’s aircraft)

relati#e altitude is displa$ed abo#e the TC+S s$mbol7 when the intruder is belowthe user’s aircraft) relati#e altitude is displa$ed below the TC+S s$mbol

Q. Oauge@& position of each intruder aircraft

5. Oauge@1 position of each intruder aircraft

This establishes the need for #ariable arra$s) for eample

>-TC+S@S$mbol@0) enum? thru >-TC+S@S$mbol _n, enum?>-elati#e+ltitude(undreds@0) enum? thru >-elati#e+ltitude(undreds _n, enum?

>-el+lt/ositionShift@0) enum? thru >-el+lt/ositionShift _n, enum?

>-,ntruderOauge&@0) enum? thru >-,ntruderOauge& _n, enum?

>-,ntruderOauge1@0) enum? thru >-,ntruderOauge1 _n, enum?

where @0E is the inde number of the first >nearest? intruder aircraft and “_n ” is the

inde of the last intruder aircraft returned in the ,Traffic,nfo search.

XM4Vars

Traditional -9ars can be used to create the arra$s but the code is length$. The easiestsolution utiliAes Tom +guilo’s XM4Vars module to create a d$namic #ariable arra$ each

time the ,Traffic,nfo search results are interrogated. ,n the eample TC+S gaugepro#ided in the :lack:o website) , use &!-9ars to store the interrogation results.

The &!-9ars module can be downloaded free of charge from

httpNNfsde#eloper.comNforumNdownloads.phpdo3fileid3405

Follow the installation and operation instructions contained in the ead!e file.



149

6CAS <?erla2 Displa2 8ample

Figure A shows airborne aircraft #ehicles displa$ed b$ -a$er9ehicles.

Figure B is the same displa$ but with Detail-a$er9ehicles 3 <) CustomDraw’s TC+S

s$mbol. Some drawbacks of using FS& CustomDraw’s -a$er9ehicles TC+S s$mbols

S$mbol does not change as alarm status changes. FS& does not pro#ide TC+S ,,alarm capabilit$

elati#e altitude and climbNdescent arrows are not a#ailable

+ll +, aircraft in map #iew are displa$ed) e#en those outside real TC+Sinterrogation limits

Figure C shows a TC+S &!- o#erla$ on the CustomDraw !ap base. ,Traffic,nfo searchparameters consistent with real TC+S units are used.

Finall$) Figure D shows the TC+S o#erla$ on the CustomDraw map base) but with-a$er9ehicles 3 0.



150



151

Figure 8 demonstrates the traffic s$mbol change as the intruder becomes /roimateTraffic >within P 6! distance and UNB 4<00 feet altitude?.

Figure F shows the intruder aircraft when alarm status is Traffic +d#isor$.

Figure = is alarm status esolution +d#isor$.

Figure 5 is a spot plane #iew taken at the same time.

8ample 6CAS XM4 gauge a?ailale from Bla1Bo wesite

+ full$ functional &!- gauge is a#ailable for download from the :lack:o website. ,t

demonstrates se#eral concepts discussed in the guidebook including scale calibration) click distanceE application) T+S and TC+S o#erla$.



152

EE

FF

GG

HH



153

3eferen1es

4. “Introduction to TCAS II Version 7.1”, 2S Department of Transportation) Federal +#iation +dministration) Februar$ <044

httpNNwww.faa.go#Ndocument-ibrar$NmediaN+d#isor$@CircularNTC+S^<0,,^<09J.4^<0,ntro^<0booklet.pdf

<. “ACAS II Guide Airborne Collision Avoidance System II (incorporating version 7.1)”,

The 8uropean rganisation for the Safet$ of +ir 6a#igation >82C6T-?) ;anuar$<04<

httpNNwww.eurocontrol.intNmsaNgaller$NcontentNpublicNdocumentsN+C+S@guideJ4.pdf

=. “Overview of ACAS II (incorporating version 7.1)”, The 8uropean rganisation for theSafet$ of +ir 6a#igation >82C6T-?) ;anuar$ <04<

httpNNwww.eurocontrol.intNmsaNgaller$NcontentNpublicNdocumentsNTraining@+C+S@o#er#iew.pdf

Q. "ochenderfer) !.;.) Chr$santhacopoulos) ;./.) "aelbing) -./. and -oAanoB/ereA) T.)“Model-Based Optimization of Airborne Collision Avoidance Logic”, -incoln -aborator$)!assachusetts ,nstitute of technolog$) ;anuar$ <040

httpNNwww.ll.mit.eduNmissionNa#iationNpublicationsNpublicationBfilesNatcBreportsN"ochenderfer@<040@[email protected]

5. :artels) +rne) “XML Traffic Radar 2.0.1”, ;ul$ <00P

httpNNlibrar$.a#sim.netNinde.phpCat,D3fs<00Qgau



154

"t&er pplications

ther special applications possible when &!- and CustomDraw scales are calibrated

include

Cli1 Distan1e; Bearing; 4atitude and 4ongitude

+ mouse click an$where on the map returns distance and bearing relati#e to an$

reference point such as the user’s aircraft) and the latitude and longitude of the clickedpoint.

Distance and :earing of an arbitrar$ point is a feature of the real Oarmin gps units goingback to the Q00 and 500 series >Oarmin’s !easure DistE function? that is not replicatedin Flight Simulator’s stock gps@500 gauge.

Translating !& and !1 into longitude and latitude has man$ uses.

!earest Sear1h Centered on a Mouse Cli1

Conducting a 6earest search on a point other than the user’s aircraft can be useful. ,fthe user clicks on or simpl$ near a facilit$) the latitude and longitude of the click pointcan be used in a 6earest search to return information about that facilit$ from the gps

database.

+s an eample) simpl$ clicking near an airport) $ou can displa$ information such as

runwa$s and fre%uencies without the need to manuall$ enter an ,dent or ,C+.Furthermore) the user could click on an$ Com or 6a# fre%uenc$ displa$ed in the list andha#e that fre%uenc$ entered into the +cti#e or Standb$ fre%uenc$ of a 6a#NCom radio.So) *ust a few pointBandBclicks to update 6a#NCom fre%uencies. hat’s the ,-Sfre%uenc$ of the approach , am fl$ingE Click) click and 6a#4 is tuned to the correctfre%uenc$. 6ot necessaril$ a realBworld instrument) this onl$ demonstrates what can bedone.

Add Wa2point to a Flight Plan

Click an$where on the map to add a new flight plan wa$point at that location.

Stationar2 Map rather than Mo?ing Map

The user aircraft s$mbol mo#es o#er a stationar$ map rather than the normal stationar$aircraft s$mbol o#er a mo#ing map. The effect is kind of cool actuall$) but it doesn’tha#e much use in a real cockpit.

These applications are demonstrated in the eample &!- gauges that can bedownloaded from the :lack:o website.



155

/*ample )ML Map Gauges

,ncluded in the :lack:oNCustomDraw !ap website are two &!- gauge eamples

a#ailable for download. The$ demonstrate se#eral of the topics discussed in thisguidebook) including

,Traffic,nfo #ariables

FS& map pro*ection schemes

Calibration of CustomDraw !ap and &!- o#erla$ map scales

Creation of &!- map o#erla$s and coordinate rotation transforms

Some interesting map applications can be written using &!- o#erla$s to theCustomDraw map base. The eample gauges include

TC+S !ap with functional /roimate) Traffic +d#isor$) and esolution +d#isor$alarm status and appropriate TC+S s$mbols

T+S map displa$. +s close as $ou can get with what FS& offers

Click Distance) :earing) -at and -on. Click an$where on the map to returnDistance and :earing from users aircraft) and -atitude and -ongitude of the clickpoint. This opens the door to interesting applications such as touch screenE

!FD displa$s >well) the mouse is $our finger?

6earest search centered on mouse click point rather than users aircraft. Clickan$where on the map to see details of the 40 nearest airports to the mouse click. + #ariation on this is to click on or simply near an$ airport shown on the map to

see an$ or all details about that airport that are a#ailable from the gps database – $ou don’t need to enter an ,dent or ,C+ to identif$ the airport or other facilit$$ou are interested in) *ust point to it b$ clicking on the map

Click to add a$point to Flight /lan. Click an$where on the map and add a new

wa$point at that location

Stationar$ !ap rather than normal !o#ing !ap. Click the M H M icon and the mapstops mo#ing but the airplane s$mbol starts mo#ing – like the flight map thatpassengers can #iew on an airliner. Toggle M H M nE and ffE to see mapreset feature

These are full$ functional gauges written using FS' &!- s$nta) but should be used in

FS& as the$ demonstrate some features a#ailable onl$ in FS&.

=auge Setup

The gauges are large) +)- *-- gauge units) and are intended to be set up as a

separate window in $our panel.cfg file) for eample



156

[Window19] or whate#er window number is appropriate in $our panel position=5size_mm=520,700visible=1

gauge00=FSMAP!ExampleMovingMap1, 0, 0, 520, 700

2se whate#er path information is consistent with $our panel. !$ installation has a

folder named FS!+/E in which , keep the &!- gauge file. The FS!+/ folder is locatedwithin the /anel folder of m$ aircraft.

XM4Vars

The TC+S application uses #ariable arra$s to store necessar$ information about intruderaircraft. +n eas$ wa$ to create such arra$s is through the use of Tom +guilo’s &!-9arsmodule which can be freel$ downloaded from

httpNNfsde#eloper.comNforumNdownloads.phpdo3fileid3405

Follow the installation and operation instructions contained in the ead!e file.

M2 eample gauges will not fun1tion without XM4Vars first eing installed'

Download =auge 8amples

The 8ampleMo?ingMap%'ml gauge contains all of the applications listed abo#eecept Stationar$ !ap.

The 8ampleStationar2Map%'ml gauge adds the stationar$ map feature. :ecause

so man$ reference points are changed when switching to a stationar$ map) , decided tosa#e this as a separate file. ,t is easier to understand m$ approach to making ano#erla$ b$ inspecting the script in the 8ampleMo?ingMap%'ml gauge.

Des1ription of Features

Figure % identifies the click spots of the gauges

Figure ) shows the se%uence to retrie#e Click Distance information and tocompare that with the gps module OeoCalc distances. The OeoCalc reference issetup up to function onl$ with airport facilities) not with 9s or 6D:s) foreample. 8nter the three to four character airport ,dent) not the full ,C+identifier



157

Figures , through K demonstrate the map calibration se%uence. 6ote thatmap calibration must alwa$s be done at Aooms under 500 km >i.e.) Aoom factors3 ranges 3 of <P' 6! or less?. +s well) Track2p must be set to 0) and thesimulation should not be in /ause mode. Calibration needs to be done each time

the siAe of the map changes

, recommend that the calibration se%uence be repeated to double checkconsistenc$ of !& and !1 returns. ,f the scales are different the second time)it is because the initial mouse clicks returned slightl$ different & and 1s than the

second attempt. , ha#e not figured out wh$) $et.

Figures * and @ show the process to add a new wa$point to a loaded flightplan b$ using a mouse click

Figures 9 through %% describe the 6earest search from a click point. ,n thiseample) , use the click latitude and longitude to perform a nearest airportsearch relati#e to the click point.

6ote the code within the 68+8ST +,/T S8+C( T+:-8E. , useOeoCalcDistance and OeoCalc:earing to return the distance and bearing relati#eto the user aircraft rather than displa$ing the normal distance and bearing to thenearest search origin point which in this case is not the user aircraft.

+dditionall$) , utiliAe &!-9ars to store the gauge unit & and 1 and ,dent of the40 nearest airports. The following code)

%(

(@c:NearestAirportSelectedLatitude, radians) (>L:OverlayObject_LAT, radians)

(@c:NearestAirportSelectedLongitude, radians) (>L:OverlayObject_LON, radians)

@GaugeXY

'ClikNrstY_' l31 scat @FindIndex (L:Gauge_Y, number) @WriteNumber

'ClikNrstX_' l31 scat @FindIndex (L:Gauge_X, number) @WriteNumber

'ClikNrstIdent_' l31 scat @FindIndex (@c:NearestAirportCurrentIdent) @WriteString

)

does not displa$ information as the rest of the StringG does) it is used within

the StringG loop to assign #alues to Clik6rst1) &) and ,dent arra$s.

The arra$ capabilit$ of &!-9ars is #er$ useful indeed.

Figure %) shows the T+S map operation. hen T+S mode is acti#e) theT+S click button displa$s the radar altimeter which is useful reference to ]NCthe T+S displa$



158

Figures %, and %I show the TC+S operation.

hen TC+S mode is acti#e) the number of intruder aircraft within the searchradius >=0 6! search radius and =0 aircraft maimum) in m$ eample? is

displa$ed in the TC+S click button. The ,Traffic,nfo search will return the user’saircraft as ,nde 0 with a 9,D34. 1ou might want to add 4 to the !a9ehicles toaccount for this.

The 9ehicle ,D is not a realBworld TC+S displa$ element but is included here for

]NC purposes. ,t can be toggled nBffE b$ clicking the 9,D button.

Figures %+ and %K demonstrate an airport information page.

,t is necessar$ onl$ to click on the map near the airport to identif$ it and initiate

a gps database %uer$ of airport information.

+dditionall$) the 6a# fre%uencies become mouse areas which) when clicked)

transfer the selected 6a# fre%uenc$ to the 6a#4 +cti#e fre%uenc$.

+s with the other applications) this is meant to pro#ide some ideas about whatbecomes possible when the CustomDraw and &!- map scales are calibrated.

+dditional features – the icons in the lower right toggle nBffE the following

6orth arrow !o#ing !ap – Stationar$ !ap

2ser aircraft s$mbol Cross hairs

Compass rose

Toggling !o#ing !ap – Stationar$ !ap in flight is interesting although not so applicablein a real cockpit.

Hoom !ap Aoom is achie#ed through use of the Hoom JE and E toggle. TheHFactor) or ange) is displa$ed abo#e the toggles. The height of the map is < times theHFactor.



159



160



161



162



163

Layerirports Additional &n$ormation

+dditional detail for -a$er+irports relating to airport s$mbol and tet generated b$ FlightSimulator

Airport S2mol Sie A Fun1tion of 3unwa2 4ength and .oom

The siAe >diameter? of the s$mbol is proportional to length of the longest runwa$ andthe Aoom setting. The relationship for inde < and = s$mbols for ange 3 40 and 456!iles is shown in the graphs abo#e. The minimum siAe rendered is alwa$s 40 screen

piels) and the maimum siAe) regardless of runwa$ length or Aoom) is P0 screen piels. +irport s$mbols become smaller as the map is Aoomed out. 6ote that a 40000 ft.

runwa$ has a QL piel s$mbol at ange 3 40 6!iles) but a =4 piel s$mbol at ange 345 6!iles. ,nde Q and 5 ha#e different siAe relationships but are similarl$ renderedproportionate to runwa$ length and Aoom. ,nde 4 >dot) which is alwa$s 4 screen piel?)(eliports) and Seaplane :ase ,nde <) =) and Q are not drawn according to runwa$length.



164

6etDetail4a2erAirports A Fun1tion of .oom

D8FA746 68X6 D>SP4A" .<<M 3A!=8S

FS& 4P00 4<00 FS& 4P00 '00Zoom range (m) ZoomFactor range (NM) Zoom range (m) ZoomFactor range (NM)

Runway Numbers 80 to 4,447 0.043 to 2.401 80 to 3,316 0.043 to 1.790

Frequencies 80 to 10,970 0.043 to 5.923 80 to 8,177 0.043 to 4.415

Elevation & Length 80 to 14,825 0.043 to 8.005 80 to 11,050 0.043 to 5.967

Name 80 to 22,237 0.043 to 12.007 80 to 16,575 0.043 to 8.950

Ident 80 to 148,250 0.043 to 80.049 80 to 110,500 0.043 to 59.665

Nothing 148,251 to 5,000,000 80.049 to 2699.784 110,501 to 5,000,000 59.666 to 2699.784

FSX: Permissible Zoom range for fs9gps:Map is 80 to 5,000,000 meters

FS' 4P00 4<00Zoom range (m) ZoomFactor range (NM)

Runway Numbers 100 to 8,745 0.054 to 4.722

Frequencies 100 to 21,862 0.054 to 11.805

Elevation & Length 100 to 43,725 0.054 to 23.610

Name 100 to 145,750 0.054 to 78.699Ident 100 to 291,500 0.054 to 157.397

Nothing 291,501 to 5,000,000 157.398 to 2699.784

FS9: Permissible Zoom range for fs9gps:Map is 100 to 5,000,000 meters



165

Airport S2mol 62pe <?errides 6et >nde Sele1tion

FSX: Despite user selection of a TetDetail-a$er+irports ,nde) the tet actuall$displa$ed will be limited b$ the choice of airport s$mbol – the lower theDetail-a$er+irports ,nde) the less label information that is displa$ed as summariAed inthe tables below. ,t is a little complicated) but it’s all part of the default deBclutteringscheme.

6et that is displa2ed 6et that is displa2ed

Airport S2mol > d e n t

! a m e

8 l e ? a t i o n G

3 w 2 4 e n g t h

C o n t r o l a n d

A d ? i s o r 2 F r e N

3 u n w a 2

! u m e r s

Airport S2mol > d e n t

! a m e

8 l e ? a t i o n G

3 w 2 4 e n g t h

C o n t r o l a n d

A d ? i s o r 2 F r e N

3 u n w a 2

! u m e r s

Dot E % Dot E %

Circle B ) Circle B )

Circle runwa$s E , Circle runwa$s E ,

:lock runwa$s B I :lock runwa$s B I

unwa$s B + unwa$s B +

6etDetail4a2erAirports >nde # % 6etDetail4a2erAirports >nde # I

Dot E % Dot E %

Circle B ) Circle B )

Circle runwa$s E , Circle runwa$s E ,

:lock runwa$s B I :lock runwa$s B I

unwa$s B + unwa$s B +

6etDetail4a2erAirports >nde # ) 6etDetail4a2erAirports >nde # +

Dot E %

Circle B )

Circle runwa$s E ,

:lock runwa$s B I

unwa$s B +

6etDetail4a2erAirports >nde # ,

8ample %: 8#en if TetDetail-a$er inde is +)onl$ ,dent and 8le#ation w$ -ength will bedispla$ed if the airport s$mbol inde is 4) <) or =.

8ample ): unwa$ 6umbers are displa$ed onl$when airport s$mbol and tet inde are both 5.



166

Font 62pe; Font Sie and 4ael <ffset

FSX: fs'gps!ap uses an +rial font) rasteriAed without antiBaliasing.

+t Aoom le#els of JQ4< meters and below >a #er$ AoomedBin #iew?) font height is Lscreen piels) and placement of the tet >offset of the upper left corner of the ,dent or6ame? is 4P screen piels right and ' screen piels up from the airport location. +n$additional lines of tet are listed below this.

+t Aoom le#els of JQ4= meters and greater >AoomedBout #iew?) font height is J screenpiels) and placement of the tet is 4= screen piels right and L screen piels up fromthe airport location. +n$ additional lines of tet are listed below this.

These are the onl$ two siAe and offset #ariations. The$ are automatic and cannot bechanged.

FS9: fs'gps!ap uses Courier 6ew font) rasteriAed without antiBaliasing. ,t demotes to

+rial font as Hoom increases. The font height and offsets are shown in the chart below.The$ are automatic and cannot be changed.



De0cluttering

!ap s$mbols need to be reduced in siAe or remo#ed from displa$ as Hoom increases >as $ou

Aoom out?. This is known as deBcluttering. The stock gps@500 gauge decluttering settingsare shown below. +dditionall$) CustomDraw has default deBcluttering settings as described

throughout the guidebook.

Sto1 gpsH+-- DeE1luttering s1heme

Case Step: )I ), )) )% )- %9 %@ %* %K %+ %I %, %) %% %- 9 @ * K + I , ) %

!auti1al Miles .oom; 3ange /!M0

3ange; .oomFa1tor /!M0: ) - - -

% + - -

% - - -

+ - -

, + -

) - -

% + -

% - -

+ -

, +

) -

% +

% -

+ ' -

, ' +

) ' -

% ' +

% ' -

- ' + * K

- ' , ) 9

- ' ) I *

- ' % K +

- ' - @ )

- ' - - -

b*ectDetail-a$er+irports (e 0 5 5 5 5 45 45 45 45 45 45 45 4F 4F 5F 5F 5F 5F 5F 5F 5F 5F 5F 5F

b*ectDetail-a$er+irports Decimal 0 5 5 5 5 <4 <4 <4 <4 <4 <4 <4 =4 =4 '5 '5 '5 '5 '5 '5 '5 '5 '5 '5

TetDetail-a$er+irports ,nteger 0 0 0 0 0 0 0 0 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

TetDetail-a$er9s ,nteger 0 0 0 0 0 0 0 0 0 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

TetDetail-a$er,-Ss ,nteger 0 0 0 0 0 0 0 0 0 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

TetDetail-a$er6D:s ,nteger 0 0 0 0 0 0 0 0 0 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

TetDetail-a$er,ntersections ,nteger 0 0 0 0 0 0 0 0 0 0 0 4 4 4 4 4 4 4 4 4 4 4 4 4

Documents

CustomDraw Map Guidebook v1.0