For odd sized Round abouts, the blue overlay suddenly is much larger. It used to put a circle on the max diameter, now it does something different which makes no sense to me; see screencap. the 190 m radius is almost 3 times the overall length of the thing. Like an inverted least squares solution or so.
It’s not hindering the actions of the script, it’s just the displaying that is odd.
Edit: Permlink to the above example: https://waze.com/nl/editor?env=row&lat=52.07261&lon=4.27650&zoomLevel=18
Hi,
Ignore the Junction Box as it was placed after the Map Update. But the roundabout already gave normal roundabout instructions despite the fact that some angles were red. Is this normal behaviour of the script?
Hi
Latest Prod update broke the script
Thanks
I’ve been told that we shouldn’t actively ask for updates and fixes to broken scripts.
So I’ll just sit here like a puppy, actively trying not to look at the sausage on the table, hoping for mercy. 
Why? Many times the author doesn’t notice the problem until someone asks for a fix.
Ideally the first post reporting the script as broken will be all that’s needed. A bunch of posts saying “It’s broken for me, too”, unless there are logs or behavior that weren’t previously included, aren’t going to add to the discussion.
Oh, surely, just once is enough 
Version 2023.12.01.01 does not work with roundabout that has only two nodes
A roundabout should always have a minimum of 3 junctions otherwise you end up with a 2 segment loop
Today I noticed a problem with JuBras.
Having the layer switched off, I changed the roundabout so much that at least one node exited the JB. This caused at the end a saving error and I had to throw everything away.
This action is preempted from the normal WME editing, but is possible through the script.
I see that it might be too difficult to prevent that while editing through the script, but maybe it would be nice to have an alert in the script UI that says: “This RB is inside a Junction box, keep its nodes inside it”.
From today it seems that the script is not working
When loading/starting the WME I got the following error message in console for RA util:userscript.html?name=WME-RA-Util.user.js&id=bb154ee1-008e-474a-a6cb-dfa6f5d2f6a0:117 WME RA Util: Error: Invalid downloadUrl paramenter. Must end with ".user.js" [
at #validateParameters (WazeWrapLib.js?_=1706461038892:2152:31)
at new Alerts.ScriptUpdateMonitor (WazeWrapLib.js?_=1706461038892:2109:41)
at loadScriptUpdateMonitor (userscript.html?name=WME-RA-Util.user.js&id=bb154ee1-008e-474a-a6cb-dfa6f5d2f6a0:113:29)
at bootstrap (userscript.html?name=WME-RA-Util.user.js&id=bb154ee1-008e-474a-a6cb-dfa6f5d2f6a0:101:13)
at Proxy.<anonymous> (userscript.html?name=WME-RA-Util.user.js&id=bb154ee1-008e-474a-a6cb-dfa6f5d2f6a0:105:37)
at Rt (<anonymous>:9:89)
at t.<computed> (<anonymous>:66:214)
at Rt (<anonymous>:9:89)
at r (<anonymous>:24:484)
at <anonymous>:25:112
Hi Justin
There’s a very good feature inside this script which is moving the roundabout. I wonder if you would like to implement this feature to a “regular segments” by create a script to move “selected segments”. As we know, sometimes due to poor aerial in the past, we just one to move the “selected segments” without having to drag and redraw the segments one by one.
thanks you very much and regards.
I cannot minimize the Roundabout Utility popup. When I click the top-right button, nothing happens, only “#divWrappers” is added to URL.
Is there a possibility that the script has broken?
It is not working for me, neither in the beta version nor in the production editor
Appears to be working for me
Is this on a new roundabout? You must save the roundabout before the script can be used.
@jm6087 @ojlaw
Thank you! After your response,
I cleared the cookies from Chrome, including both the editor and the beta editor, and reinstalled the script. It took some time, but it eventually worked.
I created a fix for the center detection of the Roundabout, where should i submit it?
Create a pull request on github, this repo:
Dave