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.
I have seen this happen several times, too. Now I understand more of what you mean. I haven't been able to determine why it does this, but it could be poor GPS reception or a poor GPS device and Waze thinks I'm now on a different road close by, so it thinks it needs to recalc. That's a valid reason to recalc.
Now, how Waze handles the recalc is another good topic. It can't recalc just a middle portion of the route, which is frustrating, and once it decides it should recalc, the old route is wiped and you're screwed. You area correct about this and it would be nice to see this changed.
You should put up a uservoice suggestion to get some votes and get it in front of the developers.