@paul69 said:
As soon as I passed this junction while heading towards waypoint 5, NN recalculated the route and began insisting that I turn around and navigate to waypoint 12.
This "normal" behavior, in case there is a recalculation. The algorithm checks max 10 route points ahead for which one is closest, and obviously nr 12 is candidate for that. It's true that when there are short loops like this, this is not always the intended way, but it's a choice between bads... BUT there are two mechanisms that should have prevented this:
why is there a recalculation in the first place, when you never took a wrong turn?
if this was the first recalculation you should have been guided to #5 anyway
In my view, if you did not take a wrong way, there should have been no recalculation and the loop would have been completed normally. But in case you actually did something to trigger multiple recalculations, this behavior is exactly like the algorithm is programmed
Thanks for sharing, because these experiences is what's needed to refine the algorithm.