SEARCH AND RESCUE

A possible career activity that users will face in Microsoft Flight Simulator 2024 is to fly some kind of search and rescue mission. In these activities you have to take an aircraft (plane or helicopter) and fly off in search of missing people in arid deserts or dense forests. Users will have to scour the wilderness and scan every nook and cranny for signs of distress, then use their piloting expertise to land and recover people safely. If you wish your aircraft to be used on this kind of activity you will need a preset that has been appropriately set up as part of the Modular SimObject, as explained below.

Example Of An Aircraft Flying A Search And Rescue Activity

 

For more information on the various other career activities and how to prepare your aircraft, please see here:

 

 

Search And Rescue Constraints

When it comes to setting up aircraft for the available search and rescue activities, there are a few requirements that must be fulfilled, depending on the aircraft being used. The following constraints are applicable to all aircraft types:

 

  • The aircraft will need to have the navigation_graph_pilot.cfg (as explained here).
  • The aircraft will need to have the ApronWithoutCovers.flt file (as explained below).
  • The operating_status must be either "in_service" or "experimental".
  • The aircraft cannot be flagged as military.
  • The aircraft cannot be flagged as premium.
  • The aircraft ui_max_range must be greater than 1.
  • Correct navigation graph set up as explained in Navigation Graph Setup section, below.

 

There are also some additional constraints depending on the type of aircraft being set up for search and rescue.

 

  • For planes, the following constraints will also be applied:
    • The object_class must be "Airplane".
    • The aircraft complexity must also be simple, as explained here: Note On Aircraft Complexity.
    • The aircraft can only have big wheels, for landing gear.
    • There must be a navigation graph called navigation_graph_rescue.cfg with the following nodes: RTC_SAR_VICTIM_ENTRANCE, RTC_SAR_VICTIM_AIRCRAFT_ENTRANCE, and SIT. This is explained in more detail below.

    Following the constraints given here will give the aircraft the COF_Cabin type. See here for more information: Note On Cabin Codes

 

  • For rotorcraft, the following constraints will also be applied:
    • The object_class must be either "rotorcraft" or "tiltrotor".
    • The engine_type must be either "Piston" or "Helo-Turbine"
    • The landing gear must be either wheels or skids.
    • There must be a navigation graph called navigation_graph_rescue.cfg (for regular search and rescue missions) or navigation_graph_hoist_rescue.cfg (for hoist rescue activities). The details of the nodes that are required by these graph files are given below.
    • If the rotorcraft is to be used on Hoist Rescue Missions, the model will need a RESCUE_ROPE_ATTACH helper node in one of the glTF files. This node should be placed on the part of the hoist apparatus where the rope should be spawned, and should be present on at least LOD0 and LOD1.
      Example Of The Position For The RESCUE_ROPE_ATTACH Model Helper Node

    Following the constraints given here will give the aircraft the SAR_Cabin type. See here for more information:Note On Cabin Codes

 

Once the aircraft model has been prepared for search and rescue activities and the Modular SimObject has been created with a preset that uses the adapted model parts and respects the constraints, the next thing to do would be to add in the required navigation_graph.cfg files. One thing that all these navigation graphs have in common is the need to set up mass stations and station loads for weight distribution. These things are explained in detail here: Weight Distribution.

 

 

Plane Search And Rescue

The navigation graph for planes to participate in search and rescue missions needs to be called navigation_graph_rescue.cfg. Within this file you will need the following nodes:

Placement Of The NavGraph Nodes For A Plane Rescue Activity

 

  • RTC_SAR_VICTIM_ENTRANCE
    This is the node where a person to be rescued will be spawned. It should be projected on the ground, around 5-6m from the aircraft, and the node heading should be pointed towards the aircraft entrance. You can place this node multiple times, to have multiple people being rescued, but note that for each of these nodes you place, you will need a corresponding RTC_SAR_VICTIM_AIRCRAFT_ENTRANCE node and - inside the aircraft - a SIT node as well.

 

  • RTC_SAR_VICTIM_AIRCRAFT_ENTRANCE
    This is the node where a rescued person will enter the aircraft. It should be projected on the ground, close to the aircraft entrance, and the node heading should be pointed towards the aircraft entrance as well. You should have the same number of these as you do RTC_SAR_VICTIM_ENTRANCE nodes. Once placed, you will need to connect the nodes using an edge.

 

 

 

Rotorcraft Search And Rescue

The navigation graph for rotorcraft to participate in search and rescue missions needs to be called navigation_graph_rescue.cfg. Within this file you will need the following exterior nodes:

Position Of The Exterior Nodes For Helicopter Rescue Activities

 

  • RTC_SAR_VICTIM_ENTRANCE
    This is the node where a person to be rescued will be spawned. It should be projected on the ground, around 5-6m from the aircraft, and the node heading should be pointed towards the aircraft entrance. You can only have one of these nodes and it requires a corresponding RTC_SAR_VICTIM_AIRCRAFT_ENTRANCE node and - inside the aircraft - a VICTIM_SEAT node as well.

 

  • RTC_SAR_VICTIM_AIRCRAFT_ENTRANCE
    This is the node where the rescued person will enter the aircraft. It should be projected on the ground, close to the aircraft entrance, and the node heading should be pointed towards the aircraft entrance as well. Once placed, you will need to connect the node to the corresponding RTC_SAR_VICTIM_ENTRANCE using an edge.

 

  • RTC_SAR_RESCUER_ENTRANCE
    This is the node that defines where the rescuer will spawn into the world at the start of the rescue mission, as a short RTC animation plays. The node heading should be pointed towards the aircraft entrance. You can only have one of these nodes and it requires a corresponding RTC_SAR_AIRCRAFT_ENTRANCE node and - inside the aircraft - a RESCUER_SEAT node as well.

 

  • RTC_SAR_AIRCRAFT_ENTRANCE
    This is the node where the rescuer will enter the aircraft at the end of the RTC animation. It should be projected on the ground, close to the aircraft entrance, and the node heading should be pointed towards the aircraft entrance as well. Once placed, you will need to connect the node to the corresponding RTC_SAR_RESCUER_ENTRANCE using an edge.

 

For the interior of the rotorcraft, the navigation_graph_rescue.cfg will need the following additional nodes (there should only be one of each of these):

Position Of The Interior Nodes For Helicopter Rescue Activities

 

  • DOOR
    This node is where the rescuer will position themselves to help the person being rescued into the rotorcraft.

 

  • VICTIM_ENTRANCE
    This is the node where the person being rescued will enter into the aircraft, helped by the rescuer.

 

  • RESCUER_SEAT
    This is the node that defines where the rescue worker will kneel while in the rotorcraft.

 

  • VICTIM_SEAT
    This is the node that defines where the person being rescued will kneel while in the rotorcraft.

 

  

Rotorcraft Hoist Search And Rescue

The navigation graph for rotorcraft to participate in search and rescue missions where a hoist is required needs to be called navigation_graph_hoist_rescue.cfg. Within this file you will need the following exterior nodes:

Position Of The Exterior Nodes For Helicopter Hoist Activities

 

  • RTC_SAR_HOISTOPERATOR_ENTRANCE
    This is the node that defines where the hoist operator will spawn into the world at the start of the rescue mission, as a short RTC animation plays. The node heading should be pointed towards the aircraft entrance. You can only have one of these nodes and it requires a corresponding RTC_SAR_AIRCRAFT_ENTRANCE node and - inside the aircraft - a HOISTOPERATOR_SEAT node as well.

 

  • RTC_SAR_RESCUER_ENTRANCE
    This is the node that defines where the rescuer will spawn into the world at the start of the rescue mission, as a short RTC animation plays. The node heading should be pointed towards the aircraft entrance. You can only have one of these nodes and it requires a corresponding RTC_SAR_AIRCRAFT_ENTRANCE node and - inside the aircraft - a RESCUER_SEAT node as well.

 

  • RTC_SAR_AIRCRAFT_ENTRANCE
    This is the node where the rescuer and hoist operator will enter the aircraft at the end of the RTC animation. It should be projected on the ground, close to the aircraft entrance, and the node heading should be pointed towards the aircraft entrance as well. Once placed, you will need to connect the node to the both the RTC_SAR_HOISTOPERATOR_ENTRANCE and RTC_SAR_RESCUER_ENTRANCE nodes using edges.

 

For the interior of the rotorcraft, the navigation_graph_hoist_rescue.cfg will need the following additional nodes (there should only be one of each of these):

Position Of The Interior Nodes For Helicopter Hoist Activities

 

  • DOOR
    This node is where:
    • the rescuer worker will leave the aircraft.
    • the hoistoperator will position themselves to operate the hoist.
    • the person being recued and rescue worker will enter the aircraft.

 

  • HOISTOPERATOR_SEAT
    This is the node that defines where the hoist operator will kneel while in the rotorcraft.

 

  • RESCUER_SEAT
    This is the node that defines where the rescue worker will kneel while in the rotorcraft.

 

  • VICTIM_SEAT
    This is the node that defines where the person being rescued will kneel while in the rotorcraft.

 

 

FLT Files

When a user starts a search and rescue activity they will not be going through the usual Preflight checks, and so they will need to have an ApronWithoutCovers.flt file in the aircraft preset for the activity instead of the Apron.flt. This file should be set up like a regular apron FLT file, however you should ensure that the following parameters and sections are setup correctly: