Parts of this work is based on original files by Kuju/Microsoft.
Some parts are done with Train Sim Modeler by Abacus.
Other parts are done with gmax by Discreet.
Installer made with QSetup by Pantaray.
See credits for contributors.

You may use and share this freely provided you do not charge for it and you keep it intact. This package may NOT be uploaded to sites without my prior permission. If you release a route based on this you should clearly state that the route uses XTracks and that XTracks is freely available at and UKTrainSim. Also state which version of XTracks your route is using and that the user needs this or a later version. Do not include XTracks as an integrated part of your routes installation. You should include the textures as part of your delivery to make it easier for the end user but XTracks should be distributed as a separate package as it affects all installed routes. You may include the complete XTracks package (installer or .zip) as a seperate add-on if distributing your route on CD or any other media provided you only charge for the handling costs.

If you are going to use the DualTracks shapes by William Adams please read and understand his original license agreement supplied with the textures in the 'Route builders extras' package.

If you want to use any part of XTracks seperately you should contact me. Uploading of single files from this package is generally not allowed without permission. You can reach me at

Regarding the use of XTracks in commercial routes

  • Use of XTracks in a commercial route is generally not prohibited.
  • The use of XTracks must be stated before purchase so that the end-user is made aware of this fact (eg outside of box and on web-site).
  • You should also state which version of XTracks the route uses.
  • The fact XTracks is free and available at no charge from and must also be stated to the end-user (eg 'This route uses XTracks v3.12 (or later) which is freely available at and XTracks v3.12 is included on this CD.' (CD part only if applicable)).
  • There must NOT be any additional cost to the route because it uses XTracks (that is same cost as comparable route without XTracks but same size route, scenery, rolling stock etc).
  • You are NOT allowed to pick bits and pieces of XTracks into your own installation.
  • You are NOT allowed to integrate the XTracks installtion into your own customized installer. The XTracks installer must be used as is. You may though start the XTracks installer from inside your own installer.
  • You may include the XTracks installer (as is) on CD for distribution purpouses.
  • There is no licensing fee for the use of XTracks, it's free for all routes commercial or not.
  • If using the DualTracks sections by Bill Adams you must have his agreement (see above).
  • You must be prepared to support end-users concerning problems that may occur due to other routes not following the community standard with the 'standardized' tsection.dat.
  • You are not required to host XTracks for download at your server but if you want to do this it must be as a free download for everyone, not only registered customers.
  • The use of XTracks does NOT free you of licensing terms for the use of MSTS original track system. XTracks is not a replacement for this track system but a complement.
If you have any questions please contact me at the address above.

Tip for route installers
Using QSetup installer you can check for the existence of XTracks during route installation. To add this feature you should include an 'Execute' item that checks for the existence of any of the shapes introduced in the version of XTracks your route is dependent upon. This check should be performed 'After Destination' when the installation directory is set. If the shape is not found you should display a message and abort the installation. Here is an example of how the Execution Item should look like:
  Click on image for a larger view.
The text in the 'Argument-1' textbox reads: "<InstallDir>GLOBAL\SHAPES\a1tBrdg60r1d.s".

The same technique can be employed to test for prior versions of your route and taking actions accordingly. QSetup can't check contents in Unicode text files thus you can't check the build of tsection.dat with it. I have included a template for a QSetup installer with the route builders package, the Route.qsp file.