SuperDave1426 wrote:Me, personally, my concern here is that it could very well be one of those things where at one time it was, in fact, a problem. But now it may not be; they may have fixed that issue. My question is: Have there been any recent examples of this being a problem?
sketch wrote:dbraughlr wrote:What basis do you have to suspect that my understanding might be wrong?
Four and a half years on Waze and its forums have given me a pretty good understanding of how it all works.
sketch wrote:dbraughlr wrote:An unsubstantiated rumor is not a substantial basis for a Validator warning.
sketch wrote:If you're not willing to take a few champs' words for it, I don't know what else to
sketch wrote:All I'm saying is that your understanding of the penalty system may be wrong. Mis-understanding. I didn't blame you for it.
Your post, the second post, in the first thread you linked shows a user that followed the "display bug" route rather than the TTS route. I don't think it's reasonable to consider something as important as the route line being displayed incorrectly is so minor as to be considered merely a "display bug". Especially when the user isn't using sound. Is the user more likely to follow the arrow in the corner, or the route line on the screen?
AlanOfTheBerg wrote:CBenson wrote:It may actually effect the user when the endpoint of the route is on one of the two segments that connects the same two junctions.
This is one of the main issues with the "same endpoint" that affects end-users directly. The routing server may start the user on the other segment instead of the one the car icon is sitting on. To my knowledge, this bug has not been fixed in the server/app.
CBenson wrote:It may actually effect the user when the endpoint of the route is on one of the two segments that connects the same two junctions.
Users browsing this forum: No registered users