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

Amazing

 

Massive update! Amazing as alwaays and great delivery! Wish i could only haave rf2 open, show where the widgets are and haaave config panel open so i can change stuff live.

 

A workaround would be to take a screenshot of your view in rF2 and use it as a reference.

 

you are awesome thank you very much
yes in fact I would have argued that the pc time is its widget ^^

 

@svictor you should think about changing the name of the overlay.
This huge job deserves a name that "explains" it's features.

Note: I don't have any problem with the current name, but many people new in rF2 doesn't know TinyPedal and the name sounds strange for them.

 

Doesn't it work in borderless mode?

 

no, it has to overlay one of the two window modes.

 

hello
there must be a problem with the temperature of the tires when I choose to display the simple tire temperature, only the front left and the rear right are displayed?

 

great job man!! very very good.

It's possible to add the best lap (from all drivers) in standings? only have the last lap. thanks in advance.
and both in all sessions.

thanks

 

thank you all for the comments and suggestions.

thanks for reporting, will be fixed soon.

Sorry, I forgot to mention in change log, actually for non-race session, the standings widget now always display driver's best lap time in "lap time" column (you can still see last lap time from relative widget during non-race session as always).

And for race session, it will show last lap time instead, the reason is because for race session, best lap time is the least important thing. Adding additional column for best lap time would be overkill and wasting of screen space.

I'll update those info to guide soon.

 

Aaah, cannot wait to try it, thanks for your great work, man.
This is a gamechanger in VR.

 

https://github.com/s-victor/TinyPedal/releases/tag/v2.0.2
Here is the bug fix update, and the interruption issue mentioned in this post is now fully fixed.

2.0.2 (2023-05-11)

• Standings Widget
  • Adjusted default setting "max_vehicles_per_split_player" value from 5 to 7.
• Steering Widget
  • Fixed scale marks not shown in correct position.
• Tyre temperature Widget
  • Fixed average temperature layout not shown correctly.
• pyRfactor2SharedMemory
  • Fixed data interruption issue in multiplayer session
    that would interrupt calculation of deltabest & a few other widgets.
• Misc
  • Add additional info in customization guide for Standings widget.

 

Thanks once again!

 

Hi
how does the odometer work? Does it count all of the circuits at the same time or does it have to count each circuit independently?
in two days I did 498km ^^

 

Currently it counts all track & cars and the value is saved per preset file. So if you wish to have it count individually, you may duplicate a preset for a specific track or car, and then manually editing "Meters Driven" value in Cruise widget config to 0 or something for start.

 

Great!
Thank you very much for your dedication.

 

Hi a small detail in the "timing" the best is not centered on the rest ^^

error on my part I badly edited the text file sorry on the other hand since this morning the usure of the tires shows me anything?

 

I have performance issues after driver swap with active TinyPedal, this has happened now after every driver swap on the Nordschleife.
After closing and restarting TinyPedal the performance is fine again.

 

display of tire wear

I found the error if we put bar panding with a value of 0, it causes the display bug

 

That's exactly how padding works. As in your screenshot, this is what it should actually read when you have 0 padding:

Since you put zero padding, that means no padding besides text, so there is no "gap" between each text and they look like a single line.

To be more clear, below shows the actual padding area in red line, putting 0 would remove this area:


PS:
Also for several widgets like tyre wear, when max value is 100, the character number is 3. But when tyre wear below, in order to display decimal place such as 99.3 , the character number would become 4 because of the extra period symbol. And in order to have enough room to display decimal places, the widget minimum character width must be at least 4 characters wide, hence you will see "fake padding" with 100 wear when bar padding is 0, but no padding with value below 100, because of the extra . symbol taking up one character space.