Remote Controller

Mobile phone remote controller support. Listens for UDP connections from the BeamNG Remote Control app, creates virtual input devices, and bridges accelerometer/button data to vehicle controls.

Public Functions

Network Protocol

Connection Flow

1. App sends: beamng|<deviceName>|<code>
2. Server validates code, creates virtual input device
3. Server responds: beamng|<code>
4. App sends binary orientation data (16 bytes: {w, x, y, z} as floats)

Input Mapping

Module State

Usage Example

-- Get the pairing code (also starts the UDP listener)
local code = core_remoteController.getQRCode()
if code then
  print("Pairing code: " .. code)
end

-- Check if any devices are connected
if core_remoteController.devicesConnected() then
  print("Remote controller active")
end

Device Lifecycle

• Discovery: Random 5-digit code generated on extension load
• Connection: Virtual input device created via core_input_virtualInput
• Timeout: Devices disconnected after 10 seconds of no packets
• UI Feedback: Vehicle outgauge data sent back to app for dashboard display

Notes

• Requires FFI for binary packet parsing (ori_t struct: 4 floats).
• Virtual devices are named "vinput" .. deviceInstance.
• Supports multiseat - each remote device can be assigned to a different player.
• The app port is listenPort + 1 (4445 by default).
• Network byte order is reversed for the orientation struct.

See Also

• virtualInput - Virtual input device creation
• multiseat - Multi-player input assignment