WME new version release 1.13

Team leader responsible for WME updates post in WME Beta Forum 18 months ago.

RE: After posting above about TENNESSEE showing up as the default state when adding new segments halfway across the state of Arkansas.

I was wrong. It extends all the way into OKLAHOMA! :roll:

Apparently it has to do where you’ve been editing and/or driving recently. Following some conversations in Slack, a few editors have reported after editing in one state, that state selection appears to get “stuck” with them regardless of where they’re currently editing.

It apparently is plaguing the city and street name auto-complete as well. I have had street names in Memphis, TN suggested when editing in central Mississippi, well over 100 miles south of Memphis! Others have stated the same has happened in the city field as well.

I’ve already reported this bug in beta cause it happens there too. If/when a fix is made, I’ll share the notice here unless he beats me to it.

That’s because the forum is not coordinated by ohad-ron anymore. :wink:

Hey Guys!

Taking care of the states bug ASAP!

Thank you for the examples and help, much appreciated.

He is in charge (still I believe) of coding, Mapsir of communication but what Ohad said back then still stands true to what Fredo-p mentioned in his post to WME and to any Operating system, except to the ones that need to maintain backwards compatibility.

It works here.
Maybe something localized in Poland?

Cut/junction issue is present with all non-driveable segment types except for Runway/Taxiway.

When junction is created (or previously existed as in railroads), turn restriction arrows do not appear.

I tried to create two separate Railroad segments, then join them at their endpoints, and while the save was successful, I got a save warning that all turns were disallowed. Selecting the junction and clicking “Allow all turns” results in a save error.
Toolbox reports the soft turns. Using “Q”, or the internal WME “Allow” followed by “Disallow” results in a save error.

The only way to manipulate the junction is to change the segment type to a driveable type.

My mistake, you could add a house number for private roads, sorry.

Wysłane z iPhone za pomocą Tapatalk

Why I cannot log in any more into Bulgarian editor?

That may mean Debs are releasing an update. It happens every now and then. If you have access to beta then use that.

Sent from my Galaxy Tab A using Tapatalk

A brief list of strange behavior of last Wme:

  1. default country of a newly created road is wrong (editing in Thailand and default country suggested is Italy)

  2. stressing snap movement of a junction/node to the previous position when try to adjust its position; need 1-2 webpage reloads before the position is free

  3. when happens 2), the segment become orange and I need anyway to reload web page

  4. when 1) the suggested states are from the suggested (wrong) country.

  5. sometimes when I connect already created road to an existing road, a “soft turn” appear on the new junction. If I disallow-allow all turns to solve the issue, no changes are recorded and “save” button is not active

Paolo

The first one has been reported.

As for the others, I belive it’s a byproduct from the update. It’s happened to me the last major update and eventually stopped after a month or so. I’ll check to see of that has also been reported.

Sent from my Galaxy Tab A using Tapatalk

vamos atualizar para melhorar

Today I tried to modify some speed limits; save was successful, but when I selected segments to verify my work, all my changes had disappeared. I tried to reload webpage 1,2,3 times but nothing to do… my work was lost

Inviato dal mio iPad  utilizzando Tapatalk

Is anyone else having an issue where all the text in the dropdown boxes is blank, unless you’re actually selecting an option?

I have noticed with the Firefox browser that edits are not being saved. Pressing the save button does nothing.

Sent from my XT1575 using Tapatalk

I had noticed that. I wasn’t able to pin down a cause.

What scripts do you have? We might have a script in common that is causing it.