I thought about adding a long reply explaining why its fine for some use cases to only require a few points but that there are other occasions, like when planning routes for large groups where multiple different "engines"/navigation devices will be used, then more points are required.... etc etc etc...
But this just made me laugh .....
The planned route above takes what I would say is the expected logical path between points 1 & 2,
click the Navigate button & ....
the route/path is re-calculated
I understand that different engines/routing algorithms can calculate different paths & there is probably a perfectly logical reason for the difference in this case. I do not expect a fix.
I just thought it was hilarious that within the same app it can display one path & then on the next screen show a different path
& this is why I prefer to use more points to "constrain" the engines/algorithms to the path I want to take.
So for a route similar to the above, where there are different possible paths that the engine/algorithms might choose, I would normally place an additional point somewhere between 1 & 2 to prevent the strange path the engines sometimes decide to take.
This simple control of the engines/algorithms obviously uses more points