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

2.17.0 update - Fuel Energy Saver Widget
https://github.com/s-victor/TinyPedal/releases/tag/v2.17.0



This update adds a new advanced Fuel Energy Saver Widget (as recently requested by @ebeninca), which allows more precise control to fuel/energy saving in real-time. This also marks the 50th widget introduced in TinyPedal so far ^^.

Other notable additions are the new "fuel bias" & "delta energy consumption" readings from Virtual energy Widget, which allows players to precisely adjust fuel & energy usage balance in real-time.

See changelog & user guide for details:
https://github.com/s-victor/TinyPedal/wiki/User-Guide#fuel-energy-saver
https://github.com/s-victor/TinyPedal/wiki/User-Guide#virtual-energy

 

Hello @svictor, great tool you have built, I love using it. Is it possible to add a brake migration value (perhaps to the brake bias widget), or is that data not available on the shared memory?

 

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

Here is a small update with two bug fixes.

The "minimum_reserve" setting from the new Fuel energy saver Widget is now working as intended.

The high memory usage issue (as mentioned earlier) with Navigation Widget is now completely eliminated, which it now uses around 1MB memory for normal tracks, and at most 3 to 4MB memory for giant tracks like Isle of Man.

Currently overall APP memory usage is around 60 to 90MB with all 50 widgets enabled, so there should be no more worries about memory usage.

----------

To @LIOTH

Thanks for suggestion, values like brake migration isn't available in sharedmemory API currently. However it maybe exist in Rest API, I'll need to check it later.

 

2.17.2 - Real-time Brake Migration display
https://github.com/s-victor/TinyPedal/releases/tag/v2.17.2


Here is the new real-time brake migration display for Brake bias Widget (as requested by @LIOTH ). Make sure to read changelog or user guide to see how it works in TinyPedal.

User guide:
https://github.com/s-victor/TinyPedal/wiki/User-Guide#brake-bias

Answer to some potential questions

Q: Why is it required to fully press braking at least once to get accurate brake migration reading?

A: Brake migration calculation is based on brake pressure telemetry data. Those brake pressure values are affected by "max brake pedal force" setting in car setup which is not output by game API (it's possible to get value from Rest API or car setup file, however those values are in string format, which depend on how developer or modder sets them and is not reliable to use). When "max brake pedal force" setting is lower than 100%, the sum of front and rear brake pressure is not equal to 100%, and requires recalibrate and calculate brake pressure scaling, and this can only be done by at least fully press brake pedal once. The good news is that when "auto-hold brake" assist is enabled in game, the game does this for you every time you exit garage (or at start grid), there is no need to do this yourself, unless you have reloaded widget or APP while on track.


Q: Why is this "electric braking allocation" option needed to get accurate brake migration reading?

A: As brake migration calculation is based on brake pressure, when electric braking is engaged on one of the axle in LMH or LMDh cars (in LMU), the brake pressure telemetry value from that axle will be greatly reduced if not to "zero", which is then replaced by this hidden electric braking force. So when brake migration calculation is based on that axle with engaged electric braking, the whole calculation will be wrong, and the only solution (as I found) is to redirect calculation to the opposite axle that is not affected by electric braking (which requires the scaling value mentioned in first question). And to do that, requires to first find out which axle is under electric braking, which is why this setting exists.

 

Hey, I've just installed this for the first time and I'm trying to set it up. Things mostly work as expected, but I have a big problem with Standings widget. It shows me one single line with one single car. I'm in an offline race session filled up with 3 classes, I'm in hypercar, but it only shows P1 GTE. What am I doing wrong?

 

Please read this guide
https://github.com/s-victor/TinyPedal/wiki/User-Guide#standings

 

I have looked at this but I cannot see anything I can do. I try changing different things but it will only show one GTE. Also in the Relative, it only shows gap to that exact GTE, and to noone else. Just blank rows below or above.

 

when i first installed it i didnt need any json fiddling,
strange that thing happens to you,maybe delete it and setup it again.
although i believe @svictor will join and help you.
maybe it has something to do if you are running full screen mode
hope to a solution soon!

 

I have it on borderless. It's just so strange because everything else works exactly how it should, straight out of the box, except relative and standings.

 

Have you tried changing these settings? Enable multi class split mode maybe?

 

Yes I have tried that setting, and also I've tried exact same settings as in the jpg, but I still only see one car in standings and in the relative.

 

AH I found the issue. I initially didn't understand that Relative module is needed for standings, so I had it turned off. Looking at that github page made me see it's related to Relative, and now it finally clicked. Ah so silly Thank you guys anyway.

 

Willing to see your livestream with Tinypedal.

 

I would love to use some of these widgets on my ddu. Is this possible? Simhub webpages could be used if tinypedal can stream through url.

 

I'll try tonight, I'll try almost completely replacing the game HUD

 

Hello, good afternoon, I need some help with Tinypedal on LMU.
When I choose "Le Mans Ultimate" in Shared Memory API, and click Apply, the app stop work, and the only option is go to task manager and kill it.
Is this normal and it shoul only work with rFactor 2 selected?
Many thanks

 

I think so, I never changed this parameter and it works on LMU.

 

2.17.3 (2024-08-19)
https://github.com/s-victor/TinyPedal/releases/tag/v2.17.3

Thank you guys for helps and bug reports.
The issue with "LMU API selector stopped working" (reported by @Jalves) is now fixed in latest v2.17.3 update.

Cheers

Changelog

• General
  • Fixed a bug (introduced in v2.17.0) in API connector that would cause TinyPedal to stop work
    when user selected "LMU API" in Shared Memory API config dialog.
    Note, LMU API option is currently only a placeholder which uses the same underlying
    RF2 API and "rF2 Shared Memory Plugin" and works exactly same as RF2.
    Updated "User Guide" info regarding API selector.
  • Optimized overlay state check to avoid unnecessary function calls.
• Command line arguments
  • Add "-h, --help" argument, which shows all available command line arguments.
  • Add "-s, --single-instance" argument for toggling single instance mode,
    which allows multiple instances of TinyPedal to be running at same time
    by adding "-s 0" or "--single-instance 0" argument.
    Default is single instance only, which only one TinyPedal may be run at a time.
  • Single instance mode now works under Linux, or running from source script.
  • Add "Single instance mode" info to log output.
  • Add "pid.log" output file in log folder when "Single instance mode" is enabled.
  • See User Guide "Command line arguments" section for details.
• Misc
  • Added new contributor (ebeninca) to contributors.md.

---------------------------
@Hany Alsabti
This is likely not possible because TinyPedal is not web-based rendering.

 

Thank you Victor, it works now.
Cheers

 

thx, I feel flattered.

I have a github user too, but not a thing that I use often.

https://github.com/ebeninca/