• Welcome to MX Bikes Official Forum. Please login or sign up.
 
July 11, 2020, 12:22:56 PM

News:

MX Bikes beta14e available! :)


Telemetry bug ? (+ bonus bug, maybe)

Started by HornetMaX, January 13, 2020, 10:37:29 PM

Previous topic - Next topic

HornetMaX

@PiBoSo:

In the thread of my MaxHUD plugin there's a report of a strange behavoiur of my LiveTiming (posts from tfc and teeds, from here).

What my LiveTiming does is to save the position (fPos) and time (fTime) in an array all along a lap (your best lap).
On subsequent laps I do the same in a different array and hence I can compute the time gap at the current point on the track, between the ongoing lap and the currently best one.

The RunTelemetry call of the output plugin seems to receive some weird data, here's an example (relevant part only):

@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.763742, fT:154767.734375
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.763926, fT:154788.375000
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154804.046875
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154825.359375
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154843.796875
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154867.578125
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154887.109375
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154907.015625
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154926.875000
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154945.796875
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154965.390625
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154984.546875
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.765946, fT:155003.312500
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.766131, fT:155022.921875

As you can see, fPos is 0.763742 on the 1st call (1st of the ones shown here), then 0.763926 on the 2nd but on the 3rd it goes back to 0.099025 and stays there for a few calls (10 in this case), before resuming with more normal values (0.765946 then 0.766131). This of course screws up my LiviTiming thing (and makes some weird telemetry graphs :) ).

Notice that the point at which this happens has nothing special (no crashed bike).

According to tfc and teeds, this seems to happen only on some tracks. I can reproduce it systematically on Ironman track: drive first lap out of pits and on the second lap (1st "real" lap) it happens always for me. So my LiveTiming of the 3rd lap is screwed.


P.S.
Another weird thing, likely unrelated.
On Ironman when you go to track from the paddock you don't cross the start/finish line, but the ghost of the 1st lap out of pits is recorded anyway. This is probably unwanted (the 1st lap out of pits is not considered as a valid lap by MXB anyway, in terms of timing).

PiBoSo


Thank you for the report.

Unfortunately it's not a simple bug, but rather a code design error, that also causes other issues, like the inability to reset the bike under a bridge.
The problem will be fixed as soon as possible.

iNsane | WW

Quote from: PiBoSo on January 14, 2020, 07:04:04 PMThank you for the report.

Unfortunately it's not a simple bug, but rather a code design error, that also causes other issues, like the inability to reset the bike under a bridge.
The problem will be fixed as soon as possible.

yey!


   🌐 MX Bikes custom content
MXB-Mods.com

   📚 MX Bikes User Wiki
MXB-Wiki.com

   💸 Feel free to donate
PayPal

HornetMaX

Quote from: PiBoSo on January 14, 2020, 07:04:04 PMThank you for the report.

Unfortunately it's not a simple bug, but rather a code design error, that also causes other issues, like the inability to reset the bike under a bridge.
The problem will be fixed as soon as possible.


Thx a lot for the info !

𝖙𝖋𝖈