[Amtrak115]

Is there a "list" of ORTS specific parameters that can be include in an OpenRails activity extension file.....What I mean in the activities folder, If I create a folder with name "OpenRails", then put an activity file with the exact name of the activity I'm running some parameters can be modified, I assume on an activity bases. Ex:
ORTSAIHornAtCrossings ( 5 )
ORTSAICrossingHornPattern ( US )

will cause AI trains to sound their horns at crossings using a US style.

So are there more parameters available to activity developers and where might I find this listing?

thanks

Barry

[cjakeman]

 Weter, on 05 April 2021 - 10:55 AM, said:

There was a topic about the complete list of all ORTS parameters (2000+ entries)

Indeed there was and these are all now documented in a spreadsheet at http://tinyurl.com/or-parameters

This link is repeated in the manual but I've just discovered it didn't get added to the openrails.org website. Fixing that now.

[Weter]

Thanks, Chris for confirming.
Else, I'd add, that it's not static list.
It's dynamically being updated, as soon as new ORTS functions are introduced.

[Amtrak115]

thanks for the list...What I was trying to figure out was how to override the user-selected "Location-Linked passing paths processing". An activity I developed is causing a warning then the system crashes if that option is set to true" Back in May of '19, there was thread where this was discussed specifically and by adding an Activity Extension file (making an OpenRails subfolder in the Activity directory, you could override the setting for the duration of the activity. This is from the last post of that Thread...

"Additional parameters have been added in the MG 20 version of OR.

A full list of the current parameters available for setting are as follows:

Comment (=== General TAB ===)
ORTSGraduatedBrakeRelease ( 1 )
ORTSViewDispatchWindow ( 1 )
ORTSRetainersOnAllCars ( 1 )
ORTSSoundSpeedControl ( 1 )

Comment (=== Video TAB ===)
ORTSFastFullScreenAltTab ( 1 )

Comment (=== Simulation TAB ===)
ORTSForcedRedAtStationStops ( 1 )
ORTSAutopilot ( 1 )
ORTSExtendedAITrainShunting ( 1 )
ORTSUseAdvancedAdhesion ( 1 )
ORTSBreakCouplers ( 1 )
ORTSCurveResistanceDependent ( 1 )
ORTSCurveSpeedDependent ( 1 )
ORTSTunnelResistanceDependent ( 1 )
ORTSWindResistanceDependent ( 1 )
ORTSHotStart ( 1 )

Comment (=== Experimental TAB ===)
ORTSLocationLinkedPassingPaths ( 1 )
ORTSAdhesionFactorCorrection ( 100 )
ORTSAdhesionFactorChange ( 10 )

ORTSAdhesionProprtionalToWeather ( 1 )
ORTSActivityRandomization ( 4 )
ORTSActivityWeatherRandomization ( 1 )
ORTSSuperElevationLevel ( 20 )
ORTSSuperElevationMinimumLength ( 200 )
ORTSSuperElevationGauge ( 1435 )
"
Since that time several of these options have been removed from the options screen and set as default (Autopilot, and AI shunting) and the Location-linked passing path processing has moved from the experimental tab to the Simulation tab. I've tried putting the "ORTSLocationLinkedPassingPaths ( 0 ) under the "simulation tab" but that didn't appear to work. I know the AIhornblowing at level crossing is working because I have that set in an extension file. So the question I guess I'm trying to answer is because the setting moved is the code not seeing the override setting in the latest MG version now??? (I tried to find it in code...still looking...lol)

Appreciate any help,

thanks

Barry