Despegue: FPV Racing de drones – Guía de configuración de telemetría de drones

En Despegue: FPV Racing de drones, Puedes enviar datos de telemetría de drones a otros lugares fuera del juego. Esto le permite verificar vuelos o solucionar problemas con otros programas que funcionan con despegue.

Esta característica en el despegue: FPV Drone Racing le permite examinar los datos de vuelo y diagnosticar cualquier problema. Más, it enables you to interact with external software that connects with Liftoff, enhancing your overall experience.

Who benefits from this?

The Drone Telemetry feature in Liftoff: FPV is geared toward players seeking highly detailed feedback or researchers interested in analyzing drone behavior. It’s not typically used by the average player, but rather by those looking to extract and analyze data for various purposes such as plotting it in other software or training AI models.

Configuración

How to enable the Drone Telemetry feature:

Para ventanas users, navegar a:

C:\Users\%userprofile%\AppData\LocalLow\LuGus Studios\Liftoff\

Para macos users, ir a:

~/Library/Application Support/LuGus Studios/Liftoff/

Para linux users, the directory is:

~/.config/unity3d/LuGus Studios/Liftoff/

Once in the appropriate directory, create a new file named TelemetryConfiguration.json. This action will activate the drone telemetry feature.

Please note that as of now, there isn’t a built-in option within Liftoff to enable or adjust this feature. Sin embargo, this functionality may be included in a future update.

Telemetry Data Configuration

Configuring the Drone Telemetry data stream involves the TelemetryConfiguration.json file, with two main parameters to adjust:

1. Data End Point: Este parámetro, etiquetado «EndPoint,» specifies where the telemetry data is sent. It’s formatted as an IP endpoint, como «127.0.0.1:9001,» where you specify the IP address and port number.
2. Stream Format: This parameter allows you to select which telemetry data points you want and the order in which they’re sent. El «StreamFormat» is a string array defining the sequence. Here are the supported data points and their layouts:
   • Timestamp: Current flight timestamp, reset to zero when the drone is reset.
   • Position: Drone’s world position as a 3D coordinate, with X, Y, and Z components.
   • Actitud: Drone’s world attitude as a quaternion, with components X, Y, Z, and W.
   • Girosía: Drone’s angular velocity rates for pitch, roll, and yaw.
   • Aporte: Drone’s input at that time, including throttle, guiñada, pitch, and roll.

Recordar, this data stream is only available for drones actively simulated by Liftoff and won’t work for drones being spectated in multiplayer or during replay sessions.

Modifying the Configuration While In-Game

Whenever the drone is reset in Liftoff, the game automatically checks if the telemetry configuration file has been modified. If any changes are detected, Liftoff reloads the configuration without requiring a full restart. This convenient feature allows you to adjust parameters on the fly without interrupting your gameplay experience.

In case there’s an error in the configuration file, Liftoff will notify you with a popup message after the drone reset. Simply correct the error in the file, reset the drone again, and Liftoff will load the updated telemetry configuration seamlessly. This iterative process ensures smooth adjustments and troubleshooting without the need for restarting the game each time.

Example Configurations

Here are some example configurations for the TelemetryConfiguration.json file:

1. Todo:
   • This configuration sends all telemetry data to a local endpoint.
   • Endpoint: 127.0.0.1:9001
   • Stream Format: Timestamp, Position, Actitud, Girosía, Aporte
   • Total size of each data frame: 60 bytes

{
  "EndPoint": "127.0.0.1:9001",
  "StreamFormat": [
    "Timestamp",
    "Position",
    "Actitud",
    "Girosía",
    "Aporte"
  ]
}

Horizontal position over time:

• This configuration sends only the drone’s position in the XZ-plane, along with the timestamp, to a local network endpoint.
• Endpoint: 192.168.1.6:6808
• Stream Format: Timestamp, PositionX, PositionZ
• Total size of each data frame: 12 bytes

{
  "EndPoint": "192.168.1.6:6808",
  "StreamFormat": [
    "Timestamp",
    "PositionX",
    "PositionZ"
  ]
}

From input to gyroscope:

• This configuration correlates input axes to the drone’s gyroscope without including a timestamp.
• Endpoint: 127.0.0.1:9001
• Stream Format: InputPitch, GyroPitch, InputRoll, GyroRoll, InputYaw, GyroYaw
• Total size of each data frame: 24 bytes

{
  "EndPoint": "127.0.0.1:9001",
  "StreamFormat": [
    "InputPitch",
    "GyroPitch",
    "InputRoll",
    "GyroRoll",
    "InputYaw",
    "GyroYaw"
  ]
}