[REL] TinyPedal - open source overlay for rF2 (Pacenotes,Radar,FFB,Deltabest,Relative,Fuel Calculator)

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.
 
Capeta said:
There you go : https://fromsmash.com/I.Bg4Mkdgv-ct
Click to expand...
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.
 
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 ...
 
DanRZ said:
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 ...
Click to expand...
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).
 
Rui Santos said:
Do we need to delete that "tinypedal.log" file with this new version? Thanks!
Click to expand...
yes, it is recommended to delete, as currently this log file does not have time stamp which may contain logs from older version.

Danny Wilde said:
thx for the overlay. It`s the best.

The time is incorrect when time acceleration is activated.
Click to expand...
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.
 
svictor said:
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.
Click to expand...

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
 
Danny Wilde said:
thx for your answer. The clock in the MFD shows the correct time, even with time acceleration.
View attachment 54652
Click to expand...
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.
 
Last edited:
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?
 
juanchioooo said:
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?
Click to expand...
Currently it is only possible to capture overlay by using "Display Capture" option in OBS. I don't know if Twitch has similar function. (anything that captures desktop should work)
 
Hi,
I'm not being able to set the P2P for Indy cars and TCC cars. Is there anything that I have to do? It's on, the dash is there, but when I click to activate it doesn't show anything. My goal is to when I activate it turns "green" for me to know that it is active, just like DRS works.

Let me know if tehre is ant solution. Thank you!
 
Create a new Profile.(just copy a working one and save it under a new name.)
Assign the P2P to a button.(This will work with both Indy & BTCC) Assign a button for how much P2P remains. Ensure you have v1134. Make sure the Message Center is on. Drive an entire lap before using either. The rules for BTCC hybrid are different than the rules for Indy P2P. You must be accelerating to enable P2P. (probably the same for the Hybrid)
 
You must log in or register to reply here.
Back
Top