When approaching it from Newark with a route set to continue north on the A46 the route looks good however the little roundabout symbol has a zero inside it instead of the required turn number, consequently the voice routing does not work.
Has anyone ever worked out how to fix this? There is nothing I can see wrong with this roundabout (except maybe the phantom turn restrictions). Ignore the aerial photography as it is at least 10 years old as the dual carriageway A46 was completed 2001/2002.
Since Papyrus still does not support roundabouts we’re stick with Cartouche for this
It happens when a segment detaches from the roundabout according to the database (rather than physically) resulting in the node being unable to count the number of exits properly. Sometimes support can reset them directly in the database. Most of those I’ve found I’ve had to rebuild from scratch!
Ouch, I had one that I did several times and support did twice. Not sure what the final fix was but it works now. If you have a troublesome one I would flag it to the powers that be!
I’ve been able to fix some of these by checking the directionality (if that’s a word) and turn restrictions of the feeder roads.
This included checking some of those stupid Y entries to roundabouts where the Y element had stupid turn permissions set prior to the directions I guess. For me the tell-tale check has been to click one leg of the Y and see if I get both orange and green on the other.
It hasn’t fixed all of the problems but seems to have got past quite a few.
I also had some invisible junction nodes shoot me in the foot.
But then I had a couple of roundabouts where I deleted everything close-by and redrew from scratch only to get the same errors - it might be worth checking the feeder road segments at the far ends in that case.
If you find the definitive fix please let me know.
Don’t get me started on effing roundabouts.
Got 1 in particular that just would not play ball (not technically a rb as you cant go all the way round, but makes more sense as an rb in the client).
Finally after literally 20 something rebuilds from scratch I get the focker working properly and some R Sole (not the users real name) edits it and fooks it up again
Fortunately, it can now only be messed with by me or higher ranked (step away mcconachie, nothing to see here) editors
I’ve found in “most” cases the routing only gets the 0 error on certain routes. I normally fix them by finding exactly which entrance/exit to the roundabout is broken by routing through it in all directions, and them simply disconnecting and reconnecting the offending road to the roundabout. Haven’t had to rebuild completely or bother alpha with any of mine (yet).
The most effective way I’ve found to fix 0 exit errors is as follows:
use Papyrus
disconnect the offending road from the roundabout
DELETE the node on the roundabout that the road was connected to
reconnect the road, forming a new node
repeat for additional roads if needed
It would be useful to have some kind of route checking tool in the editor though, as it’s begining to become a pain having to wait “weeks” for the livemap to update.
Doesn’t Papyrus edit the live map? There some such warning when you log in.
Also, I have come across several of these recently and a common element is the dual entrance/exit roads. However, when checking connectivity for the roads and roundabout, all seems to be Ok…
odd.
Would people class “straight over” as the correct instruction on a two road/four exit crossing as correct guidance rather than 2nd exit?
I’ve found that some ‘0th exit’ roundabouts have invisible nodes* left on them from previous revisions. To fix these, delete the roundabout in Papyrus, then use the the ‘Remove node’ tool in Cartouche and click randomly. This works best if you zoom out, as Cartouche tends to favour nodes to roads when you select something. Once you think you’ve got them all, create a new roundabout in Papyrus.
(*The Map Problems layer in Cartouche sometimes highlights these)
No, it means you’re editing the same map as Cartouche. It’s still subject to the same (long) wait for updates to appear on the Livemap.
I also suspect that having segments of Y entry/exit roads meeting at a single node on the roundabout causes problems.
For example, having a segment of one roundabout exit attached to the same node on the roundabout as a segment of a second exit. Here’s a random example:
Yup, it’s definitely a problem when an exit and entry road share the same node on a roundabout.
I’ve been systematically removing all Y entry/exit roads from any roundabouts I come across. They look so much better and less prone to errors when they are drawn as simply as possible.
Here’s my 5 step process for fixing any roundabout:
delete one pair of entry and exit roads
delete the old nodes on the roundabout (if not shared)
drag the two-way road up to the roundabout and connect
enable all turns for new node
save and repeat
Of course, sometimes it’s better just to delete the whole thing and draw a lovely new circle.
