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

v1.6.0 update - new Instrument Widget
upload_2022-6-24_22-26-36.png

DL: https://github.com/s-victor/TinyPedal/releases/tag/v1.6.0

The new Instrument Widget includes 5 useful and very important car instrument indicators, and is highly customizable (and very well optimized with very low CPU usage).
Note: wheel lock & slip indicator requires at least one full lap before it can get accurate wheel radius for calculating slip ratio for a given vehicle (wheel radius of last driven vehicle will be auto-saved to config.json file).

As usual, make sure to read Customization Guide:
https://github.com/s-victor/TinyPedal/wiki#instrument

TinyPedal 1.6.0 (2022-06-24)
  • [New]Instrument Widget
    • Show Headlights state.
      When Headlights on, icon turns white.
    • Show Ignition & Starter state.
      When Ignition on, icon turns white.
      When Ignition on while Engine off, icon background turns green (default color).
    • Show Auto-Clutch state.
      When Auto-Clutch on, icon turns white.
      When Clutch pressed, icon background turns cyan (default color).
    • Show Wheel Lock state.
      When Brake pressed and Slip Ratio reaches threshold, icon background flashes red (default color).
    • Show Wheel Slip state.
      When Slip Ratio reaches threshold, icon background flashes yellow (default color).
    • Include many customizable options.
    • New instrument icon by Xiang.
  • Cruise Widget
    • [New]Show current in-game clock time of the circuit.
  • Core
    • Fixed an issue where Deltatime module would fail to record deltabest laptime
      for point to point tracks after certain amount driven distance.
    • Various optimization.
    • Updated build_py2exe.py script.
  • Misc
    • Updated customization guide with new configurable setting for Instrument & Cruise Widget.
    • Updated features.md with Instrument Widget info.
    • Updated README.md.
 
Last edited:
svictor said:
v1.6.0 update - new Instrument Widget
View attachment 45938
DL: https://github.com/s-victor/TinyPedal/releases/tag/v1.6.0

The new Instrument Widget includes 5 useful and very important car instrument indicators, and is highly customizable (and very well optimized with very low CPU usage).

As usual, make sure to read Customization Guide:
https://github.com/s-victor/TinyPedal/wiki#instrument

TinyPedal 1.6.0 (2022-06-24)
  • [New]Instrument Widget
    • Show Headlights state.
      When Headlights on, icon turns white.
    • Show Ignition & Starter state.
      When Ignition on, icon turns white.
      When Ignition on while Engine off, icon background turns green (default color).
    • Show Auto-Clutch state.
      When Auto-Clutch on, icon turns white.
      When Clutch pressed, icon background turns cyan (default color).
    • Show Wheel Lock state.
      When Brake pressed and Slip Ratio reaches threshold, icon background flashes red (default color).
    • Show Wheel Slip state.
      When Slip Ratio reaches threshold, icon background flashes yellow (default color).
    • Include many customizable options.
    • New instrument icon by Xiang.
  • Cruise Widget
    • [New]Show current in-game clock time of the circuit.
  • Core
    • Fixed an issue where Deltatime module would fail to record deltabest laptime
      for point to point tracks after certain amount driven distance.
    • Various optimization.
    • Updated build_py2exe.py script.
  • Misc
    • Updated customization guide with new configurable setting for Instrument & Cruise Widget.
    • Updated features.md with Instrument Widget info.
    • Updated README.md.
Click to expand...
Wheel slip with rF2? We haven't seen any of the GT DLC cars that have that in real life have it modeled in rF2 have we? (so good job!)
 
v1.6.1 update - Race Countdown Timer for Gear Widget
upload_2022-6-29_12-44-30.png

DL: See v1.6.2 instead

This update mainly fulfills the recently request of Startlights function, which is realized in the form of Race Countdown timer. It will be shown on Gear widget during countdown game phase for standing-type start only(includes formation/standing), and has a 20ms accuracy.

In case of doubt & question about legitimacy of Race Countdown timer (as inevitably):
  1. Countdown timer is calculated using the formula below,
    Seconds to start = mLapStartET - mElapsedTime
  2. Both mLapStartET & mElapsedTime values are part of rF2's standard API.
  3. mLapStartET exists long since RF1.
  4. The interaction between the two values has been well known by players/programmers (if not by many), and has been used by some Plugins/APPs/Overlays for years, there is no secret.
  5. Both values are also essential for calculating player's current laptime, which is the reversed formula as below,
    Laptime(sec) = mElapsedTime - mLapStartET
There is NO hack, NO cheat involved. Whether to use this feature, or disable it from config.json file for maximum ethics & realism, is up to user; or, if RF2's DEV ever wishes to block access to this kind interaction.

Other improvements of this update include significantly increased accuracy of wheel radius & slip ratio reading for Instrument Widget, as well as many small optimization.

Enjoy

Edit: for faster cars, especially formula or prototype, increase "minimum_speed" value is advised (for example, value of 50 means APP will only record radius data when speed is above 180kph, this helps filter out invalid low speed spin data). See changelog below for details.

TinyPedal 1.6.1 (2022-06-29)
  • Instrument Widget
    • Add new "minimum_speed" setting in config file, default value is 16.5 (m/s),
      which is the minimum speed threshold before APP can record wheel radius samples.
    • Add new "minimum_samples" setting in config file, default value is 400,
      which is the minimum number of radius samples that required for calculating average wheel radius.
    • Both settings significantly increase accuracy of wheel radius reading.
  • Gear Widget
    • [New]Add an optional Race Countdown timer for standing-type start only(includes formation/standing),
      which only shows during countdown game phase, and has a 20ms(50fps) accuracy.
    • Add "show_countdown" setting in config, set value to false to disable Race Countdown timer.
      Note:
      • Countdown timer is calculated using the formula below,
        Seconds to start = mLapStartET - mElapsedTime
      • Both mLapStartET & mElapsedTime values are part of rF2's standard API.
  • Wheel Widget
    • Fixed wrong "rideheight_offset_rear" reference.
  • Core
    • Various optimization.
  • Misc
    • Updated customization guide with new configurable setting for Gear & Instrument Widget.
 
Last edited:
v1.6.2 update - Startlights display for Gear Widget
upload_2022-6-30_12-18-38.png

DL: https://github.com/s-victor/TinyPedal/releases/tag/v1.6.2

This update brings a new proper Startlights display feature for Gear Widget, with 20ms accuracy, which is 100% legit.

Also, due to concerns that raises within our league regarding the use of Countdown Timer, I have decided to disable Countdown Timer feature by default.

Note: Countdown Timer can still be enabled by editing config.json with a special code as documented in customization guide. It is meaningless to hide this as people already knew it for years and used on other HUD app. However it is better that user understand the consequences and potential unfair advantages could gain from Countdown Timer before trying to use it.

See customization guide for full details:
https://github.com/s-victor/TinyPedal/wiki#gear


TinyPedal 1.6.2 (2022-06-30)
  • Gear Widget
    • [New]Add Startlights display with 20ms(50fps) accuracy, which works the same way as how the game is designed.
    • Race Countdown timer feature is no longer enabled by default, which now requires a special code to enable it.
      See customization guide for details.
    • Fixed missing custom background settings.
  • Core
    • Increased Deltatime module refresh rate from 10ms to 1ms.
  • Misc
    • Updated customization guide with new configurable setting for Gear Widget.
 
Last edited:
v1.6.3 update - Auto-save last laptime for accurate Fuel calculation & Timing Widget display
DL: https://github.com/s-victor/TinyPedal/releases/tag/v1.6.3

Customization guide: https://github.com/s-victor/TinyPedal/wiki#timing

TinyPedal 1.6.3 (2022-07-03)
  • Core
    • Deltatime module now stores last laptime value to "last_laptime" key value in "timing" section of config.json.
    • Both Fuel & Timing Widget can read this saved last laptime value from Deltatime module & config.json.
    • Estimated laps & time for a given amount fuel can now be accurately calculated & displayed
      based on existing saved last laptime without having to do any additional laps.
    • Fixed a NaN value error that can happen if game crashes.
    • Optimized data handling for Relative module, Radar Widget, Relative Widget.
  • Misc
    • Updated customization guide with new configurable setting for Timing Widget.
 
Hi Svictor,
great job!!

I don't know if someone already asked for it, do you think is possible to add a pedal inputs widget with a lines graph

Pedals.jpg


Thanks in advance
 
Thanks again Svictor for your dedication and work.
I had an issue wich was on me, but who know, perhaps we can find something.

During a race, I was keeping an eye on the fuel and as it's on the timer, it was ok, then, with few seconds left to race, the leader launched a last lap, that was going to be tight and I didn't have the ability to anticipate that, I had to serve a last second pitstop wich was disastrous.

Do you think there is a way to make the fuel estimation somehow work with the leaders lap ?
 
Capeta said:
Thanks again Svictor for your dedication and work.
I had an issue wich was on me, but who know, perhaps we can find something.

During a race, I was keeping an eye on the fuel and as it's on the timer, it was ok, then, with few seconds left to race, the leader launched a last lap, that was going to be tight and I didn't have the ability to anticipate that, I had to serve a last second pitstop wich was disastrous.

Do you think there is a way to make the fuel estimation somehow work with the leaders lap ?
Click to expand...

I noticed something related, the fuel widget calculation doesn't consider when you're a lap behind the leader in fixed laps races, the widget should reduce one lap on total necessary fuel to end calculation.

but I don't know if is possible to adjust it.
 
Capeta said:
Thanks again Svictor for your dedication and work.
I had an issue wich was on me, but who know, perhaps we can find something.

During a race, I was keeping an eye on the fuel and as it's on the timer, it was ok, then, with few seconds left to race, the leader launched a last lap, that was going to be tight and I didn't have the ability to anticipate that, I had to serve a last second pitstop wich was disastrous.

Do you think there is a way to make the fuel estimation somehow work with the leaders lap ?
Click to expand...
Hi, thanks for suggestion.

You can already estimate extra lap fuel consumption from widget, which is described in feature list:
https://github.com/s-victor/TinyPedal/blob/master/docs/features.md#fuel
  • Show estimated total required fuel for finishing race, negative value indicates estimated extra fuel after race ends.
Any negative value you see in "require" box is the amount extra fuel you will have left after race timer reaches zero (in a time based race), or leader crossed finish line (in a lap based race). So all you need to do is plan & test fuel beforehand, to know how much extra negative value you want to have on fuel widget display.

For example, in a time based race as below pic shows, the amount required fuel reading is -0.5 (and last lap fuel usage is 1.47), which means you will only have 0.5 fuel left after race timer reaches zero(note, APP already counts last lap as full lap for calculation after race timer reaches zero, still it DOES NOT necessary mean leader won't do one more full lap, for example, if leader has crossed finish line just a few second before race timer ends, it will result one extra lap that APP may not foresee). And this is where you will have to do careful planning beforehand before a race. You will have to decide whether to include one extra lap fuel(that is 1.47) to total fuel, so that you don't risk being run out of fuel if leader does one extra lap, and same applies to warmup lap.
upload_2022-7-5_11-31-49.png


The important thing is always to plan, calculate and test fuel usage beforehand. If a race would possibly include one or two extra laps from warmup lap or extra leader lap, those should be carefully considered and included in fuel calculation. And in last 1.6.3 version, you can simply do a valid lap, then just adjust fuel level to see the estimated laps/time.

ebeninca said:
when you're a lap behind the leader in fixed laps races
Click to expand...
Thanks. This shouldn't be a big problem, since the driver is already one lap behind, carrying extra fuel won't change anything. Also it is not possible to "estimate" a driver himself being lapped by a lap or two in a race so that he can carry 1 less lap fuel beforehand...

Matlorc said:
I don't know if someone already asked for it, do you think is possible to add a pedal inputs widget with a lines graph
Click to expand...
Thanks. It is possible, but not viable currently. The GUI library used for this APP does not support GPU acceleration, this means heavy graphics display such as your suggested plotting function, would result huge amount CPU usage, which is not viable.
 
Last edited:
Thanks for that explanation.
Funny thing is, I did a full race distance to check fuel but the pace was so much faster because of the grip evolution wich I can't never seem to get right.
As I said, it's on me, I should be able to do some calculations while driving. :D
 
svictor said:
Hi, thanks for suggestion.

Thanks. It is possible, but not viable currently. The GUI library used for this APP does not support GPU acceleration, this means heavy graphics display such as your suggested plotting function, would result huge amount CPU usage, which is not viable.
Click to expand...

ok, I understand thanks for the immediate reply
 
Just tried this...Great job. Reminds me of Trackmap plugin.
One thing that would be nice is to have the title of the each widget as an option.

1) Does it show you relative gap to car in front an car behind?
2) How about relative sector times Like in F1. Green, yellow and purple sectors.
3) How about a short cut Key to Toggle hiding the overlays while in the menus?
 
boxer said:
Just tried this...Great job. Reminds me of Trackmap plugin.
One thing that would be nice is to have the title of the each widget as an option.

1) Does it show you relative gap to car in front an car behind?
2) How about relative sector times Like in F1. Green, yellow and purple sectors.
3) How about a short cut Key to Toggle hiding the overlays while in the menus?
Click to expand...
You can check a box to auto hide the overlay when in the pits. You can add widget titles,(although I haven't tried that yet) the link that @svictor posted has a full page or two of options you can try.
https://github.com/s-victor/TinyPedal/blob/master/docs/features.md#fuel
 
boxer said:
Just tried this...Great job. Reminds me of Trackmap plugin.
One thing that would be nice is to have the title of the each widget as an option.

1) Does it show you relative gap to car in front an car behind?
2) How about relative sector times Like in F1. Green, yellow and purple sectors.
3) How about a short cut Key to Toggle hiding the overlays while in the menus?
Click to expand...
Thanks.

Most stuff are explained in "Widget function overview" section of first post of this thread. Of course many new widgets have been added since, so some widgets may not be mentioned in that section. However you can find descriptions from feature list, as well as previous version release posts which includes pictures. (I'll try to keep widget function overview up to date, when time allows)

Most of the widgets functions are easy to understand once you have driven a few laps.

Widgets are designed to be as simple as possible. If adding caption to every widgets, that will seriously overwhelm driver view, and it will downgrade APP performance, as well as making APP more clumsy and difficult to code. So only those widgets that absolutely necessary to have captions, would have them.

Relative gap is already displayed in Relative Widget, which has the most customizable options so far. Just give it a try.

And lastly, it is not required to have every widget enabled. It is better to only enable a portion of widgets that are most useful under different condition.


Edit: First post is now updated with all current widgets function description.
 
Last edited:
I'm not sure, as I don't have VR. So far haven't heard anyone reported with success either.

I have heard that some VR programs can project "windows" into VR, which potentially could work with this APP, as every widget is basically a window. However, all the widget window is set to not shown on taskbar, which other programs may have trouble to detect this kind window. Nevertheless, there is one program I know that can "see" this APP, which is OBS studio, so may be possible.
 
Hi

I really like your app, thanks for the work.
If I may suggest an additional widget (not part of the fuel widget, so you can place it very prominently):
A "PIT NOW!" Warning, which shows a blinking, red rectangle/bar/text, as soon as the remaining fuel is less than 1.2 (configurable?) Laps, so that you don't forget to pit... ;)

Thanks
Marco
 
You must log in or register to reply here.
Back
Top