@Joaquin I think I have found the issue.
First, I’d like to thank you for taking the time for the tests and the very detailed post.
After looking at your track, I have just realized that my track is a roundtrip track, and means the same way out and back. This is something that I always do by default when I test the navigation.
And that track it also means that in the way out (going up), I also take a fork that I repeat in 2 directions and then return to the track up to a mountain. In the way back (and going down) I take the same fork doing the same repeat and then return to the track. Or sometimes I take a completely different fork, and then I return to the track.
I have tested this convoluted track in every brand of the market but Polar. And the reason is that in short trail runs or in very fast ones, sometimes you repeat parts of the tracks and knowing your watch has strong and reactive indications is interesting.
For this same reason, specially in very technical paths, is interesting to have the audio navigation indications (that can enabled/disabled with just a trigger in the navigation options of the track for most brands of the market). About this, Garmin has audio prompts for even roundabouts.
Said this. I went for an small walk to show you what I’m seeing
Have a look at this shot:
[image: 1776978252825-roundabout.png]
As you can see, there are 2 notifications for the roundabout (the way out, and the way back). When I arrive (way out, first time) to the roundabout, and when I’m almost at the roundabout, the watch is saying that there are still 18 meters left, and that’s impossible. There are perhaps 18 meters but to the point of the other notification (that should be triggered when you are back), not to the first one
[image: 1776978421588-roundabout2.png]
Is it possible the watch in this roundtrip scenario is notifying the second notification, instead the first one?
Then, I walked like 300 meters and I turned back and I did not got any roundabout notification again (this works in Garmin). I think the autoreverse is not as reactive as it should be, as I was explaining.
But this is today with an extremely small test as it’s very late now here. If a run a lot longer, I have the feeling that the watch is giving notifications inside the turns and the notifications sometimes remain after those turns. And despite the notifications are ok, and in the corresponding direction, I think there’s something very strange with the distances and response time in this roundtrip scenario.
The track I’m using means also a check that enables the roudtrip inside Komoot.
Could you test a roundtrip scenario (way out and back using the same way)?
BTW, only Garmin and Suunto can notify roundabouts and forks. And I have even seen the go straight in a fork in Suunto (not only take the fork) so this is very nice (Coros and Amazfit only notify the turn left-right and Amazfit even misses several forks, if not most).
I think that in this roundtrip scenario, Suunto has something strange here. Perhaps is something that happens where I live or in my tracks, but the thing is that I only see this discrepancy with the accuracy in responsiveness and distance in Suunto (and in this roundtrip scenario).
