Open Rails include files coming...1st up all 200 for Autoracks_Jeff_A

[R. Steele]

These files are not complete modified wag files but rather OR include files that substitute data for that found in an original identically named file.
This means (among other things):
1. No duplicate files
2. Your original files remain untouched, no modifications are made to them
3. Your original sound selections, descriptive names, and other features not written into the include file remain untouched.
4. OR interpolates MSTS data to obtain a reasonable simulation, however, using the include file will allow the simulation to use native OR physics and specifically coded OR parameters, providing more realistic performance than can be obtained by interpolating MSTS data.
5. Using the include file allows for easier modification & implementation of current & future OR parameters.
6. Excellent for both OR exclusive users and MSTS/OR users. MSTS parses the regular wag files - ignoring the include files and ORTS parses both the regular wag files and the include files - using data from both to make its calculations.

First up are include files for the complete set (200) of Jeff Auberpine's Autoracks found in this folder >>> Autoracks_Jeff_A

I'm still learning, but this is my way of repaying ( paying forward?) something to the community.
This is the type of work many do not wish to do - for whatever reason, all good to me, - I do not find it onerous and appear to have a small aptitude for the task.

Here's a draft of the doc that will come with the include files.
Read it over, I invite comment on clarifications, typos, grammer, or any questions you may have about include files

Include Files for Open Rails
LOOK HERE > ORTS Manual Reference (release X3804[Draft] 02 June 2017), Section 8.14, pg.116
  Using include files allows the user to make modifications to equipment without the need to change existing files.  
  Any folder within the TRAINSET folder can contain a subfolder named "OpenRails" (without the quotes, of course). Inside the OpenRails folder are placed the include files which are identical in file name to the eng or wag files in the parent folder (folder containing the OpenRails folder).
  Note: an include file can also contain a path to a folder that contains .inc files, which are simply text files that specify parameters for OR to use.
eg.  include ( "..\\EMD SD40\\US\\StdCoupler.inc" )  
  There can be multiple include lines pointing to other folders dealing with power, physics, brakes, traction tables, lights, sounds, etc.  Thus allowing complete user designed trainset customization for Open Rails. 
  Note on names: "file name" refers to the actual name of the file (either eng or wag) NOT the descriptive name which is found in the "Name" line in eng or wag files.
Some of the advantages of using include files:
1.  Ability to use OR specific features for improved and more realistic perfomance in adhesion, friction, coupling, power, braking, etc. without the need to change existing files.
2.  Existing files remain intact - no changes to descriptive names, sounds, etc.
3.  Any future changes to meet OR implementations or user preferences can be made to the include files without disturbing the original files.

The include file always starts with the first line blank - a space at the top of the file.
The second line [ path&name line] is written as follows:
Locomotives:
include ( "..\\ICG_SW14_1498.eng" )
Wagons 
include ( "..\\ATSF_975812_MT.wag" )
  The eng or wag file name within the brackets must be identical to the name of the file that is in the parent folder.  
  NOTE: the manual shows a backslash being used - THIS IS A TYPO - either a double back-slash is used or a forward-slash.  The correct approach and least prone to error is to use a double back-slash with path and name inside double quotes. 
  See >>> http://www.elvastower.com/forums/index.php?/topic/30366-typo-in-the-manual/page__pid__220542#entry220542
  There is more useful and necessary information in the manual section referenced above, required reading for those interested in using include files for Open Rails.

What you will find in the downloaded zip file:
1.  ReadMe files in three formats - which, if you are using WinRAR (and maybe some other utilities), you can view & read before unzipping the file.
2.  A "named" folder which will match a folder you will find in your Trainset folder - or - will find once you have downloaded the required files (**see required files doc).
If you have renamed the folder for the required files you'll have to change something...all folder and file names must match for the process to work.
3. Inside the above "named" folder you will find an OpenRails folder which contains the include files,  
There are no other files provided - eng, wag, shape or textures.
TO install the include files - Simplest Method:
1. Unzip the file to a temp location of your choice. 
[**WinRAR users choose "Extract Files" or "Extract Here" to avoid folder duplication.]
2.  You should have only TWO folders, a parent folder (which should match in name to a folder inside your TRAINSET folder).  Within the parent folder is an OpenRails folder containing the include files.
[** If you have more than two folders you have not performed the extraction correctly. You need to retain the innermost two folders and discard any other folders. Better, delete all folders and extract the folders once again from the zip file.]
3.  Simply  drop (copy&paste) the parent folder into your TRAINSET folder (wherever the location on your )system/setup).  Say yes to the overwrite.  This will deposit the OpenRails folder into your parent folder.
4. You're finished.  No modifications have been made to your files. OR will read the files in the OpenRails folder.
Now you can enjoy Open Rails using its native physics and parameters specifically coded for Open Rails.
***IMPORTANT NOTE:  If you have changed any file names, or have an incomplete set of eng or wag files in your TRAINSET folder you must read the SPECIAL CASES section below.

Second Simplest Method to install include files:
For those that know (or think they know) what they are doing, the curious & suspicious, and also the committed tinkerer ( not Phineas Mason ) or the feller flying by the seat of his pants - do this:
1.  Unzip the download. Find the OpenRails folder within the parent folder and place into the correct folder in your trainset.  If you know what you're doing, you should also know what the correct trainset folder is.
2.  You're finished.  
3.  No mods made to your files & OR will parse the files in the OpenRails folder.
Now you can enjoy Open Rails using its native physics and parameters specifically coded for Open Rails.

***SPECIAL CASES***:
If you have changed your file names and wish to keep those names they must be copied over to two locations in the include file that matches the original file name of the car in question.
1.  The file name of the include file must be changed to match your file name.
2.  The name in the include line (2nd line of file) has to match your file name.
If your folder does not contain the same identically file named cars as in the OpenRails folder you must remove any include files for which you do not have matching cars in your folder.

======Open Rails uses the include files to substitute the following data in making calculations ======
1.  Coupler settings changed to reflect more reasonable values used by OR
Couplers will break in Open Rails under the right load and track conditions. Improper throttle handling can also break couplers.  I'm still experimenting with the range OR will tolerate.  
2. MSTS Adheasion (sic) line replaced by ORTS Adhesion Curtius Kniffler numbers.
3. ORTS Bearing type line added.  I sincerely apologize if these cars do not use roller bearings...some of this stuff is quite new to me..if they do not use roller bearings then the Davis numbers need to be recomputed using FCalc2. Also the bearing type in the ORTS bearing line needs to be changed.  I know OR accepts Roller as a bearing type and possibly also Friction, Solid, Low  (for low torque) - not certain about these three.
The bearing type is used in calculating the ORTS Davis numbers .
4. MSTS Friction removed == ORTS Davis numbers added.  These are computed using FCalc2 and the data provided for the  specific wagon.  The Assumptions comment is added as an aid to show what data was used by FCalc2 to compute the Davis  numbers for Open Rails.
While OR will accept and interpolate the MSTS friction numbers...and a reasonable result is obtained in the simulation...the  use of the ORTS Davis numbers is considered to produce more accurate performance and train behavior in the simulation.  
5. Braking Sections:
Frankly, in this area, I'm still experimenting...so the operative brake section in each WAG file is the ORTS performance section - which reflects the brake parameters I'm  currently using...I welcome feedback and comments-willing to learn. If you want faster reacting brakes (not prototypical/realistic) try these settings:
MaxReleaseRate ( 20 ) - MaxApplicationRate( 20 ) - MaxAuxilaryChargingRate( 20 ) 
EmergencyResCapacity( 10 ) - 	EmergencyResChargingRate( 20 )
 
Grumbles, gripes, ideas, suggestions &  information please email: (will be in final version)

Include_ReadME.zip <<< downloadable version

[qballbandit]

Wow, Gerry! Thanks doesn't seem to cover it. But.....THANKS!