Add missing parameters to telemetry for plugins

cicci8ino

Active member
Hi,

As rF2 (already asked many times on Discord for clarification and on the forum here without ever getting a response), it seems that LMU is missing some relevant data in the telemetry. I'm talking about at least:
- TC level/mode
- TC power cut level
- TC slip angle
- Fuel mixture/Motor map
- ABS level
- Engine temperature for some cars, i.e. P2
- Water temperature for some cars, i.e. P2
- ARB
For hybrid/electric engines:
- Temperature (available as mEletricBoostMotorTemperature and mElectricBoostWaterTemperature)
- Deployment mode (electric engine power)
- Regen mode
- Recharge state (available as mBatteryChargeFraction and mElectricBoostMotorState)
Considering that the shared memory plugin is working without any change, I assume you are still using the exact rF2 Internal structures and invoking the same exported plugin functions. Therefore these parameters are probably not yet exposed by LMU too.

I kindly ask you to share if this is planned or will ever be planned.

I always hide MFD and I always rely on external devices for all the telemetry (i.e. external USB screen driven by SimHub). It would be awesome to get these values too.
It might be possible to get the same values via reverse engineering and direct memory reading but I don't think that's a viable and stable option for most of the user.

Thanks
 
Last edited:
I think it's a complicated subject.
If you open too many data, it will open the gate of automated scripts or exploits.
Today there is already some "weak" data.
In Closed practice, i can see other players running on track on my radar and relative. That gives me data i shouldn't have.

The good request would be to open those data only in "Private" mode, like pure solo and not "in game" to avoid exploits in R1aces, imo.

Then you can "work" those data, with overlays etc. but not in Race with other real players.

There is no "cheat" here, but it may open a few "exploits" if some data are too open/accessible.
No it's not complicated, we mainly need read only value so no problem.
 
It would also be nice a parameter that tells if the car has damage or not because the current 8 contact points does not show damage until there is a certain amount of contact points.
 
@herve45

The tires temps in lmu in game are not the aktual temps . Its avarge from carcass and surface inner middle outer
This works for some cars where it's off by a couple of points of a degree but with Hypercars and some others the (carcass+Inner(left, centre, right)/4) isn't correct and is off a few degrees.
 
((([GameRawData.CurrentPlayerTelemetry.mWheels01.mTireInnerLayerTemperature01]+
[GameRawData.CurrentPlayerTelemetry.mWheels01.mTireInnerLayerTemperature02]+
[GameRawData.CurrentPlayerTelemetry.mWheels01.mTireInnerLayerTemperature03])/3)+([GameRawData.CurrentPlayerTelemetry.mWheels01.mTireCarcassTemperature]))/2-273.15
This works for some cars where it's off by a couple of points of a degree but with Hypercars and some others the (carcass+Inner(left, centre, right)/4) isn't correct and is off a few degrees.
 
This works for some cars where it's off by a couple of points of a degree but with Hypercars and some others the (carcass+Inner(left, centre, right)/4) isn't correct and is off a few degrees.
thats off by a half degree because you musst take left,center and right in the formula

DataCorePlugin.GameRawData.CurrentPlayerTelemetry.mWheels01.mTemperature01,2,3
carcass
and DataCorePlugin.GameRawData.CurrentPlayerTelemetry.mWheels01.mTireInnerLayerTemperature01,2,3 and you have it
 
With the last update (1.3.3.1) the WebSocket UI has been removed. This API contained the breakdown of penalties by driver. Does anyone know if there is another way to access that information?

EDIT: Is very strange, the API is available, but not working always 😵‍💫
 
Last edited:
Something is totally broken with the APIs. “mFuelFraction” used to be updated twice per lap; now it updates whenever it feels like it.
 
Back
Top