While most XML files will have elements that are unique to the type of environmental content being created, there are some elements that are more general in use, and that can be used in multiple different contexts within the different XML files. This page documents these general elements and lists all the places where they can be used.

 

 

<Vertex />

This sub-element is used to add a vertex position to another element either as a fixed point or as a bias . Note that you should only use one of the following set of attributions for a single vertex, and that this is a self-closing element:

 

AttributeDescriptionTypeRequired
latLatitude of the vertex, in degrees between -90.0° and 90.0°.Float

Yes

(only if biasX and biasY are not used)

lonLongitude of the vertex, in degrees between -180.0° and 180.0°.Float

Yes

(only if biasX and biasY are not used)

biasX

Bias from airport reference along the longitudinal axis in meters. Please note that this is only used by the following object types:

Float

Yes

(only if lat and lon are not used)

biasZ

Bias from airport reference along the latitudinal axis in meters. Please note that this is only used by the following object types:

Float

Yes

(only if lat and lon are not used)

splineIf this attribute is set to "TRUE", then the vertex being defined will be considered a point on a spline, creating a "smooth" curved corner between the other vertices.BoolNo

 

This element can be used in the following places:

<CarParking><Polygon><GeoPol><Apron><PaintedPolygon><PaintedLine><PaintedHatchedArea><DetailPoly><EdgeLights><VectorPlacement><BlastFence><BoundaryFence>

 

 

<BiasXYZ />

This element is used to add an X, Y, Z bias in meters to the placement of an object. The acceptable range of values is unbound, but it is recommended that biases only be applied for small distances.

 

AttributeDescriptionTypeRequired
biasXBias along the longitudinal axis in meters.FloatYes
biasYAltitude bias in meters.FloatYes
biasZBias along the latitudinal axis in meters.FloatYes

 

This element is used in the following places:

  1. <VisualModel>
  2. <SceneryObject>
  3. <AttachedObject>

 

 

<Coloration />

This element can be used to change the color blending for an element. Note that this is a self-closing element and has the following attributes:

 

AttributeDescriptionTypeRequired
redRed component of the coloration (between 0 and 255).IntegerYes
greenGreen component of the coloration (between 0 and 255).IntegerYes
blueBlue component of the coloration (between 0 and 255).IntegerYes
alphaAlpha component of the coloration (between 0 and 255).IntegerNo
overrideOverride any base color already added.BooleanNo

 

This element is used in the following places:

  1. <Runway>
  2. <TaxiwayPath>
  3. <Apron>
  4. <Helipad>

 

 

<Material />

This element can be used to change the material used for another element. Note that this is a self-closing element and has the following attributes:

 

AttributeDescriptionTypeRequired
guidThe unique GUID of the material to use. You can find more information on GUID's here: GUIDsStringYes
typeThe type of blending to use for the material.

String:

  1. "Base tiled"
  2. "Base and tire marks"
  3. "Base and end cap"
  4. "Border"
  5. "Center"
  6. "Patch"
  7. "Tire gum"
Yes
tilingUThe texture tiling along the width of the runwayFloatYes
tilingVThe texture tiling along the height of the runwayFloatYes
widthRatio of the width of the item being textured with the material. A value of 1 would be full width.FloatNo
falloffThe distance in meters of alpha blending at the edges. Note this does not permit any suffixes like other distance values and is in meters only.FloatNo
opacityThe material opacity from 0 - 255.IntegerNo

 

This element is used in the following places:

  1. <Runway>
  2. <TaxiwayPath>
  3. <TaxiwayPath>

 

 

<WorldScript />

This element can be used to define a script file that is attached to the scene elements and is used by the <SceneryObject> element and <AttachedObject>. Note that this is a self-closing element and has the following attribute:

 

AttributeDescriptionTypeRequired
containerTitleThe container title of the SimObject to use.StringYes

 

 

<Ndb>

This element is either used to define general NDB navigation beacons added to scenery (see Scenery Editor Object XML), or - when used as a sub-element of the <Airport> element - it is used to add an NDB to the airport facility database.

NOTE
Editing NDB data may prevent the simulation performing further automatic updates to the navigation data for the airport. Please see the following section for more information: Note On Navigation Data

 

For example:

<?xml version="1.0" encoding="UTF-8"?>
<FSData version="9.0">
    <Ndb lat="-31.28611115" lon="-64.20872218" alt="1604F" type="H" frequency="262.0" magvar="2.00000000" region="SA" ident="H" name="CORDOBA" >
        <VisualModel name="{2fb72c66-290c-4727-b970-da20984cee83}" />
    </Ndb>
</FSData>

 

This element may contain a <VisualModel> sub-element and has the following attributes:

 

AttributeDescriptionTypeRequired
latLatitude of the NDB beacon, in degrees between -90.0° and 90.0°.

Float

Yes
lonLongitude of the NDB beacon, in degrees between -180.0° and 180.0°.FloatYes
altAltitude of the NDB beacon, in meters. You may add the "F" suffix to convert the value to feet, for example: "13.0F".

Float

Yes
altTypeThis is used to determine the referential for the alt field.

Enum:

  1. GEOID
  2. ELLIPSOID
No
typeThe type of NDB being used.

Enum:

  1. COMPASS_POINT
  2. H
  3. HH
  4. MH
Yes
frequencyThe NDB frequency in KHz, from 0.0 to 1737.0.StringYes
rangeRange of NDB in meters or nautical miles. If no suffix is supplied, then the range will be set in meters, however using the "N" suffix converts the range into nautical miles, eg: "45N". If this attribute is not set, it will default to "27N".StringNo
magvarMagnetic variation at the NDB to True North in degrees. Negative for values to the east and positive for values to the west, measured in degrees between -360.0° and 360.0°.FloatYes
regionThe beacon region code (maximum 3 characters, based on iso-3166-2).StringYes
identICAO code identity for this beacon, with a maximum of 8 characters.StringYes
nameFriendly name for ILS beacon.StringNo
bfoRequiredWhen set to "True", a beat frequency oscillator is required to receive audio ident.BoolNo

 

 

<Vor>

This element is used to define VOR navigation beacons added to scenery (see Scenery Editor Object XML) or to elements.

NOTE
Editing VOR data may prevent the simulation performing further automatic updates to the navigation data for the world. Please see the following section for more information: Note On Navigation Data

This element may contain the following sub-elements:

  1. <Dme />
  2. <VisualModel>

 

For example:

<?xml version="1.0" encoding="UTF-8"?>
<FSData version="9.0">
    <Vor lat="-41.14027786" lon="-71.18877770" alt="2800.00000000F" type="HIGH" frequency="117.40" magvar="-9.00000000" region="SA" ident="BAR" name="SAN CARLOS DE BARILOCHE" nav="TRUE" dmeOnly="FALSE" dme="TRUE" >
        <Dme lat="-41.14027786" lon="-71.18877770" alt="2800.00000000F" />
        <VisualModel name="{c0b537c3-808a-48ba-8eff-e1ca1a872e84}" />
    </Vor>
</FSData>

It has the following attributes:

 

AttributeDescriptionTypeRequired
latLatitude of the VOR beacon, in degrees between -90.0° and 90.0°.

Float

Yes
lonLongitude of the VOR beacon, in degrees between -180.0° and 180.0°.FloatYes
altAltitude of the VOR beacon, in meters. You may add the "F" suffix to convert the value to feet, for example: "13.0F".

Float

Yes
altTypeThis is used to determine the referential for the alt field.

Enum:

  1. GEOID
  2. ELLIPSOID
No
typeThe type of VOR being used.

Enum:

  1. LOW
  2. HIGH
  3. TERMINAL
  4. VOT
Yes
frequencyThe VOR frequency in MHz, from 108.0 to 117.95.StringYes
magvarMagnetic variation at the VOR to True North in degrees. Negative for values to the east and positive for values to the west, measured in degrees between -360.0° and 360.0°.FloatYes
rangeRange of the VOR in meters or nautical miles. If no suffix is supplied, then the range will be set in meters, however using the "N" suffix converts the range into nautical miles, eg: "45N". If this attribute is not set, it will default to "27N".StringNo
regionThe beacon region code (maximum 3 characters, based on iso-3166-2).StringYes
identICAO code identity for this beacon, with a maximum of 8 characters.StringYes
nameFriendly name for the beacon.StringYes
navBooleanYes
dmeOnlySets whether the beacon should be considered as only DME. If set to "TRUE" then the dme attribute should also be "TRUE" and a <Dme /> element should be added.BooleanYes
dmeSets whether the beacon should also have DME. If "TRUE" then a <Dme /> element should be added.BooleanYes
tacanSets whether the VOR is part of a Tacan system or not.BooleanNo

 

 

<Dme />

This is a sub-element of <Vor> and is used to set up the DME for the beacon. It is a self-closing element and can have the following attributes:

 

AttributeDescriptionTypeRequired
latLatitude of the DME, in degrees between -90.0° and 90.0°.

Float

No
lonLongitude of the DME, in degrees between -180.0° and 180.0°.FloatNo
altAltitude of the DME, in meters. You may add the "F" suffix to convert the value to feet, for example: "13.0F".

Float

No
altTypeThis is used to determine the referential for the alt field.

Enum:

  1. GEOID
  2. ELLIPSOID
No
rangeRange of the DME in meters or nautical miles. If no suffix is supplied, then the range will be set in meters, however using the "N" suffix converts the range into nautical miles, eg: "45N". If this attribute is not set, it will default to "27N".StringNo

 

 

<VisualModel>

This element is used to add a single visual model to an element. This element may also contain <BiasXYZ /> data and can have the following attributes:

 

AttributeDescriptionTypeRequired
headingHeading of the model placement, between 0.0° and 360.0°.

Float

No
imageComplexity

Minimum image complexity setting in Microsoft Flight Simulator 2024 for the objects to appear. For example, objects set at NORMAL will appear if the setting is DENSE, but not appear if the setting is SPARSE.

IMPORTANT! This element is DEPRECATED in Microsoft Flight Simulator 2024. It should not be used and is only listed here for legacy context.

Enum:

  1. VERY_SPARSE
  2. SPARSE
  3. NORMAL
  4. DENSE
  5. VERY_DENSE
No
nameGUID of desired model object. You can find more information on GUID's here: GUIDsGUIDYes
instanceIdOptional GUID used to identify this instance of the VisualModel element. You can find more information on GUID's here: GUIDsGUIDNo

 

This element is used in the following places:

  1. <Ndb>
  2. <Vor>