[rrroberttt]

Csantucci, on 12 December 2015 - 12:00 PM, said:

Any additional parameter may be inserted in the include file.

A big thank you, Carlos, for this improvement. Also, Jtang, for the original idea, that you made workable.

[R H Steele]

First off, :sign_thanks: Carlo and everyone who tested and contributed, fine work.

Secondly, I'm very confused....concerning how to use the include file. But let's see if I got it straight - for example the 3DTS_TEH2
In the 3DTS_TEH2 route folder I place a folder named Openrails.
Within the Openrails folder I place a file named the same as the trk file for 3DTS_TEH2 (in this case: tehachapi2.trk
The tehachapi2.trk will look like this:

include ( ../tehachapi2.trk )

ORTSUserPreferenceForestClearDistance ( 2 )

Do the same (of course changing names) for any other route that needs this type of parameter. I can use ConText to make up the new Openrails .trk file.

[Csantucci]

Yes Gerry, it's as you write. It's apparently important to leave an empty line before and after the include line, as you did.

[wellsburg]

Hi,

Does something have to be clicked to activate the include feature ? On the not yet distributed B&SR route, the include feature is not working.

A folder "OpenRails" is in the B&SR route folder. Within the OR folder is a ConTEXT file named B&SR.trk . B&SR.trk text is:


include ( ../B&SR.trk )

ORTSUserPreferenceForestClearDistance ( 2 )

with empty lines before and after the include line.

If ORTSUserPreferenceForestClearDistance ( 2 ) is directly entered as the last line in the actual route B&SR.trk file, the offending tree is gone.

ORTS version is X3368. What am I missing here ?

Mike

Csantucci, on 12 December 2015 - 11:43 PM, said:

Yes Gerry, it's as you write. It's apparently important to leave an empty line before and after the include line, as you did.

[R H Steele]

wellsburg, on 13 December 2015 - 10:23 PM, said:

Hi,....ORTS version is X3368. What am I missing here ? Mike

Mike, the code change implemented in OR begins with version 3369. Include works fine with X3369, does not work with 3368.

You can download from here: http://james-ross.co...jects/or/builds

It takes quite a lot of computing power to move the forest/trees, so if you can use the RE to make the adjustment that would be better. FPS decreases on the routes using the tree algorithm.

[Csantucci]

FPS reduction is about 2-3 accordingly to my approximate tests.

[burgerbern]

i have my OR setup to limit frame rates to the monitor at 60fps with the tree clearance on i still get the same figure of 60fps so for me its not taking anything away, and why would you need more than 60fps, my graphics card no longer raises its fan speed like it used to when the fps was left to its own devices and i ran OR, now it stays quiet.

[wellsburg]

Gerry,

Yes, the ORTS update was the answer. No drop in fps on my machine. Thanks for the quick response.

Mike

[Sid P.]

The fix in the .trk file worked for me in the Surfliner2 route - moved the trees nicely..

Somewhere, I recall that someone said that to use the "include" file method in the Route folder, the .trk file in the OpenRails folder had to have a blank line above and below the "include (../xxx.trk)" line that makes OR read the original file.
Is this still true? The reason I ask is that I have been doing some tests with .eng and .wag includes, and blank lines do not appear to be required in those cases.
I may write a summary of the OR "include" methods for the Manual.

[disc]

Sid P., on 17 December 2015 - 02:42 PM, said:

I may write a summary of the OR "include" methods for the Manual.

+1 but please mention this: if the BrakeSystemType is overridden in the include file, then ALL brake parameters should be included in the include file, as in this case the brake system is re-created, so forgets anything related to brake system, that was in the original eng/wag.