Trainz/file types by extensions

From Wikibooks, open books for an open world
Jump to: navigation, search

logo
Trainz Asset Maintenance and Creation

Trainz Annotated Reference Pages
Trainz | Introductory Trainz  | Trainz AM&C | Creation | Appendixes  |  References  • Containers • Kinds • Tags • Index • Vers
 Glossary
 HKeys-CM
 HKeys-DVR
 HKeys-SUR
 HKeys-WIN
 Mouse use
 Notations

Trainz File Types[edit]

In addition to the following list of file types, Trainz also makes extensive use of several common file types one might observe in any Windows installation set up for office or home use without the Trainz simulator, but especially various common image file formats such as .bmp, .jpg, .png, and for textures: the less common .TGA standardized file types. Most non-image file types are of the .txt (plain text) format which trainz uses extensively as ini files to control texturing and for config.txt files found within every asset self-definition folder.

These common file types will often be set off by links to the apropos en.Wikipedia articles. The following list attempts to be comprehensive, so also includes file extensions of older/obsolete as well as current file types used in the newer graphics models. Trainz major data model transitions took place during Trainz 2004, Trainz 2009, and Trainz 2012. Prior to TRS2004 config.txt files were coded BOM, and many assets will still have a BOM on the first line.


ANIM file[edit]

ANIM files — Animation, for example a steam locomotive's connecting rod movements, or water movement on a river or lake. Those wheels you see rotating under the train or that lever you can throw in the CAB all involve dynamic positioning of graphic elements.

  • The range and appearance of those motions are defined in an animation file by the CC
  • who also determines whether they are triggered by script interaction[note 1]
  • or free running (asynchronous). However, even Free running animations don't run chaotically consuming computing resources, but instead have a friendly and benificent CC set up a triggered radius within which range a camera must occur for the animation to begin repeating it's asynchronous loop.[note 2]

BMK file[edit]

BMK filesBookmark. Used to track and record the current camera position in Surveyor when defined, or to return to the same view when used.

CDP file[edit]

CDP files — Content Dispatcher Pack. A file used by Auran and some other content creators to distribute additional assets. A CDP file can contain one or more assets.

CDPA file[edit]

CDPA files — Content Dispatcher Pack Archive. An archive version of the CDP format, used by Auran to place an asset off the main database into axillary data bases controlled by the user, while keeping the asset in a loadable form. Archived assets are no longer selectable when building a route or session, but because they are still indexed, an asset which needs the dependency can still load it. Use primarily to put aside assets needed in something you want to run, but would never use in creation. Example: A North American Trainzer might archive all the Non-American rolling stock and locos, or signs or architectures not likely useful in any route he may build.

CDP2 file[edit]

CDP2 files — Content Dispatcher Pack 2. A new version of the CDP format, used by Auran and some other content creators to distribute additional assets for Trainz Classics.

CFG file[edit]

CFG files — Used to store the program's configuration details. This is a widely used file type, but the format is specific to each program.

CHUMP file[edit]

CHUMP files — Trainz pre-processed ready to load asset Cache file. These are generated by CM when an asset is committed to the database, and the data file is the actual storage locale of the asset data. Where each Trainz version keeps committed asset files has changed somewhat with major technology releases.

GND file[edit]

GND files — The terrain file that contains the topographic details of a map. This is the file that is produced and replaced when creating a map from DEM data.

GS file[edit]

GS files — GameScript source file.

GSE file[edit]

GSE files — GameScript encoded file.

GSL file[edit]

GSL files — GameScript library file.

GST file[edit]

GST files — GameScript template file.

IM file[edit]

IM files — Indexed 3D mesh.

JA file[edit]

JA files — Jet Archive. Contains compressed copies of multiple assets.

KIN file[edit]

KIN files — Kinematics. Associated with animations such as pantographs.

OBS file[edit]

OBS files — ?

PM file[edit]

PM files — Progressive 3D mesh. Obsolescent after TRS2004, but still in many older DLS assets.

SRT file[edit]

SRT Files are the mesh files for displaying SpeedTree items such as trees or grass.


SpeedTree was developed by IDVInc. N3V Games are licensed by IDVInc to use the SpeedTree format in TS2010 and TS12.
The SRT file contains all of the geometric and texture mapping data needed to render a tree object as well as data for wind movement animation.
N3V Games provides no editing or manipulation programs for SpeedTree files. Third-party SpeedTree creation may be undertaken under license between the content creator and IDV Inc.
  • Reverse engineered files from the UDK version of SpeedTree are prohibited for Trainz use under the terms of the IDVInc license.
The game has session-wide adjustments for the wind movement effect in the environment section of Surveyor. This generally needs decreased for better realism.


TEXTURE file[edit]

Not to be confused with texture.txt files which are part of what is compressed in a texture file.

TEXTURE files — A 2D ready-to-load asset texture which is to be applied to a surface of a 3D object by the game engine. Generally BMP, JPG, and most often the preferred TGA file types act as source files for texture.txt control files, both of which are combined by CM into dot-texture files. Files with a *.texture extension will generally be seen only when an asset is opened for editing, and the Trainz is an older release.

TRK file[edit]

TRK files — Usually found with a .GND file, contains information about the trackwork of a layout.

TSO file[edit]

TSO files — Trackside Object. The variations in a layout that are required for a specific scenario, for example extra trackmarks and triggers.

←   Prev: [  Glossary ]  — ↑ [  three   ] -->  —   Next: [   Notations  ]   →
<zzz!-- debugging...

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

--xxx>
  Previous page: Trainz Next page:    
⇐ Previous  Glossary    Next   ⇒   [ Notations ]  →