Search found 3915 matches

It looks like all of the slip roads and roundabout had been set to M5 to match the motorway lock level, as a quick glance at the junction seems to suggest the only reason for using the roundabout is to transit between the A3 and M25 -> locking the whole thing as if it were part of the motorway netwo...

Just for completeness, I've now checked that specific restriction in offline mode, and as with the 24/7 one I used previously, this one is also completely ignored during its active period.

Offline routing is even worse than I thought...  Before I went looking for a timed restriction against which I could test whether offline took ETAs into account, I thought I might just do a quick check against a 24/7 restriction, just to make sure that at least was being handled correctly. Nope.  Ev...

Thinking about it some more and having checked something in the URC-E source code, the problem may be related to an undesirable interaction between how URO generates those popup links, and the way URC-E is performing marker unstacking using my original method rather than the one I switched to a whil...

The server-side routing code ought to be looking ahead along the route and, based on the ETAs for each section of the route, take any restrictions into account to either route through or around them as appropriate for the ETA and restriction times.  Obviously the longer the route and the further awa...

Holy overlooked bug report, Batman!  Given that one of my posts was the very next one in the thread, I genuinely don't know how I managed to miss it at the time... That said, having now installed URC-E here, I'm not seeing the problem, so I'm thinking this might be a more subtle interaction between ...

Or just do as FUME now enables, and make the search bar fill the remaining space in the top bar - that way you provide the benefits of being able to click into everything on the right hand side of the screen, without messing with people's muscle memory when they expect to find the search bar over to...

3.211 adds lg1992's idea for hiding PURs associated with filtered places.  As this option has the potential to clash with the existing option to keep places visible when their associated PURs are filtered, the two options operate in a mutually-exclusive manner - i.e. you can select one OR the other,...

Hmm, are you sure you've got 3.210 installed?  Finally got a chance to check it out here and it's still working just fine in both Prod and Beta.  If you are running .210, please check the developer console to see if there are any script-related errors thrown when you open the closure editing UI.

Wierdly, there's *still* no evidence of you having removed a closure here