This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Control Course Point Limit during creation of course

Today I came across the course 50 point limit of my Fenix (5x) for the first time.

Is the limitation a bug ? The fenix 5x has so much memory !
If the limitation has to be there, I would like to be able to choose which 50 points I want to see !

My fenix 3 for sure did not have the issue, It just showed the track and I was able to follow.
I do not need the turn-by-turn feature at all - just show the course.

How would I be able to control the number of course points used during track creation already ?
... or can I consider this to be a bug of the current firmware (since my 60km track is neither particularly long nor complicated to track).

0 mat_mat over 2 years ago

Hi,
6 years later...
weird that nobody has answered in all this time...
I'm encountering a similar issue with the Garmin Instinct 2 watch.
The official documentation mentions a maximum of 50 points for courses.
However, the watch is obviously capable of much more.
(50 points is an impossibly low amount of points anyway for tracks.)
I'm talking about tracks here, not routes. For routes, you can do a lot with 50 points, but for tracks it's a ridiculous low limitation.
Anyway, my watch can manage much more than 50 track points,
BUT it removes some of them. Probably some optimization.
A couple of hundred pretty crucial points disappear from a source track with about 1064 points. (which is not much at all)
Unfortunately, I cannot rely on the Garmin navigation functionality if I cannot be certain that it will follow my carefully prepared courses.
I's also frustrating that I cannot find anyone capable of explaining how the Garmin products really works.
Even the Garmin support center they seem incapable of even understanding what the issue is.
Additionally, I don't know if there are any Garmin products out there that would perform better.
Because the documentation is obviously not correct.
Did you discover more about this ?