GEAR number is one higher (regression in 24.8.2)

[KAZUNA]

Since I reported the issue "GEAR number drops to 0" several months ago, HLT updated to 24.8.2 then I started having another issue.
Did you change the gear number calculation code in 24.8.2?

I'm attaching two lap data files.
20230625.csv is the same file I attached last time in "GEAR number drops to 0" thread.
20230820.csv is the new file that is showing the problem in the gear numbers.

As you can see 20230625.csv, you find gear numbers 0, 2, 3, 4...
However, if you look at 20230820.csv, you find gear numbers 1, 3, 4, 5...

This is not only in csv lap data but also Timer screen showing the gear numbers one higher.

So all gear numbers are calculated one higher in version 24.8.2.

[Harry]

Yes, I have applied some changes here and added this +1 issue. It is fixed already and will get available with the next bugfix release.

- Harry

[KAZUNA]

Do the changes happen to address the "GEAR number drops to 0" issue with DCT?

Do you happen to know when the next update will be available?

[Harry]

It has been a code refactoring to add some addition regression tests. No functions changes. I do not have a date for the next bugfix release, but the only open item are five new (and similar) sensors to add support for.

[KAZUNA]

I had a tracking weekend and I ran into this problem again without noticing it until I created a video on RaceRender.
I'm curious but do you have an ETA for the next bugfix release that is going to fix this GEAR+1 issue?

[KAZUNA]

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?

[Harry]

The gear bug fix will be part of LapTimer's Spring release.

[KAZUNA]

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