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

I just noticed that is possible also in LMU to repair brakes.

In the MHD, go to the Pits menu, and scroll to the very last option.
I was on a LMP2 in LMU and it says : Brake Repair > No
The options is there. By the way, i didn't check if i could set it to Yes, but wear is really zero, so it is useless.

It's probably the same on rF2, scroll to the end of the Pits menu and check if there is a repar option.
Or it looks like it is grouped with Damages repair ...
 
ebeninca said:
But how you can select to repair brakes on MFD Hud?
Click to expand...
index.php

scroll mfd :)
 

Attachments

yashiman said:
BTW, rF2s brakes can be repaired in the pit now.
You can set brake repair on the physics calculator (S397's spreadsheet).
Click to expand...
Thanks mate @yashiman, great find!

I just tested by adding AllBrakes=1 in [PITMENU] of skipbarber's HDV file, and "Repair brakes" option now appears in Pit Menu, and repair works as intended.

Also found that this new option was mentioned in rF2 Physics Calculator 0.42 update in April from last year:
Add "AllBrakes" repair option.
Click to expand...

To enable "Repair brakes" option in Pit Menu for existing mod:
Open vehicle HDV file in notepad, go to [PITMENU] section, add following two lines at bottom of this section:
AllBrakes=1 // 0 disable, 1 enable
AllBrakesTime=(120,12,1) // Time to repair brakes, random delay, concurrent repair

And also possible to make yourself a patch to enable brake repair by adding following line in Upgrades.ini (suitable for league race or offline playing):
Code: 
UpgradeType="Brake Repair"
{
  UpgradeLevel="Enable"
  {
    Description="Enable Brake Repair"
    HDV=[PITMENU]
    HDV=AllBrakes=1
    HDV=AllBrakesTime=(120,12,1)
    HDV=
  }

  UpgradeLevel="Disable"
  {
    Description="Disable Brake Repair"
    HDV=[PITMENU]
    HDV=AllBrakes=0
    HDV=
  }
}

@ApexModding @Nick9320 @mantasisg @Nicola59 @redapg


yashiman said:
And v2.18s "Track Clock Time Scale (cruise)" did not work in rF2.
I will check v2.19 tomorrow.
Click to expand...
I just tested and timescale(from rest API) works fine in RF2 (there wasn't change to Cruise clock or Rest API). May I ask which value have you set in Time Scale session setting?

There is one setting called "Use Race %" which will not work, because it (game) uses some kind hidden formula for calculating Race percent scale, which is not exposed from API (API would return -1 instead). If this is the case, then there nothing can be done.
 
DanRZ said:
By the way, i didn't check if i could set it to Yes, but wear is really zero, so it is useless.
Click to expand...
The main difficulty is to find the thickness threshold at the moment when brake failure occurs, but it could be difficult to do. The effective thickness is the actual brake lifespan, without this thickness threshold data available directly, user can only know the thickness threshold at the moment when brake failure happened (in RF2 dev mode, this is the moment when thickness reading suddenly changes to zero). "Mechanical failures" Time Scale setting probably can help finding this threshold faster (at least works in RF2), I hope to do more testing to see if the threshold can be found easier.

For reference, in RF2 dev mode, brake thickness millimeter readings can be displayed on screen by pressing Ctrl+D twice, then when one of the brakes reaches threshold, the thickness reading becomes zero. In actual physics file (HDV), this is defined in "BrakeFailure" value. Effective thickness range can be found by subtracting "BrakeDiscRange" and "BrakeFailure" values (plus random variation) in HDV.
 
svictor said:
Thanks mate @yashiman, great find!

I just tested by adding AllBrakes=1 in [PITMENU] of skipbarber's HDV file, and "Repair brakes" option now appears in Pit Menu, and repair works as intended.

Also found that this new option was mentioned in rF2 Physics Calculator 0.42 update in April from last year:


To enable "Repair brakes" option in Pit Menu for existing mod:
Open vehicle HDV file in notepad, go to [PITMENU] section, add following two lines at bottom of this section:
AllBrakes=1 // 0 disable, 1 enable
AllBrakesTime=(120,12,1) // Time to repair brakes, random delay, concurrent repair

And also possible to make yourself a patch to enable brake repair by adding following line in Upgrades.ini (suitable for league race or offline playing):
Code: 
UpgradeType="Brake Repair"
{
  UpgradeLevel="Enable"
  {
    Description="Enable Brake Repair"
    HDV=[PITMENU]
    HDV=AllBrakes=1
    HDV=AllBrakesTime=(120,12,1)
    HDV=
  }

  UpgradeLevel="Disable"
  {
    Description="Disable Brake Repair"
    HDV=[PITMENU]
    HDV=AllBrakes=0
    HDV=
  }
}

@ApexModding @Nick9320 @mantasisg @Nicola59 @redapg



I just tested and timescale(from rest API) works fine in RF2 (there wasn't change to Cruise clock or Rest API). May I ask which value have you set in Time Scale session setting?

There is one setting called "Use Race %" which will not work, because it (game) uses some kind hidden formula for calculating Race percent scale, which is not exposed from API (API would return -1 instead). If this is the case, then there nothing can be done.
Click to expand...
That’s good to know, thanks mate!
 
Amazing news. I wonder how could I have missed that for so long. Attention was not paid properly. Thank you @yashiman for pointing it out, and thank you @svictor for tagging me.

It will be very interesting to test it all now.
 
svictor said:
Thanks mate @yashiman, great find!

I just tested and timescale(from rest API) works fine in RF2 (there wasn't change to Cruise clock or Rest API). May I ask which value have you set in Time Scale session setting?

There is one setting called "Use Race %" which will not work, because it (game) uses some kind hidden formula for calculating Race percent scale, which is not exposed from API (API would return -1 instead). If this is the case, then there nothing can be done.
Click to expand...

Thanks for your reply.

Today, I played rF2 in normal timescale (x1).
This practice session started at 10am.
However TinyPedal's time is 10:35, like a x5 timescale.

My TP continued to update for a long time, maybe it is wrong.
I will try to clean install TinyPedal tomorrow.

View attachment upload_2024-10-17_0-17-19.png
 
yashiman said:
Today, I played rF2 in normal timescale (x1).
This practice session started at 10am.
However TinyPedal's time is 10:35, like a x5 timescale.
Click to expand...
Thanks mate for the info.

But unfortunately I cannot reproduce your issue. Also tested with various different time scale with different track mods(such as x2, x17, x49), and no issue found.

Below screenshot is taken 10:00AM @ Oschersleben 2023 (assume same as your screenshot), "Time Scale" is set on "Normal" in session setting. "Rest API" web page shows "Normal" (currentValue = 1), and widget is synced with MFD. All settings from "Rest API module" & "Cruise Widget" are on default.
index.php


ps: You can also check if clock time is synced in LMU, as both games use same session output. Also check if there is anything(such as firewall) that would block TinyPedal from accessing game's Rest API.

If anyone else has encountered this issue, feel free to report (please attach with screenshots to include both "game clock/widget" and "session time scale setting").

Thanks
 

Attachments

Last edited:
svictor said:
2.18.1 - Bug fixes
https://github.com/s-victor/TinyPedal/releases/tag/v2.18.1
  • General
    • Fixed a font weight verification error that prevents user from saving any changes in "Gear Widget" config dialog.
    • Fixed missing combo choices (text alignment, font weight options) from Elevation and Gear Widget config dialog.
  • Differential Widget
    • Fixed cooldown timer did not reset after changed or restarted a session.
  • DRS Widget
    • Add "drs_text" option for setting custom DRS display text.
    • Optimized DRS status check.
Click to expand...
If you are going to continue to post such a lonnnng list of fixes, then we shall be forced to keep NOT PAYING YOU!!! :)
 
@yashiman One more thing I forgot to ask, is it on server or singleplayer?

If on server, can you test different server time scale setting and see if time is synchronized correctly?

You can check Rest API session time scale by open following link after entered server:
http://localhost:5397/rest/sessions/setting/SESSSET_race_timescale

Then check if "currentValue" number matches your server time scale value. This is the value that TinyPedal uses to synchronize with in-game clock time. If this value is wrong, then clock time will be wrong, if it is the case there is probably not much can be done since it is currently the only reliable source to get time scale info from game.

-----------------

Thanks @davehenrie

No worries. If any one finds this APP useful, then just have fun, nothing more needed. If one day my life can no longer sustain this hobby, then I'll quit.

Again, thanks to everyone for supporting this APP.
 
Thank you @yashiman and @Jonathan07 for helping with tests.

From your screenshots, "SESSSET_race_timescale" info from Rest API wasn't correctly synced with server side for unknown reasons. One thing you can still try is to check if time scale value is correctly synced in "Race" session.

But either way, there isn't much I can do to fix this issue, as Rest API is currently the only reliable source for accessing time scale from game. May be consider report this to forum bug report section.
 
2.19.1 update
https://github.com/s-victor/TinyPedal/releases/tag/v2.19.1

As promised, here are some brake failure testing results from LMU (currently works exactly same as in RF2).

Hypercar tests:
index.php


P2 tests:
index.php


GTE tests:
index.php


Those tests were done using time scale and some special methods to quickly burn and wear out brakes. The limitation is that currently those methods can only be done on the wheel that drives the car, which are the rear brakes in those cases.

Most Hypercar & P2 have same front & rear brake thickness, so probably safe to assume they may have the same brake failure thickness threshold at front and rear brakes. GTE is probably the same, or maybe with small amount difference between front and rear.

The new 2.19.1 update now also supports to set front and rear brake failure threshold separately in case there are differences.

For example, in the test results from 499P, left rear brake hits failure threshold at 25mm thickness, with small amount variation (probably around 0.1mm judging by the rear right brake reading). So you can just set both front and rear "brake failure thickness" options in Brake Wear Widget to "25" for this car. Once all set, turn off "Show thickness" option to show percentage wear for more accuracy.

------

Below is the full testing results and reference table gathered from my testing, almost all data shows that Hypercar & P2 classes have about 25mm failure threshold, while GTE has 30mm failure threshold.

index.php


I haven't yet had time to test all cars, but so far all results shows that each vehicle shares the same amount brake failure thickness threshold within the same vehicle class.
 

Attachments

Last edited:
(Screenshot is case of x1)
I checked the Rest API session time on my online server.
Server time scale x1, x3, x5, x10, All cases have rest api had x5.
Is this rF2's error?, then It can't be helped.
Anyway TinyPedal is a great tool.
Thank you for joining me.
 

Attachments

Thanks guys.

------
@yashiman Thanks again for your help.

This is indeed very strange.

I have just tested multiple session in current official servers (Race control) as well as public community servers, and those servers are returning correct time-scale value to Rest API (which is "1" in those servers), and tinypedal is correctly synced with server and Rest API.

To further make sure, I first set time-scale setting in singleplayer mode to something other than "normal", such as "x8", then I checked Rest API which gave me "8", this makes sure if server doesn't update this value, it will always be "x8". Next I entered official & community servers, which then those servers did update Rest API time-scale value to "1" (as normal scale), and clock time is correctly synced.

I wonder if it has something to do with specific server setting? Maybe it is an issue with private server or something? If you got time, can you check in official server? Thanks.
 
You must log in or register to reply here.
Back
Top