Is the 24.9.0 update going to fix this "data fusion" and “steps OBD data” issue, by any chance?

My HLP just got updated to 24.9.0 saying "fixed a bug in gear calculation".
Is it going to fix this "GEAR number drops to 0" issue?

My HLP just got updated to 24.9.0 saying "fixed a bug in gear calculation".
Is it going to fix this "GEAR number is one higher" issue?

Any update for the Spring release?
It's Spring and the tracking day is coming soon.

That's great news!

Is the Spring release going to fix not only the "GEAR number is one higher" issue but also this "GEAR number drops to 0" issue?

Any consideration about these "data fusion for certain GPS / OBD update rate combinations" issue or the “steps” in OBD data issue? viewtopic.php?p=27861#p27861 https://www.youtube.com/watch?v=RKsuf2QNIWo Tracking days are coming around the corner and currently, the combination of PLX Kiwi ...

Are there any updates on this issue (DCT gear drops to zero(undefined))?
Are you considering a new vehicle parameter (clutch type = DCT)?

There hasn't been an update for a while since version 24.8.2 and I'm wondering about the next bugfix release that is to fix this GEAR+1 issue.
Any idea for the next bugfix release?

It's odd but this data fusion problem occurs with OBD data but not with G-force data (LATERALG and LINEALG) which is 10Hz from iPhone.
Any idea why only OBD data is affected by the external GPS data?

I tested all Storage Rate (GPS Rate, 5, 10, 20, 50 Hz) but none of them fixed the problem. Looking at the OBD data, it looks like you are sampling the OBD data at the GPS rate but most likely you are dropping an OBD sample if the timestamp of the OBD sample gets out of the range of a single GPS samp...