Characters (ClassID=30)
Dennis_Static100000030
Mei_Static101000030
Nathan_Static102000030
Nathan_Walking103000030
Nathan_Dancing104000030
Nathan_Standing105000030
Carla_Static105500030
Carla_Walking106000030
Carla_Standing107000030
Claudia_Static107500030
Claudia_Walking108000030
Claudia_Standing109000030
Eric_Static109500030
Eric_Walking110000030
Eric_Standing111000030
Manuel_Static111500030
Manuel_Walking112000030
Manuel_Standing113000030
Sophia_Static113500030
Sophia_Walking114000030
Sophia_Standing115000030
Calibration Board (ClassID=40)
CheckerBoard100000040
CirclePattern100100040
Ground Vehicle (ClassID=50)
Standard_Car_Blue100000050
Light-Emitting Object (ClassID=60)
Light_White100000060
Light_Red101000060
Light_Green102000060
Light_Blue103000060
Light_Purple104000060
Light_Yellow105000060
Light_Aqua106000060
Light_White_Strong107000060
Light_Red_Strong108000060
Light_Green_Strong109000060
Light_Blue_Strong110000060
Light_Purple_Strong111000060
Light_Yellow_Strong112000060
Light_Aqua_Strong113000060
Light_Dark114000060
Fixed-Wing (ClassID=100)
Flying_Wing100000100
Fixed_Wing110000100
Circular Ring (ClassID=150)
Ring_Target_Blue100000150
Ring_Target_Green101000150
Square Ring (ClassID=151)
Quad_Target_Red100000151
Quad_Target_Green101000151
Quad_Target_Blue102000151
Spherical (ClassID=152)
Sphere_Target_Red100000152
1.2 Free Version 3D Scene
3DDisplay
CameraRoom
ChallengeMap
Changsha
Denver
EarthMap
Grasslands
LightShow
LowGPU
MapData
MapDataHongkong
MapSmall
MatchScene
MatchScene2
MountainTerrain
MountainTerrain_Water
MoutainRoad
NeighborhoodPark
OldFactory
SLAMScene
VisionRing
VisionRingBlank
WhiteMap
II. Full Version and Above Resources
The following resources are available only in the Full Version and above.
2.1 Full Version 3D Models
Quadcopter (ClassID=3)
F450_Default10000000337-37-29 cm (static mesh)
Droneyee_QuadX33010100000353-50-21 cm (static mesh)
Droneyee_QuadX20010110000329-29-11 cm (static mesh)
DJI_Phantom_White10200000329-28-16 cm (static mesh)
DJI_Phantom_Red10300000329-28-16 cm (static mesh)
DJI_Phantom_Army10400000329-28-16 cm (static mesh)
AR_Drone_BlackGreen10500000351-51-11 cm (static mesh)
AR_Drone_Blue10600000351-51-11 cm (static mesh)
AR_Drone_Army10700000351-51-11 cm (static mesh)
Quad_Fold_Gray10800000335-34-12 cm (static mesh)
Quad_Fold_Army10900000335-34-12 cm (static mesh)
Hexacopter (ClassID=5)
HexaCopter_5501000000548-55-39 cm (static mesh)
Octocopter (ClassID=8)
Octocopter10000008133-134-77 cm (static mesh)
X8 Coaxial (ClassID=10)
X8_OCTO1000001056-56-25 cm (static mesh)
Human (ClassID=30)
Dennis_Static100000030239-70-268 cm (skeletal animation)
Mei_Static101000030239-70-268 cm (skeletal animation)
Nathan_Static102000030239-70-268 cm (skeletal animation)
Nathan_Walking103000030239-70-268 cm (skeletal animation)
Nathan_Dancing104000030239-70-268 cm (skeletal animation)
Nathan_Standing105000030239-70-268 cm (skeletal animation)
Carla_Static105500030239-70-268 cm (skeletal animation)
Carla_Walking106000030239-70-268 cm (skeletal animation)
Carla_Standing107000030239-70-268cm (skeletal animation)
Claudia_Static107500030239-70-268cm (skeletal animation)
Claudia_Walking108000030239-70-268cm (skeletal animation)
Claudia_Standing109000030239-70-268cm (skeletal animation)
Eric_Static109500030239-70-268cm (skeletal animation)
Eric_Walking110000030239-70-268cm (skeletal animation)
Eric_Standing111000030239-70-268cm (skeletal animation)
Manuel_Static111500030239-70-268cm (skeletal animation)
Manuel_Walking112000030239-70-268 cm (skeletal animation)
Manuel_Standing113000030239-70-268 cm (skeletal animation)
Sophia_Static113500030239-70-268 cm (skeletal animation)
Sophia_Walking114000030239-70-268 cm (skeletal animation)
Sophia_Standing115000030239-70-268 cm (skeletal animation)
Calibration Board (ClassID=40)
CheckerBoard100000040Calibration board 60cm_84cm_60mm
CirclePattern100100040Calibration board 60cm_84cm_60mm
Ground Vehicle (ClassID=50)
Standard_Car_Blue100000050272-118-62cm (static mesh)
Car_GreenBlack10100050502-226-171cm (static mesh)
Car_Red10200050502-226-171cm (static mesh)
Car_White10300050502-226-171cm (static mesh)
Engineering Vehicle (ClassID=51)
Roller810900051Static Mesh
Roller911800051Static Mesh
paver11900051Static Mesh
Trunk12500051Static Mesh
Light Emitters (ClassID=60)
Light_White100000060Emissive Material
Light_Red101000060Emissive Material
Light_Green102000060Emissive Material
Light_Blue103000060Emissive Material
Light_Purple104000060Emissive Material
Light_Yellow105000060Emissive Material
Light_Aqua106000060Emissive Material
Light_White_Strong107000060Emissive Material
Light_Red_Strong108000060Emissive Material
Light_Green_Strong109000060Emissive Material
Light_Blue_Strong110000060Emissive Material
Light_Purple_Strong111000060Emissive Material
Light_Yellow_Strong112000060Emissive Material
Light_Aqua_Strong113000060Emissive Material
Light_Dark114000060Emissive Material
Fixed-Wing (ClassID=100)
Flying_Wing10000010075-167-18 cm (static mesh)
Fixed_Wing110000100750-1464-240 cm (static mesh)
Circular Ring (ClassID=150)
Ring_Target_Blue10000015050-959-2763 cm (static mesh)
Ring_Target_Green10100015050-959-2763 cm (static mesh)
Square Ring (ClassID=151)
Quad_Target_Red10000015150-2050-4025 cm (static mesh)
Quad_Target_Green10100015150-2050-4025 cm (static mesh)
Quad_Target_Blue10200015150-2050-4025 cm (static mesh)
Spherical (ClassID=152)
Sphere_Target_Red100000152100-100-100 cm (Static Mesh)
Winged Aircraft (ClassID=201)
FSV9001000020145-89-22 cm (Static Mesh)
Bomber (ClassID=208)
EastBomberSU24100002082398-1682-620 cm (Animation Blueprint)
Helicopter (ClassID=229)
Helicopter110000229198-1178-334 cm (Animation Blueprint)
Fixed-Wing - UltraStick (ClassID=234)
UltraStick25E10000234134-152-39 cm (Animation Blueprint)
Tailsitter (ClassID=243)
Tailsitter1000024343-101-50 cm (Animation Blueprint)
J150 (ClassID=251)
FSJ1501000025131-21-21 cm (Animation Blueprint)
FS310 (ClassID=310)
FS310100031054-57-30 cm (Animation Blueprint)
Submarine (ClassID=600)
Submarine210000600(1766-2399-1521) 0.1 cm (Animation Blueprint)
Standard VTOL (ClassID=602)
StandardVtol210000602143-249-32 cm (Animation Blueprint)
Communication Effects (ClassID=802)
Virtual Pipeline (ClassID=803)
Target (ClassID=809)
2.2 Full 3D Scene
3DDisplay
CameraRoom
ChallengeMap
Changsha
Denver
DesertTown
EarthMap
Grasslands
LightShow
LowGPU
MapData
MapDataHongkong
MapSmall
MatchScene
MatchScene2
MountainTerrain
MountainTerrain_Water
MoutainRoad
NeighborhoodPark
OldFactory
SLAMScene
VisionRing
VisionRingBlank
WhiteMap
3. Custom Scenario Import
Required Files for RflySim3D Scenarios
A complete simulation scenario in RflySim3D requires two types of information:
1. Scenario File (****.umap)
After cooking, copy the scenario file from the directory
【UE Project Main Folder】\Saved\Cooked\WindowsNoEditor\【Project Name】\Content
to the directory
【Installation Directory】\RflySim3D\RflySim3D\Content.
Notes:
- After cooking and copying, do not rename the files or folders, nor create new folders under
\RflySim3D\Content. Renaming must be performed only within the UE editor.
- Each
****.umap map file (note: the name may differ before and after cooking) corresponds to an independent 3D scene. RflySim3D/RflySimUE5 automatically scans all .umap files in the PX4PSP\RflySim3D\RflySim3D\Content directory.
- The height below the horizontal plane in the scene must not exceed 50 m. This is determined by the reference altitude of the initial point in the CopterSim DLL model, specified by the
ModelParam_envAlitude parameter in the init.m file. To ensure the lowest point in the scene lies above the horizontal plane, the lowest point in the scene should be set as the scene reference point. The following uses the OldFactory scene as an example to illustrate this process:
First, import the scene into RflySim3D, visually estimate the lowest point in the scene, and double-click to read its elevation data. Here, it is found that the lowest point in this scene lies 70 m below the horizontal plane.

Therefore, open the Level Blueprint of this scene in UE, and set the lowest point in the scene (7000 cm below the horizontal plane) as the reference point—equivalent to shifting the entire scene upward by 70 m. Save the Level Blueprint, then repackage and import the scene into RflySim3D.

2. Terrain Elevation Data (****.png)
Before importing the scene, observe and record the approximate dimensions of the scene in the UE editor (unit: centimeters). After cooking and importing the scene into RflySim3D, use the RflyScanTerrainH (terrain scanning) command in RflySim3D with a range slightly larger than that of the ****.umap scene (unit: meters). This will generate corresponding ****.png and ****.txt files in the PX4PSP\RflySim3D directory, storing the elevation data and terrain calibration/range information, respectively. Copy these two files into PX4PSP\CopterSim\external\map to complete the import.
Notes:
- The PNG terrain file is essentially a 2D matrix stored in image format, containing the elevation map of the scene. Storing the matrix in PNG format enables efficient compression of the elevation matrix, thereby saving storage space.
- The PNG elevation file does not include information such as coordinate origin, scale, or scene boundaries. Therefore, a calibration file is required. The RflySim platform uses a TXT file to input a 9-dimensional or 12-dimensional array (the latter includes additional latitude, longitude, and altitude geodetic reference information) to provide calibration data.
3. Terrain Calibration Data (****.txt)
The TXT calibration file in the platform stores the 3D coordinates of three points:
- The top-right 3D point (both x and y are positive, z positive upward),
- The bottom-left 3D point (both x and y are negative, z positive upward),
- A third 3D point (its position can be chosen freely; theoretically, it should have a significant height difference relative to the first two points to help calibrate the vertical scale).
All units are in centimeters. The first two points define the terrain’s range and center coordinates, while the third point aids in height scale calibration.
Additionally, when using Cesium-based global large-scale scenes in RflySim3D (available only in the Personal Advanced Edition and above), the TXT file may include 3D GPS terrain data after the above 9-dimensional data. The GPS data should be entered in the order of latitude, longitude, and altitude, and can be configured to match the reference coordinate displayed in QGroundControl.