AlanOfTheBerg wrote:This could be a routing server error or something wrong with the app. Unsure, but it happened several times on Friday 11/2. Logs were uploaded at some point. Unsure if this was a beta or 3.5.

There is no way that going .4 miles will take 43 minutes. .4 miles may have been to the next turn perhaps...

This is a known and acknowledged bug that already existed before 3.5 and the betas. Sometimes (not always) the distance until the first turn is not counted in the total distance.

Kuhlkatz wrote:If WME supported both Mph and km/h via drop down or even 2 separate input fields and recalculated the figures that is sent to the back-end in one format or the other, it would not be a problem. The client just needs to support the same conversion based on what the country is set to or client preferences is using. Shizz like this is not rocket science.

Back in the days when we had cartouche I'm pretty sure in the UK we entered figures in mph. If you did this and then looked at the same camera in Papyrus (which became WME) then the figure was converted to km/h.

Does anyone else remember this or is my memory fuzzy? I guess it was 18 months ago. Sadly Cartouche is gone now may it rest in peace

If WME supported both Mph and km/h via drop down or even 2 separate input fields and recalculated the figures that is sent to the back-end in one format or the other, it would not be a problem. The client just needs to support the same conversion based on what the country is set to or client preferences is using. Shizz like this is not rocket science.

xteejx wrote:Regarding the speed camera speed issue;This will still be a problem as soon as someone from the continent drives over without the conversion, so there are many sides to the problem unfortunately

+1

jasonh300 wrote:I don't disagree with you that it should do the conversion and work either way, but it doesn't.