New Editor version v2.67-5

Map Editors Community WME Production Version Releases
1

Hi all,

A new editor version has been released.

  • TTS Button not functioning in Beta- FIXED

  • Save button is red in Beta- FIXED

  • Visiting a permalink that includes a selected object should turn on the relevant layer- FIXED

  • Mentoring: change message when mentor deleted himself (hide username) -FIXED

  • Impossible to create roundabout in the middle of segment- FIXED

  • Can’t add TBR on Difficult Turn - FIXED

  • Misplaced label of drive- FIXED

  • Venue sidebar is missing “Updated…”, “Created…” properties- FIXED

  • Unable to merge venues and HTML text display- FIXED

  • Can’t add alternative name to the segment in case primary address street = None- FIXED

  • Impossible to add all-day Difficult Turn - Time frame is requested-FIXED

  • Closure entry fields too small on smaller screen resolutions- FIXED

  • Secondary language name of MTE- FIXED

  • Moving the map can break undo/redo- FIXED

  • Moving the map makes lanes data to disappear from the segment- FIXED

  • Add New Closure" button error when scrolling the map- FIXED

  • Lanes - Turns list isn’t ordered left to right- FIXED

  • Prevent closures datepicker to take extra space- FIXED

  • HN: after exit, select initially selected segment- ENABLED

  • Updated translations

Thanks,
Maia

2

Seeing some issues with map data loading when panning the map. Specifically, side areas panned into view remain darker (grayed out). The behavior is impacting some script behavior (specifically, Magic), causing validation errors on the elements panned into view, though I freely acknowledge that’s up to the script writers to deal with. Just pointing it out as evidence of the change, in case that’s an unexpected side effect from the WME dev side. A simple map refresh seems to clear up both the darkened areas and the script issues.

This may have already been discussed in the WME beta channels, I don’t check them as often as I used to…

3

Script issues aren’t really discussed in beta since they aren’t “officially” supported. As long as it doesn’t affect editing (I haven’t seen any bug reports that it does), it should be brought up to the script devs, which I am sure this has by now.

4

Agreed and understood.

Mainly I was curious if anyone else is seeing the editing area graying out when panned, requiring a refresh to clear it up. It does not occur in incognito mode, so it is most assuredly a script issue and not a WME issue. Just haven’t dug into which one(s) are contributing to the problem, and didn’t want to spend time chasing it down unless (a) the problem is affecting others and not just me, and (b) someone hasn’t already figured out the source. :sunglasses:

5

I have the same panning issue, even if I deactivate all scripts.
In my opinion the problem is not caused by scripts.

6

I see the grayed out behavior even when in HN mode. I pan down the road while in HN mode and part of the road is still grayed out.

Also, when I add new HNs, they start out highlighted in red as if they are forced. Once I save, they are fine.

7

This issue is making editing very difficult. A refresh is needed every time I pan to a new area.

8

I’m also experiencing issues with WME.

Some segments don’t load completely, and many times I have to move the map do the side, so they finish loading.

9

Coming back to retract my initial statement that it doesn’t happen scriptless. I didn’t test it enough. It definitely happens without scripts.

Working on the Falcon Map Raid and panning sideways to realign long segment runs, after a little bit of panning, this issue is making junction nodes unselectable (in the grayed out area). Have to stop, save, refresh, then continue…

10

Hi everyone,

Thank you for reporting this issue.

Regarding " editing area graying out when panned", if you see the issue without scripts, could you please share with us permalinks and screenshots so we can report it internally?

Thank you in advance and sorry for the inconvenience.

Best,
Maia

11

I’m not sure a permalink would do any good. It’s happening literally everywhere.
Drag a node, save, pan, zoom, pan again, boom! Nodes not selectable.

12

Thank you for your reply.

In that case, a screen recording would be great so we can see the issue.

Best,
Maia

13

A short example.

14

Yeah I’m never sure what to think when staff asks for PLs for a problem that exists everywhere on a server-wide or global basis…

A secondary symptom of this off-screen data refreshing issue involves drawing new long segments. When you start a segment by snapping its initial start point to an existing segment, and then drawn it at some distance with panning, it tends to not create a JN at the start point, so you have to go back, drag the start point away, and then drag it back to force creation of a JN.

I mean, this has always been the case for really long new segments, but now it is happening much more often for segments of much shorter relative length. Seems like if your start point gets scrolled out of view much at all, it isn’t going to generate a JN when saving.

15

Not sure if staff is aware of… but some new segments are disappearing for a short lapse time, just recently they were created, and then after some time it appears as it should at first.

16

This has been the case for I don’t know how long. I always check both ends to see if the connection was made, and to check for hidden geonodes which mess up instructions. Must be WAD, because it just doesn’t get fixed.

17

Hi, after the last update, it is not possible to copy geographical coordinates in the editor. Please check it out, thank you!

18

Hi Mactryb!

Thank you for flagging this.

Could I ask you to please report it in the WME Beta bugs forum?

Thank you in advance,
Maia

19

Hi SeveriorumPatrem!

To give you more insight on why we ask for permalinks/videos/screenshots, it’s very important that we will receive an example so the WME team can reproduce the problem to understand it, even if it is happening often or in many places.

If we cannot reproduce the problem, we cannot fix it :slight_smile: The more information we can provide, the better.

Additionally, could I ask you to please report the issues in the WME Beta bugs forum?

Thank you in advance,
Maia

20

Given the fact that mactryb is not in the WME beta testers group, he doesn’t have access to that forum and probably neither to the beta editor, where beta bugs must be reproduced and should be from, preferably when reporting beta bugs, rather than the production WME only.

I can say that being able to copy coordinates works in beta with the new and not yet revealed UI for permalink and sharing options. (Sorry for spoiling the secret but it’s the only way to respond to this).
So the issue is only with the legacy functionality, unless they’re meant to continue to work as duplicates in the future.

Regardless I’ll open a beta issue for the prod WME problem.

This is already known, reported in 2017 and 10 days ago again in the closed WME beta forum. Issue ID 36769189 and 173257504 from the community, there is no open internal issue on staff’s side.