[jonas]

It is about ORTSUserPreferenceForestClearDistance ( ... )

Start this extracted route with OR ...
 Trees.zip (8.63MB)
Number of downloads: 307

...and you see this



The last line of the trk file is "ORTSUserPreferenceForestClearDistance ( 10 )". In the "OpenRails" folder an include trk file exists too with the same line.



The scene in MSTS Editor. Only 2 tracks are used in the route. I guess it is about the near of the scenery to the border of the tiles.


When flipping the 500m track it starts at the the same tile where the forest square is and then OR calculates the trees correct 10m out of the way.

[Csantucci]

In fact the tree-on-track check is done for all track sections having their start point in the same tile where the forest or part of it resides. A check for further tiles where the track section resides is not done. It requires further computing time and I wonder if it is worth doing it.

[eric from trainsim]

Hard to say... With track pieces, it's bad form to extend that far into another tile, but it does happen.

If the move to procedural track ever gains traction, then that code as-is will fail as well.