When trying to follow a course for a run. Course is added from GC/strava (tried both). When trying to navigate on the course it ends up 'calculating', then thats as far as I get...even tries going into power save I wait that long.
How long are you waiting? How many miles is the course? And how complex is the course?
I've found that with courses over 3 or 4 miles in dense urban environments, the calculating phase can take 5-8 minutes. I'm not saying that's a good thing, but it is what it is. Hopefully they'll improve the course interpretation over time.
It's 55 miles. I know that's long but surely this watch should be capable....there's many ultra runners that'll look to this watch because of it's nav.
It's non-rural main A roads mostly. I'm waiting constantly, it never seems to get there! The watch tries to go into power-save mode
I've had the same happen on an 8 mile course consisting of 7 waypoints (course: use map). I ended up running it using course - use course option
Then, exactly the same happened when I tried to navigate the activity a few days later, so it's a routing problem, not course problem.
This wouldnt be as bad if the watch at least showed the course (using course routing option) while calculating the map routing option.
In an urban setting with a combination of streets and trails a 13 mile course took 11 minutes to calculate. During this calculation period the map was not displayed. The Round-Trip Course calculation for similar distances is less than 1 minute which seems more reasonable.
In an urban setting with a combination of streets and trails a 13 mile course took 11 minutes to calculate. During this calculation period the map was not displayed. The Round-Trip Course calculation for similar distances is less than 1 minute which seems more reasonable.
My experience has been similar. When using a course downloaded from GC, 1-3 mile courses take 30s to a minute to calculate and 5-7 mile courses take several minutes to calculate. However, having the watch itself generate a round-trip course takes a lot less time for similar distances. That makes me think this should be fixable in a firmware fix at some point...
