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

ok @svictor data from 2.14.1 to 2.15.0 was the problem. I tried a new session as you suggested and now it's fine.
I have a clarification: sectorbest is from all time sectors, not the best sectors from all time best lap time. correct?
And a question: With next update(2.15.1) there will be a problem again with previously laptimes(2.15.0)?

 

To your first question:

If you set "target laptime" in Sectors Widget to "Theoretical", then it will show all time (or session) "best sector time" recorded from each individual sector.

If you set "target laptime" in Sectors Widget to "Personal", then it will show all 3 "sector time" from your personal best laptime. If you sum up all 3 "sector time", it equals your personal best laptime.

So if you want to see "all time sector best" time of each individual sector, you must set "target laptime" in Sectors Widget to "Theoretical".


To your second question:

No, there will not be issue with newer version.

The reason that your data did not match was due to that your deltabest data was not recorded at the same time with sectorbest data (as v2.14 does not have the new sectorbest recording function and data file from v2.15).

It's not a "problem" from the beginning. Delta module & Sectors module always record each of their timing data complete separately, which deltabest and sectorbest data can be reset or deleted separately without affecting one another.

 

@svictor Thanks for the clarification.
When Ι set target laptime to "Theoretical" I see all time sector best, but when Ι set it to "Personal" I cant see all 3 "sector time" from my personal best laptime. Take a look if you want, maybe I don't understand something.

 

Thanks mate, I have identified the issue. It's a display error in Sectors Widget (doesn't affect delta sector best) related to some out dated code in v2.11.2 update. I'll make a quick fix shortly.

 

Yes, doesn't affect delta sector best, only the display of 3 sector times of personal best laptime.
Thank you for your excellent work,It's a masterpiece.

 

2.15.1 (2024-07-13)
https://github.com/s-victor/TinyPedal/releases/tag/v2.15.1

Here is a quick update includes various fixes and improvement according recent suggestions & bug reports, thanks to everyone for the feedback.

• General
  • Reworked preset saving system to prevent preset file corruption in rare case.
    Saving system now creates temporary backup for old preset file before saving.
    If all saving attempts failed, saving will be aborted,
    and old preset file will be restored to avoid preset file corruption.
  • Add "maximum_saving_attempts" option in Compatibility dialog,
    which sets maximum retry attempts for preset saving.
    Default value is "10". Minimum value is limited to "3" maximum attempts.
    Note, each attempt has a roughly 50ms delay.
• Radar Widget
  • Fixed an issue where radar would not auto hide under certain condition.
• Sectors Widget
  • Fixed incorrect PB sector time display if "target time" is set on "Personal".
• Weather forecast Widget
  • Add "layout" option, which sets columns display order.
    "0" = show columns from left to right.
    "1" = show columns from right to left.
• Misc
  • Updated User Guide info for Compatibility, Sectors Module, Weather forecast Widget.

 

Hi Mate. I just wanted to pass on my appreciation for this tool, it is incredibly helpful and given how long I have been using it for, I felt bad not leaving a comment.

The only thing that I am REALLY struggling with is not being able to resize things easily enough. For example, I have a G9 57" display and the Tiny Pedal interface is incredibly small when I first open it up, I almost have to squint and occasionally get a headache trying to enable and adjust my settings.

I was also hoping that instead of adjusting the font size for certain widgets, I was not sure if there can simply be a 'scale' option at the top that allows you to adjust each widget/module accordingly.

 

Hi, thank you for feedback.

The size of most widgets are determined by font size, which can be globally adjusted by accessing Global Font Override dialog from main window Config menu.

Just change Font Size Addend value in Global Font Override dialog will do the trick. Note, there are a few widgets that are not affected by font size and need individual adjustment afterwards.

As for a single global scale setting, unfortunately it's not possible at the moment due to various limitations and underlying complexity.

 

I've been surprised yesterday by TinyPedal being wrong on fuel & NRG calculation.
Didn't cost me any position as I had enough buffer to make a very slow last lap but it's becoming frustrating to not get a rock solid plugin on this.
It was last year but for some reason, it's not anymore.

I was using 2.14.0 until now.

 

If you're doing timed race, it's recommended to add one lap more of fuel, it saved me multiple times.

The add amount keeps fluctuating during the lap, I use the value showed during the start finish line as reference.

 

Hi @Capeta
This issue has been brought up a few times recently, however it's not really a calculation problem.

The main reason that you see "refuel" value fluctuating is due to that the end (or start) of final lap is very close to finish line when the moment the race timer would be ended.

In order to explain more in details, I'll use an example below, it will be a little lengthy, so please take time to read:

1. Assume we have a race that is 18 mins length at Monza with LMH class.
2. Assume you (local driver) will be doing an average of 1:38.500 laptime through the whole race.
3. Assume leader driver will be doing an average of 1:38.000 laptime through the whole race, which is half seconds faster than your per lap.

Here is the formula for calculating "estimated end race" lap position (in fraction) at the moment race timer ends:
Your position: 18(min)*60(sec) / 98.500(sec) = 10.964467 (laps)
Leader position: 18(min)*60(sec) / 98.000(sec) = 11.0204 (laps)

For you, 10.964467 laps value means that at the moment the race countdown timer ends, your on-track position will be located at 96.467% of the track total length, which if converted to seconds it will be 0.964467 * 98.500 = 94.999 into lap (or roughly 3.5 seconds before finish line). That means you have not yet finished your 11th lap after race timer ended.

For leader, 11.0204 laps value means that at the moment the race countdown timer ends, leader's on-track position will be located at 2.04% of the track total length, which if converted to seconds it will be 0.02040 * 98.000 = 1.999 into lap (or roughly 2 seconds after crossed finish line). That means leader will have already started his 12th lap (final lap) when race timer ended.

Since final lap (checked flag) is always initiated by leader, in this case, the leader started his 12th lap 2 seconds before race timer ended, so both leader and you have to complete this extra 12th lap. If you have carried 11 laps of fuel at start, then you will missing one lap of fuel, due to the fact that leader's average laptime is little quicker that just enough for him to start lap 12.

As you can see now, the important factor here is where the leader will be on track at the moment the race countdown timer ends, which determines whether there will be an extra (final) lap for everyone. And in some case like this, the race event length (duration) and player's laptime just happen to be in a sensitive range that finishing position is very close to finish line, where a little laptime change (slower or faster by fraction of a second) can greatly affect whether you or leader will start a new lap or not when the race countdown timer ends. And in this example, the sensitive range is within half seconds from 1:38.000 to 1:38.500.

So how to avoid this kind of margin of error? Here are a few tips:
First and currently best option, is using Fuel Calculator to simulate fuel usage for both normal laptime and alien laptime, so that you will see whether there is a chance that leader (or if you are leader) will do an extra lap after race timer ends. As below picture:


Second, if you are not leader, and have not done fuel usage calculation in first tip (but you should really do that), then you will need to keep an eye on leader's position, and guess whether he will be fast enough to start an extra final lap, though this guessing will be extremely difficult. Or, more easier, as @ebeninca suggested, just add an extra lap of fuel.

So, are there any plan for tinypedal to improve this situation?
The answer is YES. In fact, I'm currently exactly working on a new widget (also mentioned on github issue a few days ago) that will make various prediction to leader and your (local player's) race-end-timer lap position to help you determine whether there will be an extra lap or not at the end of timer. However, it is important to note that there are a lot variables can affect prediction accuracy (laptime, pit time, penalty serve, overtaking, etc), so this prediction can only be used as reference, rather than used directly in refuel calculation, and it will only be relevant to last 1 or 2 stints before race ends.

--------------------------

To conclude all this, the refuel value fluctuating is not a calculation error, but it is related to race length and leader's laptime that happened to be within a sensitive range that the moment the race timer ends is near finish line (or leader starts a new final lap before timer ends). A new "lap prediction" widget is currently in the work, but not estimation when it will be finished, as all those update since v2.14 had cost me a lot sleep time and I'm still trying to recover, please be patient.

 

Thanks for the explanation @svictor

At my low level of understanding I can only say I used it a lot on rF2 in 2023 with success and no issue on that end.
I've been used to seing it go + or - when it was tight on the number of laps but not to be completely wrong by saying the player is safe by -2.0 when it's not the case.

That's why I posted, to me something has changed on this end and it's way less accurate than it was.

As usual, a big thank you for your work!

 

There's only a very specific situation that I can't trust on tinypedal's fuel widget, I race in an online multiclass championship where the league decided to do some events with fix number of laps, let's say 60 laps. It's some kind of abomination cause I never saw it in RL.

Problem is, I'm running in the slower class, so the race ends when the first car finished 60 laps, obviously the slower class will not do 60 laps, In fact I did around 54 laps last time, and I got the class win.

Maybe with some kind of magic you can adjust the calculation to work in this specific situation, probably you'll have to consider how much laps the driver is behind the leader to find the correct approximated refueling value.

I'm not expecting any miracle here, just telling you a specific situation that I have.

 

No worries, someone also mentioned this situation (lap-based multi-classes) on github issues earlier. It is definitely on my todo list along with the WIP time-based prediction stuff. There will be a lot new stuff to come in next update.

 

Hi, in the future, could you implement a red traffic light with the lights turned off only for the start of the race. It would be very nice for those who do live streaming.

 

Hi,
First of all, compliments to @svictor , great tool!

I have a problem, I just installed the latest version (also of shared mem) and everything about tyre load/forces is just 0.
It is correctly displayed, it is just 0.
Everything else seems working fine, and I didn't have any warning, everything ran just fine.
I'm running the GT3 car (the 720s).
Any clue?

Thanks

 

Coincidentally this week I have a race that probably will demand saving fuel and for the first time I stopped to analyze every detail of the fuel widget, my suggestions for improvement:

"Save": show negative values, for safety I always want to have a lap extra of fuel, so I can keep focus only on this value and forget the refuel value.
"Goal" (new): How much consumption per lap I need to do to reach Zero on Save (ideally reach Zero minus one lap of fuel on Save).
"Last" (new): copy of "used" but only update the value when the driver cross the start/finish line, so I can see if I'm reaching my goal of consumption per lap.

 

As usual, thanks and all suggestions noted, and good luck with race.

To @StefG:
Most of paid DLC cars have tyre(load force)/engine(temperature)/downforce data encrypted and disabled output from game API, that's why they are zero, it's also in frequently asked questions:
https://github.com/s-victor/TinyPedal/wiki/Frequently-Asked-Questions


To @Hidron:
If you are referring to the missing "red light/green flag" during rolling start type race, it is because game API sends "green flag" state at the beginning of rolling/formation phase rather than at the end of rolling/formation lap. It would be possible to make it work with rolling start type race by adding addition workaround, it's currently on my todo list.

 

ok, Thanks.
Should be possible to have at least the total vertical force from vertical acceleration?

 

v2.16.0 update - Relative finish order Widget
https://github.com/s-victor/TinyPedal/releases/tag/v2.16.0



The new Relative finish order Widget displays estimated relative finish order between leader and local player with corresponding refilling estimate in a table view.

The table consists of 5 fixed rows, 3 fixed columns, and 10 optional predication columns that can be customized.

First and fourth rows, starting from second cell, show estimated leader's pit time and local player's pit time, where first row first cell shows current session type in TIME or LAPS. Last cell shows last recorded total time that leader and local player had spent in pit. Note, last recorded total pit time counts from pit entry to pit exit point, it doesn't include the extra few seconds that spent while approaching or exiting from pit.

Second and third rows, starting from second cell, show estimated leader's final lap progress (fraction of lap) and local player's final lap progress that depend on current session type:

• For TIME type race, it shows final lap progress at the moment when session timer ended.
• For LAPS type race, it shows relative final total lap difference between leader and local player.
  Leader's value from second row second cell always shows integer value, because laps-type race has no timer, and the end of race is determined at the moment when leader crossed finish line, which can only be full laps.
  Local player's value from third row second cell always shows final lap progress relative to leader's value from second row second cell.
  Both leader's and local player's final lap progress values starting from third cell are offset from second cell of same row.

Third row, first cell shows relative lap difference between leader and local player that is calculated from lap time pace difference of both players, which can be used to determine whether leader has the chance to overtake local player on final lap. For example:

• If relative lap difference value shows 0.25, that means for every full lap, leader is faster than local player by 0.25 lap. If leader is at start line and player is just within 0.25 lap distance from leader, that means leader can catch up and overtake player before the end of lap.
• If relative lap difference value shows 0.25 and leader is at middle of current lap (0.5 lap), that means leader now only has roughly half of the lap distance (0.12 lap) to make successful overtake before the end of lap. If player is not within this 0.12 lap distance, then leader may not be able to overtake.

Fifth row, first cell shows refilling type in FUEL or NRG (if virtual energy available). Starting from second cell, shows estimated local player's refilling that depends on current session type:

• For TIME type race, refilling value from each column is calculated based on local player's current laptime pace, consumption, and local player's final lap progress from third row of same column. Note, each refilling value has no relation to leader's final lap progress value from same column. Refilling value from 0s column gives same reading as seen from Fuel or Virtual Energy Widget in time-type race.
• For LAPS type race, only refilling value from 0s column is calculated and displayed according to leader's leader's final lap progress value.
  Other column values are not displayed, this is done to avoid confusion. Because unlike TIME type race where all final lap progress values are within 0.0 to 1.0 range, in LAPS type race values can exceed 1.0 or below 0.0 (negative), which the number of possible lap differences would increase exponentially and not possible to list all of them in the widget.

See TIME or LAPS type race example usages below for details.


Important notes

• Predication accuracy depends on many variables and is meant for final stint estimate. Such as laptime pace, pit time, penalties, weather condition, safety car, yellow flag, can all affect predication accuracy. It requires at least 2-3 laps to get sensible readings, and more laps to have better accuracy. Do not expect accurate readings or plan fuel strategy from first few laps.
• Final lap progress values will not be displayed if no corresponding vaild lap time pace data found, which requires at least 1 or 2 laps to record. If local player is the leader, then all values from leader's row will not be displayed. Refilling values will not be displayed during formation lap for the reasons mentioned in first note.
• Refilling estimate calculation is different between TIME and LAPS type races, make sure to look at the correct value, check out example usage below for details.
• LMU currently uses absolute-refueling mechanism (how much total fuel to fill tank up to), as opposite to relative fuel (how much to add on top of remaining fuel in tank). This means user has to manually add up both "remaining" and "refuel/refill" values for total fuel/energy refill.
• This widget is meant for used in complex and endurance race situations. To avoid human error, it is necessary to have a good understanding of this widget and practicing proficiency before attempting to use any provided data in actual race. Once with enough practicing, it should be fairly easy to make the most out of it.
• Avoid using this widget if unfamiliar or unsure any of the usage or data it provides.
  

Time-type race example usage

1. Determine leader's next pit time and select leader's final lap progress (second row) value from corresponding pit time (first row) column. 0s column means no pit stop.
   
   
2. Determine local player's next pit time and select local player's final lap progress (third row) value from corresponding pit time (fourth row) column.
   
   
3. Compare the two final lap progress values from leader and local player:
   • If leader's final lap progress value is greater than local player, such as leader's 0.91 (50s column) vs player's 0.47 (30s column), it indicates that leader will be ahead of local player when timer ended, and there will be no extra final lap. So local player's refilling value from corresponding 30s column can be used, in this case, it's +7.4 fuel to add.
     However, if leader is closer to finish line (as show in orange color indicator), there is a chance that leader may be fast enough to cross finish line before the end of timer, which would result an extra final lap for local player, and requires adding an extra lap of fuel on top of +7.4 fuel in this case.
   • If local player's final lap progress value is greater than leader, such as leader's 0.10 (30s column) vs player's 0.72 (0s column), it indicates that local player will be ahead of leader when timer ended, and there will be an extra final lap for local player, and requires adding an extra lap of fuel on top of +7.4 fuel from 0s column.
     However, if the difference between the two final lap progress values is smaller than relative lap difference (from third row first cell) value, it may indicate that leader could overtake local player on final lap, which would result no extra final lap.
     
4. To sum up, if comparison shows no extra final lap, then just refill according to local player's refilling (fifth row) value from the same column of local player's final lap progress (third row). If comparison shows an extra final lap, then just add an extra lap of fuel on top of local player's refilling value.
   

Laps-type race example usage

Note, there is generally no reason to use this widget in LAPS type race unless you are doing multi-class laps-type race which is very rarely seen.

1. Determine leader's next pit time and select leader's final lap progress (second row) value from corresponding pit time (first row) column. 0s means no pit stop.
   
   
2. Determine local player's next pit time and select local player's final lap progress (third row) value from corresponding pit time (fourth row) column.
   
   
3. Subtract local player's final lap progress value from leader's final lap progress, then round down value:
   • If leader's final lap progress value is 2.00 (0s column), and local player's final lap progress value is 0.40 (0s column), then after subtracting (2 - 0.4 = 1.6) and rounding down, the final value is 1 lap difference, which means local player will do one less lap than leader.
     As mentioned earlier, for laps-type race, refilling value from 0s column is calculated according to leader's leader's final lap progress value, which any lap difference is already included in the result from local player's refilling value (fifth row second cell), in this case, it's +12.8 fuel to add.
   • If leader's final lap progress value is 1.43 (40s column), and local player's final lap progress value is -0.24 (50s column), then after subtracting (1.43 - -0.24 = 1.67) and rounding down, the final value is also 1 lap difference, which means local player will do the same one less lap than leader. So in this case, it's still +12.8 fuel to add.
   • If leader's final lap progress value is 2.00 (0s column), and local player's final lap progress value is -0.11 (40s column), then after subtracting (2 - -0.11 = 2.11) and rounding down, the final value is 2 lap difference, which means local player will do two less laps than leader. So an extra lap of fuel may be removed from local player's refilling value from fifth row second cell, in this case, it's 12.8 minus one lap of fuel 2.2, equals +10.6 fuel to add. Alternatively, it can be calculated from full lap refuel (as show in Fuel Widget), which will be 15.0 minus two lap of fuel 4.4, and equals +10.6 fuel to add.
     Be aware that carrying less fuel is risky in laps-type race due to reasons below.
     
4. Last note, since the end of laps-type race is determined by the moment that leader completed all race laps, leader can greatly affect final predication outcome. To give an extreme example, if leader is ahead of everyone by a few laps, and decides to wait a few minutes on his final lap before finish line, then everyone else will be catching up and do a few extra laps which would require more fuel. Thus it is always risky to carry less fuel in laps-type race.
   

Full user guide:
https://github.com/s-victor/TinyPedal/wiki/User-Guide#relative-finish-order


Changelog

• Delta Module
  • Add data smoothing function to filter out unusual data noise.
  • Add "delta_smoothing_samples" option, which sets number of samples
    for delta data smoothing calculation using exponential moving average (EMA) method.
    Value range in "1" to "100". Default is "30" samples. Set to "1" to disable smoothing.
    Higher value results more smoothness, but may lose accuracy.
  • Add average laptime pace calculation and output.
  • Add "laptime_pace_samples" option, which sets number of samples
    for average laptime pace calculation (EMA).
    Value range in "1" to "20". Default is "6" samples. Set to "1" to disable averaging.
    Note, initial laptime pace is always based on player's all time personal best laptime if available.
    If a new laptime is faster than current laptime pace, it will replace
    current laptime pace without calculating average.
    Invalid lap, pit-in/out laps are always excluded from laptime pace calculation.
  • Add "laptime_pace_margin" option, which sets additional margin for current laptime
    that cannot exceed the sum of "laptime pace" and "margin".
    This option is used to minimize the impact of unusually slow laptime.
    Default value is "5" seconds. Minimum value is limited to "0.1".
• Fuel Module
  • Now uses laptime pace value from Delta Module for real-time fuel calculation
    for increased consistency and accuracy.
• Vehicles Module
  • Fixed pit timer incorrectly reset after pit out.
• Flag Widget
  • "Pit Request" indicator now shows "pit-in laps countdown" alongside
    "estimated remaining laps" reading that current fuel or energy can run.
    Note, "pit-in laps countdown" value is always calculated towards
    the finish line of current stint's final lap, and thus is always
    less than or equal to "estimated remaining laps" reading.
    If countdown drops below 1.0 (laps), it indicates the final lap of current stint,
    and driver should pit in before the end of current lap to refuel.
    If countdown reaches zero or negative, there may still be some fuel or energy left in tank,
    however it will not be enough to complete another full lap.
• Friction circle Widget
  • Add "show_trace_fade_out" option, which enables trace fade out effect.
  • Add "trace_fade_out_step" option, which sets trace fade out speed.
    Value range in "0.1" to "0.9", higher value increases trace fade out speed.
    Default value is "0.2". This option is enabled by default.
• [New]Relative finish order Widget
  • New Relative finish order Widget that displays estimated relative finish order
    between leader and local player with corresponding refilling estimate.
    This widget auto-switches display mode ("TIME" or "LAPS") depends on current session type.
  • Show both predefined and customizable "leader's pit time" and "local player's pit time",
    as well as last pit stop time from leader and local player.
  • Show "leader's final lap progress" and "local player's final lap progress"
    that depend on current session type.
  • Show "relative lap difference" between leader and local player that is calculated from
    lap time pace difference of both players, which can be used to determine whether leader
    has the chance to overtake local player on final lap.
  • Show refilling type in "FUEL" or "NRG" (if virtual energy available).
  • Show estimated "local player's refilling" that depends on current session type.
  • For complete customizable options, usage examples, see User Guide "Relative finish order" section.
• Timing Widget
  • Add "show_average_pace" option, which shows personal current average laptime pace,
    this reading is also used in real-time fuel calculation.
    Note, additional "average laptime pace" calculation setting can be found in "Delta Module" config.
    After ESC or session ended, laptime pace reading will be reset,
    and aligned to "all time personal best laptime" if available.
• Weather forecast Widget
  • Add "number_of_forecasts" option, which sets number of forecasts to display.
    Value range in "1" to "4". Default is "4" forecasts.
  • Add "column_index_*" options for customizing data display order of each forecast.
• Misc
  • Updated User Guide info for Delta Module, Flag Widget, Friction circle Widget,
    Relative finish order Widget, Timing Widget, Weather forecast Widget.