From this recent thread at Elvas (Carlo Santucci)
http://www.elvastower.com/forums/ind...s/page__st__10
Downloadables for testing version X3337 found in post #11 in above thread.
This needs testing by Open Rails users, I'm trying it out on the WP3 Sub.
Excerpt from thread:
"Here
Attached File Runactivities.zip (1.35MB)
Number of downloads: 4
you can find two test .exe files and a .dll file to replace the original ones in release x.3337.
In order to have the tree remove function to work, in the route's .trk file a line
ORTSForestClearDistance ( 2 )
has to be added. The parameter value is the clear distance between the center of the track and the side of the trees (so smaller trees can have a trunk that can be nearer to the tracks than bigger trees).
As the parameter value is user selectable, everyone can find the best match accordingly to his preferences and also accordingly to the route (every route can have a different value).
The algorithm is not perfect and not complete in case of forests extending across tile boundaries (only the four adjacent tiles are considered).
It must also be very clear that such a generic algorithm cannot replace the fine-tuning that can be achieved by route-editing.
The good thing is that the algorithm works not only with forests that are laid down adjacent to the tracks, but also with forests that are laid down "above" the tracks (half at one side of the track, half at the other side).
Before considering committing it would be nice if this could be tested (also in terms of lost FPS) by people suffering from this problem.
The algorithm used is the one jtang had developed, but not made operating in release 1491. "
http://www.elvastower.com/forums/ind...s/page__st__10
Downloadables for testing version X3337 found in post #11 in above thread.
This needs testing by Open Rails users, I'm trying it out on the WP3 Sub.
Excerpt from thread:
"Here
Attached File Runactivities.zip (1.35MB)
Number of downloads: 4
you can find two test .exe files and a .dll file to replace the original ones in release x.3337.
In order to have the tree remove function to work, in the route's .trk file a line
ORTSForestClearDistance ( 2 )
has to be added. The parameter value is the clear distance between the center of the track and the side of the trees (so smaller trees can have a trunk that can be nearer to the tracks than bigger trees).
As the parameter value is user selectable, everyone can find the best match accordingly to his preferences and also accordingly to the route (every route can have a different value).
The algorithm is not perfect and not complete in case of forests extending across tile boundaries (only the four adjacent tiles are considered).
It must also be very clear that such a generic algorithm cannot replace the fine-tuning that can be achieved by route-editing.
The good thing is that the algorithm works not only with forests that are laid down adjacent to the tracks, but also with forests that are laid down "above" the tracks (half at one side of the track, half at the other side).
Before considering committing it would be nice if this could be tested (also in terms of lost FPS) by people suffering from this problem.
The algorithm used is the one jtang had developed, but not made operating in release 1491. "






















Comment