v1.48 - Updated to work with new WME

TheGo2SWATking wrote: ↑Thu Nov 17, 2022 1:27 am Appears to be broken with latest WME. Is an update in the works?

A new version (v1.49) was uploaded yesterday to make it work on newest WME.

If you've edited your local copy, it won't update until you reinstall it from Greasyfork.

TheGo2SWATking wrote: ↑Thu Nov 17, 2022 1:27 am Far lanes never worked and paths probably wouldn't work either. If this is still being developed, is support planned for both of those?

Waze does not include this information in the routing data, so it is not possible to display the effect of far lanes or paths. Sorry.
 
 
 

SuperDave1426 wrote:Does this tool still work? And if so, how the heck to I activate it? I don't see anything in WME that looks like the image (General, Route) in the first posting, and I can't seem to find a tab that says Route Checker in it. A pointer would be much appreciated!

As Timbones said, treat it like Route Speeds by selecting a start and end segment. Then look for the tab in the left panel.

Timbones wrote:There's still the issue that when you have a route showing, you cannot deselect one of the segments to select another. You can only click to deselect all of them, and start again. This is because the route layer is now shown on top of the segment selection layer, and I can't figure out a work around.

Any reason why the obvious solution - adding a "pointer-events:none" style to the layer container div - isn't suitable? A quick play around with this version of the script suggests there's no need for it to capture any mouse events on the route layer, so letting them all fall through to the underlying WME layers seems safe enough.

Feature Request:

It'd be handy to have an indication of when the most recent edit was done along the routes being displayed, to save us having to click on each segment manually to see if there've been any changes made since the UR was submitted and which might then account for the WMERC results failing to confirm what the UR reporter is complaining about...

I am having a problem with a route -- route checker seems to be picking the wrong destination point/segment. Perhaps this is because another segment crosses at the midpoint of the selected segment. Is it possible to drag the destination point a little further along the segment?

https://www.waze.com/editor/?env=usa&lo ... 1,83162659

The route is like this:
https://www.waze.com/livemap?lon=-75.91 ... 9862302085

But it should be like this:

https://www.waze.com/livemap?lon=-75.90 ... 62&zoom=15


Thanks for this really amazing script. It has allowed me to find all kinds of things that need to be fixed.

iainhouse -- thanks. That's the workaround I used.
PesachZ -- So obvious -- once you point it out. Doesn't have to junction anything, be saved, or even be in ones editing area. Only there to generate an endpoint. Thanks.

I've noticed difference in road instructions (prompts) produced by the script and Live Map at roundabouts with certain configuration. Script produces different than Live Map instructions if entering and exiting segments are connected to one node on roundabout.
You can check this on WME here.
Screenshot form WME: http://prntscr.com/gb7z9n
Screenshot from Live Map: http://prntscr.com/gb81mm

This script has stopped working in Bulgaria as of today. Probably it has something to do with the applied vignette restrictions.

If routes cannot be generated with LiveMap due to a problem on Waze's end, Route Checker keeps trying indefinitely. It never stops, and doesn't give the user any feedback.

Can a time to live or similar be put in place with a message?