I didn't think it was a big problem during testing at home, but I drove about 1200 miles over the last couple days—in unfamiliar territory, they come too late. That instruction should be early enough that you can start braking at that moment for your turn, or get over a lane if you're in the wrong one.AlanOfTheBerg wrote:My experience has been the opposite: freeway speeds announcements seem just fine but surface street announcements are way too early for the final instruction.sketch wrote:I agree with some other posters that the final instruction comes too late, far too late at freeway speeds.
The Waze release candidate had the same TTS scheme as the current version—except for the first instruction, which came just after the last turn instead of at up to 4.3 miles. I tested the Waze release candidate alongside a Garmin on the route. The Waze release candidate and the Garmin had essentially the same TTS scheme, with one fundamental difference: the Garmin's second and final instructions were more flexible. At city speeds, Garmin and Waze were pretty much the same. At freeway speeds, though, where Waze warns at ½ mile, Garmin warns at 1.1 mile; where Waze warns at about 400 feet, Garmin warns closer to 800 feet. I found the Garmin's instructions to be perfectly timed.
That's why the name is included in the final instruction—so you know where exactly to turn, based on the street sign and/or the map display. The instruction would be way too late to be useful if it actually came AT the street.
Sent from my iPhone using Tapatalk 2
Re: iOS 3.8.0 Official Feedback Thread