Map Editor version (April 9, 2012) Official Feedback

[jasonm128]

Am I really the only one who cannot access WME at all in Chrome/Win7? This is really odd.

Working fine for me with Chrome and Win 7 64-bit.

[jasonh300]

Just found a bug in the new WME...

1) Select a road
2) Create a permalink
3) Open the permalink and the road isn't selected. however it does appear in the URL as "segments="

Not anything new and I don't think it's a bug. I've seen that happen occasionally in every version of Editor and in Papyrus. I think it happens when the road layer is loading at a snail's pace, which has been happening today. If you wait long enough, it will appear, or sometimes if you reload it will work right.

[AndyPoms]

Just found a bug in the new WME...

1) Select a road
2) Create a permalink
3) Open the permalink and the road isn't selected. however it does appear in the URL as "segments="

Not anything new and I don't think it's a bug. I've seen that happen occasionally in every version of Editor and in Papyrus. I think it happens when the road layer is loading at a snail's pace, which has been happening today. If you wait long enough, it will appear, or sometimes if you reload it will work right.

I just retried it... and it's sort of working... It works at all zoom levels, EXCEPT the two furthest zoomed out levels... Which is where I was trying to permalink in the first place...

This works: https://www.waze.com/editor/?zoom=2&lat=41.3251&lon=-72.30634&layers=BFTFTTTFTTTTTTTTTTTTFT&segments=64014366
This doesn't: https://www.waze.com/editor/?zoom=1&lat=41.33129&lon=-72.31364&layers=BFTFTTTFTTTTTTTTTTTTFT&segments=64014366

[jasonh300]

I just retried it... and it's sort of working... It works at all zoom levels, EXCEPT the two furthest zoomed out levels... Which is where I was trying to permalink in the first place...

This works: https://www.waze.com/editor/?zoom=2&lat=41.3251&lon=-72.30634&layers=BFTFTTTFTTTTTTTTTTTTFT&segments=64014366
This doesn't: https://www.waze.com/editor/?zoom=1&lat=41.33129&lon=-72.31364&layers=BFTFTTTFTTTTTTTTTTTTFT&segments=64014366

Ok, that makes sense...certain segments can't be selected at certain zoom levels. You might be able to select a segment, zoom all the way out, an then zoom all the way back in, and it's still selected, but that gets lost when you do a reload, which the permalink forces you to do.

I'm guessing if you select a regular Street and zoom out to 1000m, you'll get the same effect.

[CBenson]

Working fine for me with Chrome and Win 7 64-bit.

Also, working fine for me with Chrome and Win 7 64-bit.

[Spil]

I didn't see this documented, but I noticed that when I select a junction and "enable all turns", the adjoining segments whose turn restrictions were altered become highlighted in orange, and show me as the "updated by" editor upon saving. This may become pretty useful in the future for trying to determine whether a junction has been edited (and updated in the livemap) before or after a UR was submitted.

[foxitrot]

WME does work for me correctly on the NA server, with e.g. the AndyPoms' mentioned permalinks. But it is still completely black on the INTL server.

[jasonh300]

I didn't see this documented, but I noticed that when I select a junction and "enable all turns", the adjoining segments whose turn restrictions were altered become highlighted in orange, and show me as the "updated by" editor upon saving. This may become pretty useful in the future for trying to determine whether a junction has been edited (and updated in the livemap) before or after a UR was submitted.

It only does this the first time a junctions turn permissions have been set (cleared the 'unknown' state).

Has anyone checked to see if existing reverse connectivity has been fixed, or do we still have to QW each junction?

[AlanOfTheBerg]

Has anyone checked to see if existing reverse connectivity has been fixed, or do we still have to QW each junction?

I don't believe I saw an announcement saying they'd go through and fix anything which was set improperly. I think Q/W, or whatever keys anyone has customized, is still necessary if you think that reverse connectivity is enabled.

[AlanOfTheBerg]

My problem could only be resolved by clearing all cookies as well. It appears that WME should have been prompting me to log in, but it didn't, so I wasn't able to access resources necessary which were requiring credential information.

This looks like, to me, a bug whereby a login is required but it is not asked for.