Loading courses in Edge 820 is slow

The software update version 3.0 released yesterday claims "Improved course route calculation times."


https://forums.garmin.com/showthread.php?358368-Firmware-Version-3-00-Now-Available

The software update version 3.0 released yesterday claims "Improved course route calculation times."


https://forums.garmin.com/showthread.php?358368-Firmware-Version-3-00-Now-Available

I tested this last night when my Edge updated.
It loads very similarly to the previous firmware 2.3! This is a course created in Garmin connect too.

When the map is in 3D mode its still a guess when this is done as the percentage still doesn't show!

Something is not correct.
I get a calculation % showing on the map page in 3D mode.
Do you have Turn Guidance enabled under course options?

So the percentage does show when Map type is 3D and

Activity Profiles -> "Ride" -> Navigation -> Map -> Guide Text = Always Display

When the above is set to 'Never' then the percentage doesn't display therefore a guess when it completes and gives a map lag.

Turn guidance setting seems irrelevant with this (i think I just have turn guidance enabled and course points disabled along with guide text.

I've emailed Garmin and they don't seem bothered.
I just load the course and finish getting ready, therefore leaving it a few minutes before setting off.

I have the same problem.

It's calculating at 10% for about 5 min. Then slowly the percentage increment up. Took about 15 min to complete the calculation. On default settings. Course created on Garmin Connect. Actually, it doesn't seem to care where the course was calculated. It does this to all of my courses - Strava and previously ridden rides.

On firmware 3.10.

The map -> Guide Text option only affects the visibility of the "calculating message", but does not skip the calculation phase and therefore the route takes a while (or a lot) to appear. To skip the calculation phase, just switch off turn by turn under Navigation -> Courses -> options icon. Loading the route is almost instantaneous and turn by turn indications will disappear - I believe that they are almost useless when following a route.

Fernando

... turn by turn indications will disappear - I believe that they are almost useless when following a route...

For many of my rides I find TBT very useful and it's one of the main reasons I got an 820 over a 520. I frequently ride routes with many small random roads.
With TBT I can hit the road, hammer, concentrate on traffic and road conditions and not miss any turns. Knowing a turn is coming up and some idea of what it will be like allows you to start to look and plan the best way to expeditiously negotiate it with respect to switching lanes, taking the lane, speeding/slowing, integrating with traffic, etc..


(I'm fully aware of TCX turn notification on a 520).

For many of my rides I find TBT very useful and it's one of the main reasons I got an 820 over a 520. I frequently ride routes with many small random roads.
With TBT I can hit the road, hammer, concentrate on traffic and road conditions and not miss any turns. Knowing a turn is coming up and some idea of what it will be like allows you to start to look and plan the best way to expeditiously negotiate it with respect to switching lanes, taking the lane, speeding/slowing, integrating with traffic, etc..

I understand your point. And you are not alone, after I start promoting this idea, some people called my attention that they do like TBT over courses. I am a slow rider, so probably that is not so much an issue for me :-). And I fully agree that, being an announced feature, Garmin has to make it work. But in fact the two or three times I used TBT over courses the 820 generated too many "turn" points to be useful (and sometimes the device got stuck). I quote "turn" because, in most cases, they were just a "go straight on road", and they were generated by the 820 because a small trail ended up in the main road. I am not sure if this behaviour is Garmin fault, since it may result from some issue with OSM routable maps in my particular area.

This is a course created in Garmin connect too.

It doesn't matter where the course came from. There's no special magic in the Garmin Connect files.

All of the course planners produce equivalent files.

But in fact the two or three times I used TBT over courses the 820 generated too many "turn" points to be useful (and sometimes the device got stuck).

The "Turn Guidance" is useful but the 820 might not be implementing it well. That is, an issue with TBT on the 820 in particular doesn't mean TBT isn't useful.

It isn't perfect. There can be issues when there are alternative roads/paths close together.

Are you using a course created on a route planner (Connect or ridewitgps) or using a recorded ride as a course?

Recorded rides are a bit messy and might produce more spurious "turn" points.