collision.action doesn't work

[zlh212]

I configured <collision.action value="teleport" /> in the sumocfg file, but it doesn't seem to work

[m-kro]

This looks like a collision during changing lanes with the sublane model. Can you provide the scenario to reproduce it easily?

[zlh212]

suburb.zip At around 220, there will be a collision

[zlh212]

What does that mean? Does that collision happen because of step-length

[m-kro]

No, it is just another issue which emerged from your sample data. I will look into your case during this week.

[namdre]

collisions on junctions are only detected if option --collisions.check-junctions is set (for efficiency reasons)

[namdre]

It's a netconvert bug: The collision check doesn't work even when setting --collisions.check-junctions because the two connections are not marked as being in conflict in the .net.xml file. Arguably, connections starting from the same edge and going to the same edge should not cross in any sane intersection design but netconvert should still flag the conflict.