fdbryant3 wrote:Then for whatever reason the system decides it needs to recalculate the route, for whatever reason that this point the server times out. That is when the route disappears at least till it recalculates again.
What Waze should do is once the Waze client receives a route it should be cache. That way when it recalculates if it is unable to receive a new route it can continue to display and work off the cache route.
True! Searched on a username in combination with 'login' 'button' and those where too common.RallyChris wrote:Note that the built in search on the forum is useless. The common word filter is on, and it's basically removed all the words anyone would search on.
cobra wrote:What area are you in? It shouldn't recalculate unless you leave the route it set. Is this happening? If the maps in your area are very inconsistent, then that will cause it to re-calc a lot.
There does seem to be a bug in the re-calc, as you mention. I see it happen also. I'm not sure if it fails to re-calc the route, and then stops displaying routing, or if the server connection fails and it stops displaying the routing, but it does sometimes seem to just go away without any notification in this case.
Waze is an online nav system. it doesn't keep the a full world or US map saved to do local route calculations. It requires the server.
Users browsing this forum: Bing [Bot], Google [Bot], paulkok_my