Hallo All
I did a test with the new guiding navigation feature this afternoon and it was not very good. To be precise it was so bad, that I changed back to "normal" guiding because otherwise I maybe did not find the way out of the forest again.
I did the test in an unknown area for me on very small paths with a mountainbike. The track had several crossings within itself. See here:

I planned the track on the computer with not many points, what means, that the track is often besides the real way. See here for example:

Why I did that? I recognized earlier this week that the new navigation test routine simplifies tracks before it gives them the voice notifications. See what I mean:
Original track with a lot of points (recorded track):

Track now with notifications text:high:

too much notifications, not feasable.
Track with text:medium:

here now ok, but:

no notifications on real crossings.
Back to my test today......So I decided not to do to much points, because otherwise I have to trust the simplification algorithm which I don't want, see pictures above.
This leads to the following problems:
1. When I start the navigation, it starts in "car" mode. This mode does not only mean, that I get the notifications which were "calculated", it also means that my "GPS position" sticks to the track. As long as I am not too far away from the track, I do not see my real position. That means if the track is besides the way I'm also besides the way. And if there is a crossing and I could not see were I am in real, I do not know where to go.
2. The map orientation with the compass is also locked somehow in "car" mode. In normal guiding mode I can move my handle bar around to see where exacly the track is going to. In "car" mode the map is not moving.
3. The 50m notification is far to late. You often hear the 50m notification, when you have to go right immediately.
4. If your off the track (I set 50m with three beeps), the following happens:

I'm coming from the right and followed wrong the red arrows. I get three beeps from the first red arrow on, but because of the sticking to the track, I did not see on the map, why I'm wrong. At the red point I can see on the map, that I took the wrong way and there is a line which should lead me to the blue point. Meanwhile I got a lot of beeps. So I go back in opposite to the red arrows (beep, beep, beep) and I'm on the track again (beep, beep, beep). I'm on the right track now, but I get beeps. And I get beeps until I reached the blue point.
5. The automatic display activation is activated from an upcoming notification. If after that notification, the next notification follows right away (within the display timeout) the timeout is not resetted. So the display goes off although there is the next upcoming notification.
6. The display goes off, although I'm beside the track (beep, beep, beep) and I'm trying to get back on track.
To sum it up:
I have to turn at 50m notifications (to late), on crossings where I cannot see where I am (sticked to the track), where I cannot see where to go (no compass movement of map) and when I'm on track, I hear beeps (sticking) and after recognizing that I'm wrong I cannot see where to go (display is off) and after finding the right way again, I hear beeps further on and I miss the next turn because the display is off (timeout).
Proposal:
1. No sticking. Position behavior like in the old guiding mode.
2. Compass moving map, like in the old guiding mode.
3. 50m notification earlier
4. When your off the track, always pointing back to the nearest point and not the next notification point
5. Reset of display timeout with each single notification
6. Blocking of display off, when away from the track
Thanks
Good night