I'm not sure if this is a known bug: When you select about 50 new segments and try to apply a city name to all of them the extension starts checking for angles (could see it happening in the console) and takes forever to end, twice google asked if I wanted to kill the page and the 3rd time it crashed chrome.

Try 1.13 from milkboy: https://github.com/milkboy/WME-ja/raw/d ... le.user.js

Interesting example! It seems that JAI is simply evaluating each endpoint's turn angle independently and comparing their difference, presuming a mostly-straight median segment. To truly check for parallelism would require evaluating absolute directions of departure segments instead of relative angles between connected segments.

Is there any reason not to push that beta version to general release? I've been using it for months without problems.

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: And the debugger takes me to this statement at line 122: Line 2198 is the call to junctionangle_init.

I'm using development version 1.12

ituajr wrote:It appears that the U-turn avoidance conditions are not being evaluated correctly by JAI. The third condition is described in Preventing median U-turns as "In/out parallelism: The in and out segments (A and C) are within ±5° of parallel to each other."

I believe that JAI is correct, whereas that Wiki page is not. "Parallelism" is not the criterion. The criterion is 2 turn angles that add up to 180° (or very close).

If all the segments are straight, then 2 turns adding up to 180° means that the incoming & outgoing segments will be parallel. But if the middle segment is curved (as shown in your example above), then 2 angles adding up to 180° means the incoming & outgoing segments definitely won't be parallel.

In fact, the easiest way to "break" u-turn prevention (if you want to enable u-turns) is to kink the connecting segment. In & out remain parallel, but the total angle is no longer 180°

Or you could use WME RA Util which shows the angles and whether they will produce normal instructions or not.

If the angles are wrong, you can use the script to move the attachment points until they are; plus you can rotate, resize & move the entire roundabout.

I reckon you'll find that a lot easier than playing with an overlay.

The latest WME update has made some changes to the layers menu. Since JAI adds an option to the layers menu, it will need updating to match the changed style of the new menu.

Not an urgent matter - it still works, just looks a bit different.

Hi there.

WME is deprecating the use of OL as an alias to access the OpenLayers object in WME. As of the latest production version of WME, a warning is produced in the console every time OL is used.

Since that production release I've been having some performance issues with WME. In particular, if I open the Chrome console, something is causing WME to produce thousands of these alerts continuously. With the console open, Chrome uses up all the available memory within a minute or two and then becomes unresponsive when the memory runs out.

I'm sorry to say, but it looks like JAI is the culprit. There are 28 references to OL in the script. When I replace them all with OpenLayers the problem stops completely. I'm not sure why it would be continuously generating these errors, but it definitely is.

The fix is simple enough - replace all occurrences of "OL." with "OpenLayers.". You'll need the ".", otherwise you'll replace the characters "OL" in the icon string on line 10.

Thanks, Seb - that's working nicely.

karlcr9911 wrote:Thanks Iain...looks like a whole lot of scripts are still using OL vs OpenLayers.

To be honest, mine is one of them!

At the moment, this is nothing but a warning message produced in the console. I'm only producing a few warnings and I didn't expect them to have any impact on WME. Presumably you have to cause a lot before there's an issue!

Interestingly, the warning comes from a part of the native WME code marked up as being for the assistance of community scripts. So WME includes specific features/warnings that are only there to help us stay compatible with WME changes.