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

May I make two suggestions?
I know there is a user manual, but what has been written in the posts on this forum are much more explanatory with pictures and graphs.
As a result if I want to look for something to find out how it works I have to go through the pages one by one to find the post that was updated and explained how it works.
Could the pictures and explanations be included in the user manual?

Also, is it possible to be notified through the widget if there are updates?

 

Thank you all for your kind comments.

@emd86 thanks for suggestions.

Currently there is no plan to add auto-update feature. The primary goal of this APP is still to keep it as simple and minimalistic as possible with only the necessary features & functionalities that matter to driving experience, and keeping it running efficiently.

All info in Changelog is already included in User Guide, which should be enough for existing or new users to find out necessary info. And default settings are good enough for normal usage in most cases without customization. One way to easily keep the APP updated with latest changes is to use "git" command line to pull new changes and run from source (see project homepage for details).

For preview screenshots, the best I can do is posting preview screenshots of new changes in each update post in this thread, which I've been already doing.

The difficult part is that it takes a lot extra time to create preview screenshots. It usually take half to an hour to prepare screenshots for a new update release, and takes much longer for major update with a lot new stuff. Because it involves setting up game sessions properly with specific car and track combo, and driving in the right situation to take the required screenshots, and finally marking annotations and prepare changelog. It would be even more difficult and time consuming to maintain every new and old preview screenshots to keep them updated with changes. For me, it is really much easier just posting info on github alone than having to posting them on both sides.

It might be possible to ask some members of the community to help. However those kind things are difficult to keep up with. Previously, I had been part of some leagues admins & esports racing team for many years, and one of the common things we experienced was that people's enthusiasm and motivation will eventually fade away (almost nothing last sadly), and usually much quicker than we would initially anticipated. Often time we got players who were very passionate and promised us to help out the league voluntarily (as we all did), but eventually people had disappeared after a few weeks or months. As a result, our RF2 league ceased activities for 2 years now, and no one seems to be interested in taking the responsibility and reviving it. Though it's understandable, as how hard and busy life is nowadays, cannot really ask too much from the others.

This is the reason that I prefer to keep things as simple as possible to reduce maintenance difficulty, and focus on improving the APP.

Happy driving.

 

Totally understandable and thanks again for the hours you spend on this app.

Have a good year

 

Thank you for the support, wish you a happy new year too.

 

Happy new years.
Again thanks for the work.
It's possible on the relative to add an indicates visual drivers are within 1 sec of each other.
When race on multi-categories. i find it important.

 

thanks, I'll try add it in next update.

 

Hello, good morning and happy new year to you!
Would it be possible to add a sign on the track map indicating where we will leave after the pitstop?

 

@Marcelo Prestes thanks, assume your request is similar to the request from this post earlier? https://forum.studio-397.com/index....ve-fuel-calculator.71557/page-38#post-1145750

I think it is possible, but it probably will take some work. I'll see what I can do.

 

Hi, I can't get the brandlogos to work. I've downloaded the file from DanRZ, placed the files in the tinypedal folder and activated them in the Standings and Relative HUDs and refreshed the tinypedal preset, but they're not showing up.
Am I missing something?

 

You need to get the list of vehicles from brand editor. There is a query to do while the game runs (bottom left), and save it. And then it will work.

 

Thank you, I've got it working now Also a big thanks for the logos!

 

would it be possible to create an option showing the app even in fullscreen mode like MSI Afterburner can do. Rfactor2 and LMU create massive framestutters and spikelags since Windows 11 on my new system with 7800x3d and 4070ti Super

 

According to this thread, its up to the overlay developer to make the app gsync compatible https://forums.blurbusters.com/viewtopic.php?t=9592

Is this possible to implement with tiny pedal?

 

Unfortunately no, it is not possible to show the APP in fullscreen, this has been always the limitation from the beginning, as the same limitation other sim-racing overlay APPs are having.

Those other "system performance" overlay that mentioned, most of them did fullscreen by "DLL injection" methods, which cannot be done for normal GUI programs, and "injection" stuff has its own problems and limitations.

Recently "nvidia app" has been reported to cause noticeable performance issue for many users, may be check if it was causing stutter issue, details and solution in following link:
https://www.tomshardware.com/pc-com...ames-run-up-to-15-percent-slower-with-the-app

 

Thank you for the great updates @svictor . Nice change to the track map with the classes. But is it possible to have colours per class and numbers for overall standings instead of which place they are in class on the track map?

 

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.