A to B route choice bug

[Corjan Meijerink]

On recalculation, the newest faster route is calculated.
Could be that a recalculation occurred and it immediately decided to take the other route

It's a tradeoff between sticking to user choice and forcing back to a route you want anymore because the other is faster.

[OGRIII]

@Corjan-Meijerink Txs Corjan, but how do I make sure it fixes the route I choose, not the default fastest?

[Corjan Meijerink]

@OGRIII You can't

[Con Hennekens]

@OGRIII, To put it into perspective : A single destination is considered as a request for the fastest (or shortest) route. Any calculation will generate just that. That's why the route can change big time when you deviate. It is by public request on this forum that this method was chosen.

@Corjan-Meijerink, I am very much in favor of how it works now, but @OGRIII has a point than when you chose a specific (non-default) one from the suggested options, it is a bit strange that it is thrown overboard at the first occasion. Maybe it is an option to start a track instead of a route when any of the non-default route options are chosen? Then it would stick to the track instead of going for the fastest recalculation. Just a thought...

[OGRIII]

@Con-Hennekens thanks for your reply.
I find it hard to believe that people requested to ignore the route options and to always use the default. What's the point of giving options if the system ignores them? As I said earlier the TomTom App offers alternative A to B routes. When you select a non default it takes you on that route. Furthermore as you ride the route it shows green faster alternatives en route that you can ignore or take.
This is clearly a bug in the MRA software!

[Con Hennekens]

@OGRIII, It is not for you to decide if it is a bug or not. That's a developers prerogative .

In this case I can be clear: it is by design. The straight line option to destination is intended just like that: fastest way to destination. Options like avoid highway are still respected, aren't they? People requested that as a measure against being send back into the route when deviating. Other people than you found it "a bug" when the route was respected while explicitly chosen for the straight line route. It's one or the other, with a possible solution I presented in my earlier post above. It's for the dev team to decide what to do with it. To be honest, I think there are more urgent matters, since you are the first and only one to complain about this.

[OGRIII]

@Con-Hennekens Txs again Con, but as you are not affiliated to MRA I would prefer an answer from the developers.
I accept that MRA main function is not a "simple" A to B route. I can use other more suitable apps for that. However, sometimes if the simple things aren't pointed out and rectified they can create a knock on effect in the future.

[Con Hennekens]

@OGRIII, here you go

Source: https://forum.myrouteapp.com/post/56221

[OGRIII]

@Con-Hennekens Cheers Con. Txs for your positive inputs. Warm regards OGRIII.

[Con Hennekens]

@OGRIII, you're welcome Mind you that I feel like your suggestion was valid. If you choose a specific one out of 3 suggestions, it is a bit strange for it to not be honored at the first possible occasion. Most people use that feature like a "get me there fastest way, I don't care how" option. Choosing one of the non-default options should perhaps reconsider that.

[OGRIII]

@Con-Hennekens Agreed. Cheers.

[Corjan Meijerink]

Thanks @Con-Hennekens

@OGRIII we specialise in scenic routing.
Sticking to a specific AB fastest route resulted in many unwanted recalculations forcing you to stick to that option where another option is available. It is indeed a deliberate choice.