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

The official display does have water and oil temperature, therefore the third party ones will work, unless the third party developer installs it.

 

v2.5.0 - Suspension position & Carcass Widgets, Vehicle class editor
https://github.com/s-victor/TinyPedal/releases/tag/v2.5.0



User guide:
https://github.com/s-victor/TinyPedal/wiki/User-Guide#classes-preset-file
https://github.com/s-victor/TinyPedal/wiki/User-Guide#units-and-symbols
https://github.com/s-victor/TinyPedal/wiki/User-Guide#suspension-position
https://github.com/s-victor/TinyPedal/wiki/User-Guide#tyre-carcass-temperature


2.5.0 (2023-11-27)

• General
  • Rename "Display units" config dialog to "Units and symbols",
    which is now used for unified units and symbols configuration.
  • Moved all (five) "tyre_compound_list" options to "Units and symbols"
    config dialog, and is now called "tyre_compound_symbol".
  • Adjusted & unified default value for "bkg_color_circle" options
    that used in Friction circle, Heading, Navigation, Radar Widgets.
  • "show_fade_out" option no longer crops background.
  • Add option reset confirmation to various config dialog.
    Note, option reset will still only be saved and take effect
    after clicking apply or save button.
• [New]Vehicle class editor
  • Add "Vehicle class editor" that can be accessed from "Config" menu in main window,
    which provides easy-to-use vehicle class name customization.
  • The new editor can auto-detect and fill-in "full vehicle class name"
    from current active session.
    It is recommended to join or start a session with corresponding vehicle
    before adding new class entries.
    See user guide for details.
• Force Widget
  • Add "show_front_downforce" & "show_rear_downforce" options,
    which show front & rear downforce reading in Newtons.
  • Add "warning_color_liftforce" that shows color indicator
    when generating lift force.
• Navigation Widget
  • Add "show_circle_background" & "bkg_color_circle" options (enabled by default),
    which shows circle background color below navigation map.
  • Add "circle_outline_color" & "circle_outline_width" options,
    which draw outline for circle background.
• Radar Widget
  • Add "show_circle_background" & "bkg_color_circle" options (disabled by default),
    which shows circle background color below vehicle radar.
• [New]Suspension position Widget
  • Show visualized suspension position (millimeter).
• Timing Widget
  • Add "show_session_personal_best" option (disabled by default),
    which shows personal best lap time from current session.
• [New]Tyre carcass temperature Widget (by Sasker)
  • Show carcass temperature of each tyres
    based on Tyre temperature Widget design,
    which helps analyzing and managing tyre grip
    and wear relative to carcass temperature change.
  • Many customizable options.
• Misc
  • Updated user guide.
  • Updated contributors.md with new contributor (Sasker).

 

Does the suspension position gives you the min and max of each car suspension? Can we have a min and max position for each car suspension values? Thank you @svictor !!

 

You can manually set visible max suspension position range (the game does not tell you the max suspension travel). Default is set on 100mm range (both positive and negative travel).

Note, The suspension position value are read from mSuspensionDeflection value in API(same as motec), which the value starts from 0 and extends both way (positive or negative travel) depends on load, susp setup, etc. When position goes negative, it will show negative text reading and a different bar color, which can be customized as well.

 

I'm afraid that since one of the last updates, TinyPedal isn't as reliable to me.
Of course the reload button help, but more often than before, it either freeze or doesn't start (online session).
And yesterday, to my surprise, it got the fuel calculation wrong, it never showed that I could require an extra lap, and I had plenty of time to manage it if needed.
As I've been relying on it for almost all 2023 and it been consistently as reliable as a spreadsheet, I have stopped to "think" about fuel during a race.

Not sure if that will help but that's some feedback regarding the lastest updates.

 

Same issue here, i play less thes times but i noticed i had to push "reload" on a few sessions after entering, or i get nothing.
Then it works properly along the session ... Just a freeze on the very start of the session.

 

Thank you for feedback.

There are a lot underlying code has changed for the past week (since last version 2.5.0), I packaged a new version 2.5.1 here which you can test:
https://github.com/s-victor/TinyPedal/releases/tag/v2.5.1

This includes several important fixes that may be related to your mentioned issue.

Also please check folder C:\Users\yourname\AppData\Roaming, see if there is a tinypedal.log file, and post here if any, thanks. If you are testing newest version, it is best delete this log file before running, as the log file could keep all records from older versions.

 

There you go : https://fromsmash.com/I.Bg4Mkdgv-ct

 

Thanks. I have checked the log and all errors were from old v1 version (which were fixed in v2 long ago). Let me know if there is further issue, thanks.

Note, I forgot to mention that there were 2 incorrect lap reading references in fuel module that was introduced in 2.3.0 (which I suspected they may causing the issues you mentioned with fuel calculation), and those two values were already fixed in 2.5.1, so all fuel calculation are now identical to old version prior to v2.2.0.

 

As usual, thank you very much.

 

I checked too but have no tinypedal.log in the Roaming directory ...
I probably was also an an intermediate version. I installed the last one ...

 

There was some API accessing code changed in v2.3.0, which could potentially causing freeze. Those codes were already removed/reverted in v2.5.1 from today's update. So it should no longer causing any freeze issue.

 

v2.5.1 - important bug fix update
https://github.com/s-victor/TinyPedal/releases/tag/v2.5.1

This is a re-post of 2.5.1 update as from earlier post today.
This update includes several important fixes to various issues introduced since v2.3.0.

Due to significant part of code has changed since 2.3.0-2.5.0, testing & reporting issue from early versions may not help. Please base test reports on latest version instead, thanks for all help.


2.5.1 (2023-12-05)

• General
  • Fixed APP malfunction while switching API or reloading under rare cases.
  • Sort heatmap on load.
  • Add User guide & FAQ link to main window Help menu.
  • Reworked About window, add contributors tab.
  • Don't draw sector line on map if not available.
  • Various corrections & fixes.
  • Removed additional index check methods (introduced in 2.3.0 update)
    in API access module that may potentially cause issues.
• Fuel Module
  • Fixed several incorrect lap number reference (introduced in 2.3.0 update).

 

Do we need to delete that "tinypedal.log" file with this new version? Thanks!

 

thx for the overlay. It`s the best.

The time is incorrect when time acceleration is activated.

 

yes, it is recommended to delete, as currently this log file does not have time stamp which may contain logs from older version.

If it is the in game track clock time from Cruise widget, you will need to manually config "Track clock time scale" option in Cruise widget to match game session time scale setting in order to synchronize time display. The reason for this is due to that game API does not provide track time scale info, and there is no way to find out time scale info, so a manual correction is required for time scaled session.

 

thx for your answer. The clock in the MFD shows the correct time, even with time acceleration.
View attachment upload_2023-12-6_6-2-33.jpeg

 

It's correct, MFD is part of in-game HUD, which reads data directly from RF2.

However third party APP or HUD requires to read data from RF2 game API (as intermediary), which not every data is provided through this API interface. Time scale is one of the data that is not available from API, so in this case it can not be automatically synchronized with in game time or MFD HUD. (for example, some of other data that is not available from API are TC ABS Mixture level info, etc)

------------
To give more details about in game track clock:

The game API does not directly output track clock time. In order to get track clock time, it has to be calculated from those two API values: "mStartET" and "mCurrentET".

Explain from API document:
mStartET is the start time stamp (seconds since midnight) of the event (session).
mCurrentET is the current time(seconds) elapsed since the start time (mStartET) of the session.
Note: mCurrentET is not affected by "Time Scale" from game session setting, however it does scale with "Time Acceleration" from hotkey.

And the base formula to calculate track clock will be:
track clock = mStartET + mCurrentET
Since clock time is a loop, additional time offset is required when time value exceeded 24 hours, this is only for x1(normal) time scale.

For time scale other than x1, it requires to multiply "mCurrentET" value with time scale. However the issue here is that game API does not output a "time scale" value, so there is nothing to multiply from, other than setting up an option for user to manually config.

 

@svictor
Thank you for feedback.

 

How can I capture tiny pedal on Twitch, I don't mind not seeing it in VR like I want, but how can I get Twitch to capture it? I would like the people who follow me to see how the race is going, does anyone know how to capture it without OBS?