I'm finding the "ahead / behind" time to be very unreliable lately. As in, it will tell me I'm ahead by 10s then just a few moments later behind by 10s. Or the reverse. How exactly is the ahead/behind time calculated, aside from the obvious "remaining distance divided by average speed of segment so far"? That doesn't seem like what the calculation is and how often it's updated internally.
Bugs:
1. Sometimes I've seen the "KOM finished" notification happens shortly after the start of the segment. I've also seen it somewhat related to choosing a new target during a segment.
2. Corrupt segment list. A segment that I'm not near pops up, or the segment list seems to be corrupted -- the names, distances, and leaderboards are mixed up. Had to delete the segment from the device and try to re-sync it.
3. Some segments have just KOM and PR. Others have several more items along with names. Why are they different? Some segments were sync'd over wifi and others via garmin connect app.
All bugs have been encountered with both the 8.10 firmware and the 8.34 beta.
I'd also like to suggest some enhancements for segment :
1. The average speed for the current "goal" would be nice to know for pacing yourself. If not as a field, as part of the popup somewhere.
2. Your average speed so far for the segment.
3. Average speed required to tie the current goal, e.g. how fast you need to go from this moment on. This is handy for pacing yourself on long segments, not so much on short ones.
4. It's hard to be sure, but many times the "distance left" seems to lag a bit.
5. The segment popup can obscure a lot of the screen for segments with long names. This is annoying when you're trying to pace yourself up to speed for the start. Even though you can tap it away, it's a distraction that requires you to take your hands off the bars.
6. As the segment nears completion, is it possible to increase the frequency of data updates for the fields to make them more accurate? I've had segments that I know end before an intersection not complete until I'm practically in the intersection. Is that due to lag in how often the "distance to go" is updated?