Thanks, this will be fantastic and I shall look forward to the latest servive release.
My own preference would definately be yards, (probably bias because I also play golf so am very used to working in these units). Metres would also be fine but find feet very difficult.
Right! Thanks for the report. The bug only occurs when the distance format is set to miles and the altitude format is set to meters.
The bug will be instantly fixed in an extra service release 2.2.6 build 1165 coming out this evening.
One question, especially to US and UK citizens: Which unit would you prefer for turning instructions?
[ ] meters
[ ] feet
[ ] yards?
e.g. "turn slightly left after 200 meters"
I double checked and can confirm it definately does say 300 metres, however I played around with the distance and altitute settings as you suggest and discovered that when I change the altitude setting from metres to feet, the voice output also changes from metres to feet. Regardless of the altitude setting, the voice output is given at exactly the same distance before the turn so is basically correct when the altitude setting is in feet but wrong when it is set to metres. This would suggest to me that a bug fix may be required?
It would be interesting if someone else could test this out and see whether they experience the same problem.
Are you sure it says "300 meters"? I think it probably says "turn after 300 feet", which is about 90 meters.
Voice output is either "after 100 meters" or "after 300 feet" but never "after 300 meters". How are your distance and altitude units (general settings) set?
Problems with voice guidance when approaching turn
Whilst following a route using voice guidance, I recently noticed the initial instruction when approaching a turn is out by some distance. I consistently get an insruction saying turn right (or left) after 300 metres. This occurs when I am more like 80 metres from the turn. The second warning telling me when that I should actually make the turn is much more accurate usually within 15 yards of the turn itself. Also the "distance from route" message seems perfectly accurate.
I have tested this on several different maps and routes and find the same problem each time. Do you think there is anything I can do to correct this or is it something that could be corrected in the software?