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

It will be added in next update.

 

2.23.0 (2025-01-15)
https://github.com/s-victor/TinyPedal/releases/tag/v2.23.0

• General
  • Add "Remember Size" option in main window Config menu, which remembers last window size.
    This option is enabled by default.
  • Apply laptime pace margin after laptime pace calculation instead of before.
• Relative Widget
  • Add "show_highlighted_nearest_time_gap" option (requested by @Jonathan07),
    which highlights opponents within nearest time gap threshold.
  • Add "nearest_time_gap_threshold_*" options for customizing nearest time gap threshold (in seconds).
    Default is "1" second for front, and "2" seconds for behind.
  • Add "show_time_gap_sign" option, "-" indicates opponent's relative position is in front of player,
    "+" indicates the opposite. This option is disabled by default.
  • "show_lap_difference" option no longer applies to "time gap" column to avoid confusion with
    "show_highlighted_nearest_time_gap".
• Track map Widget
  • Add "show_pitout_prediction" option (requested by @David levis & @Marcelo Prestes),
    which shows estimated pit out on-track position indication for each pit stop duration.
    Note, pit out position prediction is based on "delta best" data which scaled with player's latest
    "lap time pace" for accurate real-time position prediction under various track conditions.
    Pit out prediction requires both valid "track map" and "delta best" data to display.
    At least "one valid lap" for any car and track combo is required to display pit out prediction.
    For accurate prediction, the location of "pit out line" must be found first.
    And since each track has different pit out line location,
    it is required to "pit out" at least "once per session" to mark the correct pit out line location.
    This can be easily done by driving out of pit lane.
  • Add "number_of_predication" option that sets number of pit out predication to display.
    Value range is limited in "1" to "20".
  • Add "pitstop_duration_minimum" option that sets pit stop duration (in seconds) of first predication.
  • Add "pitstop_duration_increment" option that sets each pit stop duration (in seconds) increment
    after previous predication. Default increment is "10" seconds.
    Note, each time when pit stop duration of the nearest predication exceeded current pit stop timer,
    the predication circle will be removed, and a new predication circle will be appended
    with pit stop duration increment after the last predication.
  • Add "pitout_time_offset" option that sets amount time offset (in seconds) for catching up with
    vehicle speed after pit out. Default is "3" seconds.
    Note, this value is important for accurate prediction, as initial vehicle speed is much slower after pit out,
    so extra time is needed for driver to catch up, and also affected by pit out line location.
    For most tracks, this extra time after pit out is roughly within "1" to "5" seconds,
  • Add "show_pitstop_duration" option that shows pit stop duration reading on top of each predication circle.
  • Add "show_position_in_class" option, which shows position in class while "enable_multi_class_styling"
    is also enabled, otherwise this option has no effect.
    While "enable_multi_class_styling" is enabled, disable this option to show overall standings with
    multi-class color (requested by @Lazaros Filippakos).
• Misc
  • Updated "Application", "Relative", "Track map" sections in User Guide.

 

The new prediction pit out thing is a very nice feature.

Does it take in account tyres and fuel ?

 

Thanks. Prediction position is determined by "pit stop duration" and "delta best data" that scaled with laptime pace. It doesn't matter whatever player is doing in pit lane (whether adding fuel or changing tyres or serving penalties, etc, no matter). All it matters is the total time driver will spend in pit, just keep your eye on pit timer from Flag widget or standings/relative widgets, and guess how much time you would spend in pitstop (this is one thing cannot be predicted at the moment, so you probably have to test to know your average pit stop duration for a track), then find closest prediction circle (that marked with pitstop duration) on map. Give it a few tries, and it should pick up easily.

 

Hello.
Is it possible to know the status of other cars' penalties during an online race?
In reality I can get those information from the spotter, but I would like to know to avoid an unintentional battle with someone who has been given a penalty.

 

Drivers use TINY Pedal....drivers fail to finish...not even one single race....
Cause?
They can't SEE past ALLLLLLL these tiny pedal widgets...1st turn...everybody is out... lol...
seriously.... You keep piling the features on....what a marvelous effort on your part!

 

Yesterday I was running LMU, and I noticed in the relative widget a "-1" in 2 other cars right after the start, laps after both went to the pits, in the end I discovered that both got penalties for false start.

 

@kznanasi @ebeninca
Correct, number of penalties display feature was added in v2.22.0 update for Standings, Rivals, Relative Widgets, as the "negative number with purple background" you see from "pitstop count" column (negative sign is added to distinguish from normal pit stop numbers. for example -3 means driver has three accumulated penalties).

See old v2.22.0 changelog (or user guide) for details:
https://forum.studio-397.com/index....ve-fuel-calculator.71557/page-43#post-1148261

 

victor, ebeninca

Thanks both of you for the info.
I'm sorry I completely missed this great feature.
By the way, do you have any idea of the type of penalty? (Drive-through, Stop and Go and End of Longest)

 

No worries. Unfortunately penalty type is not available from game API, so it is not possible to show the type.

 

Understood.
The current functionality alone is useful enough. Thank you.

We look forward to more great updates in the future.

 

I've just changed computers and when I try to start tiny pedal for the first time I get this error in %appdata% - FileNotFoundError: [WinError 3] The system cannot find the path specified: 'settings/'. I saved my user data from rF2 and transferred it into the new install. Is that a problem?