So, I’ve been suffering from this problem lately. The script is not running in WME Beta, both v1.10.0 from Chrome Web Store and v1.11 from Greasyfork.
Does anyone have any kind of workaround?
See opening post: 1.9 is outdated.
send from my SGS4, using Tapatalk
Now it’s not running in regular WME. 
Yeah, since the release of the best version of WME prod. But we can see that many other scripts have stopped working properly.
Let’s hope someone fix it soon! 
Enviado do meu iPhone usando Tapatalk
Works for me. Just use version 1.12 development. Link in first post of topic.
Extensions and the greasyfork version will probably be updated tomorrow once I’ve verifoed they all work as intended
Addons tested and uploaded to Chrome webstore and addons.mozilla.org (may take a while until they become available). The Greasy Fork site seems a bit unreliable, but I guess the most recent version was synced there also.
For Firefox addon users: the addon is now marked as supporting the new multiprocess architecture of Firefox. It works nicely for me, but ymmv. Oh, and I added “private-browsing” permission also, so it should now work in private mode also (only settings are stored anyway, no browsing history or other data).
This is a handy feature to have, but would it be possible to have this bubble use a different color than the “Color for angles to avoid” color? Makes you think it’s a bad thing when you see it when it really means a good thing. Using v1.11, by the way.
milkboy, maybe you could create new topic for JAI? otherwise this one contains many old info, and is not yours 
Can someone corroborate something for me? On an H intersection, if I select the cross segment it shows the inside angles for all of the segments connected. When I select the three segments that make up a u-turn it looks like JAI calculates the angles for the three segments wrong. Is anyone seeing the same?
By my math the interior angles should be 190, JAI says 170.
https://www.waze.com/editor/?env=usa&lon=-117.69383&lat=33.46256&zoom=9&segments=61651887,6803762,68560968&problemsFilter=false&update_requestsFilter=false&mapProblemFilter=0&mapUpdateRequestFilter=0&venueFilter=1
Or I could be looking at this all wrong…
95 + 75 is 170
But I see what you mean.
The angle is displayed differently when you select two segments vs one segment.
The turn angle is obviously over 90 degrees, yet is displayed as 75 rather than 104.
That’s the key. The 105 degrees when individually selected shows as 75 when part of multiple selected segments and the 85 degrees individually is shown as 95. In the end it’s still accurate to determine +/- 5 degrees for u-turns, but it threw me for a loop.
Was there any changes to TTS calculation not shown in WME Junction Angle Info? (see below)
PL: https://www.waze.com/pt-BR/editor/?env=row&lon=-47.05621&lat=-22.91649&zoom=7&segments=154104010
Not one which I have surgically noticed. However the turn angle on the right branch there is 43° which is still very close to 45°. I always recommend to editors to leave a 5-10° buffer for turn angles (meaning don’t use angles between 35°-55°, or at least 40°-50°) just to be safe. It is possible that due to the method for calculating angles, and distance the threshold could change slightly in different parts of the globe as well.
Sent from Android using Tapatalk
It looks like JAI may have been hit by the latest WME update. I’m seeing no functionality at all from the script.
I’m seeing this in the console:
VM2448:122 Uncaught TypeError: Cannot read property 'on' of undefined
junctionangle_init @ VM2448:122
(anonymous function) @ VM2448:2198
And the debugger takes me to this statement at line 122:
window.Waze.model.segments.events.on({
"objectschanged": ja_calculate,
"objectsremoved": ja_calculate
});
Line 2198 is the call to junctionangle_init.
I’m using development version 1.12
Seems to be working okay here on Firefox
It’s been working off and on for me in Chrome today. Sometimes I have to reload the page to get the junction info to show.
JAI does not work for me either, Chrome as well. No amount of refreshing is bringing it up.
Works for me… but I have 1.11
Try this
https://greasyfork.org/en/scripts/7887-wme-junction-angle-info
I use Chrome and JAI 1.11, and it works fine for me also.