Waze forum

YUL you should contact Glodenox by MP or in discord, i have the same problem with some perma generated by validator

perma ?

Hello,

i think that the perma generated by validator are no more valid
it seems that there's a problem in lat and lon values (gps coordinates)

perma generated by validator
https://www.waze.com/fr/editor?zoomLeve ... =411555374

.../fr/editor?zoomLevel=19&lat=6060345.91664&lon=-192908.63409&env=row&segments=411555374


valid perma in the same area
https://waze.com/fr/editor?env=row&lat= ... s=66672387


.../fr/editor?env=row&lat=47.68735&lon=-1.73281&marker=true&zoomLevel=18&segments=66672387
 
 
 
 

Hello Richard, in Chrome before running a validator scan, I disable all Tampermonkey scripts otherwise it never works

a simple click on the first line of the Tampermonkey menu allows you to do this
 

The current version is in the US Wazeopedia, but the language is the same. I'll admit, I wasn't clear on whether one-way roads could exhibit this problem, but I according to Mike they do. I always just fix them anyway.

I am in the US and was using Validator on Chrome. It stopped working for me today. I tried reinstalling 1.1.16 and all it says is "Sorry, You cannot use WME Validator over here. Please check the forum thread
for more information." I couldn't find any info in this thread

I have determined that this is probably due to a bug in WME that caused my username to be [missing %{username} value]. There's a separate topic on this.

bmtg wrote:New version of WME interface rolled out this morning. No more "me" tab, and therefore no more Validator settings. And the script doesn't appear to work, at least on my system.

bmtg

Just for some additional confirmation, I see the same.

Restricted turns are now absolute and no longer penalty based, which can cause problems when all access into an area, such as a dead-end or a private installation, are restricted. Full details here, but essentially the route ends early and potentially in erroneous locations.

I thought I'd flag this here in case this is something WME Validator could potentially test for. As I write this though, didn't we have something like this way back? Was this impacted by the same change that lost some other functionality?

Is the script truly encrypted or merely obfuscated?