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

Hi, unfortunately, with the new GUI library used in v2.0 , OBS "Window Capture" does not work with TinyPedal any more.
Currently the only way to capture overlay is to use "Display Capture".

 

Thank you for your reply.
I will continue streaming with display capture.
I wish happy if many people knew about the wonders of TP.

 

https://github.com/s-victor/TinyPedal/releases/tag/v2.1.5


This update adds rake display in millimeters, horizontal style pedal display, and more improvements to delta & fuel calculation.

User guide:
https://github.com/s-victor/TinyPedal/wiki/User-Guide#pedal
https://github.com/s-victor/TinyPedal/wiki/User-Guide#rake-angle

2.1.5 (2023-06-04)

• Fuel Widget
  • Fixed a display issue with very large number formatting.
• Pedal Widget
  • Add "enable_horizontal_style" option,
    which shows pedal bar in horizontal style.
    This option is disabled by default.
  • Add "inner_gap" option,
    which sets gap between pedal and max indicator.
    Note, to completely hide indicator & extra gap space,
    set both "inner_gap" & "max_indicator_height" value to 0.
• Rake angle Widget
  • Add "show_ride_height_difference" option,
    which shows average front & rear ride height difference in millimeters.
• Delta Module
  • Improved accuracy of delta data calculation.
  • Fixed inaccurate reading issue that could happen
    during first lap of race or garage-out lap.
• Fuel Module
  • Improved accuracy & consistency of estimated fuel usage calculation.
    First lap of race & pit-in/out laps no longer affect overall fuel calculation,
    which gives more consistent stint fuel readings.
  • Accurate estimated fuel consumption & fuel delta readings
    from race first lap & pit-in/out laps.
  • Record delta fuel data from valid lap only.
  • Fixed invalid delta fuel data readings from
    tracks that uses fast timing mechanism.
• Core
  • Various improvements to sharedmemory data access methods.
• Misc
  • Updated user guide with new options for Pedal & Rake angle Widget.

 

First of all thanks and congratulations for this app.
It would be useful for me an option for configuring the number of decimals in the different data of the fuel widget. Something like
fuel_mask = "1f" can be enough for me.
Two decimals can be too much "noise" for a quick look during race and I don't need this level of detail.

 

thanks for suggestion, next update will add decimal places options for every fuel readings.

 

Thanks! I also miss in this fuel widget the total fuel tank capacity and the current capacity (total capacity - current fuel in tank). I use this info for knowing when I can refuel (when the current capacity is greater than fuel needed).
I can see in the code the variables are already there.

 

This app is great... love all the customization you can do on it. Great work SVictor.

Ever thought have making a groups just for moving purposes? ... Say if one groups Gear & Pedals, flags, DRS and Lap-best... together.... Then when you move one widget in the group all the other widgets would move along with it.

 

Thanks, tank capacity is already visualized on "fuel level bar".
Edit: if to add another column for capacity, I could probably also add another estimated number of pitstops that is based on current fuel level when pitting at the middle of a stint rather than end of stint.

Thanks. This probably would be difficult to achieve since every widgets are individual windows. I'll add it to wishlist.

 

A suggestion for fuel meter... Can the estimate be green if making it to the end. Red if needing to pit before the end? Right now it just turns red if the tank is nearly empty, not if you are going to run out.

 

Thanks for suggestion.

I could add a red indicator on refuel reading, however there is an issue. For any race that requires at least 1 or more pit-stops, it will basically always display red (which is distracting) since fuel is not enough to finish in one stint.

Note, the current fuel widget already has multiple readings that indicate whether the amount fuel currently in the tank can make to the end of race:


First is the plus & minus signs on the refueling estimate reading "refuel". Positive value indicates additional refueling and pit-stop is required. Negative value indicates the amount extra fuel left at the end of race, which is enough to finish the race without pits.

Another is the estimated number of pit-stops reading "pits", which also indicates whether additional refueling & pit-stops are required to finish race. Any non-zero decimal places would be considered for an additional pit-stop, since it is not possible to do a half pit-stop.

An important note is that this estimated pits value concerns only pit-stop made at the end of stint, it does not estimate early or half way pit-stops, which may require another pit stop estimated reading that calculated based on the current lap as mentioned earlier.

 

v2.1.6 - Early pit stop fuel calculation
https://github.com/s-victor/TinyPedal/releases/tag/v2.1.6

This update adds early pit stop fuel calculation and many related improvements as recently requested.

Here is full explanation of the new "early" reading from Fuel Widget (also see user guide for more info):

And explanation to "refueling level mark":

And new options:


User guide:
https://github.com/s-victor/TinyPedal/wiki/User-Guide#fuel-1

2.1.6 (2023-06-12)

• Deltabest Widget
  • Add "delta_display_range" option,
    which sets max display range (gain or loss) in seconds
    for delta reading, accepts decimal place.
    Default value is "99.999" seconds.
• Fuel Widget
  • Add "*early" option, which shows estimate number of pit stop counts
    when making an early pit stop at end of current lap.
    This value can be used to determine whether an early pit stop
    is worth performing comparing to "pits" value.
    More example usage and explanation in user guide.
  • Add "show_refueling_level_mark" option,
    which shows estimated fuel level after refueling.
    If the mark is not visible on fuel level bar,
    it indicates total refueling has exceeded fuel tank capacity.
    Default mark color is green.
  • Add "decimal_places" options for each individual fuel info.
    Maximum value is limited to "3".
  • Add "bar_width" options, which sets each column width in chars.
    Default value is "5". Minimum width is limited to "3".
  • Add "caption_text" options, which sets custom caption text.
  • Renamed several fuel options for consistency.
  • Removed "*start" option and starting fuel reading.
• Fuel Module
  • Add early pit stop calculation.
  • Improved calculation accuracy under certain conditions.
  • Exclude delta fuel calculation from estimated fuel consumption reading
    while vehicle is in garage stall.
• Force Module
  • Use standard deviation for max average g force comparison.
• Misc
  • Updated user guide with new options for Fuel Widget.

 

I went directly from v2.14 to v2.16 and my delta bar isn't working properly, it increases the time difference very fast like my car was stopped on track.

Do I need to delete the config and start from scratch? No problem, just to know.

 

Ok, I deleted the files of the track I was running on the deltabest folder, solved!

 

Hi, if you still have the old deltabest file of the track, please upload it here so I can take a look to see if there is any potential issue (otherwise no worries), thanks.

 

Sry, I deleted already, seems that was something specific with Watkins Glen Boot, because I tried other tracks and it not happened, probably the file has been corrupted.

 

https://github.com/s-victor/TinyPedal/releases/tag/v2.1.7

A small update with a new incoming traffic indicator for Flag widget, which shows the time gap between player and nearest incoming on-track traffic while player is in pit-lane or exiting pit.


Additional delta data validation and error correction methods are also added for delta & fuel module, which auto corrects any potential data desync issue found.

User guide for flag widget:
https://github.com/s-victor/TinyPedal/wiki/User-Guide#fuel-1

2.1.7 (2023-06-16)

• Flag Widget
  • Add "pit_closed_text" option, which sets custom pit closed text.
  • Add "show_traffic" option, which shows incoming on-track
    traffic indicator (time gap) while in pitlane or after pit-out.
  • Add "traffic_maximum_time_gap" option, which sets
    maximum time gap (seconds) of incoming on-track traffic.
  • Add "traffic_pitout_duration" option, which sets
    traffic indicator extended duration (seconds) after pit-out.
• Delta & Fuel Module
  • Add additional delta data validation and error correction methods,
    which auto corrects potential data desynced & disordered issue
    between recorded laptime and corresponding distance data
    that could happen in rare cases.
• Misc
  • Updated user guide with new options for Flag Widget.

 

I noticed some kind of bug on the P2P widget, at least for BTCC...

There's a rule that after you release the P2P button a cooldown timer of 4 seconds activates, if you press the P2P before the timer ends, it reset and you need to wait more 4 seconds to use.

It's visible that a disconnection between the widget and the car dash exists in this specific point. In the situation mentioned above the P2P widget goes blue (P2P ready), meaning that theoretically you can use the P2P, but the blue bar in the car dash stills off. So if you take the widget as a reference you end up pressing the P2P button reseting the timer again, entering in a loop, creating a mess for the driver.

I tried to take a screenshot of the moment but I wasn't able to do it, almost impossible to do a print screen while you're driving fast.



Do you think that is possible to correct it, making the P2P ready indicator (blue color) always synchronized with the car dash?

 

Hi, this issue is a limitation in the API, which game API's does not expose "when" next "legal" activation is available (there is no API data which tracks player's p2p button state).

This is also stated in the first implementation of P2P widget in this post:
https://forum.studio-397.com/index....ve-fuel-calculator.71557/page-18#post-1125386

Unfortunately there is nothing can be done. Currently it is best use in game HUD for P2P indication.

 

v2.1.8 - Add new configuration options for accessing Shared Memory API
https://github.com/s-victor/TinyPedal/releases/tag/v2.1.8

A lot things have changed to support more customizable options for API accessing, it is now possible to restart API, override active state (which mainly affects autohide & data updating) and player index (which can be used to display other player's data on overlay, can even used to record other player's deltabest data, etc). See user guide for detailed explanation.


And a new option to enable customizable map background:


New options explained in User guide:
https://github.com/s-victor/TinyPedal/wiki/User-Guide#shared-memory-api
https://github.com/s-victor/TinyPedal/wiki/User-Guide#track-map


2.1.8 (2023-07-13)

• [New]Shared Memory API configuration
  • Add "Restart API" option to main menu bar & tray context menu,
    which can be used to quickly restart shared memory API accessing.
  • Add "Shared Memory API" config dialog,
    which can be accessed from main menu bar "Config" menu.
  • Add "shared_memory_api" section in user config file.
  • Add "access_mode" option,
    which sets access mode for shared memory API.
    Mode value "0" uses copy access and additional data check
    to avoid data desync or interruption issues.
    Mode value "1" uses direct access, which may result
    data desync or interruption issues.
    Default mode is copy access.
  • Add "rF2_process_id" option,
    which sets rF2 process ID string for accessing API from server.
    Currently this option is a placeholder, and should be left blank.
  • Add "enable_active_state_override" option,
    which enables "active state" manual override.
  • Add "active_state" option,
    which overrides local player on-track status check,
    and updates or stops overlay & data processing accordingly.
    Set "true" to activate state.
    Set "false" to deactivate state.
    This option works only when "enable_active_state_override" enabled.
  • Add "enable_player_index_override" option,
    which enables "player index" manual override.
  • Add "player_index" option,
    which sets "player index" override for displaying data from specific player.
    Valid player index range starts from "0" to max number players minus one,
    and must not exceed "127".
    Set value to "-1" for unspecified player, which can be useful
    for display general standings and trackmap info (ex. broadcasting).
    This option works only when "enable_player_index_override" enabled.
• Vehicles Module
  • Renamed "Standings Module" to "Vehicles Module",
    which provides vehicles data.
• Force Widget
  • Fixed a display issue with very large readings.
• Trackmap Widget
  • Add "show_map_background" & "bkg_color_map" options,
    which shows background of the inner map area.
    This option only works for circular type tracks.

 

Nice update, again ...
Will it work in Spectator mode ?