Over the years I have noticed it difficult to simulate camera streams on simulated drones at geo-specific locations. In addition, existing options for geo-specific image generation are tied to simulators. This project aims to only handle the image generation portion of drone simulation. Because of this, the project is extensible, distributable and usable with any existing PX4 or Ardupilot drone simulator.
An image generator is a application that can perform rendering of perspectives in distributed simulations. This is a common approach in professional aerospace flight simulators. For example in a large projector flight simulator room, the resolution of the view may be too high for a single computer to render. In this case, image generators are deployed to multiple computers which are in charge of rendering portions of the view.
Demo Video 1: Plane and Copter Demo Video 2: Ardupilot Follow Mode
This project leverages Cesium for unity to bring geo-specific 3d map tiles into Unity. I have currently elected to use Google Maps as my 3d map tile provider. The map tile provider may be configurable in the future. The project then leverages FFmpeg to create video streams from the Unity cameras. The location of aircraft are brought into Unity using a websocket connection to a mavlink2REST server.
-
Game Engine: I considered using Unreal Engine, or GoDot as an alternative to Unity. Unreal would have worked just as well, however I am more familiar with unity and feel like the environment is easier to use. I did look at goDot, which would have been good because it would have alieviated licensing concerns some organizations will likely have with Unity. However, Godot did not have a Ceisum plugin and I did not want to write one.
-
Aircraft State Data Interface: Mavlink2REST While I could have used mavlink directly over UDP or TCP, I elected to use MAVLink2REST, because it allows for mavlink over websockets, which will allow for TLS encryption and enable the mavlink data to sit behind a reverse proxy, such as in the Intelligent Quads Cloud Simulator
- Use 3d Map tiles to be able to have 3d image generation from any where in the world
- generate udp h264 video streams from unity cameras
- support multiple aircraft
- create configuration file system to be able to configure
- number of cameras
- camera settings
- aircraft meshs
- surface deflections and prop rotations
- in game menus for configuring settings
- modelling of mavlink based gimbal control
- load in custom aircraft meshes
- add ground clipping system to allow ground vehicles to move across the terrain
- support multiple map tile providers
- Set time of day
- Set weather conditions
- Some amount of world customization
- generate a maps API key from google. follow this tutorial
- Download the latest release from the releases page
- unzip the release
- copy the file
config.json.exampletoconfig.json - configure the
config.jsonfile in theIntelligent Quads Image Generator_Data/StreamingAssetsfolder- set the
"tileURL": tohttps://tile.googleapis.com/v1/3dtiles/root.json?key=<your google maps api key> - set the
"mavlink2RestURL"to a mavlink2rest server. if using inteligentquads.com as the sim backend set it to"wss://sim.intelligentquads.com/<uuid>"if using the example simulation set it to"ws://127.0.0.1:6040"
- set the
The Image generator loads the file config.json from the Intelligent Quads Image Generator_Data/StreamingAssets folder. The configuration file is a json file that allows you to configure cameras for each aircraft in the simulation.
here id an example config file
{
"tileURL": "https://tile.googleapis.com/v1/3dtiles/root.json?key=<YOUR_API_KEY>",
"mavlink2RestURL" : "ws://127.0.0.1:6040",
"vehicles" : [
{
"id" : 1,
"cameras" : [
{
"id": 1,
"position" : [3, 0, 0],
"orientation" : [0, 0, 0],
"vFOV" : 26,
"streamingEnabled" : "false",
"encoding" : "H264Nvidia",
"destination" : "udp://192.168.1.255:5600"
},
{
"id": 2,
"position" : [3, 0, 0],
"orientation" : [0, -90, 0],
"vFOV" : 26,
"streamingEnabled" : "false",
"encoding" : "H264Nvidia",
"destination" : "udp://192.168.1.255:5601"
}
]
},
{
"id" : 2,
"cameras" : [
{
"id": 1,
"position" : [3, 0, 0],
"orientation" : [0, 0, 90],
"vFOV" : 26,
"streamingEnabled" : "false",
"encoding" : "H264Nvidia",
"destination" : "udp://192.168.1.255:5610"
}
]
}
]
}cameras will automatically spawn on aircraft based on the number of cameras in each of the cameras arrays.
Note: there does not need to be entry for each aircraft in the simulation. Aircraft are spawned into the world via their mavlink heartbeat. The simulation will automatically spawn an aircraft mesh based on their vehicle type in the heartbeat message. If you would like an aircraft to have a camera attached to it you must add an entry for that aircraft in the vehicles array with the associated camera configuration.
- Use
cto cycle through follow cameras - follow cameras can be repositioned by using
wasdand scroll wheel - press
escto bring up menu. Note menu is not yet functional
This project provides a simulation environments in a docker compose file. There is an environment provided for ArduCopter and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are arducopter and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile arducopter up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
Note: I usually run my simulator on a virtual machine with a bridged network adapter. This should work in WSL, but I have not tested it.
I am not planning on adding CIGI support to this project, because I do not have an immediate need for it. However, I am open to pull requests that add CIGI support.