TS 2017 ROUTE BUILDING #3 - Railworks File Information

Written By

TS 2017 ROUTE BUILDING #3 - Railworks File Information

Let's begin this tutorial with one simple fact that some people just cannot seem to grasp:
"Computers can't think! They just run programs."

Some folks would swear that their computer has gremlins. It just will not do what they want it to do. The one thing that they fail to consider is that computers are "absolute," which means that they cannot figure out what you want of them. They do what they are told, and nothing else! And so, if something isn't working, it's not likely the computer. It would be the file.

Railworks uses a number of files with file extensions unique to the simulation. This is well and good to prevent folks from reverse engineering their product, or from using the files in another application. It does, however, present a challenge to developers because of the enormous amount of file conversions that have to be made to models and textures in order to make them appear in Train Simulator.

It is not enough to copy an asset from one Asset folder and paste it into another. It probably won't work because of the many cross-references pointing to and from the file. Asset files are also written to assign the asset to a particular Provider/Product. As an example, you cannot copy an asset from an RSC product folder and paste it into a DTG product folder and expect it to work.

--SAFETY TIP--
You've probably heard it a million times before but I'm going to say it again... BACK UP any file that you intend to alter in any way. I cannot overemphasize this enough! Back up every 15 minutes or you may find yourself repeating a lot of previous work.

I might suggest a simple way to back up original files is by adding a .oem extension to the file name, including its original file extension. As an example: "Horse.bin" becomes "Horse.bin.oem". I have found this to be the easiest method of backing up an original file in the original folder just in case I have to put it back. The file has retained its original name. I just simply remove the .oem extension and the original file is back the way it was.

Direct file manipulation is not recommended unless you are very sure of what you are doing. One little spelling error or omission could completely render the file useless. Direct editing of another author's file could also constitute theft, especially if one intends to redistribute the file to anyone else, whether it be in a Freeware or Payware route.

File Clutter is another issue that ought to be kept in check. I have particularly noted this with the distribution of Freeware routes. Since freeware routes typically use assets belonging to others it is necessary that the asset be stored in the Provider/Product folders in which the asset came. Imagine, if you will, using a tree from one provider, an automobile from another, a building from yet another, and so on. In a short while your Asset folder could become very cluttered with hundreds of Provider and Product folders. For this reason (and this is just my preference) I tend to steer clear of Freeware routes.


More in TS2017 ROUTE BUILDING #4 - Supplementary Programs
Back to Tutorials Index Page

Posts Most Viewed

TS2017 ROUTE BUILDING #5 - The Railworks World Editor

Written By
Image
Route Building #5 - The Railworks World Editor From this point onward, it is highly recommended that you build your route in a windowed mode of Railworks. Full screen mode hides the 'close window' button in the upper right-hand corner of the window. Clicking this button is the only way I know of to close the program without saving. SUMMARY of Previous Tutorials By this point in the process: You ought to have completed the previous tutorials and have devised a plan for Where, When, What, and How.  You will need to have your start point coordinates written down for when you first create your route template. These coordinates use the Lat/Long format (eg. 55.83625  -115.3392) You will have chosen the Provider and Product names for your route, being careful to avoid names that may already be in use. A lot of authors will use their forum handle as their Provider folder name in order to avoid naming conflicts with others. The Product folder name is the unique name of the rout
Read more

TS2017 ROUTE BUILDING #6 - Getting Started (The Golf Course)

Written By
Image
TS2017 ROUTE BUILDING #6 - Getting Started (The Golf Course) ROUTE MARKERS Unless you wish to "walk" your way throughout the route you are building, you're going to need some route markers for navigating your way around the World Editor. Route markers are nothing more than a geographical locator within the Route Editor to travel from one place in the route to another. It saves you a lot of time in going from A to B. In the case of my own route I created a series of markers (known as landmarks in Google Earth) of key locations within the route. Once the landmarks were created I exported the file as a .kml file to the RouteMarkers folder located in my Product folder, awaiting conversion for use in Railworks. RW Tools comes back into service again for converting the .kml file to a set of two files that Railworks can use. To convert the .kml file to Railworks, proceed as follows: Open RW Tools and select the tab, Route Building Tools and hover your cursor over Ma
Read more

TS 2017 ROUTE BUILDING #2 - Railworks Folder Hierarchy

Written By
Image
TS 2017 ROUTE BUILDING #2 - Railworks Folder Hierarchy Most often, the Railworks installation directory is located in C:\Program Files\Steam\Steam Apps\Common\Railworks. Yours may differ somewhat, depending on your computer configuration. Within the Railworks root folder (also called a parent folder) you will find a number of other folders. The only ones we need concern ourselves with are the Assets, Content, Dem, and Source folders. ASSETS Within the Assets folder you will find the folders of all the Providers to your installation. Inside the Provider folders are the Products supplied by that Provider. Within the Products folder are all the files and folders pertaining to the assets of that particular product. A inside of a typical Product folder might look something like this: Audio Environment PreLoad RailNetwork RailVehicles RouteMarkers Scenery Stations TemplateRoutes TimeOfDay Weather You will also find in there, a file called Blueprints.pak.
Read more