Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
I agree it could be improved. In its current state it simply calculates how long it would take at your current speed to reach the point on the track where the other car is. Of course, that is not reality because you will either be accelerating or decelerating most of the time. This is worse on road courses than it is on ovals. The only way to improve on this is to divide the track up into many segments and keep track of the time spent in each segment and then use that to project your time. This has its own flaws. Do you use your best time or an average, etc. I’m not even sure how iRacing does it. But I will not be able to match them. Knowing this, your feedback is welcome. - Jeff…
On Mar 19, 2019, at 11:52 PM, NekoDisc ***@***.***> wrote: SIMRacingApps's relative data has not enough accuracy. In the worst case, it is near twice as time as ingame blackbox. I hope that SIMRacingApps has more correctly relative data. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
I have an idea that perhaps relative's accuracy improve than now, but I have no confidence to explaining well in English.
This idea has the problem that the large track like the Nordschleife need too many checkpoints.