Odd Forest Regions Happening.

[Noisemaker]

Toodling around Paul Charlands cute little Thousand Island RR route on OR, and noticed a few of the MANY Forest Regions he uses come out a bit funny in OR. Some of the trees come right out onto the tracks in a couple of places. I'm slowly going at replacing a lot of regions with suitable static forms, so it's good in a way to show me areas I still need to work on. But figure I should be pointing this out to the OR team in case people with other routes may experience this problem as well at some point.

[baldwin]

The method that MSTS uses for forest regions avoiding placing trees on tracks is unknown, so OR is unable to do the same at present.

[eric]

MSTS didn't have logic to keep trees off track, but the seeding algo in MSTS is different than in ORTS.

In the MSTS RE and game, trees were consistently placed within an object unless you change the parameters. In ORTS, trees can show up where they weren't expected, especially if the bounding box of the forest object is too close to the tracks.

[charland]

The difference is that when you are working in MSTS Route Editor and place a forest, where ever the trees appear is exactly where they are going to be in the sim OR uses a different algorithm to place the trees, so that makes the difference. Now when building a route with this in mind, you have to ensure the forest regions do not cross roads or rails.

Paul :-)

[Snowman]

It would be nice if it were coded in that no matter if you place trees on the actual tracks, OR will ignore and place trees either at a predefined distance away from the tracks, or a hard coded (3m?) distance. You could then set the route to ignore trees at a specified distance from the track, lets say 5m and it will start the forest region 5m away from the track automatically. Any trees accidentally place in the RE that go over this 5m threshold you've set will be ignored and not rendered. Maybe a text file place in the route folder that OR looks for to see if the predefined distance exists if not it will follow the fall back hard coded distance of 3m or whatever.