Waze forum

G_W1Z wrote: ↑Mon Feb 26, 2024 11:18 am With only this script running I get this error:
Screenshot 2024-02-26 061724.jpg

The list of routes does not load either.

 

Seen that often, I've noticed that flipping the route direction and/or moving pins by grabbing those usually gets it to work.

Did the WME update affect this too? Can't get it to do anything at the moment.

I'm using version 1.4.9 (doesn't seem to be a version since then) and it's misbehaving. I can see Route Speeds in my left hand pane. I can click on the tab and I see my options.

what I'm used to, is clicking on the tab, then clicking on segment 1 and control-clicking on the 2nd segment and route speeds takes over.

However, now, when I click on the 2nd segment, nothing is happening with route speeds.

If this is a result of the v1.33 WME and not enough time to update, I get it. just checking as this is one of my most useful scripts.
thanks.

Never mind. I solved the problem. Nothing to see here. keep it movin folks...

i've noticed yesterday and today that route speeds seems to "hang" when you change the time in the drop down menu. The "calculate" button turns orange. You press. the screen does not update and the button remains orange.

I've been successful by disabling script and re-enabling to change behavior back to expected.

Really appreciate the script. thanks for helping.

i don't know how "quickly" I do it but I was certainly changing times to try and determine if signal avoidance was an issue at an intersection.

thanks. I reported it because it was different. it has been working for me since i reported.

MapOMatic wrote:Update released - 2017.11.15.001 (MapOMatic fork)

New features (thanks to tonestertm, who did all the work):
- Added "Avoid Difficult Turns" option
- Added a checkbox and functionality to place results in Livemap's natural sort order, to help with troubleshooting around penalties.
* Note that when Routing Order is checked, the Try More option is ignored, to better approximate Livemap results

cool beans.

thanks.

I'm posting to see if this is a bug in route speeds or if some other thing is going on here.

The problem:
Waze appears to be routing around a traffic signal (signal avoidance) and that's no surprise. What is new is that I had route speeds selected to "shortest" vice "fastest" and route speeds still selected the longer (SA) route.

The bonus phenomenon:
This video shows how sensitive route speeds is to a very small change in the start (or "A") position in route speeds.
https://content.screencast.com/users/sa ... -13.27.GIF

A slight movement of the start position causes route speeds with "shortest" selected to go from what makes sense, ie shortest route, to the longer route which is signal avoidance.

The permalink is https://www.waze.com/en-US/editor/?env= ... s=74747491

This only started yesterday but I've found that after checking a route in route speeds, if I then try to move either the A or the B points, I can drag the point but cannot release it. Once this happens, the only thing I can do is reload the WME window. using chrome, up to date, on a mac.

https://www.youtube.com/edit?o=U&video_id=zCZdHGusZTc

(10 second video to show what I'm describing)