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

Kind of solution, I'll not complain if svictor decides to do it.

 

Just think of it as an opportunity to get into the slipstream of the car in front!

SS

 

Having dozens of widgets up on your HUD isn't DISTRACTING?

 

In fact I use few widgets

 

v2.12.0 - New Rest API accessing module, Auto-hide Radar in Private Qualifying, Auto-synchronize track clock (time scale)
https://github.com/s-victor/TinyPedal/releases/tag/v2.12.0

Here is the Auto-hide Radar in Private Qualifying (requested by @ebeninca and others) and Auto-synchronize track clock time scale (requested by @DanRZ and others) features implemented through accessing game's Rest API.



Happy driving

https://github.com/s-victor/TinyPedal/wiki/User-Guide#rest-api


2.12.0 (2024-05-31)

• General
  • Add "power_unit" option in "Units and symbols" dialog,
    which sets power unit for Electric motor & Engine Widgets.
    Available units: "Kilowatt", "Horsepower", "Metric Horsepower".
• [New]Rest API Module
  • Add Rest API Module, which connects to RF2 or LMU Rest API
    for accessing data that is not available through Sharedmemory API.
    Note, the APP auto detects RF2 or LMU.
    This module is enabled by default.
  • Add "module_rest_api" section in JSON preset.
  • Add "url_host" option, which sets RF2 or LMU Rest API host address.
  • Add "url_port_rf2" and "url_port_lmu" options, which set port for host address.
  • Add "connection_timeout" option, which sets connection timeout duration in seconds.
• Cruise Widget
  • Now reads session "time scale" value from Rest API
    for calculating correct in game track clock time.
    Note, if Rest API Module is disabled or Rest API data is not available,
    "track_clock_time_scale" option value will be used instead.
• Electric motor Widget
  • Add "show_power" option, which shows motor power.
  • Renamed some old option names for better readability & consistency.
• Engine Widget
  • Add "show_torque" option, which shows engine torque.
  • Add "show_power" option, which shows engine power.
• Radar Widget
  • Add "auto_hide_in_private_qualifying" option,
    which auto hides Radar in private qualifying session.
    This option is enabled by default.
  • Now reads "private qualifying" value from Rest API
    for used in "auto_hide_in_private_qualifying".
    Note, if Rest API Module is disabled or Rest API data is not available,
    "auto_hide_in_private_qualifying" option will not take effect.
• Misc
  • Updated User Guide info for Units and symbols, Rest API Module,
    Cruise Widget, Electric motor Widget, Engine Widget, Radar Widget.

 

Thx

 

Finally the Rest API is included. Great News !
And still compatible with LMU. Really nice update.
Great work.

 

v2.13.0 - new Elevation Widget
https://github.com/s-victor/TinyPedal/releases/tag/v2.13.0

Here is the new Elevation Widget specifically made for hill climb and rally drivers. It draws elevation plot that commonly seen from some real life hill climb videos, and is fully customizable with many options.

Here is how elevation looks like for Isle of Man:


And a small improvement added to Flag Widget, which now displays nearest incoming traffic indicator (time gap) when local player's vehicle speed is below certain threshold (default 8 m/s). This feature can be useful for user to quickly determine nearby traffic situation after a spin or crash while trying to recover safely.

There are also a few bug fixes and improvements to Rest API Module.

New entries in user guide:
https://github.com/s-victor/TinyPedal/wiki/User-Guide#rest-api
https://github.com/s-victor/TinyPedal/wiki/User-Guide#elevation
https://github.com/s-victor/TinyPedal/wiki/User-Guide#flag
https://github.com/s-victor/TinyPedal/wiki/User-Guide#track-map-1

 

Hello, @svictor ... Just asking if you worked with the LMU Team to make their radar ?

It's almost exactly the same output and scale.
I made a video switching both radars :



I still prefer TinyPedal radar, way more configurable

And seeing tracks elevation is quite interesting. I tried the last widget. Very nice feature.

 

Tiny is awesome.

btw, DanRZ, with new LMU update seems your pack of logos for cars not working 100% have you fixed in some way?

 

Hello, just updated it, i added the bmw logo for LMU and stored a few other logos inside other folders if someone prefer older/different logos. Cadillac, Aston Martin, for example have new logos slightly differents ...

Edit : And here is the last json i extracted from LMU to import in Brands tool.

 

I'm going to disable LMU radar on settings.json then I can use the same profile pro RF2.

This new LMU tires are shit, the HUD shows green when the tires hits around 75C, really wrong, feels like iceracing, they should run at 94C+. I post the motec data on forums showing the problem.

 

Thank you guys for the feedback as usual.

Nope, I didn't.

The new tyre physics is indeed quite more challenging and harder to manage than before.

 

Tinypedal is open source, so you never know.

Anyway, I really think that you deserve more merit for what you do for the community.

Unfortunately Stephen Hood said in an interview to Traxion.gg that they don't intent to transfer the updates from LMU back to rF2, well, considering the tires, better not to do.

 

2.14.0 - Virtual Energy Widget + Calculator
https://github.com/s-victor/TinyPedal/releases/tag/v2.14.0

Long story short, Virtual Energy Widget is finally here, along with virtual energy calculator accessible from Fuel calculator, and many virtual energy related new stuff added, see change log & user guide for details.





have fun!

New user guide entries:
https://github.com/s-victor/TinyPedal/wiki/User-Guide#brands-preset
https://github.com/s-victor/TinyPedal/wiki/User-Guide#fuel-calculator
https://github.com/s-victor/TinyPedal/wiki/User-Guide#flag
https://github.com/s-victor/TinyPedal/wiki/User-Guide#fuel-1
https://github.com/s-victor/TinyPedal/wiki/User-Guide#lap-time-history
https://github.com/s-victor/TinyPedal/wiki/User-Guide#stint-history
https://github.com/s-victor/TinyPedal/wiki/User-Guide#virtual-energy

 

Auto import for Brands ! Thanks for that.

There are still some vehicules that need to be added manually. Weirdly, some vehicules only show on certain conditions on LMU. Maybe LMU has solved that.

But now we can do all, from Rest Api or manually. Really useful.

Another great update.

 

Here is an example & some tips for using the new Virtual Energy Widget:

Note, with v2.14.0 update, both Fuel & Virtual Energy Widget can be re-arranged by rows, which you can now place same rows next to each other to help with comparison, as shown in pictures at th end.

Below I setup a 18 mins race session with 499P at monza, with 17% starting energy and 40kW motor map for showing basic steps to adjust pitstop refilling strategy while driving.

First, in the pitstop panel, "Virtual energy" selector is showing the "total refilled energy after pitstop", which is different from RF2's pitstop panel (that shows how much to add). So in order to correctly set how much total energy to refill, here we just need to do a simple math, by adding values from "end" & "refill" column together, this assumes that the pitstop is made at the "end of current stint". In this case (picture below), it would be 1.60 + 24.9 = 26.5%. So here I just set "Virtual energy" selector to 27% in pitstop panel.

Note, if you decide to make an early pitstop a few laps before "end of stint", the formula will be "end" + "refill" + "used" * "number of extra laps before end of stint" (use "laps" column to determine). For example, to pit 2 laps earlier, in this case (3.79% energy per lap), it would be 1.60 + 24.9 + 3.79 * 2 = 34.08% to set in pitstop panel.

Next, looking at the "ratio" column that shows 0.902 fuel ratio, this reading is calculated in real-time from estimated fuel & energy consumption that heavily affected by "electric motor map" setting. So I just set "Fuel ratio" selector to 0.90 in pitstop panel.

After I made a pitstop with above adjustment, widgets now show estimated 0.69% virtual energy & 0.71L fuel that would remain at the end of race.

Finally, after crossed checked flag, the readings show 0.48% virtual energy & 0.51 fuel remaining in vehicle, which were very close to the early estimation. In actual race, don't forget to take leader's laps into consideration, and may be add some extra % for possible margin of error.

 

Thanks for this tutorial very useful "on the fly".

Calculating the real ratio while driving is a bit complex.

Now we have the real value in real time and we can update it at Pits stop if necessary, to make sure we get the less fuel possible on next stint and so less weight too.

If i change the regen/motor, the ratio will take time to update i suppose. Maybe, there is a way to do some kind of alert that the ratio is not stable ... or just a "tendancy", lowering, stable ...

 

Thanks a lot for your work, once again!
Is there any chance of a memory leakage with the lastest updates ?

 

I just check memory on mine in LMU. No issue. Fixed memory ... 94 MB max, 53~60 MB dynamic going up/down.

@Capeta You have a significant memory usage on TinyPedal ?