anyone has same problem?
830 is great but 840‘s strava live segement sucks
anyone has same problem?
830 is great but 840‘s strava live segement sucks
The x40 series switch to use a different data field. Change it to Distance to Next.
See forums.garmin.com/.../tip-4---if-segment-distance-time-to-go-is-not-working
still don't work. "Diastance to Next" seems always 500m more to the destination
I’ve already tried that and it still doesn’t work. The issue is that the “distance to next” data field isn’t providing the accurate length of the segments. The length of the segments is always off by anywhere…
The x40 series switch to use a different data field. Change it to Distance to Next.
See forums.garmin.com/.../tip-4---if-segment-distance-time-to-go-is-not-working
still don't work. "Diastance to Next" seems always 500m more to the destination
Would you be willing to share the activity file, segment file and activity profile you were using. A screenshot of video would really help.
aweatherall the calculation of the "Time Dest." is a "weird" a bit, it is starting from a huge not realistic number all the time, if a segment is only 2-3mins long, this value is 10-15mins for example, and decreasing with 2-4-6-8 seconds per sec , i think it could not have such a big amplitude, the distance of the segment is known, the starting and actual speed is known also, so honestly i cant imagine how can be this calculation so wrong... If You need, i can make a video also about it (i will try today with Time Next also, but i think the Time Dest and Time Next is the same in this case, as the Distance Dest and Distance Next also)
I can take a look. I typically don't display the estimated time, just the distance left.
yesterday where it was very annoying it was on a long climbing segment (30km long/1700m ascent), maybe it is too long for the calculation (started from many hours and very slowly went down to the ~1h:45m time ). Tomorrow i will test it more detailly on a climb, today i couldnt make video due to rain, i didnt reach the marked segment, i had to turn back and go home...
I suspect that it is not taking the entry speed or prior speed information into consideration and is starting with null values.
yes, probably it is the reason why calculation is changing (decreasing the time) so fast.
aweatherall did You raise a ticket to Garmin about it or shall i need to make a bug report in the beta section?