After splitting a segment by connecting any other segment to it I can’t then connect another segment to the newly split segments.
When saving after splitting the segment AND then reloading, the second segment can be connected. If I don’t reload after the save in 9/10 cases an error pops up, when trying to save again (I’ve seen “Container has no generated ID for property fromSegID” and “internal error”).
Tested on a clean browser with no scripts or extensions (Firefox) and my editing browser with scripts (Edge).
It’s a good thing that connecting the new segment to the same connected segment is not allowed.
If it were possible, it would create a two-segment loop, which is not good editing practice. While a two-segment loop can still be created, at least WME helps prevent it in this way. Always try to prevent a two-segment loop.
To work around this, you’ll need to split the new segment and turn it into a three-segment loop, then it will work.
I tried the same approach when creating a three-segment loop, and indeed, it’s not possible either.
You’ll need to save first before connecting another segment.
I am aware that this would create a loop. So far, however, I have kept to this procedure: created the segment as shown in the video, created the needed node manually (so it’s not a loop) and saved then. However, WME should not prevent creating loops by generating a script error…
Incidentally, I get the same error as @endradon if I use the procedure you described @Leorenaud. Saving shows the error ‘Container has no generated ID for property fromSegID’ then.
I believe that is working as designed. You should not be able to create a 2 segment loop (even if you plan on cutting it later). If it allowed it, many editors would create the loop and move on.
If it works as intended, it should be implemented in a slightly different way. Disallowing it by generating a script error is not a good way, in my opinion. For example: It’d be the same if I made software crash if an user typed letters instead of numbers in the “phone” input field, instead of displaying an error message… Maybe a blatant example, but I think you get what I’m getting at.
And I remember in WME there used to be an error message when trying to save a loop before.
Hi everyone! I get what @endradon meant and I had the same issue.
Is this a…:
Standard bug Steps to reproduce this issue:
If you are connecting two points on a segment with only 1 other segment, this would create a loop. To avoid routing issues, WME prevents this action.
However, the issue discussed in this topic occurs when you connect a new segment (A) to an existing segment (B) and then try to add a second new segment (C) between A and B. This is the correct way to connect two points on a road without creating a loop, but WME is not allowing this operation correctly. Environment where the bug occurs…:
ROW Permalink: Not Apply Browser name and version:
Google Chrome v134.0.6998.89 Are you using scripts? Please detail which ones.:
I performed the test with scripts enabled and disabled
Standard scripts used: WME JAI, WME Color Highlights, WME Route Checker, WME ClickSaver, WME SpeedHelper + extensions WME Toolbox and WME UR FAST
I am experiencing this in Chrome production with no scripts or extenstions.
I am seeing that if you connect one road to an existing segment and make two new segments then you can’t add another new segment to the segment of the existing one.
Existing segment is the Street. Adding segment 1 to it generates segment 1 and Existing a and Existing b. When you add Segment 2 to connect to Existing b, you are not able to connect it. Segment 2 is generated but has to be saved as an unconnected segment. But you can add Segment 3 to segment 1 and it connects.
This is the error you get because of segment 2 There might be something wrong with this edit possible disconnection.
Please note this is not trying to create a two segment loop. This is three segments and also not a loopl
To clarify this comment, WME will inherently not allow a two segment loop when you draw a new segment and each end is connecting to the same two ends of another segment.
It will normally, however, allow you to force this when you draw one end as disconnected then connect it. When you save, you get this error.
As I already said some time ago, detecting the loop should happen during the validation step when saving (the regression checker should do it) and not be prevented while editing.
Is this a…:
Performance issue Steps to reproduce this issue:
Create a few new segments, sometimes it takes only 1, sometimes about 20. Then, all of a sudden when you are creating a new segment, it’ll show as an ‘Action’ in the save menu. Then, it won’t connect to the connecting segments, nor will it let you connect them as it doesn’t create nodes until after saving.
Environment where the bug occurs…:
ROW Permalink:
Irrelevent - Happens in multiple countries Browser name and version:
Firefox 137.0b7 Are you using scripts? Please detail which ones.:
No. However adding scripts doesn’t affect the outcome either.
I disabled all my TM scripts & TB for the screen recording.
