[Jovet]

Goku, on 26 January 2017 - 03:53 PM, said:

But I don't know, what issue you are reffering to.

He's referring to his initial post. Placing a LevelCr object on a track and road puts LevelCr objects on the same road when other tracks cross that road, even at quite a distance.

[Goku]

Ok. In 0.668 it is possible to delete these "even at quite a distance" items. In next update maybe I can make a distance limit, but what value will be reasonable? MSTS RE behaviour is definitely not good here.

[Jovet]

Goku, on 27 January 2017 - 09:31 AM, said:

Ok. In 0.668 it is possible to delete these "even at quite a distance" items.

That is also a useful feature, thanks.

Goku, on 27 January 2017 - 09:31 AM, said:

In next update maybe I can make a distance limit, but what value will be reasonable? MSTS RE behaviour is definitely not good here.

I think MSTS's behavior is good, other than stopping at only 4 tracks. When the user clicks, it places the LevelCr right there, provided the track and road are close enough. It then follows the road lane vector a certain distance... 10 to 20 meters, and if it finds another track vector within that distance, it puts another LevelCr there. It repeats this 10-20m at a time until there are no more tracks found or four LevelCr objects are placed. I would think 20 or 30 meters would be a reasonable distance, but you could also make it user-configurable.

[Goku]

0.669 has default max distance set to 30m, but user can change it in levelcr properties window.
Also it is possible to move track items using T.

[Jovet]

Goku, on 27 January 2017 - 03:47 PM, said:

0.669 has default max distance set to 30m, but user can change it in levelcr properties window.
Also it is possible to move track items using T.

This is excellent, Goku. Very well done!

[edwardk]

Goku,

Just wanted to let you know that since your level crossing fix, the crossing issue that was reported has been corrected.

Edward K.