Tehachapi trees

[Curt C]

I recently switched over to OR, and am slowly getting the hang of it. While running Tehachapi today, I noticed that some of the trees, that were well-back from the tracks while running MSTS, are now in the middle of the tracks. Is there a fix for that? Thanks in advance.

[PennCentral1970]

I recently switched over to OR, and am slowly getting the hang of it. While running Tehachapi today, I noticed that some of the trees, that were well-back from the tracks while running MSTS, are now in the middle of the tracks. Is there a fix for that? Thanks in advance.

I've noticed that with several routes, particularly the Rich Garber routes.

[gremlin1812]

G'day Curt C, yes there is:-
Using a text editor (Wordpad, ConTEXT, etc.), open your ConnRiv.trk or whatever your trk file name is (after backing it up, of course) and navigate to the bottom of the page. Insert this line as the last line above the final bracket:

ORTSUserPreferenceForestClearDistance ( 1 )

This will move all trees and foliage off of the right of way. Be sure that the last ")" is below this line.

Numerically adjustable parameter - usually 2 works for most routes, have not gone above 4

I hope this helps, it has for me
Regards
Barrie

[ossie]

That's an easier way than the solution I picked from somewhere Barrie. The method I'd learned had been to create an openrails folder inside the route, create a new text file in that folder and then add the "...cleardistance" line to the file. I still have a bunch to do so suddenly it's a quick copy, paste "fix" instead of what I'd been doing. Thanks.

[PerryPlatypus]

That's an easier way than the solution I picked from somewhere Barrie. The method I'd learned had been to create an openrails folder inside the route, create a new text file in that folder and then add the "...cleardistance" line to the file. I still have a bunch to do so suddenly it's a quick copy, paste "fix" instead of what I'd been doing. Thanks.

This is the proper method. Unfortunately I have had issues doing the "include" method so usually I just copy the entire .trk file into the OpenRails subfolder and at the entry to that file, keeping the original .trk file as it was with no modifcations. If you directly edit the .trk files, you may run into errors if you try to use MSTS or the MSTS Editors, I know I have.

[ossie]

Thanks for the heads up Sean. I'll keep doing it the way I have been then and hopefully stay out of any potential trouble.

[baldwin]

I only place that line in the MSTS .trk file. As the line starts with ORTS it is unknown to MSTS and therefore should cause no problems because what it does not "know" it ignores. The making of an Open rails sub folder in the route folder is recommended, but not needed, specially if you no longer use MSTS.