Waze forum

bgodette wrote:Fixed and published.

Working much better now!

However, in that example I provided, now this link: https://www.waze.com/editor/?env=usa&lo ... 9,81376011 the extra junctions which are part of the loop split do not have turns enabled. I think that by default they should be.

BellHouse wrote:Just to be sure: which version of JNF are you running? I am not aware that the current 0.0.9.6 produces any button "Automatically fix node (Q)".

That's not a button, but it is text suggesting that you tap 'Q' on the keyboard to fix.

Olestas wrote:Just if you have toolbox, don*t install this script. Its already embedded.

The functionality is slightly different though? JNF standalone enabled u-turns at dead ends and Toolbox embedded disables them? Or did that get changed in TB? I know for sure JNF enables them.

olestas wrote:Hmm, script not working?

With FireFox I have no problem. Since Chrome version 27, it does not work correct native. But I deinstalled, installed Tampermonkey and installed it again in Tampermonkey - and it worked perfect again (and many other scripts)

bgodette wrote:Updated and Chrome Webstorized.
Version 0.0.9.0
This is now a Chrome Webstore Extension
Chrome Webstore

Is this version also available for Greasemonkey and FF?

doctorkb wrote:Totally agree.
I've enabled some u-turns in my 'hood so I can see how the routing works (when it is all enabled) -- particularly one at the end of a segment where my mailbox is (I usually pull a u-turn there anyhow, and Waze thinks I need to drive around the block to get home).

I'll let you know how that works out.

I've tested a few of these new u-turns on INTL and I couldn't get the client to take the u-turn route (and it's not a dead-end). It always ignored it and took a longer route. Weird, since the whole reason for fixing selfcons was to stop these incorrect u-turns from being used for routing in the first place.

Now that it looks like Waze is handling Dead-End U-Turns properly, can we have this script updated so it DISABLES the U-Turn at the end of a dead end?

With a U-Turn Disabled, if I go off route & turn down a dead-end street Waze will route me to the end of the street & tell me to make a U-Turn (I do this all the time in a parking lot at work while looking for a spot).

With a U-Turn Enabled, Waze will route me down a dead end street in the middle of my trip to make a U-Turn.

Waze still needs to resolve a few issue with U-Turns at dead-end streets as I've gotten two URs where users were routed off the highway, down a dead end with a disabled U-Turn, go get on a different highway that then merges back with the original highway. This is clearly the Traffic Avoidance system working - except for the U-Turn - the exit after the one users are being routed off backs up daily (the right lane is practically at a stand still, the middle lane is very slow as well (people merging right) and the left lane is probably doing 35-45 (where the speed limit is 55 (or maybe 65). I've reported these U-Turns using the routing form already.

I am getting the following error on the beta version of WME for the USA:
I'm running the latest version of Chrome for MacOS and version 0.0.7.6 of JNF. FYI, I do not see the error on the regular version of WME.

I installed the latest JNF yesterday by dragging into ext. window. It worked OK, with develop mode on.
But today i got the message that all extensions were disabled, if not coming from the chrome store. and there's a checkbox to re-enable them, but on the JNF and other waze tools, its grey. So not working currently, also in dev.mode as said.

Using Chrome 33.0.1750.70 beta-m

Going to install the tampermonkey now.

My chrome is disabling JNF, because it's no Chrome-extension. Could you make it one?