Trainz/File Types (File Extensions)

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, especially various common image file formats such as .txt}}, .bmp, .jpg, .png, and for textures: the less common .TGA standardized file types.

These common file types will 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.

ANIM
Animation, for example a steam locomotive's connecting rod movements, or water movement on a river or lake.
BMK
Bookmark. Used to note the current camera position in Surveyor (?).
CDP
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.
CDP2
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
Used to store the program's configuration details. This is a widely used file type, but the format is specific to each program.
CHUMP
Cache file.
GND
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
GameScript source file.
GSE
GameScript encoded file.
GSL
GameScript library file.
GST
GameScript template file.
IM
Indexed 3D mesh.
JA
Jet Archive. Contains compressed copies of multiple assets.
KIN
Kinematics. Associated with animations such as pantographs.
OBS
 ?
PM
Progressive 3D mesh.
TEXTURE
A 2D texture which can be applied to a surface of a 3D object.
TRK
Usually found with a .GND file, contains information about the trackwork of a layout.
TSO
Trackside Object. The variations in a layout that are required for a specific scenario, for example extra trackmarks and triggers.
Last modified on 3 July 2013, at 16:53