Turn-by-turn for trail running

Former Member over 6 years ago

I had a pretty horrible experience with turn-by-turn on a trail run yesterday. I created a route on PC and synced it to the watch. I started a Trail Run, selected the new course from 'options', and began receiving turn-by-turn notifications once I pushed start. The course and tracking were really accurate, but I immediately noticed it wasn't displaying a turn alert when I came to a fork in the trail. Every time the trail came to an intersection, I had to guess which trail to take and then rely on the off course alerts. Then, it started giving me a turn alert every time the trail veered to the left or right. My watch was literally buzzing every 5 seconds telling me to go left, right, u-tun, slight left, slight right, while I followed the same trail along a hillside. This was maddening. I couldn't find a way to turn off the buzzing, so I stopped turn-by-turn and did my best to get home with the map.

I don't need turn-by-turn to tell me which way my trail is going, I need it to tell me which trail to take. Any ideas?

- 5.0
- Using stock maps on the 5+
- Routing is set to 'follow course'

0 bdub25 over 6 years ago

I never had any luck with course turn by turn navigation. Once I was running a trail and did the do course and it was telling me I was off course for about a .25 mile until it “figured out” that I was on course. This was a trail that I didn’t really need the navigation I just wanted to see how it was. After this experience I just used the map on unfamiliar trails.

0 nickcrebbin over 6 years ago

I had a similar problem yesterday. I created a course and downloaded it. I had my routing set to use map and my watch got stuck on calculating. Eventually I set it to follow course and it finished calculating. Turn by turn worked for about the first and last 10% of the course, on the remaining 80% it didn't work at all. Also, my screen showing the elevation profile was only correct for the first and last parts of the route, for the rest it was just a flat line. I suspect a 5.0 bug.