[REL] TinyPedal - open source overlay APP for rF2 (Radar,Pedal,FFB,Deltabest,Relative,Fuel calculator)

It is because the dallara IR18 official DLC does not use the new electric motor physics that introduced with those new BTCC. The IR18 DLC still uses the old "engine mixture" internally that emulates P2P function (397 did not update this car to use the new electric motor physics), which is why battery & P2P data is not available for this car.

 

ok thx domage...

 

Thanks, I can confirm there are no issues with Windows Defender with the newer versions.

 

v2.11.0 - Fuel Calculator & Brake performance Widget
https://github.com/s-victor/TinyPedal/releases/tag/v2.11.0

Major new features:

• "Brake performance Widget" to help track braking efficiency in live action.
• "Wheel lock" & "Wheel slip" plotting in Trailing Widget to help find braking and acceleration grip limits.
• "Fuel Calculator" to help prepare race fuel more easily, including session fuel usage history data that can be used for calculation.

2.11.0 (2024-03-28)

• [New]Fuel calculator
  • New "Fuel Calculator" can be accessed from Tools menu in main window.
    Editable options:
    • Lap time (minute:second:millisecond), can be auto-filled by Reload.
    • Tank capacity (liter or gallon), can be auto-filled by Reload.
    • Fuel consumption (liter or gallon), can be auto-filled by Reload.
    • Race length in minutes.
    • Race length in laps.
    • Formation/Rolling.
    • Average pit stop in seconds.
    • Starting fuel (liter or gallon).
      Output values:
    • Total required race fuel (liter or gallon).
    • End stint remaining fuel (liter or gallon).
    • Total required pit stops.
    • One less pit stop fuel consumption (liter or gallon).
    • Total laps can run based on "Total fuel" value.
    • Total minutes can run based on "Total fuel" value.
    • Average refueling (liter or gallon) per pit stop.
  • "Reload" button to load fuel usage & stint data from recent sessions
    into calculator without having to manually set values.
  • "History" table which lists "lap number", "lap time", "fuel consumption",
    "remaining fuel" data from recent sessions.
    Invalid lap time or fuel consumption data is highlighted in red.
  • Select any "lap time" or "fuel consumption" values from history table,
    and click "Add selected data" to send value to calculator.
    Select multiple values of same column and click "Add selected data" button
    to calculate average reading of selected values and send to calculator,
    which can be useful for planning long race.
    See user guide "Fuel calculator" section for details.
• [New]Brake performance Widget
  • Show transient max braking rate (g) from last braking input,
    and resets after 3 seconds.
  • Show max braking rate (g), and resets after a set period of time
    that defined by "max_braking_rate_reset_delay" value in Force Module.
  • Show max braking rate difference (g) against
    transient max braking rate, and resets on the next braking.
  • Show max braking rate difference (g) in percentage (%) instead.
  • Show front and rear wheel lock duration (seconds)
    per lap under braking.
    Duration increases when tyre slip ratio has exceeded
    "wheel_lock_threshold" value, and resets on first
    braking input of a new lap.
• Gear Widget
  • Add "battery_bar_color_regen" option,
    which shows energy regeneration color indicator for battery bar.
• Instrument Widget
  • Changed "wheel_lock_threshold" default value to "0.3".
• Trailing Widget
  • Add "show_wheel_lock" option,
    which shows wheel lock (slip ratio) plot under braking
    when slip ratio has exceeded "wheel_lock_threshold" value.
    Default plot style is yellow dots.
    Default "wheel_lock_threshold" value is "0.3".
  • Add "show_wheel_slip" option,
    which shows wheel slip (slip ratio) plot under acceleration
    when slip ratio has exceeded "wheel_slip_threshold" value.
    Default plot style is purple dots.
    Default "wheel_slip_threshold" value is "0.1".
  • Fixed plot lines that kept drawing after game paused.
• Force Module
  • Add "braking rate" calculation and output.
  • Add "max_average_g_force_reset_delay" option,
    which sets time delay (in seconds) for resetting
    max average g force. Default is "30" seconds.
  • Add "max_braking_rate_reset_delay" option,
    which sets time delay (in seconds) for resetting
    max braking rate. Default is "60" seconds.
  • Renamed "max_g_force_freeze_duration" option
    to "max_g_force_reset_delay" for consistency.
• Fuel Module
  • Add fuel "consumption history" logging and output for Fuel Calculator.
    Currently fuel log is not saved to user file, which resets after APP closed.
• [New]Wheels Module
  • "Wheels Module" now calculates and outputs wheel radius
    and slip ratio data for other modules and widgets.
• Config Window
  • Add "Spectate Mode Enabled" status notification,
    which shows when spectate mode is enabled.
    Click on the notification will show Spectate tab.
  • Add "Tools" menu, moved all editors to "Tools" menu.
• Shared Memory API
  • Always use direct access for "rF2ForceFeedback" and "rF2Extended"
    which don't require synchronizing.
  • Reduced "pause" detection timeout duration from 5s to 2s.
• Misc
  • Added Fuel calculator, Brake performance Widget, Wheels Module info in User Guide.
  • Updated Trailing Widget, Force Module info in User Guide.

Thanks to @DanRZ for suggestions and testing feedback.

New changes in user guide:
Fuel calculator: https://github.com/s-victor/TinyPedal/wiki/User-Guide#fuel-calculator
Brake performance widget: https://github.com/s-victor/TinyPedal/wiki/User-Guide#brake-performance
Trailing widget: https://github.com/s-victor/TinyPedal/wiki/User-Guide#trailing
Force module: https://github.com/s-victor/TinyPedal/wiki/User-Guide#force
Wheels module: https://github.com/s-victor/TinyPedal/wiki/User-Guide#wheels

 

One suggestion for the trailing widget: by default the brake trail (red) should be over the gas one (green) when they are overlapping.
This is important during trail-braking, when the amount of brake input is difficult / impossible to see if the gas green line is over it.

 

v2.11.1 - add plot draw order for Trailing Widget
https://github.com/s-victor/TinyPedal/releases/tag/v2.11.1

Here is a quick small update that adds an important "draw order" feature to Trailing Widget, as requested by @coasting&cruising. Braking line is now placed at top by default.

 

Nice update. With bigger lines for slip/brake some lines can be hidden, and that ensures readability.

 

Recently there have been reports about LMU game crashes since game last update, and some users were confused and thinking that game crash was caused by TinyPedal.

Here is clarification to some of the misunderstandings, and possible solution.

First, TinyPedal currently does not, in any way, directly interact with either RF2 or LMU. TinyPedal only accesses and reads shared memory data that outputs by rF2sharedmemory plugin. If there are any game crashing issues, they are likely caused by other reasons, and user should consider report game crash issue to game bug report forum instead.

Secondly, both RF2 and LMU are known to have issues with anti-virus false-positive issues (for example, mostly from Windows Defender), which was also listed in LMU's known issues in this page:
https://community.lemansultimate.co...i-virus-interfering-with-le-mans-ultimate.16/

And a common cause of game crash issue could come from this anti-virus issue that falsely tagged one of the game files as virus and deleted those files, which it can lead to game crash or not opening issue. This behavior had been seen and happened to RF2 before as well, especially after a new game version update. So the possible solution to fix game crash is to do what the known issues page says to add game to windows defender(or other anti-virus software) exception list:
https://community.lemansultimate.co...i-virus-interfering-with-le-mans-ultimate.16/
And then make sure to re-verify game integrity to make sure all game file is intact.

 

you are killer victor ^^

 

Just minutes ago, another LMU game API issue was identified thanks to this issue report:
https://github.com/s-victor/TinyPedal/issues/49

What happens:

Since last LMU update(26th patch), all GTE cars are no longer outputting "Filtered Throttle" input through game API, there is now only "Raw Throttle" input from GTE. User now will only see the left half "thin" pedal bar(raw input) from Pedal Widget, the right half "thick" bar(filtered input) is not showing any input.

And for Trailing Widget, since it uses "Filtered Throttle" data from plotting (by default), it will always show throttle plot line at zero for GTE. The temporary solution is to enable both "Show Throttle" and "Show Raw Throttle" options in Trailing widget, which will show raw pedal input and is working correctly at the moment.

As for "filtered" throttle data, since it is no longer output from API, there is nothing I can do about it. The reason for it's output been disabled in GTE cars is unknown. User may consider report this issue to official forum if necessary.

Note, all hyper cars are still outputting "Filtered Throttle" data through API and not affected by above issue. (and this does not affect RF2 either)

 

At some point rF2 and LMU will diverge on the SharedMemory, fo sure.
Sad, but inevitable.

I will try to check on the LMU forum if this is a known evolution to hide the filtered throttle or a bug.

 

Interesting, people are using the github issues directly instead of writing here, not a bad idea.

 

hi guys, is it possible to create these two bars?

 

Hi, currently Virtual Energy consumption data are not available from game API, which means there is no way to calculate actual virtual energy usage in relation to Virtual Energy capacity. There is no information whether this data will be provided in the future.

 

That's great, thank you!

 

@svictor

I had left this thread for quite some time
This is amazing what you brought in this monitoring tool especially these latest brake and wheel lock/slip reporting it’s going to be super helpful
Really big thank you from a casual RF2 driver

 

v2.11.2 update
https://github.com/s-victor/TinyPedal/releases/tag/v2.11.2

Notable changes:

"Bar padding" option will no longer crop text, and this option can now be used to increase widget width in case some very wide none mono-type fonts that exceeded widget width. So if you find some font cannot fully displayed in widget(or repeatedly change in size), just increase "Bar padding" value will do the trick.

Deltabest & Deltabest extended Widgets will now briefly freezes lap time difference reading for a few seconds (default 3 seconds) after crossing finish line, which can help player see how much laptime they have gain or loss from previous lap.

Pedal Widget now has new options to turn off filtered pedal input display, which can come in handy when some vehicles don't provide filtered pedal input data from API, such as P2 & GTE that had their filtered pedal data output disabled in recent LMU updates.

Sectors Widget has been reworked to briefly show "time gap" on "target time" bar when passing sectors or finish line (previously "time gap" was show in a separated bar). And a new "Target Laptime" option replaces the old "target_time_mode" option, which now sets either "Theoretical" or "Personal" laptime for displaying laptime difference and sector time difference against it (in previous version, only theoretical best lap sector time difference was available for displaying).