Next instruction problem and request.

[RetiredWingMan]

I previously reported this problem as a bug in the app. No matter what, the information being displayed is wrong.
I think the second turn should continue to show the distance from your current position. It just makes more sense and to me is more intuitive. So my vote is to fix the bug and leave it the way it is ... but yes it could be a little larger.

[Con Hennekens]

@Nick-Carthew said in Next instruction problem and request.:

What are your thoughts about showing the fixed distance of the second turn after the next turn?

Well I usually have strong opinions, but on this one I don't care much
I find it somewhat strange to do one distance dynamically and the other not. So I have a light bias towards it being dynamically, as is the first turn info. For a waypoint you also show the distance from current location, I think that should be the default everywhere in the app. But what I think is much more important, is that it is always the same, and that one should not have to notice whether it is dynamically or not.

[Stefan Hummelink]

@Doug-Robinson said in Next instruction problem and request.:

It just makes more sense and to me is more intuitive.

Well, I just can't comprehend why a dynamic distance countdown just like the main instruction, is more intuitive than having a fixed distance of the upcoming instruction that in fact comes after the main instruction that is counting down. After all, the second instruction will become the dynamic main one, after the current main one is achieved.

Consider the situation where the main instruction is dynamically counting down and showing "turn right in 10km" and suppose the second instruction is dynamically counting down and "turn left in 10.05km"... how does that make more sense than having a dynamic main instruction and a static "Turn left in 50m".

By having it static, you easily know that when you've turned right, immediately after you shall turn left. Without this static delta info, one has to at some moment in time, calculate the distance difference between the main and second instruction in their head, to know what to do next. Now, if the two maneauvres are far apart, that is not an issue, but the point of this second instruction is to provide you with info to plan your driving ahead.

My example above are easy numbers, and we all know that we can think of numbers that are much more difficult to calculate fast while driving a bike or car.

Imho a static distance between the first and second instruction is the most intuitive way.

To me, in it current form, the 2nd field is just useless most of the time and I solely use the voice instruction for these close together maneuvers.

A toggle perhaps?

[Con Hennekens]

@Stefan-Hummelink said in Next instruction problem and request.:

Consider the situation where the main instruction is dynamically counting down and showing "turn right in 10km" and suppose the second instruction is dynamically counting down and "turn left in 10.05km"... how does that make more sense than having a dynamic main instruction and a static "Turn left in 50m".

Well, you are not turning left in 50m but actually in 10.05km, so why not show that?

My example above are easy numbers, and we all know that we can think of numbers that are much more difficult to calculate fast while driving a bike or car.

That's exactly why I have a bias towards dynamical. You don't need to calculate anything. It just says what you can expect.

A toggle perhaps?

In Corjan's words: "NO!"

[Dave J 0]

@Con-Hennekens I see both sides but it depends on how you view the second turn. Dynamic has its uses but if I was wanting directions from someone they would say in 10 miles turn Left/right then 0.5 miles turn etc. not how you would describe it dynamically! Each have our own preference and for me I go with @Nick-Carthew and the others and would like the choice if I can.

[Con Hennekens]

@Dave-J-0, I agree both viewpoints are defendable, but I think it is REALLY too small of a thing to make it a toggle. Sometimes it counts as "it is what it is".

[Dave J 0]

@Con-Hennekens maybe but there are a number of us who find it a 'slight annoyance' as @Nick-Carthew has said. Moreover, the user interface needs to be adaptable to all users although I accept that this is not a priority at the moment given other aspects downstream. However, I remain hopeful that we have a toggle downstream.

[Nick Carthew]

@Con-Hennekens I’m not a fan of ‘it is what it is’. I firmly believe that if something can be improved upon then all effort should go into improving it.
Certainly the dynamic countdown error to the next route point should be investigated when time allows.

I’ve had a few days to think about this now and I still cannot see any logic or usefulness in having a second dynamic countdown for the second turn instruction.
The most important information for me is knowing the distance after the first turn.

[Con Hennekens]

@Nick-Carthew, haha, like @Stefan-Hummelink it seems you take this very high I think the level of user-adaptability already is extremely high, especially if you compare it to TomTom and Garmin devices which take "it is what it is" to pretty extreme levels, and no one ever complains about that. Configurability is great, too many insignificant toggles are not. I am sure Corjan will make a wise decision about this

[Inge Bakermans]

@richtea999 I absolutely agree with you. Would be really nice if that could be fixed in next update.

[Stefan Hummelink]

@Con-Hennekens Hahaha we're merely dedicated to make this the best app for all.

[Con Hennekens]

@Stefan-Hummelink, You know I am too, but I just don't think too many toggles is going to do it I'd rather have the distance being static from the first upcoming turn, then have another toggle.

[Stefan Hummelink]

@Con-Hennekens said in Next instruction problem and request.:

You know I am too

Hahahaha offcourse I know you do. I expected a response like yours muhaha.

[UltraStar]

@Nick-Carthew After over 5700 miles tour, I totally support both requests. I do not how many times I have looked at the second turn, and have been trying to figure out the distance. The fixed distance from the first turn would be perfect.
As for the size of text, man it hurts to be old. In addition to the stupid dimming of the screen on iPhone due to the high temperature, the small size of text does not help.

[UltraStar]

@UltraStar Change that to ...I do not know... in second sentence please.

[Nick Carthew]

@UltraStar You can edit your post by clicking on the 3 dots.

[UltraStar]

@Nick-Carthew Thanks.

[Corjan Meijerink]

Happy to inform all of you that after some painstaking hours, the issue has been resolved!

Distances are now calculated correctly for the next maneuver

Besides thar, the next maneuver UI has been increased in size.

We haven’t yet changed the displayed distance value, gonna give that another night of sleep.

[Dave J 0]

@Corjan-Meijerink Brilliant job. Look forward to the next update.

[Nick Carthew]

@Corjan-Meijerink said in Next instruction problem and request.:

We haven’t yet changed the displayed distance value, gonna give that another night of sleep.

Great job in fixing the problem

Now I don’t want to influence your nightly sleep but the fixed displayed distance after the next turn does make more sense

Sweet dreams buddy