From FSDeveloper Wiki
Jump to: navigation, search

Pilots earn Rewards for completing various missions, and reaching specific accomplishments throughout the game, (in 'Free Flight').

Some of these rewards exist as hidden Easter Eggs to be discovered by pilots. Some missions have multiple and hidden rewards, receipt being dependent on performing additional actions.

Achieved rewards are viewable in the user's pilot records.

Available In

Free Flight

FSX comes with some rewards which you've probably seen, for things like your first landing and first ten landings. These rewards are obviously not granted explicitly by a mission action, so how do they work?

Each 'free flight' reward needs to have an additional section added to it's definition, the 'Criteria'. These are detailed in the SDK and cover things like the number of landings, types of aircraft flown and airports landed at. You can combine these in any way you like to come up with your specific criteria. When the sim detects that each of the requirements has been met, your reward is granted.


In a mission, a reward can be granted explicitly using a GrantRewardAction. This gives you fine control over exactly what requirements the reward has.

For mission-based rewards you shouldn't define Criteria because FSX will pick that up and possibly grant the reward outside the mission, (unless that criteria is for having completed another mission).


Like the other mission elements, Rewards are created as an XML file. Unlike the others, they must be compiled before they can be used.

To create/edit an XML file, you must use a pure text-editor, e.g. Notepad

You must not use a wordprocessor, e.g. Wordpad, Word, etc., as these insert control/formatting characters into the xml.

See Tools section below.

Example XML

The XML file looks like this:

<FSData version="9.0">
  <Reward    rewardId = "{00000000-0000-0000-0000-000000000000}"
                 name = "Demo Reward"
          description = "Postcard for doing something right"
                 type = "POSTCARD"
               bitmap = "Images\small-1.jpg" 
   rewardDetailBitmap = "Images\big-1.jpg"
   <Criteria landings="3" differentAirports="2"/>

As with all other XML, it is very sensitive and removing any symbols, or changing the case of the keywords, will break it. You should be able to see which bits have to be changed though.

Field values are wrapped in double-quote characters.
Field values must not include -

  • Additional double-quote " characters within your text. Instead use single-quotes ' characters.
    • Incorrect - description="Thank you for visiting the home town of Virgil "Gus" Grissom, Mitchell, IN, 6.5 NM south of KBFR".
    • Correct   - description="Thank you for visiting the home town of Virgil 'Gus' Grissom, Mitchell, IN, 6.5 NM south of KBFR".
  • The ampersand character &. Instead use the word 'and'.
    • Incorrect - name="Ben & Jerry's"
    • Correct   - name="Ben and Jerry's"
  • Extra spaces prefixing or suffixing filenames.
    • Incorrect - rewardDetailBitmap=" Grissom_large.bmp "
    • Correct   - rewardDetailBitmap="Grissom_large.bmp"
  • Extra characters in ICAO fields.
    • Incorrect - RewardAirport ident="(KBFM)"
    • Correct   - RewardAirport ident="KBFM"


The rewardId is a GUID (unique identifier), name and description are free text.

Create the GUID using -

Recommend the latter, it's part of several MS SDKs, but available standalone for Exchange.


The type element must be one of this list:



Finally, the two bitmap elements must point to images, either JPG or BMP, which show small and detailed icons for your new reward.
The bitmap image is the small icon, at 100 x 80 pixels, (wide x high),
the rewardDetailBitmap image is larger at 300 x 370 pixels, (wide x high), and is shown as part of the more detailed information.

If creating a large number of rewards, recommend using jpgs rather than bmps.
Example - For a file comprising 250 rewards, the resulting compiled reward file for -

  • BMPs - Was a ludicrously large 91 MB.
  • JPGs - Was less than 4 MB.


There are a few different criteria you can set.


Filtering by the number of hours the player has flown in a particular aircraft type is done with a RewardHours element and can be one of the following:

  • ANY
  • DAY
  • VFR
  • IFR

For example, to grant a reward after the player has flown five hours at night:

<RewardHours hoursType="NIGHT" hours="5.0" />


Filtering by the airports the player has been to is done using a RewardAirport element. You need to specify the four-letter airport code rather than the name.

This would allow FSX to grant the reward after the player has landed at Heathrow:

<RewardAirport ident="EGLL" />


Finally, you can make a reward dependent on the player having already achieved another reward.

<DependantRewardId rewardId="{a guid}" />

An entire Criteria section may look something like this:

  <Criteria landings="3" differentAirports="2"
    <RewardHours hoursType="NIGHT" hours="5.0" />
    <RewardAirport ident="EGLL" />
    <DependantRewardId rewardId="{a guid}" />

... which would mean that FSX would automatically grant this reward after the player has -

  • landed at Heathrow


  • flown for five hours at night,


  • already been granted another reward with a specific GUID


  • made at least three landings at two different airports.

You don't need to specify all the types of criteria, only the ones you want to use.


If you're using the reward as part of a mission, don't leave the Criteria section there, even empty,
otherwise FSX will grant the rewards automatically because it will see it has having a criteria of "0 landings at 0 different airports" -
which is achieved just by running the sim.

To Sort

Data type & size to be incorporated

    <xs:attribute name="rewardId" form="unqualified" type="stGuid" use="required" />
    <xs:attribute name="type" form="unqualified" type="stReward" use="required" />
    <xs:attribute name="name" form="unqualified" type="stString48" />
    <xs:attribute name="description" form="unqualified" type="stString1024" />
    <xs:attribute name="bitmap" form="unqualified" type="stString1024" use="required" />
    <xs:attribute name="rewardDetailBitmap" form="unqualified" type="stString1024" use="optional" />
    <xs:attribute name="rewardDetailDescription" form="unqualified" type="stString1024" use="optional" />

It's not the logbook file, it's grantedrewards.bin
Both are re-read on flight completion.

No GrantReward call is required.

The GUID is essential,
it's whats stored in the grantedrewards.bin,
this is compared against the content of rewards folder.

Achieved reward's images are held within the .rwd file,
and displayed conditional to GUIDs stored in grantedrewards.bin.
Removing a .rwd file will cause non-display of that image.

Recompiling the reward with a different GUID, will allow you to re-earn the reward.

CRITERIA are AND only.
OR can be achieved within mission logic goals.


Tools overview blurb.

OS Tools

Available with the OS.

Tool Description Rating OS
Tool Name Descriptive blurb * * * * * XP
Tool Name Descriptive blurb * * * * * Vista
Tool Name Descriptive blurb * * * * * XP
Tool Name Descriptive blurb * * * * * Vista

3rd Party Tools

From 3rd party sources.

Tool Description Rating Availability URL
Tool Name Descriptive blurb * * * * * Payware Download Page (SizeMb)
Tool Name Descriptive blurb * * * * * Freeware Download Page (SizeMb)
Tool Name Descriptive blurb * * * * * Payware Download (SizeMb)
Tool Name Descriptive blurb * * * * * Freeware Download Page (SizeMb)



Compiling Rewards - Compilation of a reward xml file.


If you haven't found what you're looking for here, then we'd recommend, (in order of preference) -

  • AVSIM - Mission downloads (newest first).