BeamNG OutGauge bug: Coolant temp stuck at 92°C and jumps with throttle

Racing Simulators BeamNG Drive
1

Hello RealDash Support Team,

I am reaching out to report a persistent and very frustrating bug regarding the telemetry connection between BeamNG.drive and RealDash via the UDP OutGauge protocol. I have spent hours trying to debug this on my tablet, but it happens on absolutely every single dashboard/skin in the app, meaning it is a core application issue.

The Problem:
The engine coolant temperature gauge is completely broken. Most of the time, it is frozen exactly at 92°C (acting like a default placeholder value). However, whenever I press the throttle pedal in the game, the coolant temperature needle suddenly jumps straight to the maximum value, and then drops back to 92°C as soon as I release the gas. It behaves as if the coolant temperature input is somehow bound to or overwritten by the throttle position or boost pressure data bytes.

What I have already tried to fix this (none of it helped):

  1. I verified the game data using the in-game “Engine Thermal Debug” UI widget. The game engine calculates and shows the coolant temperature absolutely correctly (it rises and falls naturally).
  2. I double-checked the input bindings in RealDash. The gauge is correctly assigned to ENGINE/ECU INPUTS: Coolant Temperature.
  3. I tried creating a completely blank new gauge from scratch, but it shows the exact same behavior (stuck at 92°C, jumps with throttle).
  4. I changed the UDP ports in both the game and RealDash (moved from 4444 to 4445) to eliminate any network port conflicts, but the bug persists.
  5. Other temperature inputs, such as Oil Temperature, work flawlessly on the exact same connection.

Crucial Fact:
I tested the exact same car and connection setup on the same device using another telemetry application (Sim Dashboard), and the coolant temperature works perfectly fine there. This proves that BeamNG.drive is broadcasting the correct data over OutGauge, but RealDash’s built-in decoder is misinterpreting the data bytes, causing the coolant temperature channel to conflict with the throttle input and lock into a failsafe 92°C mode.

Please look into the BeamNG.drive OutGauge byte-mapping parser and fix this issue in the upcoming update. RealDash has amazing interactive dashboards, and I really want to use it, but this bug makes it impossible to monitor basic engine vitals.

Thank you for your time and help!