Introduction:

This kit is designed to give you the resources to produce a Microsoft Train Simulator (MSTS) engine file compatible with the RailDriver Train Cab Controller.  The engine file will allow your users to run your route or activity with the RailDriver Modern Desktop Controller, using the RailDriver manager software in MSTS.

Background:

With MSTS there is no provision for external hardware control in the game whatsoever. To work around this and to make the RailDriver operate like a game device we use the Heads Up Display (HUD) to generate the feedback necessary to interpret control position and operation effects. An engine file, along with the calibration, ensures that the controls move for the correct amount for the train being driven.

The engine file is a duplicate section of the train's engine file which matches the brakes and throttle configurations of the train you are driving.

At development, RailDriver was optimized for the default trains that were included in the original package and, in theory you could just take the relevant sections of the train's engine file and create a new short version to run as the RailDriver version for the controller.  However, this has caused quite a few issues due to the complexities involved with the way we have to work.

By far the easiest way to produce RailDriver compatible trains is to insert the relevant entries from the default RailDriver files, into your model's engine file in MSTS.  Creating a RailDriver compatible duplicate and including the file with your model will allow your users to run your models on the RailDriver controller.  By doing this, the actual physics of the train are unaffected and the only thing that changes are the control positions and number of notches if applicable.

Format:

When you have finished the model, if you decide to create a RailDriver compatible engine file in addition to your Keyboard driven one, I would suggest the following ways to incorporate this into your model.

1. Make up your train folder as normal but make 2 folders within your train folder: one containing the original engine file and another containing the RailDriver engine file.  Please make sure you provide instructions telling the user how to copy over the RailDriver file into their train. One other point to note, you could also use a batch file to make the change over process easier for users.
2. Modelers using installers should use the preferred method of making a single installer for their model and an additional installer which when double clicked, installs the RailDriver compatible file into the train ready for use.

The only issue here should be that RailDriver compatible files should only be included alongside the install of the train to ensure that just an engine file does not get installed alone, which would cause errors in MSTS.

Routine:

Included in this pack are examples of the RailDriver engine files in both unicode and Word format. In the word format files the items in Blue are the entries that need to be the same as their equivalent RailDriver engine file.   Do not change any of the values in these entries.  The entries for the controls should match their equivalents in the RailDriver files.The simple way to do this is to copy over the relevant entries in the RailDriver files, into their equivalents in your models engine file.

Please pay particular attention to making sure all the brackets (()) and spaces are correct as per the RailDriver equivalent.

There is no need to test these files with a RailDriver controller. If the file runs in MSTS, then it will run with the RailDriver.

When making your readme files, also please make sure that the user knows which RailDriver engine file you made the train to be driven with (This will be the engine file you copied from).

Commercial work:

Developers creating a separate pack of RailDriver engine files for their products may use the included RailDriver Banner in their work provided it relates to the RailDriver system.

Freeware:

A RailDriver banner is included in this pack which you may use as your Upload picture if you are uploading additional engine files for your models, although we would recommend that RailDriver modified engine files be distributed with new models to ensure that the user has the model that the file refers to.

Copyrights:

This pack is distributed by P.I. Engineering as a freeware information pack for developers of models for Microsoft Train Simulator Version 1- 1.2 to enable them to create models that are compatible with the RailDriver controller.

The included RailDriver banner is only to be used for the purpose of showing users that your model is RailDriver compatible.  This banner is not to be used for any other form of advertising without the permission of P.I. Engineering Inc.

This pack is intended for use by 3^rd party commercial and freeware modelers only.  P.I. Engineering cannot be held responsible for damage to software and /or computer equipment by individual users.  By downloading this pack you accept that P.I. Engineering are not liable for any issues arising from use of this information.