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

It would be great if you could rotate the map clockwise and counterclockwise to optimize the space on your monitor. Thank you for your great work!

 

A setting for preferred orientation, vertical or horizontal, I think would work well.

 

I will be the GPS police and say any fake floating track map should be oriented as seen from space. No flipping or twisting! The alignment should center on the entryway to the circuit and North should always be at the top. (just kidding!)

 

Thanks for the suggestions guys.


Here is the new update with map rotation and some of the recently requested features:
https://github.com/s-victor/TinyPedal/releases/tag/v2.29.0

Besides new features, this update also addressed a recently reported "Pit Menu" (MFD) flickering issue related to LMU's Rest API "pit data accessing". This issue is now resolved with new and optimized data accessing methods, as well as an option to disable "pit data accessing" completely if needed. See change log for details.

• Major change
  • Optimized "Rest API" accessing methods, which adds additional update time delay that reduces unnecessary data accessing if API data has not changed recently.
    For example, data from Rest API is accessed every 0.1 seconds on default setting, but if API data has not changed recently, the update interval will be increased up to every 2 seconds instead (for example, "pit strategy" data is only changed when user changes it in MFD menu).
  • Separated "pit strategy" data accessing from other none-pit data (fuel, energy, damage, etc), and can be turned off completely via the new "enable_pit_strategy_access" option in RestAPI Module.
    Note, recently there has been reports regarding an issue related to MFD "Pitstop" menu flickering in "LMU", which can be caused by accessing "pit strategy" data frequently. This flickering issue should not be a concern now for TinyPedal with the new accessing methods mentioned above.
    Additionally, a new "enable_pit_strategy_access" option is provided in RestAPI Module, which allows disabling "pit strategy" data accessing completely and avoids the flickering issue.
    However note, flickering issue can still be triggered by other programs or plugins that have frequently accessed to those "pit strategy" data.
• RestAPI Module
  • Apply additional time delay to update interval when data has not changed recently, up to 2 seconds max update interval. Update interval will be reset if data has updated recently. This change helps avoid unnecessary frequent data accessing.
  • Add "enable_pit_strategy_access" option, which allows turning off "pit strategy" data accessing completely. Note, "Pit stop estimate Widget" will not be able to display pit data if this option is turned off.
• [New]Suspension force Widget
  • Show visualized suspension force (Newtons) and ratio (percent).
• Suspension position Widget
  • Add "show_third_spring_position_mark" option, which shows front and rear third spring position mark relative to each suspension position.
• Track map Widget
  • Add "display_orientation" option (requested by user "peterkasbergen" and @lucamilan87), which sets track map display orientation in degrees.
    For example, a "270" value will rotate map by "270" degrees clockwise. Default value is "0", which always displays track map "north up" in game's coordinate system.
  • Improved "display_detail_level" calculation to work with smaller maps.
• Pit stop estimate Widget
  • Add "stop_go_penalty_time" option, which sets stop go penalty time in seconds. Default value is "10" seconds.
• Misc
  • Add "horizontal_gap", "vertical_gap" options for following widgets: Brake pressure, Ride height, Slip ratio, Suspension force, Suspension position, Tyre load.
  • Fixed an issue that would add time increment on pitout prediction (Track map Widget) while outside pit lane.
  • Renamed "display_orientation" option to "show_inverted_orientation" in Friction circle Widget.

 

Since recently there has been a lot questions and controversies related to LMU's Rest API accessing with various third party APPs or Plugins, I think it is time write this post to clear up some issues and doubts, and hopefully it may help others to avoid similar issues while working with LMU Rest API.

First of all, as other APP developers already mentioned in various posts on LMU forum, LMU's Rest API is quite buggy, and as many know that there is no support for Rest API from game developer. And it is unknown what fate it will be with potential game API update in future.

---

Currently there are two game-breaking issues exist in LMU's Rest API, which include:

1. Some of the Rest API "URI resource" addresses can crash game if they are accessed or opened under certain conditions.

For example, opening any of the following URI addresses in Web Browser while LMU is running in main menu will immediately crash the game:

Spoiler: URI addresses that can crash game

http://localhost:6397/rest/garage/PitStrategy/getAllPitStrategies
http://localhost:6397/rest/garage/Pitstop/getPitstopTimes
http://localhost:6397/rest/garage/getVehicleCondition

However, if those bugged URI addresses are opened while in a loaded track session, then they would not cause crash. But as soon as player leaves current session and back to main menu, accessing those addresses again will cause game to crash.

This is considered a very serious and game-breaking issue. I had contacted with one of the RF2 staff about this Rest API issue approximately twelve months ago , but unfortunately this Rest API issue is still not fixed to this date.

The current solution is to not access them to avoid any chance to cause game crashes.

Note, there are several more URI addresses that can crash game, which are not listed here, it is best to test each URI address you plan to use.

2. Accessing any of the Rest API "pit menu" URI addresses at high frequency can cause "Pitstop" MFD menu flickering. Currently there are several URI addresses related to "pit menu" data and affected by this flickering issue, include but may not limited to:

Spoiler: URI addresses that can cause pit menu flickering

http://localhost:6397/rest/garage/UIScreen/PitCarReview
http://localhost:6397/rest/garage/UIScreen/RepairAndRefuel
http://localhost:6397/rest/garage/UIScreen/TireManagement
http://localhost:6397/rest/garage/PitMenu/receivePitMenu

Among those URI addresses, "PitCarReview", "RepairAndRefuel", and "TireManagement" are more likely to cause flickering from testing results, while "receivePitMenu" has the least chance to cause flickering (probably due to its small data size).

---

As for TinyPedal, a lot tests and precautions were made to avoid those issues mentioned above while providing more telemetry data from Rest API, and all those were working without issue before v2.28.0.

In v2.28.0 update, "pit menu" data accessing was added for the first time to allow calculating and estimating pit stop duration, which is done by reading data from "RepairAndRefuel" URI address. And later on, it was reported that accessing "RepairAndRefuel" can cause flickering if accessed frequently.

So in order to avoid flickering issue, the v2.29.0 update introduced dynamic update interval methods. And instead of accessing "RepairAndRefuel" (which has high chance to cause flickering), "pit menu" data was read from alternative URI addresses "receivePitMenu" and "getPitstopTimes".

However shortly after, "getPitstopTimes" was found to be one of those bugged URI addresses that can crash game if not accessed from a track session, as mentioned above.

(It's my mistake for not testing this "getPitstopTimes" address in different situations, partially because it has been a long time since I reported Rest API game-crash issue to game developer, which is almost one year ago, and I thought it was fixed by then, but apparently they are still not fixed. In v2.29.1 hot fix, all URI addresses were extensively re-tested to ensure they work without crash in all possible situations.)

So in v2.29.1 hot fix, this "getPitstopTimes" address is completely removed from accessing. Because "getPitstopTimes" data is crucial for calculating accurate pit timing estimate, in order to compensate the loss of this data, the "RepairAndRefuel" address (which includes the same reference data as from "getPitstopTimes") was added back, but it is now only accessed once per session and then the data is cached, so it will not cause flickering issue. The only downside of this change is that some of the pit time data such as "car damage repair" may not report accurate estimated time, because the reference time for "car damage repair" changes with live car damage severity, which will not be reflected on old-cached data.

To conclude the changes mentioned above, the only major difference between the latest v2.29.1 and v2.27.1 (or earlier) is the addition of "receivePitMenu" and "RepairAndRefuel" URI addresses for accessing pit menu data from Rest API. And those two data accessing can be completely disabled via the new "enable pit strategy access" option, which then there is no difference from v2.27.1 in terms of Rest API URI accessing.

---

It is also important to note, TinyPedal only reads data (resource) from Rest API via http "GET" requests, this APP does not modify Rest API data in any way.

The reason I mention this is because, recently there have been reports about LMU's pitstop menu selections sometimes would be modified unexpectedly for reasons that currently unknown of. And some users were questioning whether this or other APPs could be the cause. However as said, this APP only reads data from Rest API, there is no data modified. And so far I have never encountered similar issue.

For reference, one of the most recent report of "pitstop menu selection issue" was from following thread:
https://community.lemansultimate.co...sets-changes-your-pit-strategy-mid-race.7736/
And the OP appears not using any overlay applications.

You may also wonder what happens with RF2's Rest API. The answer is simple, RF2's does not have all those data available in Rest API, and thus none of the above issues exist in RF2.

---

Finally, TinyPedal is a community-oriented, completely Free and Open source telemetry overlay project (licensed under the GPL v3 License), it has evolved greatly thanks to many people for contributing in various ways. You are welcome to report issues, make suggestions, help with bug fixes or feature implementations, etc. And all source code is available on github project page, feel free to check them out.

Thanks and happy driving.

 

Thanks for providing all the detail, I was not aware of the issues. Crew Chief uses the LMU REST API but only when needed (so at a very low frequency) and no-one has reported any problems. It does POST RepairAndRefuel to set the Pit Menu when the user gives a pit command (and on entering the pits if "Enable LMU auto refuelling when entering pit in race" is selected) but it seems it is not the cause of the bug reported in that LMU post. (If "Enable LMU pit manager" is not selected it will not POST at all.)

Like TinyPedal, Crew Chief is Open Source and relies on people reporting any problems: https://gitlab.com/mr_belowski/CrewChiefV4

 

Thanks for your work on crew chief and sharing the methods and thoughts, on demand access could be a very good alternative solution.

 

2.30.0 (2025-06-04)

• Major change

New "Preset Transfer" dialog is now available by clicking "Transfer" button from "Preset" tab in main window (requested by user "Wigg1es"),
which allows to quickly transfer selected settings and options from currently loaded preset to another preset.
This new addition can make life much easier for users with a lot presets and options to manage and keep them updated with latest changes.
See "Preset Transfer" section in User Guide for usage and example.

• Wheels Module

Optimized average wheel radius data sampling and calculation.

• Weather Widget

Add "decimal_places_temperature" option for customizing number of decimal places for displaying track and air temperature (requested by user "Dean688"). Default is "1" decimal place, set to "0" to hide decimals.
Note, when number of digits is less than expected, extra leading zero or decimal place will be added to fill the gap.
Release v2.30.0 · s-victor/TinyPedal · GitHub

 

Just a heads up, with today's LMU, there are some major changes in LMU's Rest API, and several API data addresses are no longer available (or may be changed), so some data will no longer be able to display in current v2.30.0 TinyPedal version.

Note, some API data (virtual energy, damage, etc) can still be displayed by using old v2.28.1, as RepairAndRefuel address is still available in today's game update, so if you currently really need those data it, use v2.28.1 instead ( https://github.com/s-victor/TinyPedal/releases/tag/v2.28.1 ).

I'll investigate and see what can be done (this may take time, please be patient), until then.

Cheers

 

2.30.1 (2025-06-12)
https://github.com/s-victor/TinyPedal/releases/tag/v2.30.1

This update updated all Rest API related data accessing to work with LMU's June update. See change log for details.

• Major change to API accessing
  • Updated URL addresses for accessing data from LMU's Rest API (due to changes from June update), including new penalty time data that used for accurate pit time estimate.
  • Virtual energy, brake wear, vehicle damage, pit stop related data are now read from "RepairAndRefuel" URL address (same as in v2.28.1).
    Important note:
    "RepairAndRefuel" URL address previously was known to have chance to cause MFD pitstop menu flickering issue if accessed at high frequency. This flickering issue has been acknowledged by game developer, but not yet fixed by game.
    "RepairAndRefuel" is the only address for accessing those important data from LMU Rest API (as of LMU June update), currently there is no other alternatives.
    This "flickering issue" should not be a concern for user using only TinyPedal, as the default "update interval" in RestAPI Module is set on 100ms.
    For user concerned or experienced with this issue, you can either increase the value of "update interval" in RestAPI Module (such as "500" or "1000"); or, disable "RestAPI Module" entirely (which then those crucial data will not be available).
    Also note:
    There are currently other third-party APPs or Plugins that also have access to this "RepairAndRefuel" URL address, and running them at the same may have higher chance to trigger MFD "flickering issue".
  • Removed "enable_pit_strategy_access" option from RestAPI Module, this option no longer works due to game API changes.
  • Various improvements and optimization to game API accessing.