Romainrob's collection

the dropbox links are not working

@oibaf Hi, Dropbox suspended all my public links 🙁
Too much traffic they said.
It seems it will be stuck like that for 24H.
Sorry about that.

Huge thanks for your work here. 

IRacingExtraProperties.iRacing_LapsRemaining - Can we get this value as a float instead of an integer for timed races.  I'm trying to get accurate refuel amounts and it would be good to know how much this accounts for. For ex. if you estimate there are 10.7 laps remaining, I'm going to take 11 laps of fuel. However if there are 10.3 laps remaining, I'm very likely taking 10L of fuel and will save 1-2s over my opponents in the pits. 

Better yet, is there any chance of showing what goes into this calculation. I appreciate if you want to keep that closed source.

@fullyjosh Hi, I'll take a look.
From memory, it's simply the remaining session time / best lap time, rounded up.

• - Reworked the lapsRemaining and totalLaps properties for time limited session.
  - Added a lapsRemainingFloat property.

Thank you for adding this! What do you use for the laptime calculation? Is it my(user) best lap time like you suggested earlier?

@fullyjosh 
Hi,
Yes, I divide the remaining time by the driver best lap time if available.
In order of priority, it will use BestLapTime, AlltimeBest and LastLapTime to get first estimate as quick as possible.

@romainrob appreciate you sharing. Have you thought about using - DataCorePlugin.GameRawData.SessionData.DriverInfo.CompetingDrivers01.CarClassEstLapTime ? I'm not sure where this coming from or if it's worth considering.

@fullyjosh 
These are theoretical static lap times.
I use these for gap computation.
I could use these as fall back for when no time at all as been set too.
But I like using the best time in priority. It at least adjust to the driver max pace.

Hi,
"Stealthy" hotfix. (still named 1.0.7)

I added CarClassEstLapTime as fall back for the total laps estimation.
Now it in order of priority, it will use BestLapTime, CarClassEstLapTime.

I also tweaked the gridding audio alert to prevent false positive.

I love the Input Display overlay with iRacing, but wonder about this red line on the clutch display.  Is that intentional, and if so what is it indicating?  Or perhaps its a glitch?

I do have an exaggerated ceiling value for the clutch set in the joycalib.yaml file to allow for dual clutch style launches but experimenting with that does not change the red line on the Input Display.

@robertsmania
When you first drive a car, the input plugin learns the clutch bite point from the first 3 standing starts (based on change in speed).
The learned threshold is displayed as a red line and exported to a property (ExtraInputProperties.ClutchBitePoint) so it can be used to make a custom clutch friction shaker effect.

This cannot account for clutch wear.
"Teach" the plugin with a fresh car and release the clutch slowly for a more accurate result.

If the saved value is incorrect after 3 starts go to "Additional plugins" / "RSC - input Display" screen and click the button to discard the saved bite
point. The plugin will learn again during the next 3 standing starts.

Edit: The property for the shaker effect is ExtraInputProperties.ShakeIt_ClutchFriction

Fascinating!  Thank you for the prompt and comprehensive reply @romainrob 

Hello everyone, yesterday for the first time I used your dashboard, and the standing and relative overlays, I have a problem with the overlays in the sense that they are not updated, but this only happens to me in the race, do I need to change any settings?

Hi @marco-pavona
Could you please zip and share this folder? C:\Program Files (x86)\SimHub\Logs

This could also be related to this issue:
https://www.simhubdash.com/community-2/postid/2056/
In dash studio settings, you can map a button to quickly reload the overlay layout on the fly, and see if reloading it fixes it.