TrainzOnline - User contributions [en]

Help:Trainz Content (Content Manager)

2013-12-10T06:24:18Z

Fabartus: Begin writing

== Content Manager Tech Manual ==
{{FUN-top}}
{{user-contrib}}
To the new user, '''ContentManager.exe''' (usually just ''''CM'''') has the appearance of a Windows-XP-era style spreadsheet with a over-busy left side pane of some sort occupying the left margin and the right pane initially having a somewhat confusing spreadsheet-like format—which on initial boot is alarmingly incomplete. It won't help the new users state of calm that the first thing the tool displays is an inadequate message about the initial long wait the new Trainzer is now experiencing in an alarming way, but that's our beloved N3V Geeks for you.
[[file:Content Manager of TS2009-SP3 Filters-2 = (setting Local+Routes).JPG|thumb|left|TS2009-SP3's Content Manager 2.0 shown displaying the 42 local routes included; because of the last update, there are several routes showing the red exclamation mark signifying a fault in an asset.]]
They're not real good at walking in another man's shoes. There is nothing to worry about. While there is plenty of time to go make a cup of tea or void the bladder of previously ingested caffeine—fortunately the wait while the database manager initializes its local list of assets available on the [[Download Station]] will soon be over. Of course if you hadn't connected to the internet, or haven't yet signed in and registered your copy with Planet Auran, this wait will be indefinite, so quit out and go take care of the paperwork! {{-}}
'''TIP:''' when all else fails in Trainz, try the escape (ESC) key.
There at first seem to be a bewildering number of columns of information or indexing, only some of which stand out initially as comprehensible. The [[kuid]], author, and [[Trainz assets|asset name]] columns readily jump out as identifiers, while the default column set does not display them, the region and era, or the dates columns at least seem to make immediate sense—though how such data might either be used or even be useful is not immediately clear. This page and its several sub-pages is meant to give you a basic set of skills and a knowledge reference about ContentManager, a data base manager, download manager, upload manager, archive controller, asset status indicator, and update manager tool can be used to make your Trainz experience even better.

Unlike the rest of Trainz, Content Manager is an actual windowed application, but the first lesson to learn about living with CM is that Trainz has a hidden part called [[TADdaemon]] that takes a while to shut down when quitting out so you want to wait plenty of time (as much as 5-6 minutes) when leaving Trainz for this facility to close up shop. Then and only then will it be safe to reboot or shut down the computer.
{|
|-
|
{{UserTip|width==50%|Content and asset in Trainz-speak are nearly always used in interchangeable contexts, but do have a technical difference. Technically, an asset isn't content until it's included in some other asset, such as the normal two grouping containers: Sessions or Routes. Until placed in the virtual world by one of those, assets are just potential content that appears as menu choices on menus.
}}
|[[File:Content Manager of TS2009-SP3 (after build 40040 (SP2) to 41844 (SP3)-2 (cropped+resized).JPG|thumb|48%|Trainz 2009 after upgrade to Service Pack 3; all releases after this list the Trainz-build version in the Windows Title Bar where this image shows "ContentManager 2.0" like earlier [[TS2009]] versions. Service Pack 4 showed "ContentManager 3.3" in the same spot, TS2010 started with "ContentManager 3.2", and TS2012 "ContentManager 3.6" or 3.7 for SP1.]]
|}
Content Manager has a number of functions rolled into one integrated package giving you control and access to the hundreds of thousands of assets available for Trainz. The main functions that Content Manager offers are:

* Download Station Indexer and searching
* Downloading Manager to acquire new Content
* Content Management
* Archiving/Backup
* Uploading Content
* Creating/Editing/Verifying Content

The following pages provide detail on using the Content Manager interface.

== Getting Started ==
* [[#Menus]]
* [[#Bars]]
* [[#Main View Panel]]
* [[#Action Panels]]
* [[#Icons]]
* [[#Settings]]
* [[#First Class Ticket]]

== Sorting, Searching and Organizing Content ==
* [[#Sorting]]
* [[#Searching]]
* [[#Default Search Filters]]
* [[#Adding a Search Parameter]]
* [[#Removing a Search Parameter]]
* [[#Current Search and Saving Search Filters]]
* [[#Keywords]]
* [[#Disabling, Enabling and Deleting Assets]]

== The Download Station and Downloading ==
* [[#Selecting Assets to Download]]
* [[#A word about dependencies]]
* [[#Managing your Download Helper List]]
* [[#Starting and Stopping a Download]]

== Importing Content and CDPs ==
* [[#Importing Content]]
* [[#Importing CDPs]]

== Exporting Content and CDPs ==
* [[#Exporting Content]]
* [[#Exporting CDPs]]

== Archiving ==
* [[#Creating Archives]]
* [[#Installing Assets from Archives]]

== Creating and Editing Content ==
* [[#Creating Content]]
* [[#Editing Content]]
* [[#Reverting Content]]

== Uploading ==
* [[#Uploading]]

[[Category:Help|Content Manager]]
{{FUN-bot}}

Content Manager

2013-12-10T06:00:30Z

Fabartus: /* Content Manager */ link

{{FUN-beg}}{{FUN-BOT}}{{ORP-top}}
:'''''Trainz Beginners''' seeking How-To guidance and instruction on running ContentManager should refer to '''[[Help:Content Manager]]'''.''
==Content Manager==
'''Content Manager''' (abbreviated as '''CM''') is the included content management {{wp|Graphical user interface|GUI}} utility for managing assets, uploading and downloading content from the [[Download Station]], and for exporting and importing [[cdp file]]s for archiving or sharing. It has been part of Trainz releases since the debut of [[TRS2006]] (then called Content Manager Plus and '''CMP''') in the fall of 2005, and was the major improvement made to the four service packs that evolved [[TRS2004]]'s advances replacing several separate .exe file modules with a single common user interface to manipulate and manage assets and content. CM includes the ability to archive assets, disable them so they would not appear in Surveyor asset selection APIs and a filter definition and selection system which allowed the Trainz user to fine tune the selections presented in the menuing of the Surveyor module tools APIs.

==Functionality==

Content Manager is intended to address the following functions:
* Install and remove custom content.
* Archive custom content.
* Search both local and DLS content.
* Download DLS content.
* Create and edit custom content.
* Provide a platform for executing [[Content Manager Tools]].

==Ideology==

Content Manager is designed to allow content creators to produce new content, and to allow end-users to download with a minimal of hassle. It is tightly integrated with the Download Station (DLS) to allow content to be uploaded and downloaded in a reliable fashion.

Content Manager is specifically not intended for users to perform regular editing of content created by others; this behavior is considered fairly counter-productive for the following reasons:
* It is expected that DLS content will be available in a working format, and that Content Manager will transfer the content to the local machine in a working format.
** This is historically inaccurate, please see the [[Download Station Cleanup]] page. It was found that many legacy content items, had typos, misspellings, and formatting errors of one sort or another that were further linked to Trainz run-time crashes.
* Trainz software was revised to trap and expose these errors.
* It is required that local content maintains parity with the original DLS content, such that dependencies and updates continue to work appropriately.
** By editing DLS content locally, the user is establishing that they will take responsibility for maintaining not only the edited asset, but potentially all assets which share some kind of dependency on the edited asset.
* When a user downloads or purchases a new item of content, they have a reasonable expectation that it will work "out of the box".
** This expectation is in direct conflict with the user performing significant edits to other content.
There are some obvious cases where edits are harmless, and CMP attempts to allow for the most useful of these- such as renaming or hiding an asset.

==Ramifications-asset validation==
It is expected that the Trainz environment will be optimised and extended with each new version release. To allow existing custom content to work with newer versions of Trainz, N3V has adopted an "installation" process for custom content, in favor of the original "drop it in a folder" process. During this process, the Trainz environment performs the following steps:
* Validates that the content will work with the current Trainz installation.
* Precaches various metrics from the content that Trainz requires at runtime such that the entire item of content does not need to be loaded at game startup (as was the case in the earliest Trainz versions.)
* Upgrades files within the content to the latest file formats, such that the upgrade process does need to not occur during loading.
* Converts some files from human-readable form to a machine-optimized format.
* Moves the raw content files to storage within the Trainz Asset Database.
* Notifies running Trainz executables of any changes.

==Changes since TRS2004==
Users are no longer provided with direct access to installed custom content, for the following reasons, but such assets may be cloned under a user kuid code:
* Installed content may be stored in a custom internal format, rather than in the public distribution format.
* Edits made to files which have supposedly been pre-processed will result in runtime errors where the cached data no longer matches the actual content on disk.

Since direct access is not possible, Content Manager provides a mechanism for users to 'check out' items for editing, and to check them in again after the edits are complete. (Open for Edit, asset validation, and Committing the asset) The normal installation steps are performed during the check-in process allowing Trainz to use the updated content safely. Trainz will issue a query and warning when installed content has been modified, or as has sometimes happened, imported from an older version of Trainz, then the separate asset (now part of the new release) might be in the situation of overwriting an updated validated version.
{{ORP-bot}}

"Category-region" tag

2013-12-10T05:54:00Z

Fabartus: /* About Category-region codes */ Annotate how seen in CM, +2nd example

{{FUN-beg}}{{ORP-top}}
==About Category-region codes==
'''Category-region codes''' are a single ("UK") or multiple codes ("AU;DE;UK;US") in a quoted string that is included in the config.txt file for user defined filters.
* Assets with narrow single country scope would contain a single code after the tagname.
* Assets which were widely found in many regions (e.g. ''''Caterpillar D7 bulldozer'''', will list the series of country codes of the region.)
** The codes have only a minor importance in TRAINZ and are primarily used in Trainz as a sort and selection criteria in user defined filters.
** These codes do show up under the region column in [[Content Manager]] where they can be included in defining filters one can also use in [[Surveyor]]. This eliminates looking at undesired assets when focuses on developing your routes.
* For content that exists in multiple areas, when creating new assets, select appropriate codes in [[Content Creator Plus]] (CCP) or hand edit them into the config.txt ini files.
; For example: a locomotive that was available in the United States and Canada would be specified as follows:

category-region     "US;CA"
: One that was available in Australia, Canada, the United States and in the United Kingdom would be specified as follows:

category-region     "AUS;CA;UK;US"

==Tables of codes==
<big>'''The category-region codes below are in alphabetical order by sort criteria.

Legal codes that are recognized by Trainz are as follows:'''</big>

===by region code order===

{|
|-
! AD-EE || EG-LI || LK-SC || SD-ZZ
|-valign="top"
|
# AD Andorra
# AE United Arab Emirates
# AF Afghanistan
# AG Antigua and Barbuda
# AI Anguilla
# AL Albania
# AM Armenia
# AN Netherland Antilles
# AO Angola
# AQ Antarctica
# AR Argentina
# AS American Samoa
# AT Austria
# AU Australia
# AW Aruba
# AZ Azerbaidjan
# BA Bosnia-Herzegovina
# BB Barbados
# BD Bangladesh
# BE Belgium
# BF Burkina Faso
# BG Bulgaria
# BH Bahrain
# BI Burundi
# BJ Benin
# BM Bermuda
# BN Brunei Darussalam
# BO Bolivia
# BR Brazil
# BS Bahamas
# BT Buthan
# BV Bouvet Island
# BW Botswana
# BY Belarus
# BZ Belize
# CA Canada
# CC Cocos (Keeling) Isl.
# CF Central African Rep.
# CG Congo
# CH Switzerland
# CI Ivory Coast
# CK Cook Islands
# CL Chile
# CM Cameroon
# CN China
# CO Colombia
# CR Costa Rica
# CS Czechoslovakia
# CU Cuba
# CV Christmas Island
# CY Cyprus
# CZ Czech Republic
# DE Germany
# DJ Djibouti
# DK Denmark
# DM Dominica
# DO Dominican Republic
# DZ Algeria
# EC Ecuador
# EE Estonia
|
# EG Egypt
# EH Western Sahara
# ES Spain
# ET Ethiopia
# FI Finland
# FJ Fiji
# FK Falkland Isl.(Malvinas)
# FM Micronesia
# FO Faroe Islands
# FR France
# GA Gabon
# GB Great Britain
# GD Grenada
# GE Georgia
# GH Ghana
# GI Gibraltar
# GL Greenland
# GP Guadeloupe (Fr.)
# GQ Equatorial Guinea
# GF Guyana (Fr.)
# GM Gambia
# GN Guinea
# GR Greece
# GT Guatemala
# GU Guam (US)
# GW Guinea Bissau
# GY Guyana
# HK Hong Kong
# HM Heard & McDonald Isl.
# HN Honduras
# HR Croatia
# HT Haiti
# HU Hungary
# ID Indonesia
# IE Ireland
# IL Israel
# IN India
# IO British Indian O. Terr.
# IQ Iraq
# IR Iran
# IS Iceland
# IT Italy
# JM Jamaica
# JO Jordan
# JP Japan
# KE Kenya
# KG Kirgistan Ex-USSR
# KH Cambodia
# KI Kiribati
# KM Comoros
# KN St.Kitts Nevis Anguilla
# KP Korea (North)
# KR Korea (South)
# KW Kuwait
# KY Cayman Islands
# KZ Kazachstan
# LA Laos
# LB Lebanon
# LC Saint Lucia
# LI Liechtenstein
|
# LK Sri Lanka
# LR Liberia
# LS Lesotho
# LT Lithuania
# LU Luxembourg
# LV Latvia
# LY Libya
# MA Morocco
# MC Monaco
# MD Moldavia Ex-USSR
# MG Madagascar
# MH Marshall Islands
# ML Mali
# MM Myanmar
# MN Mongolia
# MO Martinique (Fr.)
# MR Mauritania
# MS Montserrat
# MT Malta
# MU Mauritius
# MV Maldives
# MW Malawi
# MX Mexico
# MY Malaysia
# MZ Mozambique
# NA Namibia
# NC New Caledonia (Fr.)
# NE Niger
# NF Norfolk Island
# NG Nigeria
# NI Nicaragua
# NL Netherlands
# NO Norway
# NP Nepal
# NR Nauru
# NT Neutral Zone
# NU Niue
# NZ New Zealand
# OM Oman
# PA Panama
# PE Peru
# PF Polynesia (Fr.)
# PG Papua New Guinea
# PH Philippines
# PK Pakistan
# PL Poland
# PM St. Pierre & Miquelon
# PN Pitcairn
# PT Portugal
# PR Puerto Rico (US)
# PW Palau
# PY Paraguay
# QA Qatar
# RE Reunion (Fr.)
# RO Romania
# RU Russian Federation Ex-USSR
# RW Rwanda
# SA Saudi Arabia
# SB Solomon Islands
# SC Seychelles
|
# SD Sudan
# SE Sweden
# SG Singapore
# SH St. Helena
# SI Slovenia
# SJ Svalbard & Jan Mayen Is
# SK Slovak Republic
# SL Sierra Leone
# SM San Marino
# SN Senegal
# SO Somalia
# SR Suriname
# ST St. Tome and Principe
# SU Soviet Union
# SV El Salvador
# SY Syria
# SZ Swaziland
# TC Turks & Caicos Islands
# TD Chad
# TF French Southern Terr.
# TG Togo
# TH Thailand
# TJ Tadjikistan Ex-USSR
# TK Tokelau
# TL East Timor
# TM Turkmenistan Ex-USSR
# TN Tunisia
# TO Tonga
# TR Turkey
# TT Trinidad & Tobago
# TV Tuvalu
# TW Taiwan
# TZ Tanzania
# UA Ukraine
# UG Uganda
# UK United Kingdom
# UM US Minor outlying Isl.
# US United States
# UY Uruguay
# UZ Uzbekistan Ex-USSR
# VA Vatican City State
# VC St.Vincent & Grenadines
# VE Venezuela
# VG Virgin Islands (British)
# VI Virgin Islands (US)
# VN Vietnam
# VU Vanuatu
# WF Wallis & Futuna Islands
# WS Samoa
# YE Yemen
# YU Yugoslavia
# ZA South Africa
# ZM Zambia
# ZR Zaire
# ZW Zimbabwe
|}

===by country name order===

{|
|''' Aa—Ear || Eas— Ecu || Les—Lib || San—Sau'''
|- valign="top"
|
# Afghanistan AF
# Albania AL
# Algeria DZ
# American Samoa AS
# Andorra AD
# Angola AO
# Anguilla AI
# Antarctica AQ
# Antigua and Barbuda AG
# Argentina AR
# Armenia AM
# Aruba AW
# Australia AU
# Austria AT
# Azerbaidjan AZ
# Bahamas BS
# Bahrain BH
# Bangladesh BD
# Barbados BB
# Belarus BY
# Belgium BE
# Belize BZ
# Benin BJ
# Bermuda BM
# Bolivia BO
# Bosnia-Herzegovina BA
# Botswana BW
# Bouvet Island BV
# Brazil BR
# British Indian O. Terr. IO
# Brunei Darussalam BN
# Bulgaria BG
# Burkina Faso BF
# Burundi BI
# Buthan BT
# Cambodia KH
# Cameroon CM
# Canada CA
# Cayman Islands KY
# Central African Rep. CF
# Chad TD
# Chile CL
# China CN
# Christmas Island CV
# Cocos (Keeling) Is CC
# Colombia CO
# Comoros KM
# Congo CG
# Cook Islands CK
# Costa Rica CR
# Croatia HR
# Cuba CU
# Cyprus CY
# Czech Republic CZ
# Czechoslovakia CS
# Denmark DK
# Djibouti DJ
# Dominica DM
# Dominican Republic DO
# East Timor TL
|
# Ecuador EC
# Egypt EG
# El Salvador SV
# Equatorial Guinea GQ
# Estonia EE
# Ethiopia ET
# Falkland Isl.(Malvinas) FK
# Faroe Islands FO
# Fiji FJ
# Finland FI
# France FR
# French Southern Terr. TF
# Gabon GA
# Gambia GM
# Georgia GE
# Germany DE
# Ghana GH
# Gibraltar GI
# Great Britain GB
# Greece GR
# Greenland GL
# Grenada GD
# Guadeloupe (Fr.) GP
# Guam (US) GU
# Guatemala GT
# Guinea GN
# Guinea Bissau GW
# Guyana GY
# Guyana (Fr.) GF
# Haiti HT
# Heard & McDonald Isl. HM
# Honduras HN
# Hong Kong HK
# Hungary HU
# Iceland IS
# India IN
# Indonesia ID
# Iran IR
# Iraq IQ
# Ireland IE
# Israel IL
# Italy IT
# Ivory Coast CI
# Jamaica JM
# Japan JP
# Jordan JO
# Kazachstan KZ
# Kenya KE
# Kirgistan Ex-USSR KG
# Kiribati KI
# Korea (North) KP
# Korea (South) KR
# Kuwait KW
# Laos LA
# Latvia LV
# Lebanon LB
# Lesotho LS
|
# Liberia LR
# Libya LY
# Liechtenstein LI
# Lithuania LT
# Luxembourg LU
# Madagascar MG
# Malawi MW
# Malaysia MY
# Maldives MV
# Mali ML
# Malta MT
# Marshall Islands MH
# Martinique (Fr.) MO
# Mauritania MR
# Mauritius MU
# Mexico MX
# Micronesia FM
# Moldavia Ex-USSR MD
# Monaco MC
# Mongolia MN
# Montserrat MS
# Morocco MA
# Mozambique MZ
# Myanmar MM
# Namibia NA
# Nauru NR
# Nepal NP
# Netherland Antilles AN
# Netherlands NL
# Neutral Zone NT
# New Caledonia (Fr.) NC
# New Zealand NZ
# Nicaragua NI
# Niger NE
# Nigeria NG
# Niue NU
# Norfolk Island NF
# Norway NO
# Oman OM
# Pakistan PK
# Palau PW
# Panama PA
# Papua New Guinea PG
# Paraguay PY
# Peru PE
# Philippines PH
# Pitcairn PN
# Poland PL
# Polynesia (Fr.) PF
# Portugal PT
# Puerto Rico (US) PR
# Qatar QA
# Reunion (Fr.) RE
# Romania RO
# Russian Federation Ex-USSR RU
# Rwanda RW
# Saint Lucia LC
# Samoa WS
# San Marino SM
|
# Saudi Arabia SA
# Senegal SN
# Seychelles SC
# Sierra Leone SL
# Singapore SG
# Slovak Republic SK
# Slovenia SI
# Solomon Islands SB
# Somalia SO
# South Africa ZA
# Soviet Union SU
# Spain ES
# Sri Lanka LK
# St. Helena SH
# St. Pierre & Miquelon PM
# St. Tome and Principe ST
# St.Kitts Nevis Anguilla KN
# St.Vincent & Grenadines VC
# Sudan SD
# Suriname SR
# Svalbard & Jan Mayen Is SJ
# Swaziland SZ
# Sweden SE
# Switzerland CH
# Syria SY
# Tadjikistan Ex-USSR TJ
# Taiwan TW
# Tanzania TZ
# Thailand TH
# Togo TG
# Tokelau TK
# Tonga TO
# Trinidad & Tobago TT
# Tunisia TN
# Turkey TR
# Turkmenistan Ex-USSR TM
# Turks & Caicos Islands TC
# Tuvalu TV
# Uganda UG
# Ukraine UA
# United Arab Emirates AE
# United Kingdom UK
# United States US
# Uruguay UY
# US Minor outlying Isl. UM
# Uzbekistan Ex-USSR UZ
# Vanuatu VU
# Vatican City State VA
# Venezuela VE
# Vietnam VN
# Virgin Islands (British) VG
# Virgin Islands (US) VI
# Wallis & Futuna Islands WF
# Western Sahara EH
# Yemen YE
# Yugoslavia YU
# Zaire ZR
# Zambia ZM
# Zimbabwe ZW
|}


==Notes==
==Categories==
[[Category:Config Tag|Category-region]]
{{ORP-bot|Category-region}}<div>{{FUN-bot|Category-region}}

"Category-region" tag

2013-12-10T05:36:44Z

Fabartus: /* Categories */ +pipetricks

{{FUN-beg}}{{ORP-top}}
==About Category-region codes==
'''Category-region codes''' are a single ("UK") or multiple codes ("AU;DE;UK;US") in a quoted string that is included in the config.txt file for user defined filters.
* Assets with narrow single country scope would contain a single code after the tagname.
* Assets which were widely found in many regions (e.g. ''''Caterpillar D7 bulldozer'''', will list the series of country codes of the region.)
** The codes have only a minor importance in TRAINZ and are primarily used in Trainz as a sort and selection criteria in user defined filters.
* For content that exists in multiple areas, when creating new assets, select appropriate codes in [[Content Creator Plus]] (CCP).
** For example, a locomotive that was available in the United States and Canada would be specified as follows:

category-region "US;CA"

==Tables of codes==
<big>'''The category-region codes below are in alphabetical order by sort criteria.

Legal codes that are recognized by Trainz are as follows:'''</big>

===by region code order===

{|
|-
! AD-EE || EG-LI || LK-SC || SD-ZZ
|-valign="top"
|
# AD Andorra
# AE United Arab Emirates
# AF Afghanistan
# AG Antigua and Barbuda
# AI Anguilla
# AL Albania
# AM Armenia
# AN Netherland Antilles
# AO Angola
# AQ Antarctica
# AR Argentina
# AS American Samoa
# AT Austria
# AU Australia
# AW Aruba
# AZ Azerbaidjan
# BA Bosnia-Herzegovina
# BB Barbados
# BD Bangladesh
# BE Belgium
# BF Burkina Faso
# BG Bulgaria
# BH Bahrain
# BI Burundi
# BJ Benin
# BM Bermuda
# BN Brunei Darussalam
# BO Bolivia
# BR Brazil
# BS Bahamas
# BT Buthan
# BV Bouvet Island
# BW Botswana
# BY Belarus
# BZ Belize
# CA Canada
# CC Cocos (Keeling) Isl.
# CF Central African Rep.
# CG Congo
# CH Switzerland
# CI Ivory Coast
# CK Cook Islands
# CL Chile
# CM Cameroon
# CN China
# CO Colombia
# CR Costa Rica
# CS Czechoslovakia
# CU Cuba
# CV Christmas Island
# CY Cyprus
# CZ Czech Republic
# DE Germany
# DJ Djibouti
# DK Denmark
# DM Dominica
# DO Dominican Republic
# DZ Algeria
# EC Ecuador
# EE Estonia
|
# EG Egypt
# EH Western Sahara
# ES Spain
# ET Ethiopia
# FI Finland
# FJ Fiji
# FK Falkland Isl.(Malvinas)
# FM Micronesia
# FO Faroe Islands
# FR France
# GA Gabon
# GB Great Britain
# GD Grenada
# GE Georgia
# GH Ghana
# GI Gibraltar
# GL Greenland
# GP Guadeloupe (Fr.)
# GQ Equatorial Guinea
# GF Guyana (Fr.)
# GM Gambia
# GN Guinea
# GR Greece
# GT Guatemala
# GU Guam (US)
# GW Guinea Bissau
# GY Guyana
# HK Hong Kong
# HM Heard & McDonald Isl.
# HN Honduras
# HR Croatia
# HT Haiti
# HU Hungary
# ID Indonesia
# IE Ireland
# IL Israel
# IN India
# IO British Indian O. Terr.
# IQ Iraq
# IR Iran
# IS Iceland
# IT Italy
# JM Jamaica
# JO Jordan
# JP Japan
# KE Kenya
# KG Kirgistan Ex-USSR
# KH Cambodia
# KI Kiribati
# KM Comoros
# KN St.Kitts Nevis Anguilla
# KP Korea (North)
# KR Korea (South)
# KW Kuwait
# KY Cayman Islands
# KZ Kazachstan
# LA Laos
# LB Lebanon
# LC Saint Lucia
# LI Liechtenstein
|
# LK Sri Lanka
# LR Liberia
# LS Lesotho
# LT Lithuania
# LU Luxembourg
# LV Latvia
# LY Libya
# MA Morocco
# MC Monaco
# MD Moldavia Ex-USSR
# MG Madagascar
# MH Marshall Islands
# ML Mali
# MM Myanmar
# MN Mongolia
# MO Martinique (Fr.)
# MR Mauritania
# MS Montserrat
# MT Malta
# MU Mauritius
# MV Maldives
# MW Malawi
# MX Mexico
# MY Malaysia
# MZ Mozambique
# NA Namibia
# NC New Caledonia (Fr.)
# NE Niger
# NF Norfolk Island
# NG Nigeria
# NI Nicaragua
# NL Netherlands
# NO Norway
# NP Nepal
# NR Nauru
# NT Neutral Zone
# NU Niue
# NZ New Zealand
# OM Oman
# PA Panama
# PE Peru
# PF Polynesia (Fr.)
# PG Papua New Guinea
# PH Philippines
# PK Pakistan
# PL Poland
# PM St. Pierre & Miquelon
# PN Pitcairn
# PT Portugal
# PR Puerto Rico (US)
# PW Palau
# PY Paraguay
# QA Qatar
# RE Reunion (Fr.)
# RO Romania
# RU Russian Federation Ex-USSR
# RW Rwanda
# SA Saudi Arabia
# SB Solomon Islands
# SC Seychelles
|
# SD Sudan
# SE Sweden
# SG Singapore
# SH St. Helena
# SI Slovenia
# SJ Svalbard & Jan Mayen Is
# SK Slovak Republic
# SL Sierra Leone
# SM San Marino
# SN Senegal
# SO Somalia
# SR Suriname
# ST St. Tome and Principe
# SU Soviet Union
# SV El Salvador
# SY Syria
# SZ Swaziland
# TC Turks & Caicos Islands
# TD Chad
# TF French Southern Terr.
# TG Togo
# TH Thailand
# TJ Tadjikistan Ex-USSR
# TK Tokelau
# TL East Timor
# TM Turkmenistan Ex-USSR
# TN Tunisia
# TO Tonga
# TR Turkey
# TT Trinidad & Tobago
# TV Tuvalu
# TW Taiwan
# TZ Tanzania
# UA Ukraine
# UG Uganda
# UK United Kingdom
# UM US Minor outlying Isl.
# US United States
# UY Uruguay
# UZ Uzbekistan Ex-USSR
# VA Vatican City State
# VC St.Vincent & Grenadines
# VE Venezuela
# VG Virgin Islands (British)
# VI Virgin Islands (US)
# VN Vietnam
# VU Vanuatu
# WF Wallis & Futuna Islands
# WS Samoa
# YE Yemen
# YU Yugoslavia
# ZA South Africa
# ZM Zambia
# ZR Zaire
# ZW Zimbabwe
|}

===by country name order===

{|
|''' Aa—Ear || Eas— Ecu || Les—Lib || San—Sau'''
|- valign="top"
|
# Afghanistan AF
# Albania AL
# Algeria DZ
# American Samoa AS
# Andorra AD
# Angola AO
# Anguilla AI
# Antarctica AQ
# Antigua and Barbuda AG
# Argentina AR
# Armenia AM
# Aruba AW
# Australia AU
# Austria AT
# Azerbaidjan AZ
# Bahamas BS
# Bahrain BH
# Bangladesh BD
# Barbados BB
# Belarus BY
# Belgium BE
# Belize BZ
# Benin BJ
# Bermuda BM
# Bolivia BO
# Bosnia-Herzegovina BA
# Botswana BW
# Bouvet Island BV
# Brazil BR
# British Indian O. Terr. IO
# Brunei Darussalam BN
# Bulgaria BG
# Burkina Faso BF
# Burundi BI
# Buthan BT
# Cambodia KH
# Cameroon CM
# Canada CA
# Cayman Islands KY
# Central African Rep. CF
# Chad TD
# Chile CL
# China CN
# Christmas Island CV
# Cocos (Keeling) Is CC
# Colombia CO
# Comoros KM
# Congo CG
# Cook Islands CK
# Costa Rica CR
# Croatia HR
# Cuba CU
# Cyprus CY
# Czech Republic CZ
# Czechoslovakia CS
# Denmark DK
# Djibouti DJ
# Dominica DM
# Dominican Republic DO
# East Timor TL
|
# Ecuador EC
# Egypt EG
# El Salvador SV
# Equatorial Guinea GQ
# Estonia EE
# Ethiopia ET
# Falkland Isl.(Malvinas) FK
# Faroe Islands FO
# Fiji FJ
# Finland FI
# France FR
# French Southern Terr. TF
# Gabon GA
# Gambia GM
# Georgia GE
# Germany DE
# Ghana GH
# Gibraltar GI
# Great Britain GB
# Greece GR
# Greenland GL
# Grenada GD
# Guadeloupe (Fr.) GP
# Guam (US) GU
# Guatemala GT
# Guinea GN
# Guinea Bissau GW
# Guyana GY
# Guyana (Fr.) GF
# Haiti HT
# Heard & McDonald Isl. HM
# Honduras HN
# Hong Kong HK
# Hungary HU
# Iceland IS
# India IN
# Indonesia ID
# Iran IR
# Iraq IQ
# Ireland IE
# Israel IL
# Italy IT
# Ivory Coast CI
# Jamaica JM
# Japan JP
# Jordan JO
# Kazachstan KZ
# Kenya KE
# Kirgistan Ex-USSR KG
# Kiribati KI
# Korea (North) KP
# Korea (South) KR
# Kuwait KW
# Laos LA
# Latvia LV
# Lebanon LB
# Lesotho LS
|
# Liberia LR
# Libya LY
# Liechtenstein LI
# Lithuania LT
# Luxembourg LU
# Madagascar MG
# Malawi MW
# Malaysia MY
# Maldives MV
# Mali ML
# Malta MT
# Marshall Islands MH
# Martinique (Fr.) MO
# Mauritania MR
# Mauritius MU
# Mexico MX
# Micronesia FM
# Moldavia Ex-USSR MD
# Monaco MC
# Mongolia MN
# Montserrat MS
# Morocco MA
# Mozambique MZ
# Myanmar MM
# Namibia NA
# Nauru NR
# Nepal NP
# Netherland Antilles AN
# Netherlands NL
# Neutral Zone NT
# New Caledonia (Fr.) NC
# New Zealand NZ
# Nicaragua NI
# Niger NE
# Nigeria NG
# Niue NU
# Norfolk Island NF
# Norway NO
# Oman OM
# Pakistan PK
# Palau PW
# Panama PA
# Papua New Guinea PG
# Paraguay PY
# Peru PE
# Philippines PH
# Pitcairn PN
# Poland PL
# Polynesia (Fr.) PF
# Portugal PT
# Puerto Rico (US) PR
# Qatar QA
# Reunion (Fr.) RE
# Romania RO
# Russian Federation Ex-USSR RU
# Rwanda RW
# Saint Lucia LC
# Samoa WS
# San Marino SM
|
# Saudi Arabia SA
# Senegal SN
# Seychelles SC
# Sierra Leone SL
# Singapore SG
# Slovak Republic SK
# Slovenia SI
# Solomon Islands SB
# Somalia SO
# South Africa ZA
# Soviet Union SU
# Spain ES
# Sri Lanka LK
# St. Helena SH
# St. Pierre & Miquelon PM
# St. Tome and Principe ST
# St.Kitts Nevis Anguilla KN
# St.Vincent & Grenadines VC
# Sudan SD
# Suriname SR
# Svalbard & Jan Mayen Is SJ
# Swaziland SZ
# Sweden SE
# Switzerland CH
# Syria SY
# Tadjikistan Ex-USSR TJ
# Taiwan TW
# Tanzania TZ
# Thailand TH
# Togo TG
# Tokelau TK
# Tonga TO
# Trinidad & Tobago TT
# Tunisia TN
# Turkey TR
# Turkmenistan Ex-USSR TM
# Turks & Caicos Islands TC
# Tuvalu TV
# Uganda UG
# Ukraine UA
# United Arab Emirates AE
# United Kingdom UK
# United States US
# Uruguay UY
# US Minor outlying Isl. UM
# Uzbekistan Ex-USSR UZ
# Vanuatu VU
# Vatican City State VA
# Venezuela VE
# Vietnam VN
# Virgin Islands (British) VG
# Virgin Islands (US) VI
# Wallis & Futuna Islands WF
# Western Sahara EH
# Yemen YE
# Yugoslavia YU
# Zaire ZR
# Zambia ZM
# Zimbabwe ZW
|}


==Notes==
==Categories==
[[Category:Config Tag|Category-region]]
{{ORP-bot|Category-region}}<div>{{FUN-bot|Category-region}}

File:Content Manager of TS2009-SP3 Filters-2 = (setting Local+Routes).JPG

2013-12-10T05:17:33Z

Fabartus: TS2009 SP3 routes list of a fresh install after upgrade to SP3 (build 41844) -- the last tech plateau before TADdaemon. {{PD-User}} {{Fabartus-image}} {{FUN-image}}

[[TS2009 SP3]] routes list of a fresh install after upgrade to SP3 (build 41844) -- the last tech plateau before TADdaemon.

{{PD-User}}

{{Fabartus-image}}

{{FUN-image}}

File:Content Manager of TS2009-SP3 (after build 40040 (SP2) to 41844 (SP3)-2 (cropped+resized).JPG

2013-12-10T04:44:54Z

Fabartus: +cat

cropped and resized version of: [[:file:Content Manager of TS2009-SP3 (after build 40040 (SP2) to 41844 (SP3).JPG]]
* Trainz 2009 after upgrade to Service Pack 3; all releases after this list the Trainz-build version in the Windows Title Bar where this image shows "ContentManager 2.0" like earlier TS2009 versions. Service Pack 4 showed "ContentManager 3.3" in the same spot, TS2010 started with "ContentManager 3.2", and TS2012 "ContentManager 3.6" or 3.7 for SP1.
* Image shows two levels of menu dropdowns in Alt-V mode.
[[file:Content Manager of TS2009-SP3 (after build 40040 (SP2) to 41844 (SP3).JPG|thumb|Source file = Content Manager of TS2009-SP3 (after build 40040 (SP2) to 41844 (SP3).JPG]]
{{PD-User}}
{{Fabartus-image}}
{{FUN-image}}

Template:Fabartus-image

2013-12-10T04:42:51Z

Fabartus: genesis

<includeonly>[[Category:Images uploaded by Fabartus|{{{1|{{PAGENAME}}}}}]]
</includeonly><noinclude>[[Category:Images uploaded by Fabartus|${{PAGENAME}} ]]
;purpose
This template is used to auto-categorize images uploaded by [[User:Fabartus]] while fixing up the wiki.

[[Category: Username indexed templates]]
</noinclude>

File:Content Manager of TS2009-SP3 (after build 40040 (SP2) to 41844 (SP3).JPG

2013-12-10T04:36:38Z

Fabartus: Parent version of: :File:Content Manager of TS2009-SP3 (after build 40040 (SP2) to 41844 (SP3)-2 (cropped+resized).JPG * Trainz 2009 after upgrade to Service Pack 3; all releases after this list the Trainz-build version in the Windows Title Bar whe...

Parent version of: [[:File:Content Manager of TS2009-SP3 (after build 40040 (SP2) to 41844 (SP3)-2 (cropped+resized).JPG]]
* Trainz 2009 after upgrade to Service Pack 3; all releases after this list the Trainz-build version in the Windows Title Bar where this image shows "ContentManager 2.0" like earlier TS2009 versions.
* TS2009 + Service Pack 4 showed "ContentManager 3.3" in the same spot, TS2010 started with "ContentManager 3.2", and TS2012 "ContentManager 3.6" or 3.7 for SP1.
* Image shows two levels of menu dropdowns in Alt-V mode.

{{PD-User}}
{{Fabartus-image}}

File:Content Manager of TS2009-SP3 (after build 40040 (SP2) to 41844 (SP3)-2 (cropped+resized).JPG

2013-12-10T04:26:14Z

Fabartus: cropped and resized version of: file:Content Manager of TS2009-SP3 (after build 40040 (SP2) to 41844 (SP3).JPG * Trainz 2009 after upgrade to Service Pack 3; all releases after this list the Trainz-build version in the Windows Title Bar where this ...

cropped and resized version of: [[file:Content Manager of TS2009-SP3 (after build 40040 (SP2) to 41844 (SP3).JPG]]
* Trainz 2009 after upgrade to Service Pack 3; all releases after this list the Trainz-build version in the Windows Title Bar where this image shows "ContentManager 2.0" like earlier TS2009 versions. Service Pack 4 showed "ContentManager 3.3" in the same spot, TS2010 started with "ContentManager 3.2", and TS2012 "ContentManager 3.6" or 3.7 for SP1.
* Image shows two levels of menu dropdowns in Alt-V mode.

{{PD-User}}
{{Fabartus-image}}

Template:FUN-beg

2013-12-04T17:18:37Z

Fabartus: Undo revision 5762 by Windwalkr (talk) FUN is for FUNDAMENTALS pages you haven't bothered writing in four years

<div style="font family: sans-serif,arial,verdana,Garamond,Times,Serif,Arial; font-size:11pt;">
<table style="width:100%; border:2px solid grey; align:left; background:#DDDDDD; text-align:left; padding:0px; margin:0; font-size:18pt; font-face: arial,sans-serif,Garamond,Times,Serif,Arial;">
<tr>
<td style="align:left; margin-right:5px; valign:center;">[[File:Wikilogo.png|50x50px|right|alt=N3V logo|]]</td>
<td style="text-align:center; width:83%; padding:0; margin:0; white-space: nowrap; align:center;" >'''Fundamentals for Trainz Trainees'''</td>
<td style="align:right; margin-left:5px; valign:center; width:65px;"></td>
</tr></table><noinclude>
<div style="width:100%; font-face:Verdana,Garamond,Times,Serif,Arial; font-size:12pt;">
;This is the base (edit in one place) Trainz Fundamentals pages header template

;Purpose
:This template is used by {{Tl|FUN-top}} with {{Tl|FUN-bot}} to set off Trainz Beginner oriented and organized TrainzOnline Wiki pages from ''[[:category:Trainz reference pages]]'' (Trainz basics and beginer classed reference topics) on the N3V TrainzOnline Wiki.

* It will not auto-categorize the page to the [[:category:Trainz fundamentals pages]], you must use {{Tl|FUN-bot}} to do that.

* It can be given the <code><nowiki>{{{1}}}</nowiki></code> default parameter to suppress the automatic assertion of {{tl|TOCright}} moving the Table of Contents to the left margin.
 
[[category:mbox templates|{{PAGENAME}}]]
{{FormTemp}}
[[Category:Self-documenting templates|{{PAGENAME}}]]
[[Category:Trainz fundamentals pages|*{{PAGENAME}}]]
</noinclude>

User talk:Mikey186

2013-11-29T23:32:11Z

Fabartus: welcome

{{welcome}}// [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:32, 30 November 2013 (EST)

HowTo/Export from Blender

2013-11-23T00:55:42Z

Fabartus: refactor, tweak

{{FUN-beg}}
== Introduction of Blender ==

{{plain link|http://www.blender.org |Blender}} is an open source free {{Wp|3D graphics|3D modelling}} application or tool supported by the contribution of programming and development time by the user community. For more information on Blender and its capabilities, please visit the {{plain link|http://www.blender.org |Blender website}}. Blender evolves rapidly and it is not uncommon to see releases about every two months. As of November 03, 2013, the current version is 2.69.

Blender is extendable through the use of "add-ons" produced either by the Blender Foundation or by Blender users. One of those add-ons is the Trainz Blender exporter that was built and is maintained by USCHI0815 (Torsten). Torsten usually announces updates to the Exporter through the Trainz Content Creation Support forum. The current version of the Blender exporter is V0.95.
{{TOCright}}
===Caveat===
[http://www.blender.org Blender] is not currently supported by N3V as a modeling source for Trainz, however third-party tools exist for this purpose.

=== About This Tutorial ===

The scope of this tutorial has been extended to include installation of Blender and installation of the Blender Exporter since this has been an issue discussed several times in the N3V Content Creation forum.

=== Requirements ===

To export to Trainz you need the following:

:* Trainz (TS09 or later preferred)
:* [[Downloads|TrainzMeshImporter.exe]]. This is provided by N3V.
:* Blender V2.57 or later.
:* [https://bitbucket.org/uschi0815/blender-exporter-for-trainz/downloads/ The Blender Exporter].
:* Windows XP, Vista, Windows 7 (32 or 64 bit) or Windows 8 (32 or 64 bit) or Mac OS X (32 or 64 bits).

=== Blender Installation Notes ===

Blender is available for a number of operating systems including Windows XP, Windows Vista and Windows 7. Both 32 bit and 64 bit versions are available.
You can choose either the installer version or a zip archive. Please read any notes on the Blender.org download page: particularly if you are upgrading from a previous version.

=== Installer Version ===

The Installer Version is the easiest way to install Blender but there can be complications. If you install Blender into the default directory you should choose "Use Application Data Directory" during installation of Blender. Otherwise it might not be possible to save your preferred Exporter options due to insufficient permissions.

=== Blender Zip Archive Version ===

The zip archive version allows you to unzip the entire Blender folder structure and locate it in any location that suits you. The only drawback is that you will need to set up your own links to the Blender executable (Blender.exe).

== Installing the Exporter ==

The Blender exporter add-on must be installed in the "scripts\addons" area of the Blender data space. The following process will install it in the correct location.

=== Install Blender Exporter for Trainz ===

:* Download the exporter.
:* Start Blender.
:* Open a new project(File -> New).
:* Open User Preferences(File -> User Preferences...).
:* Select Add-Ons panel and press button "Install from file..." down at the panel button bar.
:* Select and install downloaded file: you don't need to extract it.
:* Enable "TRAINZ Exporter" in Add-On list and press button "Save As Default" to keep it enabled for all subsequent Blender starts.

=== Install the N3V TrainzMeshImporter ===

:* Download the [http://online.ts2009.com/mediaWiki/index.php5/Downloads TrainzMeshImporter.exe]. The file is in the RAR format that can be extracted by most zip file management programs.
:* Before using the exporter you must copy the TrainzMeshExporter.exe to the same location as the Blender Exporter add-on. The following will help find that location:

:* Start Blender and leave the default cube mesh in place.
:* If necessary, open the console window so you can read the error messages. In versions 2.5 through 2.63a, the console window is opened using the "toggle system console" menu entry in the "help" menu in the Blender menu bar. Beginning with version 2.64, the "toggle system console" menu has been moved to the "window" menu in the Blender menu bar. Those running a Blender version 2.49 or earlier can disregard this step, as the system console is in a window that is open whenever Blender is active.
:* Go to File->Export and select "Trainz Mesh and Animation". Use the default settings but make sure that the save location is a temporary or working space.
:* The Exporter will complain about a missing file in a specific folder. The missing file is TrainzMeshImporter and the folder name is the location you need.
:* The location is usually in the form of "ERROR" file "C:Users\your name\AppData\Roaming\Blender Foundation\Blender\2.59\scripts\addons\TrainzMeshExporter.exe" not found". This example is typical of using the default Blender Installer. If you chose to install Blender using the zip archive then the location will be different.
:* Copy TrainzMeshExporter.exe to the location provided. If you cannot access the AppData folder see the [http://online.ts2009.com/mediaWiki/index.php5?title=HowTo/Export_from_Blender&action=submit#Additional_Notes Additional Notes] section for help.
:* Once you have copied TrainzMeshExporter.exe to the correct location retry the export.

== Exporting an Asset ==

The creation of an asset suitable for Trainz is a long and complex process. For the purposes of this tutorial we will only export the standard Blender cube. Some knowledge of Blender and creation of assets for Trainz purposes is assumed.

:* Start Blender and save the default cube as "cube.blend" in your preferred working location.
:* Create a simple material such as "cube.m.onetex" and allocate a simple colour texture file. For the purpose of this tutorial leave the default mapping technique to "generated". This will cause an error.
:* UV map the cube to the texture.
:* Save the Blender file.
:* Go to File->Export and select Trainz Mesh and Animation.
:* The dialog box that appears gives a output save location for the XML, log, texture description and other files produced by the process. Select your preferred location.
:* All the other options can be left as default. If you were exporting a mesh that included animation, then you would also select "Export Animation Data".
:* When you are ready, select "Export Trainz" in the top right hand corner.
:* This export process will fail with an error since the "generated" mapping option for textures is not supported when using an image file. Go back to the Texture section and change the mapping option to UV and then export again. This time it should export correctly.

== Exporter Output ==

=== Files Created ===
The Exporter produces:

:* An XML file. This is used by TrainzMeshImporter.
:* The IM mesh file required by Trainz.
:* The texture description files (nnn.texture.txt) required by Trainz.
:* The KIN animation file required by Trainz if animation is used.
:* A log of the export process.

=== Error Reporting ===
Errors are reported in the Blender System Console and the Exporter log. Errors will prevent the production of the target IM file and therefore must be addressed.
Typical errors are:

==== Mesh Errors ====

:*Objects without a parent where a root bone exists.

==== Material Related Errors ====

:* No UV layer for UV mapped objects. Blender usually creates a default.
:* Use of the same material for both single and double sided meshes. Recommend only using single sided meshes.
:* Objects without an assigned material. Recommend assigning a material for each object.
:* Faces without a material in an object. The faces will have been collected into a Vertex Group to enable correction. This error can also be caused by material slots in blender to which no material is assigned.
:* Use of similar material names if character case is ignored. i.e. "Black" and "black" are considered the same by Trainz.
:* Not using UV mapping for textures that are either using alpha, normal or specular.
:* Not using UV or reflect mapping for diffuse textures.

==== Animation Errors ====

:* More than one root bone

=== Warnings ===
Warnings are basically flaws or possible flaws that the user may wish to address. Warnings do not prevent production of the IM output files. Some typicals warnings include:

==== Animation Warnings ====

:* Possible incorrect location and rotation of root bone.
:* Bones not found or no animation data found.
:* Events not found or unrecognised.
:* Event frame numbers in wrong positions.

==== Mesh Warnings ====

:* Vertices influenced by more than four vertex groups.

==== Name Warnings ====

:* Unrecommended characters. Material, texture, object and path names should only be composed of a-z, A-Z, 0-9 or -_./\ characters. A typical error is use of a space character in a path name. The Exporter will change Blender file names that include upper case letters to lower case letters. Generally, it is recommended you avoid the use of upper case characters in names.

==== Material Warnings ====

:* Surfaceless faces in an object. The Exporter will gather these faces and put them into a Vertex Group to aid identification. The Vertex Group can be found in the triangle panel associated with the Safety Valve object.
:* Objects exported with double sided faces. This will become an error if a material is used for both single and double sided objects.
:* Material renamed. If the name does not match one of the standard Trainz material names then the Exporter will try and effect a solution. Typically a name such as "black" will be renamed "blackm.onetex".

=== The Export Log ===

The Exporter Log contains a record of events during the export process including errors and warnings. The numTriangles report is the number of polygons (aka polys) in the mesh.

== Material Recognition by the Exporter ==

The Exporter tries to identify materials in use by the asset mesh and will provide a warning if the detected material decoration varies from that declared in the Blender file. The term "material decoration" is one of the standard Trainz material names such as "m.onetext" or "m.tbumptex". The following decision process, provided by Torsten, may be useful for developers.

The decision which material decoration is used is made by the texturing schema used for the material:

: no texture used -> '''m.onetex'''

: one texture used:
:: invalid texture -> '''m.onetex'''
:: diffuse texture -> '''m.onetex'''
:: reflection texture -> '''m.reflect'''

: two textures used:
:: diffuse & alpha -> '''m.onetex'''
:: diffuse & reflection -> '''m.reflect'''

: three textures used:
:: diffuse & alpha & reflection ->''' m.gloss'''

: normal texture used:
:: normal & diffuse & alpha & no reflection -> '''m.tbumptex'''
:: normal & diffuse & reflection & no alpha -> '''m.tbumpgloss'''
:: normal & diffuse & no alpha & no reflection-> '''m.tbumpenv'''

As material '''m.notex''' causes problems with specific assets''', m.onetex''' is used instead. It also works perfectly without any texture.
The problem with '''m.tbumptex''' and '''m.tbumpenv''' is that, besides the usage of an alpha texture (which is not used for '''m.tbumpenv'''), both use a diffuse and normal texture. In this case '''m.tbumpenv''' is chosen.

Generally, you can use any material decoration you want. The script does not change a syntactically correct material decoration(e.g. Material'''m.billboard''' would pass unchanged). It only drops a message to remind you that you either use an unsupported material(as warning) or that it had chosen another material(as info).

If you check the issue and find it to be OK than you can safely ignore those messages.

Blenders texture influences are nearly equivalent to MAX material maps. Because diffuse textures and reflection textures both influence diffuse color, the decision between them is made by checking texture mapping coordinates to:

: '''MAX map -> Blender texture influence'''
: Ambient Color -> Shading Ambient
: Diffuse Color -> Diffuse Color & UV mapping
: Specular Color -> Specular Color
: Specular Level -> Specular Intensity
: Glossiness -> Specular Hardness
: Self-Illumination -> Shading Emit
: Opacity -> Diffuse Alpha
: Filter Color -> Diffuse Translucency
: Bump -> Geometry Normal
: Reflection -> Diffuse Color & Reflection mapping
: Refraction -> not available(not found?)
: Displacement -> Geometry Displacement

== Torsten's Hints ==

''These hints are reproduced from the Exporter script since many will not want to edit or view the actual script contents.''

In Trainz models you can have two kinds of special objects: attachment points and bones. For attachment points, the exporter expects objects of type "Empty". For bones, objects of type "Lattice" and "Armature" will be accepted. All of them need to be named according the naming conventions in effect for attachements( a.* ) and bones( b.r.* ). Objects of other type and objects with proper type but names not matching this conventions will be ignored as attachment points or bones.

If you want to export animations with events, than you have to create a Blender TX object and enter the lines as you would do to create an event file. By renaming this object to "events" you ensure the exporter will not ignore your event list.

It is possible to make parent-child-relations between meshes to simplify the design process. However, the chain must be end with a valid parent bone.

==Additional Notes ==

=== Blender Data Files ===

Blender keeps certain data files, such as add-on utilities, in a special location. This has given Trainz content creators some difficulties due to access rights. If you used the Blender Installer then this is usually in the Windows logged on user space.

Say, for example, your user name is Patrick, then the location is likely to be similiar to "C:\Users\Patrick\AppData\Roaming\Blender Foundation\Blender\2.59\scripts\addons".

If you cannot see this folder in the user folder then it is likely the folder has been hidden by Windows. You can unhide folders in the Windows Explorer by going to Tools->Folder Options->View and selecting "Show hidden files, folders and drives".

== Under The Hood or, How the Exporter Works ==

Basically the Blender export process works in three phases:

:* Phase 1 is the checking process where the Exporter does some validation. Where it can, the Exporter will make minor corrections and just issue a warning. Warnings do not stop the process but an error will. The warnings and errors should provide enough information to enable correction.
:* Phase 2 is the creation of the XML file required by the TrainzMeshImporter. The XML file is a text file using a common language used by many applications. It is also N3V's preferred import format.
:* On succession completion of the first two phases, the Exporter passes control to the TrainzMeshImport program which takes the XML file plus other information and produces the IM mesh file used by Trainz.

== Acknowledgements ==

Many thanks to USCHI0815 (Torsten) for his time and effort that went into producing and supporting the Blender Exporter. Without it there would be no Blender models in Trainz.

Thanks to Mick_Berg and Jananton for their comments, and to Mick_Berg for his [http://www.mickberg.com/blenderexport1.html Blender installation tutorial].

== Tutorial Updates ==
Please feel free to update as necessary and correct errors in this tutorial. It is a WiKi contribution and intended to be maintained this way.

== References ==
[[Material Types]]

[[Category:Blender]]
[[Category:How-to guides]]
{{FUN-bot}}

"Category-region" tag

2013-11-22T17:39:22Z

Fabartus: /* Tables of codes */ tweak font size, better wrapping

{{FUN-beg}}{{ORP-top}}
==About Category-region codes==
'''Category-region codes''' are a single ("UK") or multiple codes ("AU;DE;UK;US") in a quoted string that is included in the config.txt file for user defined filters.
* Assets with narrow single country scope would contain a single code after the tagname.
* Assets which were widely found in many regions (e.g. ''''Caterpillar D7 bulldozer'''', will list the series of country codes of the region.)
** The codes have only a minor importance in TRAINZ and are primarily used in Trainz as a sort and selection criteria in user defined filters.
* For content that exists in multiple areas, when creating new assets, select appropriate codes in [[Content Creator Plus]] (CCP).
** For example, a locomotive that was available in the United States and Canada would be specified as follows:

category-region "US;CA"

==Tables of codes==
<big>'''The category-region codes below are in alphabetical order by sort criteria.

Legal codes that are recognized by Trainz are as follows:'''</big>

===by region code order===

{|
|-
! AD-EE || EG-LI || LK-SC || SD-ZZ
|-valign="top"
|
# AD Andorra
# AE United Arab Emirates
# AF Afghanistan
# AG Antigua and Barbuda
# AI Anguilla
# AL Albania
# AM Armenia
# AN Netherland Antilles
# AO Angola
# AQ Antarctica
# AR Argentina
# AS American Samoa
# AT Austria
# AU Australia
# AW Aruba
# AZ Azerbaidjan
# BA Bosnia-Herzegovina
# BB Barbados
# BD Bangladesh
# BE Belgium
# BF Burkina Faso
# BG Bulgaria
# BH Bahrain
# BI Burundi
# BJ Benin
# BM Bermuda
# BN Brunei Darussalam
# BO Bolivia
# BR Brazil
# BS Bahamas
# BT Buthan
# BV Bouvet Island
# BW Botswana
# BY Belarus
# BZ Belize
# CA Canada
# CC Cocos (Keeling) Isl.
# CF Central African Rep.
# CG Congo
# CH Switzerland
# CI Ivory Coast
# CK Cook Islands
# CL Chile
# CM Cameroon
# CN China
# CO Colombia
# CR Costa Rica
# CS Czechoslovakia
# CU Cuba
# CV Christmas Island
# CY Cyprus
# CZ Czech Republic
# DE Germany
# DJ Djibouti
# DK Denmark
# DM Dominica
# DO Dominican Republic
# DZ Algeria
# EC Ecuador
# EE Estonia
|
# EG Egypt
# EH Western Sahara
# ES Spain
# ET Ethiopia
# FI Finland
# FJ Fiji
# FK Falkland Isl.(Malvinas)
# FM Micronesia
# FO Faroe Islands
# FR France
# GA Gabon
# GB Great Britain
# GD Grenada
# GE Georgia
# GH Ghana
# GI Gibraltar
# GL Greenland
# GP Guadeloupe (Fr.)
# GQ Equatorial Guinea
# GF Guyana (Fr.)
# GM Gambia
# GN Guinea
# GR Greece
# GT Guatemala
# GU Guam (US)
# GW Guinea Bissau
# GY Guyana
# HK Hong Kong
# HM Heard & McDonald Isl.
# HN Honduras
# HR Croatia
# HT Haiti
# HU Hungary
# ID Indonesia
# IE Ireland
# IL Israel
# IN India
# IO British Indian O. Terr.
# IQ Iraq
# IR Iran
# IS Iceland
# IT Italy
# JM Jamaica
# JO Jordan
# JP Japan
# KE Kenya
# KG Kirgistan Ex-USSR
# KH Cambodia
# KI Kiribati
# KM Comoros
# KN St.Kitts Nevis Anguilla
# KP Korea (North)
# KR Korea (South)
# KW Kuwait
# KY Cayman Islands
# KZ Kazachstan
# LA Laos
# LB Lebanon
# LC Saint Lucia
# LI Liechtenstein
|
# LK Sri Lanka
# LR Liberia
# LS Lesotho
# LT Lithuania
# LU Luxembourg
# LV Latvia
# LY Libya
# MA Morocco
# MC Monaco
# MD Moldavia Ex-USSR
# MG Madagascar
# MH Marshall Islands
# ML Mali
# MM Myanmar
# MN Mongolia
# MO Martinique (Fr.)
# MR Mauritania
# MS Montserrat
# MT Malta
# MU Mauritius
# MV Maldives
# MW Malawi
# MX Mexico
# MY Malaysia
# MZ Mozambique
# NA Namibia
# NC New Caledonia (Fr.)
# NE Niger
# NF Norfolk Island
# NG Nigeria
# NI Nicaragua
# NL Netherlands
# NO Norway
# NP Nepal
# NR Nauru
# NT Neutral Zone
# NU Niue
# NZ New Zealand
# OM Oman
# PA Panama
# PE Peru
# PF Polynesia (Fr.)
# PG Papua New Guinea
# PH Philippines
# PK Pakistan
# PL Poland
# PM St. Pierre & Miquelon
# PN Pitcairn
# PT Portugal
# PR Puerto Rico (US)
# PW Palau
# PY Paraguay
# QA Qatar
# RE Reunion (Fr.)
# RO Romania
# RU Russian Federation Ex-USSR
# RW Rwanda
# SA Saudi Arabia
# SB Solomon Islands
# SC Seychelles
|
# SD Sudan
# SE Sweden
# SG Singapore
# SH St. Helena
# SI Slovenia
# SJ Svalbard & Jan Mayen Is
# SK Slovak Republic
# SL Sierra Leone
# SM San Marino
# SN Senegal
# SO Somalia
# SR Suriname
# ST St. Tome and Principe
# SU Soviet Union
# SV El Salvador
# SY Syria
# SZ Swaziland
# TC Turks & Caicos Islands
# TD Chad
# TF French Southern Terr.
# TG Togo
# TH Thailand
# TJ Tadjikistan Ex-USSR
# TK Tokelau
# TL East Timor
# TM Turkmenistan Ex-USSR
# TN Tunisia
# TO Tonga
# TR Turkey
# TT Trinidad & Tobago
# TV Tuvalu
# TW Taiwan
# TZ Tanzania
# UA Ukraine
# UG Uganda
# UK United Kingdom
# UM US Minor outlying Isl.
# US United States
# UY Uruguay
# UZ Uzbekistan Ex-USSR
# VA Vatican City State
# VC St.Vincent & Grenadines
# VE Venezuela
# VG Virgin Islands (British)
# VI Virgin Islands (US)
# VN Vietnam
# VU Vanuatu
# WF Wallis & Futuna Islands
# WS Samoa
# YE Yemen
# YU Yugoslavia
# ZA South Africa
# ZM Zambia
# ZR Zaire
# ZW Zimbabwe
|}

===by country name order===

{|
|''' Aa—Ear || Eas— Ecu || Les—Lib || San—Sau'''
|- valign="top"
|
# Afghanistan AF
# Albania AL
# Algeria DZ
# American Samoa AS
# Andorra AD
# Angola AO
# Anguilla AI
# Antarctica AQ
# Antigua and Barbuda AG
# Argentina AR
# Armenia AM
# Aruba AW
# Australia AU
# Austria AT
# Azerbaidjan AZ
# Bahamas BS
# Bahrain BH
# Bangladesh BD
# Barbados BB
# Belarus BY
# Belgium BE
# Belize BZ
# Benin BJ
# Bermuda BM
# Bolivia BO
# Bosnia-Herzegovina BA
# Botswana BW
# Bouvet Island BV
# Brazil BR
# British Indian O. Terr. IO
# Brunei Darussalam BN
# Bulgaria BG
# Burkina Faso BF
# Burundi BI
# Buthan BT
# Cambodia KH
# Cameroon CM
# Canada CA
# Cayman Islands KY
# Central African Rep. CF
# Chad TD
# Chile CL
# China CN
# Christmas Island CV
# Cocos (Keeling) Is CC
# Colombia CO
# Comoros KM
# Congo CG
# Cook Islands CK
# Costa Rica CR
# Croatia HR
# Cuba CU
# Cyprus CY
# Czech Republic CZ
# Czechoslovakia CS
# Denmark DK
# Djibouti DJ
# Dominica DM
# Dominican Republic DO
# East Timor TL
|
# Ecuador EC
# Egypt EG
# El Salvador SV
# Equatorial Guinea GQ
# Estonia EE
# Ethiopia ET
# Falkland Isl.(Malvinas) FK
# Faroe Islands FO
# Fiji FJ
# Finland FI
# France FR
# French Southern Terr. TF
# Gabon GA
# Gambia GM
# Georgia GE
# Germany DE
# Ghana GH
# Gibraltar GI
# Great Britain GB
# Greece GR
# Greenland GL
# Grenada GD
# Guadeloupe (Fr.) GP
# Guam (US) GU
# Guatemala GT
# Guinea GN
# Guinea Bissau GW
# Guyana GY
# Guyana (Fr.) GF
# Haiti HT
# Heard & McDonald Isl. HM
# Honduras HN
# Hong Kong HK
# Hungary HU
# Iceland IS
# India IN
# Indonesia ID
# Iran IR
# Iraq IQ
# Ireland IE
# Israel IL
# Italy IT
# Ivory Coast CI
# Jamaica JM
# Japan JP
# Jordan JO
# Kazachstan KZ
# Kenya KE
# Kirgistan Ex-USSR KG
# Kiribati KI
# Korea (North) KP
# Korea (South) KR
# Kuwait KW
# Laos LA
# Latvia LV
# Lebanon LB
# Lesotho LS
|
# Liberia LR
# Libya LY
# Liechtenstein LI
# Lithuania LT
# Luxembourg LU
# Madagascar MG
# Malawi MW
# Malaysia MY
# Maldives MV
# Mali ML
# Malta MT
# Marshall Islands MH
# Martinique (Fr.) MO
# Mauritania MR
# Mauritius MU
# Mexico MX
# Micronesia FM
# Moldavia Ex-USSR MD
# Monaco MC
# Mongolia MN
# Montserrat MS
# Morocco MA
# Mozambique MZ
# Myanmar MM
# Namibia NA
# Nauru NR
# Nepal NP
# Netherland Antilles AN
# Netherlands NL
# Neutral Zone NT
# New Caledonia (Fr.) NC
# New Zealand NZ
# Nicaragua NI
# Niger NE
# Nigeria NG
# Niue NU
# Norfolk Island NF
# Norway NO
# Oman OM
# Pakistan PK
# Palau PW
# Panama PA
# Papua New Guinea PG
# Paraguay PY
# Peru PE
# Philippines PH
# Pitcairn PN
# Poland PL
# Polynesia (Fr.) PF
# Portugal PT
# Puerto Rico (US) PR
# Qatar QA
# Reunion (Fr.) RE
# Romania RO
# Russian Federation Ex-USSR RU
# Rwanda RW
# Saint Lucia LC
# Samoa WS
# San Marino SM
|
# Saudi Arabia SA
# Senegal SN
# Seychelles SC
# Sierra Leone SL
# Singapore SG
# Slovak Republic SK
# Slovenia SI
# Solomon Islands SB
# Somalia SO
# South Africa ZA
# Soviet Union SU
# Spain ES
# Sri Lanka LK
# St. Helena SH
# St. Pierre & Miquelon PM
# St. Tome and Principe ST
# St.Kitts Nevis Anguilla KN
# St.Vincent & Grenadines VC
# Sudan SD
# Suriname SR
# Svalbard & Jan Mayen Is SJ
# Swaziland SZ
# Sweden SE
# Switzerland CH
# Syria SY
# Tadjikistan Ex-USSR TJ
# Taiwan TW
# Tanzania TZ
# Thailand TH
# Togo TG
# Tokelau TK
# Tonga TO
# Trinidad & Tobago TT
# Tunisia TN
# Turkey TR
# Turkmenistan Ex-USSR TM
# Turks & Caicos Islands TC
# Tuvalu TV
# Uganda UG
# Ukraine UA
# United Arab Emirates AE
# United Kingdom UK
# United States US
# Uruguay UY
# US Minor outlying Isl. UM
# Uzbekistan Ex-USSR UZ
# Vanuatu VU
# Vatican City State VA
# Venezuela VE
# Vietnam VN
# Virgin Islands (British) VG
# Virgin Islands (US) VI
# Wallis & Futuna Islands WF
# Western Sahara EH
# Yemen YE
# Yugoslavia YU
# Zaire ZR
# Zambia ZM
# Zimbabwe ZW
|}


==Notes==
==Categories==
[[Category:Config Tag]]
{{ORP-bot}}<div>{{FUN-bot}}

User talk:Jamesmoody

2013-11-22T01:33:00Z

Fabartus: /* Speak and write English to the audience! */ new section

Please do not leave comments here. I am unlikely to spot them.

If you need to contact me, please send me an email. If you do not have my address, send a forum Private Message.

Note: Do not contact me directly for technical support. Technical support requests should be sent to the Helpdesk.

== See {{wp|Wikipedia:Etiquette}} ==

:: Please note that this isn't wikipedia. We might use the same software, but don't assume that their rules and conventions apply here. [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]]) 12:27, 21 August 2013 (EST)
:: In particular note that we are not "NPOV". Documents on this wiki should reflect N3V Games point of view. [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]]) 12:39, 21 August 2013 (EST)

* Sorry we seem to have a different definition of profanity and the appropriate. S***ty is a rather apt term when things don't work right. For example, I'll address wiki business on the wiki, and expect the same—wiki's are about collaborative efforts, it's fairly plain something you guys have done failed in that respect... things never took off. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
:: No, we don't have a different definition of profanity. You may see it as acceptable to use such words, but we don't. This includes "bleeping" words out; you're obviously aware of the words you're using, so just don't use them. If you feel the need to use such words, go outside and take a break instead of replying. Keep it up and you'll be banned. It's that simple. [[User:Windwalkr|Windwalkr]] ([[User talk:Windwalkr|talk]]) 09:54, 21 August 2013 (EST)
::
:: Also, we used a wiki initially because it was easy for us to edit - I can come back and add a page whenever I have new information to publish. If we get some community assistance, that's great - but it really is a secondary consideration. [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]])

: I think it embarrassing that a wiki started so long ago is in such a P*** Poor state, it wasn't even initialized with Public Domain standard help pages, and even ParserFunctions (which I badly need, I couldn't even begin to write [[Template:N3V-Help-Image]] and [[Template:Help-Image]] a while ago as I can't test conditions, files, parameters, so have a Sh***th temporary placeholder workaround... NOT HAPPY FACE MAKING! {{Tl|Tlx}} is not yet useable, which is pretty much needed for any smart template exposition and help... all that TAKES UP AND WASTES my freely donated TIME... So stop that!). // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
:: We're not trying to be wikipedia. We welcome collaboration, but this is NOT a community-owned site. This is a corporate site, with corporate goals. Where our goals align with your goals, that's great. If your goals work against our goals, then our goals take precedence. That may be a harsh way to put it, but I don't want you to misunderstand the reality of the situation here. [[User:Windwalkr|Windwalkr]] ([[User talk:Windwalkr|talk]]) 09:54, 21 August 2013 (EST)

: Think Chris is or has gotten the picture that I only mean well, and if I wanted to be confrontational, I could really roast the company on the forum, and the Wikibook. I'm only trying to make you all look better, but ''that certainly means changing the status quo''. For starters, if someone comes out with a browser that requires HTML 5, the whole site is non-compliant. There's no Common.css and Common.js files in place. No classes to call, only HTML 4, which have been obsolescent now for what, five or six years?
: Coming in this spring after years of casual browsing to see in detail how little Trainz has progressed, how few changes and how dead this wiki is (Hasn't really progressed much since I first saw it back in late 2009, iirc) has been an eye opener. Not sure what you guys actually do, but I guess you can be proud you don't use coarse language. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
:: Thankfully, all common browsers work fine on our site, so it's not something that we're remotely concerned about at the current time. [[User:Windwalkr|Windwalkr]] ([[User talk:Windwalkr|talk]]) 09:54, 21 August 2013 (EST)

On the other commentary/responses... [[Talk:TADDaemon]], I have to parse what you changed to understand all your answers. Wikiquette when interleaving is to indent in between 'voices' (responses). Numerous people can then address a paragraph's point... or just the two. Taking things out of order to change the original text makes it rather difficult to see the conversational flow. Breaking the context seems to be a bad thought habit in N4V group think. Sign each para/post with four tildes, that adds a date stamp and your sig, which you can customize under preferences. (See mine)
:: You're quite correct, but nobody here really cares. We don't see the wiki as a workable chat tool. The software is not built with that in mind, and while some conventions have developed on other wikis to make it work "as best possible" we have better tools at our disposal and thus have minimal interest in learning the hacks that people have come up with for dealing with communication in a wiki. James has already suggested you use our forums. If you choose to use a backwards chat process such as this rather than the better tools which we have available, then don't complain when it's hard to use. [[User:Windwalkr|Windwalkr]] ([[User talk:Windwalkr|talk]]) 09:54, 21 August 2013 (EST)
::: I have gone back and fixed that chat page (with indenting and tildes). Please note though that what you posted is still purely a personal rant, and is still not welcome on a corporate site. You may wish to edit it... [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]]) 12:27, 21 August 2013 (EST)

I have to reconstruct the original text to make sense of your rebuttal. Again... a time investment for me. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
: ... and a time investment for me to learn a new way of formatting text when writing using a tool for what appears to be /obviously/ the wrong purpose, and also by someone elses fairly arbitrary rules. And when I could have been working on something productive instead.

Regardless, as Chris understands, I'm here to help, and TADDaemon with all it's time wasting is [http://forums.auran.com/trainz/showthread.php?102671-Insight-into-periodic-pauses-in-Surveyor&p=1192261#post1192261 NOT something which is working well or properly] in the real user world. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
: I'm a real world Trainz user too. My first version of Trainz was 1.1.1. I became a betatester for UTC, a content creator for TRS2004, and joined Auran around the time of TC3. I see TADDaemon as an immense improvement over the problems we had previously - particularly from a content creator workflow. As an end user, I /vehemently disagree/ with your apparent viewpoint that TADDaemon is the spawn of satan and should be killed with fire, and that doing so would fix all problems ever. It saves me countless hours waiting for Trainz or CM to start up. I can run multiple CM windows in parallel, and even Trainz at the same time as well, none of which was even remotely practical before TADDaemon. [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]]) 12:27, 21 August 2013 (EST)

I'm like Chris there, what counts is what I see, the trouble for you guys is we have thousands of times the number of eyes, time on the job and places where we're seeing insufficient progress, or worse, a [http://forums.auran.com/trainz/showthread.php?102671-Insight-into-periodic-pauses-in-Surveyor&p=1192261#post1192261 lack of attention or acknowledgement] that there are serious issues. I know of three long time content creators, people with hundreds of DLS assets created between them that won't use [[TS2009 SP3]] and beyond because of all the time TADDaemon wastes reconnecting when it should be connected (assuming it's needed at all), why it's active at all when we're in surveyor is a mystery. Makes no sense. You go with the local data base, no one is upgrading or downloading from in surveyor. [http://commons.wikimedia.org/wiki/File:Collected-Trianz-Releases-2013-0727,about_half_the_EnglishLang_Releases.jpg As you can see], I've got a few Trainz versions to choose from, and TS12 is not one anyone should be happy with as an operator given all it's pauses and time wastes. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
: TADDaemon *is* the local database. It existed in pretty much the same form before we split it into it's own process, and we did that because:
: * A Trainz crash used to reliably require a DB repair afterwards. Trainz would do it during the loading process. Just a black screen, no progress report. User reports at the time often suggested that Trainz needed a reinstall after crashing because it was "broken". I personally experienced this in TRS2006.
: * Multiple processes can use the database at once - e.g. CM and Trainz in parallel, multiple CM windows, etc.
: * It frees up process space for Trainz to use for other things. Just "maintaining the database listings" was starting to be a significant drain on process space for people with large installs.
: * People *can* and *do* download within the game - the content updates menu, when getting DLC packs, and when joining multiplayer sessions, to name the obvious ones.
:
: To address some other points: TADDaemon is continually necessary because it provides asset listings. When you use the tabs in surveyor, or the filter dialog, or in fact /anything that asks for a list of assets/ (which is way more common than you think as asset scripts can do it), TADDaemon is what gives you that list back. And Trainz can use the process space (i.e. RAM) freed up by using TADDaemon for other things. [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]]) 12:27, 21 August 2013 (EST)

So sorry if you're offended by my casual choice in language, but do credit that we are from different societies. That language doesn't raise anyone's eyebrows over here. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
: That kind of language doesn't raise eyebrows in "general society" here either - particularly the more, ummm, bogan parts of society. But it does a lot more than raise eyebrows in some of our critical markets, so we obviously don't want it easily visible in our end user documentation. [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]]) 12:27, 21 August 2013 (EST)

But do get used to having other computer professionals taking a serious look at your work, for as far as I'm concerned if I did my job as you guys have seemed to have done yours, the F-22 Raptor would crash every 99th flight, the Patriot missile would turn around and blast it's launcher or control vans, Laser eye surgery would burn through into peoples' cornea, and the Trident missile wouldn't ever threaten to launch from Ohio class submarines... so you'd likely be forcibly learning Chinese or Russian there down under. Those are only a fraction of the complex things I've been part of in my career, and when something runs worse than the version three releases before, something smells.

BTW, Given the ridiculously annoying wait for Parserfunctions, interwikis and so forth, I'm perfectly happy to wait for a talk response here. If you turn on email notification (since you are a site bureaucrat, that's in your toolkit) you can then see when pages change without using a watchlist tab.

The N3V staff admin seems to have trouble changing a boolean value when given a link to the how-to, don't you know. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
:: You're making the assumption that he's remotely interested in taking advice on configuration from someone outside the company. Again, we work to our goals, not yours. [[User:Windwalkr|Windwalkr]] ([[User talk:Windwalkr|talk]]) 09:54, 21 August 2013 (EST)

Perhaps you can help him appear competent in that little thing. Like much of N3V's visible output, it's leaving a bad taste at the moment. Chris wants me to put up new user pages, in the Help namespace, but I'm not about to start that without further cleanup and having things straight first. I've already tagged too much using {{tl|FAB-todo}}, and for [http://online.ts2009.com/mediaWiki/index.php/Special:WhatLinksHere/Template:FAB-todo every page there], there are three that don't have an overt tag that are dependent upon ParserFunctions.

Best regards // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)

== Small words and big pictures ==

If you can use some small words and big pictures to explain to me why N3V wouldn't want the power of parserfunctions I'd really appreciate it. Having one template do ten things is much preferable than ten doing ten when the same branching and testing logic that allows that, can allow things like having pop-open collapsed elements like the table {{Tl|TBS}}. I'd like to make that and other such table structures where it makes sense so people can expand them or not as it suits them, allowing them to see a big picture in the context. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 14:22, 12 October 2013 (EST)

: It's not that N3V wouldn't want ParserFunctions. It's that someone at N3V wouldn't want to stop what else they are doing long enough to look into it, decide if it's a sensible request, act on it, and test what breaks afterwards. And more to the point, explain what they were doing for the past 'N' hours to their boss, when there's something else more urgent they should have been working on. [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]]) 17:55, 14 October 2013 (EST)

== Please verify conclusion ==

Please verify the tag region is obsolescent as I inferred from config.txt entries whilst fixing errors. I made an appropriate [http://online.ts2009.com/mediaWiki/index.php/Index_of_Tags_%26_Containers#qu-rz annotation here] which should be verified. Thanks // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 12:18, 13 October 2013 (EST)

: The "region" tag is obsolete, and hasn't been used for many years. It's been replaced by "category-region" which has a well-defined format. [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]]) 17:55, 14 October 2013 (EST)

== Speak and write English to the audience! ==

re: [http://online.ts2009.com/mediaWiki/index.php?title=KIND_TrainzBaseSpec&diff=5701&oldid=5682 this edit], YOU may understand what the three or four of you may mean by Classes, but what percent of your users have the first clue? AND BTW... what root? Who understands what you mean by that outside of your cubicle area.

From the standpoint of the customers you guys are most anxious to seduce, land, and hook--the younger crowd who will indubitably be trying to make sense of this unfinished collection of documents (2500+ routes on the DLS are a big big attraction! And that means error fixing, and so you have a big big 250,000 asset problem as even Hilliam knows--and have wasted five years it might have been resolved), to those new customers, and to the old technically challenged... '''the ROOT to them ''in the heat of the moment of frustration at having to figure out what another friggin' error is''... is the fact each asset has a config text file''' which need certain items.

My presentation may not have been the best, but ''" Each of the TrainzBaseSpec file elements can be specified in any asset that has a defining [[Config.txt file]]."'' conveys the relationships far clearer than a school-boy abstraction of Classes. That certain of those elements in the spec are mandatory is enforced by error checking. It's addressed in any case, iirc. Similarly Parent and Child classes just muddle the understanding of the users. In point of fact, the config.txt files for a KIND require those common items to be defined, set the threshold level for warnings and errors and define how the text INI file is processed and considered... without a config file to hold it, all those tag labels in the TrainzBaseSpec have no substance, they are merely conjectural, ideas. Recording them in a config.txt file puts them in context.

KINDs are your true classes, the TrainzBaseSpec is just a collection of common elements defined within each, or sometimes not. The software system uses them to bootstrap the asset, in effect. Since they define all asset types in your software, calling such a disparate changeable set of data definitions a class, means your true classes are meaningless. I have a bit of trouble wrapping my head around such a reversal of cause and effect. Put another way, The trainzBaseSpec is a mix of things which must be defined and others which may optionally be defined (user ID, description, licenses, email, etc.) to make a KIND--which provides the commonality one can then classify as a class.

Things in the TrainzBaseSpec can be defined in any asset, or you guys really need to drop programming and work on the documentation before moving forward with anything. Perhaps you misread or interpreted the quoted string. If you guys understood that (and begin acting like) you are in a collaborative enterprise with thousands of interactive colleagues and associates, that you are, perhaps you could begin to see you aren't facilitating understanding with such an edit, but stepping on it. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 11:33, 22 November 2013 (EST)

"Trainz-build" tag

2013-11-21T20:06:54Z

Fabartus: /* Trainz-build tag number */ +cautionary pic

{{ORP-top}}
==Trainz-build tag number==
The '''Trainz-build tag''' number indicates the minimum '''[[Trainz build versions|Trainz Code Version]]''' required to use the asset. Trainz will not attempt to load an asset which has a trainz-build tag that is newer than it's own version number, but unfortunately ContentManager will continue to report there are updates, even when they are entirely inappropriate.

This tag is also an indication of the age of the asset, and the general technical configuration and standards to which it is built. The values will range up from the oldest [[Trainz 1.0]] release (2001) with three {{wp|service pack|Service Packs}} making the version commonly referred to as Trainz V-1.3, or Trainz 1.3. Assets with old Trainz-build numbers are not built to take advantage of new Trainz features that did not exist in the version of Trainz that the asset was built for, and the oldest used approaches which have been entirely abandoned. Newer Trainz releases do their best to translate these older technologies into the newer releases standards (data organization and graphical tech) but some small percentage of assets cannot be converted.
 
{{UserTip|The word ''version'' is used in Trainz to refer to three different concepts. There is the '''Trainz Retail Version''', the '''Trainz Version''' and the '''Trainz Build Number'''.
The '''Trainz Retail Version''' is a text string for a product release, such as ''Trainz Simulator 2009''.
The '''Trainz version''' is a numeric code (e.g ''2.4'' or ''3.6'') which is incremented for each major release. This code is updated whenever a significant change to Trainz is made. Most service packs (which introduce significant functionality changes) will have a new ''Trainz Version'', but hotfixes (which do not introduce significant functionality changes) do not see a ''Trainz version'' number change. Different language versions of the same product will also generally share the same ''Trainz Version''.
The '''Trainz Build Number''' is a unique number (e.g. ''44653'' or ''58414'') that identifies an individual Trainz release. All releases (including minor changes and language translations) have a different ''Trainz Build Number''.
The '''Trainz-build''' tag uses the ''Trainz Version'' numeric code.
}}
 
[[file:CM will input Versions too advanced-TS10-SP2 shown.JPG|thumb|400px|'''TS10 SP2's Content Manager (V-3.2)''' happily imported TS12 version (V-3.4) texture cdp's for TransDEM.exe in November 2013. Other legacy versions of Trainz will also import 'Version unidentified' trainz content. 

* '''For the new Trainz users:'''' the moral of this story is to examine trainz-build tags (versions) ASAP after importing new content into CM and provide human intelligence as to whether to delete, keep the asset, or set it aside; seek advice before trying to use, or risk breaking Trainz for while. 
* Some content can be retrograded to work in earlier Trainz releases. More recently published Routes and Sessions cannot. ]]

{| border=2 cellpadding=5 cellspacing=2
|-
! colspan=2|Trainz-Build version numbers and their mapping to official Trainz release versions are as follows:
|-
!'trainz-build' || Trainz product for which the asset was designed
|-
| {{center|1.3 }} || [[Trainz SP3|Trainz SP3]]
|-
| {{center|1.5 }} || Ultimate Trainz Collection
|-
| {{center|1.6 }} || Ultimate Trainz Collection SP1
|-
| {{center|2.0 }} || [[TRS2004]]
|-
| {{center|2.1 }} || [[TRS2004]] SP1
|-
| {{center|2.2 }} || [[TRS2004]] SP2 - Passenger Pack
|-
| {{center|2.3 }} || [[TRS2004]] SP3
|-
| {{center|2.4 }} || [[TRS2004]] SP4
|-
| {{center|2.5 }} || [[TRS2006]]
|-
| {{center|2.6 }} || [[TRS2006]] SP1
|-
| {{center|2.7 }} || Trainz Classics 1&2
|-
| {{center|2.8 }} || Trainz Classics 3
|-
| {{center|2.9 }} || [[TS2009]]
|-
| {{center|3.0 }} || [[TS2009 SP1]]
|-
| {{center|3.1 }} || [[TS2009 SP2]] / [[TS2009 SP3]]
|-
| {{center|3.2 }} || [[TS2010]] / [[TS2010 SP1]]
|-
| {{center|3.3 }} || [[TS2010 SP2]] / [[TS2010 SP3]] / [[TS2009 SP4]]
|-
| {{center|3.4 }} || [[TS2010 SP4]]
|-
| {{center|3.5 }} || [[TS12]]
|-
| {{center|3.6 }} || [[TS12]] and [[Trainz Simulator Mac]]
|-
| {{center|3.7 }} || [[TS12 SP1]]
|}

==Asset compatibility==
It is important for an asset to list the correct Trainz-build in the [[config.txt file]]. It specifies the version of Trainz the asset was intended to be used with. An earlier version of Trainz will refuse to load the asset. A later version of Trainz will enable appropriate backwards compatibility workarounds (e.g. using different validation requirements) as required.
 

A correctly-constructed asset built for an older version will usually function in a newer version of Trainz. However, Trainz content validation is improved over time, and newer versions of Trainz detect errors that older versions did not pick up on. Some content may be detected as 'faulty' in a current Trainz version that was missed in the version it was originally created for.
 

It should be noted that content that is uploaded to the [[Download Station]] is validated by the most recent version of Trainz, using the validation compatibility for the trainz-build specified by the asset.
 

If [[Content Creator Plus]] is used to modify an asset, it will automatically update the trainz-build version in the config.txt file to the current Trainz version. If this version has changed significantly, other changes to the config.txt file will probably be required.
Assets which are manually edited will need the appropriate version entered. If the line is omitted entirely, the lowest possible version is assumed. This is currently ''Trainz-build 1.3''.
 

==Obsolete Versions==
Trainz-build numbers up to and including 2.8 are considered obsolete as of September 2012 and can no longer be uploaded to the [[Download Station]]. See the [[Trainz Life-Cycle Policy]] for additional details.

{{TBKR|trainz-build tag}}
[[Category:Config Tag|trainz-build tag]]
[[Category:Trainz fundamentals pages|trainz-build tag]]
{{ORP-bot|trainz-build tag}}

File:CM will input Versions too advanced-TS10-SP2 shown.JPG

2013-11-21T19:55:19Z

Fabartus: For use in cautionary illustration in "Trainz-build" tag

For use in cautionary illustration in [["Trainz-build" tag]]

"Trainz-build" tag

2013-11-21T15:57:55Z

Fabartus: /* Trainz-build tag number */ link Trainz build versions

{{ORP-top}}
==Trainz-build tag number==
The '''Trainz-build tag''' number indicates the minimum '''[[Trainz build versions|Trainz Code Version]]''' required to use the asset. Trainz will not attempt to load an asset which has a trainz-build tag that is newer than it's own version number, but unfortunately ContentManager will continue to report there are updates, even when they are entirely inappropriate.

This tag is also an indication of the age of the asset, and the general technical configuration and standards to which it is built. The values will range up from the oldest [[Trainz 1.0]] release (2001) with three {{wp|service pack|Service Packs}} making the version commonly referred to as Trainz V-1.3, or Trainz 1.3. Assets with old Trainz-build numbers are not built to take advantage of new Trainz features that did not exist in the version of Trainz that the asset was built for, and the oldest used approaches which have been entirely abandoned. Newer Trainz releases do their best to translate these older technologies into the newer releases standards (data organization and graphical tech) but some small percentage of assets cannot be converted.
 
{{UserTip|The word ''version'' is used in Trainz to refer to three different concepts. There is the '''Trainz Retail Version''', the '''Trainz Version''' and the '''Trainz Build Number'''.
The '''Trainz Retail Version''' is a text string for a product release, such as ''Trainz Simulator 2009''.
The '''Trainz version''' is a numeric code (e.g ''2.4'' or ''3.6'') which is incremented for each major release. This code is updated whenever a significant change to Trainz is made. Most service packs (which introduce significant functionality changes) will have a new ''Trainz Version'', but hotfixes (which do not introduce significant functionality changes) do not see a ''Trainz version'' number change. Different language versions of the same product will also generally share the same ''Trainz Version''.
The '''Trainz Build Number''' is a unique number (e.g. ''44653'' or ''58414'') that identifies an individual Trainz release. All releases (including minor changes and language translations) have a different ''Trainz Build Number''.
The '''Trainz-build''' tag uses the ''Trainz Version'' numeric code.
}}

Trainz-Build version numbers and their mapping to official Trainz release versions are as follows:
{| border=2 cellpadding=5 cellspacing=2
|'''trainz-build''' || Trainz product for which the asset was designed
|-
| {{center|1.3 }} || [[Trainz SP3|Trainz SP3]]
|-
| {{center|1.5 }} || Ultimate Trainz Collection
|-
| {{center|1.6 }} || Ultimate Trainz Collection SP1
|-
| {{center|2.0 }} || [[TRS2004]]
|-
| {{center|2.1 }} || [[TRS2004]] SP1
|-
| {{center|2.2 }} || [[TRS2004]] SP2 - Passenger Pack
|-
| {{center|2.3 }} || [[TRS2004]] SP3
|-
| {{center|2.4 }} || [[TRS2004]] SP4
|-
| {{center|2.5 }} || [[TRS2006]]
|-
| {{center|2.6 }} || [[TRS2006]] SP1
|-
| {{center|2.7 }} || Trainz Classics 1&2
|-
| {{center|2.8 }} || Trainz Classics 3
|-
| {{center|2.9 }} || [[TS2009]]
|-
| {{center|3.0 }} || [[TS2009 SP1]]
|-
| {{center|3.1 }} || [[TS2009 SP2]] / [[TS2009 SP3]]
|-
| {{center|3.2 }} || [[TS2010]] / [[TS2010 SP1]]
|-
| {{center|3.3 }} || [[TS2010 SP2]] / [[TS2010 SP3]] / [[TS2009 SP4]]
|-
| {{center|3.4 }} || [[TS2010 SP4]]
|-
| {{center|3.5 }} || [[TS12]]
|-
| {{center|3.6 }} || [[TS12]] and [[Trainz Simulator Mac]]
|-
| {{center|3.7 }} || [[TS12 SP1]]
|}

==Asset compatibility==
It is important for an asset to list the correct Trainz-build in the [[config.txt file]]. It specifies the version of Trainz the asset was intended to be used with. An earlier version of Trainz will refuse to load the asset. A later version of Trainz will enable appropriate backwards compatibility workarounds (e.g. using different validation requirements) as required.
 

A correctly-constructed asset built for an older version will usually function in a newer version of Trainz. However, Trainz content validation is improved over time, and newer versions of Trainz detect errors that older versions did not pick up on. Some content may be detected as 'faulty' in a current Trainz version that was missed in the version it was originally created for.
 

It should be noted that content that is uploaded to the [[Download Station]] is validated by the most recent version of Trainz, using the validation compatibility for the trainz-build specified by the asset.
 

If [[Content Creator Plus]] is used to modify an asset, it will automatically update the trainz-build version in the config.txt file to the current Trainz version. If this version has changed significantly, other changes to the config.txt file will probably be required.
Assets which are manually edited will need the appropriate version entered. If the line is omitted entirely, the lowest possible version is assumed. This is currently ''Trainz-build 1.3''.
 

==Obsolete Versions==
Trainz-build numbers up to and including 2.8 are considered obsolete as of September 2012 and can no longer be uploaded to the [[Download Station]]. See the [[Trainz Life-Cycle Policy]] for additional details.

{{TBKR|trainz-build tag}}
[[Category:Config Tag|trainz-build tag]]
[[Category:Trainz fundamentals pages|trainz-build tag]]
{{ORP-bot|trainz-build tag}}

KIND Texture

2013-11-20T16:42:10Z

Fabartus: --KIND Texture (redundant, wikimarkup rendering produces automatically)

{{ORP-top}}
[[KIND Texture]] is a kuid-assigned data type definition which 'exposes' a simple texture within the Trainz data base as an general kuid selectable asset, ''as opposed to a 'private' texture available only to the self-definition of a single asset''.

These explicitly defined textures become a public and shared resource that can be referenced by [[KUID]] for use as a custom corona, for example for several or many content assets. This is a desirable practice with respect to file byte-counts—textures in a typical Trainz install have been shown by independent Trainz users to take up over half the HDD data space needed in local content.

Exposing and reusing a common texture allows many assets to share it and minimizes the HDD footprint of the asset whilst also cutting down the amount of memory the texture needs in RAM memory. This in turn can have large posative performance benefits in the case where an texture asset is used frequently on a Trainz-board region, for example as part of the definition of the streets, roads, and bridges in a town or alternatively as the bark or leaf texture in a forest of trees, in a common spline scenery object such as shrubbery, and so forth. The more instanced objects are enumerated for the graphics engine to render, the more incremental payback a common element such as this texture asset will return.

==Parent Classes==
* [[KIND TrainzBaseSpec]]
==Child Classes==
* Whichever assets make use of the new common texture resource.

==Supported Tags==
TBD.

==Example Config.txt==
*'''[[Texture file]]s''' are ASCII specification files (text format) instructing ContentManager (CM) how to render each single texture.
*Texture files have a ".texture.txt" name extension within the assets' folder
*Texture files within a config.txt file such as the below ''MUST NOT'' have the ''''.txt'''' extension, or CM will generate an error.
<tt>
{|width="100%" text-align="center" float="center" bgcolor="#FAFAFC"  padding="9px"
|- border="1"
| '''Tag or structure braces''' || '''Data fields'''
|-
| kuid ||<kuid:56113:1267>
|-
| trainz-build || 2.5
|-
| category-class || "JO"
|-
| category-region|| "AU"
|-
| category-era || "2000s;2010s"
|-
| username || "testTexture"
|-
| kind || "texture"
|-
| '''texture || "eg.texture"'''
|-
| thumbnails||
|-
| { ||
|-
| 0||
|-
|       {||
|-
|       image || "thumb.jpg"
|-
|       width || 240
|-
|       height || 180
|-
|       }||
|-
| }||
|}
</tt>
The above "texture" tag specifies a [[Texture file]] located within the [[asset folder]].

==Categories==
[[Category:Asset KIND|Texture]]
[[Category:TBD|Texture]]
{{ORP-bot|Texture}}

KIND Texture

2013-11-20T16:40:46Z

Fabartus: +{{ORP-top}}+{{ORP-bot}} and clarify

=KIND Texture=
{{ORP-top}}
[[KIND Texture]] is a kuid-assigned data type definition which 'exposes' a simple texture within the Trainz data base as an general kuid selectable asset, ''as opposed to a 'private' texture available only to the self-definition of a single asset''.

These explicitly defined textures become a public and shared resource that can be referenced by [[KUID]] for use as a custom corona, for example for several or many content assets. This is a desirable practice with respect to file byte-counts—textures in a typical Trainz install have been shown by independent Trainz users to take up over half the HDD data space needed in local content.

Exposing and reusing a common texture allows many assets to share it and minimizes the HDD footprint of the asset whilst also cutting down the amount of memory the texture needs in RAM memory. This in turn can have large posative performance benefits in the case where an texture asset is used frequently on a Trainz-board region, for example as part of the definition of the streets, roads, and bridges in a town or alternatively as the bark or leaf texture in a forest of trees, in a common spline scenery object such as shrubbery, and so forth. The more instanced objects are enumerated for the graphics engine to render, the more incremental payback a common element such as this texture asset will return.

==Parent Classes==
* [[KIND TrainzBaseSpec]]
==Child Classes==
* Whichever assets make use of the new common texture resource.

==Supported Tags==
TBD.

==Example Config.txt==
*'''[[Texture file]]s''' are ASCII specification files (text format) instructing ContentManager (CM) how to render each single texture.
*Texture files have a ".texture.txt" name extension within the assets' folder
*Texture files within a config.txt file such as the below ''MUST NOT'' have the ''''.txt'''' extension, or CM will generate an error.
<tt>
{|width="100%" text-align="center" float="center" bgcolor="#FAFAFC"  padding="9px"
|- border="1"
| '''Tag or structure braces''' || '''Data fields'''
|-
| kuid ||<kuid:56113:1267>
|-
| trainz-build || 2.5
|-
| category-class || "JO"
|-
| category-region|| "AU"
|-
| category-era || "2000s;2010s"
|-
| username || "testTexture"
|-
| kind || "texture"
|-
| '''texture || "eg.texture"'''
|-
| thumbnails||
|-
| { ||
|-
| 0||
|-
|       {||
|-
|       image || "thumb.jpg"
|-
|       width || 240
|-
|       height || 180
|-
|       }||
|-
| }||
|}
</tt>
The above "texture" tag specifies a [[Texture file]] located within the [[asset folder]].

==Categories==
[[Category:Asset KIND|Texture]]
[[Category:TBD|Texture]]
{{ORP-bot|Texture}}

"Soundscript" container

2013-11-20T16:12:02Z

Fabartus: /* Categories */ +pipetrick

{{ORP-top}}
A container type tag for defining asset sounds.

==Supported Tags==
Each soundscript subcontainer supports the following tags. Each tag is shown here with its default value.

repeat-delay 0,0
distance 50,150
ambient 0
attachment ""
nostartdelay 0
priority 1
trigger ""
volume 1
sound
{
}

====repeat-delay====
:Type: Decimal Pair
:Desc: Time range (in seconds) to delay, after the sound finishes playing, before playing the sound again. To set a constant delay either set both these values the same or only provide one of them, otherwise a random value between them will be chosen. When used with a trigger event (see the 'trigger' tag), a positive value indicates that the sound should not repeat, but should wait until triggered again.

====distance====
:Type: Decimal Pair
:Desc: Distance range from the source, in meters, where the sound is audible. The minimum distance defines the radius within which the sound remains at 100% volume. Beyond that distance, the sound volume will begin to decay naturally. The maximum distance defines a radius beyond which the game will no longer play the sound. This does not mean that the sound will fade to zero by the maximum distance, but rather that the sound will cut off abruptly at that point. It is up to the content creator to choose an appropriate distance - smaller is better for performance.

====ambient====
:Type: Boolean
:Desc: If true this is an 'ambient' sound, ambient sounds are played in 2D and do not make use of 3D positioning in the world other than to affect volume. Unlike positional sounds, ambient sounds may be stereo.

====attachment====
:Type: String
:Desc: Point to attach the sound source to. Attachment points are specified in the mesh file during creation.

====nostartdelay====
:Type: Boolean
:Desc: If added and true this tag specifies that the sound will play immediately once triggered. By default sounds have a random start delay between 0 & 4 seconds. Start delay should be left active in most cases, as turning it off may cause significant audio artifacts when several identical sounds are in proximity.

====priority====
:Type: Integer
:Desc: Sets the priority of the sound, if their are not enough sound channels available higher priority sounds will be played first. Defaults to 1, can be negative.

====trigger====
:Type: String
:Desc: The 'trigger' tag gives your sound a name that can allow it to be played from [[Scripting|TrainzScript]], animations and certain predefined events. (At least one of these "predefined events" is to use the word "toggle" when including a soundscript container in the config.txt of a "MOjunction". This will make the sound fire each time the turnout is switched)

====volume====
:Type: Decimal
:Desc: Specifies the volume gain of the sound. Defaults to 1 (100%).

====sound====
:Type: Container
:Desc: Contains a list of the sound files to play. If th elist has more than one entry then one file will be picked at random from the list. The value of each tag in this container is the filename of a WAV sound file. Filenames are relative to the base directory of the asset, i.e. relative to the location of the config file. The keys used within the list are not important: Trainz convention for lists like this is to numerically number each option from zero, and while it is strongly recommended to follow this convention, there is no technical requirement to do so.

Valid WAV files are:
* Uncompressed.
* 8 or 16 bit
* Mono, Stereo or Surround (As of build 3.7 Surround is not fully tested)

Sampling rate can be 22kHz (22,050Hz) or 44kHz (44,100Hz). The higher sampling rate doubles the size of the file for no significant improvement in quality, and is not recommended. For some purposes there are additional requirements - for instance directional sounds must be mono.

==Example Config.txt==
Sample [[config.txt file]] for a map asset that has a different day and night background sounds:

kind map
kuid <KUID:0:0>
soundscript
{
morning
{
ambient 1
value-range 1, 0.1
volume 0.3
sound
{
0 ctry_day_1.wav
1 ctry_day_2.wav
}
}
night
{
ambient 1
value-range 0, 0.9
volume 0.3
sound
{
0 night_loop.wav
}
}
}

==Categories==
[[Category:Config Container|Soundscript container]]
{{ORP-bot|Soundscript container}}

"Soundscript" container

2013-11-20T01:54:12Z

Fabartus: +{{ORP-top}}+{{ORP-bot}} +pipetricks

Template:Plain link/doc

2013-11-17T22:58:11Z

Fabartus: /* Examples */ tweak

<noinclude>{{Documentation subpage}}
</noinclude><includeonly>{{Usage-style}}</includeonly>

;Purpose of {{Lts|{{BASEPAGENAME}}}}
* Create a 'Pretty-Print' external url link inside text.

*:This template will allow you to create a local or [[Help:Interwiki linking|interwiki link]] (such as a link to the [[Help:Page history|history of a page]]) on a page without having the ['''" [[File:External.png|10px]] "'''] follow the link.
* This can be used, for example, when internal or interwiki links appear as external links.
* See [[Help:URL#URLs on_other Wikimedia projects]] for more information.

== Caution ==

You can use {{Plain link|MW|magicword}} to generate URLs to Wikipedia pages.
==Pass parameters==
__NOTOC__
Arguments or ''''positional/default pass parameters'''' are separated by the pipe character in Wiki markup language, so the first default parameter (placeholder is <nowiki> {{{1}}}</nowiki>) is assigned the link url address. The second (<nowiki> {{{2}}}</nowiki>) is the 'pretty text' for how you want to have it appear.
# ''''|1='''' is the same as ''''| url = '''' (or in wiki template code: <nowiki> {{{1}}}</nowiki> = <nowiki> {{{url}}}</nowiki>)
# ''''|2='''' is the same as ''''|name='''' (or in wiki template code: <nowiki> {{{2}}}</nowiki> = <nowiki> {{name}}}</nowiki>)

==Examples==
<big>
* <code><nowiki>{{Plain link|http://www.google.co.uk|Google}}</nowiki></code> gives <code> {{Plain link|http://www.google.co.uk|Google}} </code>
:: compare normal external wiki-link:
* <code><nowiki>[http://www.google.co.uk Google]</nowiki></code> gives <code> [http://www.google.co.uk Google] </code>
</big>

==Caution on url insides==
Note that if your url or link title contains an equals sign <code>=</code> you must use named parameters:
*<code><nowiki>{{ Plainlink | url=http://en.wikipedia.org/w/index.php?title=Equals_sign&oldid=282228764 | name="this edit" }}</nowiki></code> gives {{Plain link|url=http://en.wikipedia.org/w/index.php?title=Equals_sign&oldid=282228764 |name="this edit"}}
whereas
*<code><nowiki>{{Plain link|http://forums.auran.com/trainz/showthread.php?14511-Having-Problems-with-Multiple-industry-New-Setup&highlight=%26lt%3Bkuid%3A107727%3A100012%26gt%3B |Having Problems}}</nowiki></code> gives {{Plain link|http://forums.auran.com/trainz/showthread.php?14511-Having-Problems-with-Multiple-industry-New-Setup&highlight=%26lt%3Bkuid%3A107727%3A100012%26gt%3B |Having Problems}} ''''which link-to-be'... is ''clearly broken'' with a mal-formed url due to the internal equals sign''', ''whilst:
*<code><nowiki>{{Plain link|url=http://forums.auran.com/trainz/showthread.php?14511-Having-Problems-with-Multiple-industry-New-Setup&highlight=%26lt%3Bkuid%3A107727%3A100012%26gt%3B |2=Having Problems}}</nowiki></code> gives {{Plain link|url=http://forums.auran.com/trainz/showthread.php?14511-Having-Problems-with-Multiple-industry-New-Setup&highlight=%26lt%3Bkuid%3A107727%3A100012%26gt%3B |2=Having Problems}}'' works the same as if default parameter ''''|1='''' and ''''|name='''' are defined, since url is just an alternative that is a bit more explicit to <nowiki> {{{1}}}, and the default parameter {{{2}}}</nowiki> is used (mapped) the same as the ''''|name='''' parameter.

<includeonly>

[[Category:External link templates]]
{{Wikipedia}}

</includeonly>

Template:Plain link/doc

2013-11-17T22:53:13Z

Fabartus: /* Caution on url insides */ tweak

<noinclude>{{Documentation subpage}}
</noinclude><includeonly>{{Usage-style}}</includeonly>

;Purpose of {{Lts|{{BASEPAGENAME}}}}
* Create a 'Pretty-Print' external url link inside text.

*:This template will allow you to create a local or [[Help:Interwiki linking|interwiki link]] (such as a link to the [[Help:Page history|history of a page]]) on a page without having the ['''" [[File:External.png|10px]] "'''] follow the link.
* This can be used, for example, when internal or interwiki links appear as external links.
* See [[Help:URL#URLs on_other Wikimedia projects]] for more information.

== Caution ==

You can use {{Plain link|MW|magicword}} to generate URLs to Wikipedia pages.
==Pass parameters==
__NOTOC__
Arguments or ''''positional/default pass parameters'''' are separated by the pipe character in Wiki markup language, so the first default parameter (placeholder is <nowiki> {{{1}}}</nowiki>) is assigned the link url address. The second (<nowiki> {{{2}}}</nowiki>) is the 'pretty text' for how you want to have it appear.
# ''''|1='''' is the same as ''''| url = '''' (or in wiki template code: <nowiki> {{{1}}}</nowiki> = <nowiki> {{{url}}}</nowiki>)
# ''''|2='''' is the same as ''''|name='''' (or in wiki template code: <nowiki> {{{2}}}</nowiki> = <nowiki> {{name}}}</nowiki>)

==Examples==

*<code><nowiki>{{Plain link|http://www.google.co.uk|Google}}</nowiki></code> gives {{Plain link|http://www.google.co.uk|Google}}

==Caution on url insides==
Note that if your url or link title contains an equals sign <code>=</code> you must use named parameters:
*<code><nowiki>{{ Plainlink | url=http://en.wikipedia.org/w/index.php?title=Equals_sign&oldid=282228764 | name="this edit" }}</nowiki></code> gives {{Plain link|url=http://en.wikipedia.org/w/index.php?title=Equals_sign&oldid=282228764 |name="this edit"}}
whereas
*<code><nowiki>{{Plain link|http://forums.auran.com/trainz/showthread.php?14511-Having-Problems-with-Multiple-industry-New-Setup&highlight=%26lt%3Bkuid%3A107727%3A100012%26gt%3B |Having Problems}}</nowiki></code> gives {{Plain link|http://forums.auran.com/trainz/showthread.php?14511-Having-Problems-with-Multiple-industry-New-Setup&highlight=%26lt%3Bkuid%3A107727%3A100012%26gt%3B |Having Problems}} ''''which link-to-be'... is ''clearly broken'' with a mal-formed url due to the internal equals sign''', ''whilst:
*<code><nowiki>{{Plain link|url=http://forums.auran.com/trainz/showthread.php?14511-Having-Problems-with-Multiple-industry-New-Setup&highlight=%26lt%3Bkuid%3A107727%3A100012%26gt%3B |2=Having Problems}}</nowiki></code> gives {{Plain link|url=http://forums.auran.com/trainz/showthread.php?14511-Having-Problems-with-Multiple-industry-New-Setup&highlight=%26lt%3Bkuid%3A107727%3A100012%26gt%3B |2=Having Problems}}'' works the same as if default parameter ''''|1='''' and ''''|name='''' are defined, since url is just an alternative that is a bit more explicit to <nowiki> {{{1}}}, and the default parameter {{{2}}}</nowiki> is used (mapped) the same as the ''''|name='''' parameter.

<includeonly>

[[Category:External link templates]]
{{Wikipedia}}

</includeonly>

Template:Plain link/doc

2013-11-17T22:46:36Z

Fabartus: expand and translate

<noinclude>{{Documentation subpage}}
</noinclude><includeonly>{{Usage-style}}</includeonly>

;Purpose of {{Lts|{{BASEPAGENAME}}}}
* Create a 'Pretty-Print' external url link inside text.

*:This template will allow you to create a local or [[Help:Interwiki linking|interwiki link]] (such as a link to the [[Help:Page history|history of a page]]) on a page without having the ['''" [[File:External.png|10px]] "'''] follow the link.
* This can be used, for example, when internal or interwiki links appear as external links.
* See [[Help:URL#URLs on_other Wikimedia projects]] for more information.

== Caution ==

You can use {{Plain link|MW|magicword}} to generate URLs to Wikipedia pages.
==Pass parameters==
__NOTOC__
Arguments or ''''positional/default pass parameters'''' are separated by the pipe character in Wiki markup language, so the first default parameter (placeholder is <nowiki> {{{1}}}</nowiki>) is assigned the link url address. The second (<nowiki> {{{2}}}</nowiki>) is the 'pretty text' for how you want to have it appear.
# ''''|1='''' is the same as ''''| url = '''' (or in wiki template code: <nowiki> {{{1}}}</nowiki> = <nowiki> {{{url}}}</nowiki>)
# ''''|2='''' is the same as ''''|name='''' (or in wiki template code: <nowiki> {{{2}}}</nowiki> = <nowiki> {{name}}}</nowiki>)

==Examples==

*<code><nowiki>{{Plain link|http://www.google.co.uk|Google}}</nowiki></code> gives {{Plain link|http://www.google.co.uk|Google}}

==Caution on url insides==
Note that if your url or link title contains an equals sign <code>=</code> you must use named parameters:
*<code><nowiki>{{ Plainlink | url=http://en.wikipedia.org/w/index.php?title=Equals_sign&oldid=282228764 | name="this edit" }}</nowiki></code> gives {{Plain link|url=http://en.wikipedia.org/w/index.php?title=Equals_sign&oldid=282228764 |name="this edit"}}
whereas
*<code><nowiki>{{Plain link|http://forums.auran.com/trainz/showthread.php?14511-Having-Problems-with-Multiple-industry-New-Setup&highlight=%26lt%3Bkuid%3A107727%3A100012%26gt%3B Having Problems}}</nowiki></code> gives {{Plain link|http://forums.auran.com/trainz/showthread.php?14511-Having-Problems-with-Multiple-industry-New-Setup&highlight=%26lt%3Bkuid%3A107727%3A100012%26gt%3B Having Problems}} '''is broken''', ''whilst:
*<code><nowiki>{{Plain link|url=http://forums.auran.com/trainz/showthread.php?14511-Having-Problems-with-Multiple-industry-New-Setup&highlight=%26lt%3Bkuid%3A107727%3A100012%26gt%3B |2=Having Problems}}</nowiki></code> gives {{Plain link|url=http://forums.auran.com/trainz/showthread.php?14511-Having-Problems-with-Multiple-industry-New-Setup&highlight=%26lt%3Bkuid%3A107727%3A100012%26gt%3B |2=Having Problems}}'' works the same as if default parameter ''''|1='''' and ''''|name='''' are defined, since url is just an alternative that is a bit more explicit to <nowiki> {{{1}}}, and the default parameter {{{2}}}</nowiki> is used (mapped) the same as the ''''|name='''' parameter.

<includeonly>

[[Category:External link templates]]
{{Wikipedia}}

</includeonly>

Template:Plain link/doc

2013-11-17T22:14:30Z

Fabartus: tweak usage

<noinclude>{{Documentation subpage}}
</noinclude>

;Purpose of {{Lts|{{BASEPAGENAME}}}}
* Create a 'Pretty-Print' external url link inside text.

*:This template will allow you to create a local or [[Help:Interwiki linking|interwiki link]] (such as a link to the [[Help:Page history|history of a page]]) on a page without having the ['''" [[File:External.png|10px]] "'''] follow the link.
* This can be used, for example, when internal or interwiki links appear as external links.
* See [[Help:URL#URLs on_other Wikimedia projects]] for more information.

== Caution ==

You can use {{Plain link|MW|magicword}} to generate URLs to Wikipedia pages.

==Examples==

*<code><nowiki>{{Plain link|http://www.google.co.uk|Google}}</nowiki></code> gives {{Plain link|http://www.google.co.uk|Google}}

Note that if your url or link title contains an equals sign <code>=</code> you must use named parameters:
*<code><nowiki>{{ Plainlink | url=http://en.wikipedia.org/w/index.php?title=Equals_sign&oldid=282228764 | name="this edit" }}</nowiki></code> gives {{Plain link|url=http://en.wikipedia.org/w/index.php?title=Equals_sign&oldid=282228764 |name="this edit"}}

<includeonly>

[[Category:External link templates]]
{{Wikipedia}}

</includeonly>

Template:Plain link/doc

2013-11-17T22:11:33Z

Fabartus: genesis, port slightly changed from WikiPedia+cat w/{{Wikipedia}

{{Documentation subpage}}

;Purpose
* Create a 'Pretty-Print' external url link inside text.

*:This template will allow you to create a local or [[Help:Interwiki linking|interwiki link]] (such as a link to the [[Help:Page history|history of a page]]) on a page without having the ['''" [[File:External.png|10px]] "'''] follow the link.
* This can be used, for example, when internal or interwiki links appear as external links.
* See [[Help:URL#URLs on_other Wikimedia projects]] for more information.

== Caution ==

You can use {{Plain link|MW|magicword}} to generate URLs to Wikipedia pages.

==Examples==

*<code><nowiki>{{Plain link|http://www.google.co.uk|Google}}</nowiki></code> gives {{Plain link|http://www.google.co.uk|Google}}

Note that if your url or link title contains an equals sign <code>=</code> you must use named parameters:
*<code><nowiki>{{ Plainlink | url=http://en.wikipedia.org/w/index.php?title=Equals_sign&oldid=282228764 | name="this edit" }}</nowiki></code> gives {{Plain link|url=http://en.wikipedia.org/w/index.php?title=Equals_sign&oldid=282228764 |name="this edit"}}

<includeonly>

[[Category:External link templates]]
{{Wikipedia}}

</includeonly>

File:External.png

2013-11-17T22:08:00Z

Fabartus: {{Wikipedia}}

KIND Traincar

2013-11-16T02:23:36Z

Fabartus: ++{{ORP-top}}+{{ORP-bot}}

{{ORP-top}}
[[KIND Traincar]] provides the basis for all individual train Vehicles, for example, a single item of the locomotive, a single item of rollingstock, or a single tender.

This asset type inherits all trackside positioning and mesh display characteristics, and adds Vehicle-specific functionality such as physics and control mechanisms.

==KIND Hierarchy==
===Parent Classes===
* [[KIND Scenery-trackside]]
===Child Classes===
* ''none.''

==Supported Tags==
Each traincar asset supports the following tags. Each tag is shown here with its default value.

kind "traincar"
cabinsway 1.0
company "QueenslandRail"
ditch_color 0,0,0
low_beam_value 2,2,2
high_beam_value 1,1,1
flash_scale 1
engine 0
real-engine 1
enginespec (KUID)
enginesound (KUID)
fonts 1
hornsound (KUID)
cabin_muffle 0.4
light_color 0,0,0
mass 37000
max-coupler-gap 0.08
origin "AU"
pantograph (KUID)
smoke_shade 0.09
smoke_random 2.9
smoke_slowlife 3
smoke_fastlife 0
smoke_height 0.8
smoke_fastspeed 10
tender 0
use-coupler-sounds 1
fonts-path ""
[[Bogeys_container|bogeys]]
{
}
paintshed-template-used (KUID)
paintshed-skin-used (KUID)
product-id ""
product-version ?
product-type ""
disable-extra-track-sounds 0
max-tractive-effort 0

====cabinsway====
:Type: Decimal
:Desc: Controls the amount of 'sway' the interior view has as the vehicle takes corners. A bigger number will result in more sway.
====company====
:Type: English Text String
:Desc: Text string to indicate which railway company or organisation this vehicle is in service with as represented.
====ditch_color====
:Type: Color(RGB)
:Desc: Color of ditch lights (values are integer between 0 and 255, comma separated for red, green, and blue).
====low_beam_value====
:Type: Decimal array
:Desc: Comma separated sequence of decimal values - used to configure the brightness of the lights when in low beam mode. First number applies to first headlight point, and so on. Values are divisors - e.g. a value of 2 means half brightness.
====high_beam_value====
:Type: Decimal array
:Desc: Comma separated sequence of decimal values - used to configure the brightness of the lights when in high beam mode. First number applies to first headlight point, and so on. Values are divisors - e.g. a value of 2 means half brightness.
====flash_scale====
:Type: Decimal
:Desc: Sets the speed that the ditch lights flash at.
====engine====
:Type: Boolean
:Desc: If 1, vehicle is a locomotive, if 0, vehicle is an unpowered traincar. Locomotives are expected to have cab interiors, hornsounds, enginesounds, and so on.
====real-engine====
:Type: Boolean
:Desc: This will enable an unpowered vehicle to have an audible horn and visible headlights when set to 0. This is useful for cab cars, driving trailers, and unpowered end cars of multiple units.
====enginespec====
:Type: KUID
:Desc: [[KIND Engine|Enginespec Asset]] to use with this locomotive. Defines locomotive performance characteristics.

====enginesound====
:Type: KUID
:Desc: [[KIND Enginesound|Enginesound Asset]] to use with this locomotive.
====fonts====
:Type: Integer
:Desc: Number of running-number fonts to use on this locomotive.
====hornsound====
:Type: KUID
:Desc: [[KIND Hornsound|Hornsound Asset]] to play when locos horn is blown.
====cabin_muffle====
:Type: Decimal
:Desc: Amount that the enginesound volume should be reduced to when in-cab. Default of 0.4 is 40% volume, intended to represent a fully enclosed and noise deadened cab. Note: Steam locos have a different default. They default to 1.0 - no muffling at all. (Steam loco cabs are very frequently not fully enclosed, let alone fitted with noise deadening material.)
====light_color====
:Type: Color(RGB)
:Desc: Color of headlight (values are integer between 0 and 255, comma separated for red, green, and blue).
====mass====
:Type: Decimal
:Desc: Mass of the vehicle in Kilograms when empty - i.e. the tare weight, not the gross weight. The mass of any products loaded into queues will be added to this by the game.
====max-coupler-gap====
:Type: decimal
:Desc: Specifies the amount of permissible coupler slack on this vehicle in Metres. Note: The observable slack between any two vehicles will be the average of the values for each vehicle. Cannot be zero.

====origin====
:Type: Text
:Desc: ''Obsolete''
====pantograph====
:Type: KUID
:Desc: [[KIND Pantograph|Pantograph Asset]] to attach to pantograph attachment points.
====smoke_shade====
:Type: Decimal
:Desc: Value in the range (0.0 .. 1.0) which controls the color (including Alpha - so 0.0 will be transparent, 0.1 a dark mist, 1.0 a thick white) of each smoke particle. The alpha value will decay to zero (transparent) over the life of the particle.

====smoke_random====
:Type: Decimal
:Desc: Controls the amount of randomness introduced into the direction of new smoke particles. Larger numbers == more randomness.
====smoke_slowlife====
:Type: Decimal
:Desc: Length of time (seconds) smoke particles will exist for when vehicle is moving 'slow'.
====smoke_fastlife====
:Type: Decimal
:Desc: Length of time (seconds) smoke particles will exist for when vehicle is moving 'fast'.
====smoke_height====
:Type: Decimal
:Desc: Additional speed for 'slow' smoke to make it drift higher from the traincar.
====smoke_fastspeed====
:Type: Decimal
:Desc: Speed (m/s) at which traincar is considered to be moving 'fast'.
====tender====
:Type: Boolean
:Desc: Used by the AI to determine if it should take this vehicle with the loco when doing orders like 'run round'.
====use-coupler-sounds====
:Type: Boolean
:Desc: Enables or disables the coupler slack sounds for this specific vehicle.
====fonts-path====
:Type: Text
:Desc: Asset name to use when determining where running numbers are stored. Used in the same way 'asset-filename' used to be on v2.4 and earlier assets.
====bogeys====
:Type: [[Bogeys_container|Bogeys Container]]
:Desc: Specifies what bogies are attached where, and with what modifiers. Documented separately [[Bogeys_container|here]].
====paintshed-template-used====
:Type: KUID
:Desc: ''Obsolete''. Was KUID of paintshed template used to create this reskin - used by Paintshed to reload the reskin for further editing.
====paintshed-skin-used====
:Type: KUID
:Desc: ''Obsolete''. Was KUID of paintshed skin used to create this reskin - used by Paintshed to reload the reskin for further editing.
====product-id====
:Type: Text String
:Desc: ''Obsolete''. Was used by Paintshed to indicate that this asset was for use with paintshed.
====product-version====
:Type: Decimal
:Desc: ''Obsolete''. Was the version number of Paintshed that the model was intended to be used with.
====product-type====
:Type: Text String
:Desc: ''Obsolete''. Was used with Paintshed, to mark out a traincar as being repaintable in paintshed, but not for placement in-game.

====disable-extra-track-sounds====
:Type: Boolean
:Desc: Disables extra track sounds for this vehicle. Useful for making drivable ships, aircraft, road vehicles, etc. - anything that should not make wheel-on-rail type sounds.
====max-tractive-effort====
:Type: Decimal
:Desc: Maximum tractive effort this vehicle can put into the track in Newtons. (Only used for Diesel and Electric locos - Steam locos use a different system defined in the enginespec.)

==Example Config.txt==
Sample [[config.txt file]] for a traincar asset, with the Standard Tags excluded for brevity:

kind "traincar"
engine 1
mass 100000
max-tractive-effort 400000

max-coupler-gap 0.1

interior <kuid:523:666>
enginespec <kuid:-1:42004221>
enginesound <kuid:-1:42003000>
hornsound <kuid:-1:42003101>
pantograph <kuid:-1:101395>

smoke_shade 0.3
smoke_random 2.5
smoke_slowlife 6
smoke_fastlife 0.8
smoke_height 1.7
smoke_fastspeed 1.6

fonts 2
fonts-path "traincar"

[[%22mesh-table%22_Container|mesh-table]] {
default {
mesh "traincar-body.im"
auto-create 1
}
shadow {
mesh "shadow\traincar-shadow.im"
}
}

[[Bogeys_container|bogeys]] {
0 {
reversed 0
rotation-permitted 0
sideplay-permitted 0
bogey <KUID2:xxxxx:yyyyy:zzz>
}
1 {
reversed 0
bogey <KUID2:xxxxx:yyyyy:zzz>
}
2 {
reversed 0
sideplay-permitted 1
bogey <KUID2:xxxxx:yyyyy:zzz>
}
3 {
reversed 0
sideplay-permitted 1
bogey <KUID2:xxxxx:yyyyy:zzz>
}
}

company "Company Name"
description "Textual description of traincar in English"

==Downloads==
* [[Media:SD40-2.zip]] - The MAX source for the [[Auran]] [[TS2009]] SD40-2 traincar. Distributed from the TrainzDev site for education purposes only. No license for the reproduction or redistribution of the included model or textures is granted.

==Categories==
[[Category:Asset KIND]]
{{ORP-bot}}

TS2010

2013-10-15T00:19:36Z

Fabartus: ++{{FUN}} templates

{{FUN-beg}}
==TS2010: Engineers Edition==
{{TOCright}}
===Available Updates===
* [[TS2010 SP1]] is a free update to this product.
* [[TS2010 SP2]] is a free update to this product.
* [[TS2010 SP3]] is a free update to this product.
* [[TS2010 SP4]] is a free update to this product which includes a public beta of [[Trainz Multiplayer]] but removes support for compatibility mode and scenarios.

==New Features==

The following is a summary list of major features:

* SpeedTree

* Seasonal Assets

* Surveyor Layers

* [[TADDaemon]]

* Improved [[Content Manager]] / [[Download Station]] integration

* New scriptable front-end menu system

* Native mode is now active by default and generally performs better (both visually and in terms of frame rate) across the board than compatibility mode. Compatibility mode is still available for those people who have older problem content. (Note: support for compatibility mode is removed by [[TS2010 SP4]].)

==Licenses==
The following licenses are relevant to users of this product:
* [[TS2010 License Agreement]]
* [[Download Station License Agreement]]

==Included Content==

* ''TBD''

[[Category:TBD]]
[[Category:Trainz Versions]]
{{FUN-bot}}

Build Numbers

2013-10-14T23:41:37Z

Fabartus: /* TS2010 - Trainz 2010 */ tweak, title link, note

{{ORP-top}}
=Code build number=
The '''Code build number''' or '''Trainz build version''' (two names meaning the identical 'tracking number') is the unique software level identifier that increments not only with 'named' main retail releases, but with each release for specific language groups, and by {{wp|Hotfix}}es, as well as by {{wp|Service_pack}} releases. 

Initial Trainz code build versions are not released in initial retail release versions for all world wide languages at the same time, but these are produced as available translations, so typically, non-English releases lag by some months, but may have hot fixes or service packs already installed. As the translation needs are satisfied and an overall ''release stabilizes'', subsequent service pack releases apply to those code build numbers and effectively combine language releases into a merged common product. At the end of the process, the final service pack produces a ''single stable '''code build version''''', creating the final corresponding Trainz (two digit) version number and corresponding identical [["Trainz-build" tag]] level found in assets config.txt.

=Currently Supported Releases=
Trainz versions are known best by their ''''''Retail Release name'''''', after which N3V Games/Auran, following general software industry practices subsequently release bug fixing '''hot fixes''' and usually a succession of service packs. Each

:'''Note:''' ''Legacy version releases and build numbers are listed at the bottom of the page, reserving this area for currently supported versions.''
The following builds exist for [[TS2009]]. Where patches are available, these are noted beside the build number.
==TS2009 - Trainz 2009==
{{anchor|TRS2009|TS2009|Trainz2009|TRS 2009|TS 2009|Trainz 2009}}
:<big>'''Trainz 2009: World Builder Edition'''</big> 
{| border=1 cellpadding=2 cellspacing=0 style="text-align:center; "
|'''Build Number'''||'''Patches available'''||'''Build description'''
|-
|Build 37625||auto-patch to 40040||English Online Release
|-
|Build 38017||auto-patch to 40040||[[TS2009 SP1]]
|-
|Build 38411||auto-patch to 40040||English Retail
|-
|Build 38599||auto-patch to 40040||[[TS2009 SP1]] hotfix
|-
|Build 38610||PROTECTED||Steam English Retail
|-
|Build 38808||auto-patch to 41590||French Retail
|-
|Build 38824||-||Dutch Retail
|-
|Build 38869||PROTECTED||UK Retail
|-
|Build 39176||-||German Retail
|-
|Build 39413||auto-patch to 40040||Czech, Polish, Hungarian Retail
|-
|Build 39561||-||Spanish Retail
|-
|Build 39979||auto-patch to 40040
|[[TS2009 SP2]]
|-
|<big>Build 40040</big>
|<big>{{center|-auto-patch Common version-}}</big>
|<big>[[TS2009 SP2]] + hotfix </big>
|-
|Build 40357||-||Cabon City English Online Release
|-
|Build 40542||-||Russian Retail
|-
|Build 40702||-||Cabon City English Online Release
|-
|Build 40702||-||Treez English Online Release
|-
|Build 40762||-||Murchison English Online Release
|-
|Build 40837||-||S&C English Online Release
|-
|Build 40895||-||Spanish pre-SP3
|-
|Build 41497||-||Dutch, German pre-SP3
|-
|Build 41546||-||Italian Retail
|-
|Build 41590||-||French pre-SP3
|-
|<big>Build 41844</big>
|<big>{{center|-auto-patch Common version-}}</big>
|<big>[[TS2009 SP3]]</big> [[TADDaemon]] ("Trainz Asset Database Daemon") introduced
|-
|<big>Build 44653</big>
|<big>{{center|-auto-patch Common version-}}</big>
|<big>[[TS2009 SP4]]</big>
|}

==TS2010 - Trainz 2010==
:<big>'''Trainz 2010: Engineers Edition'''</big>
The following builds exist for [[TS2010]]. Where patches are available, these are noted beside the build number.

{| border=1 cellpadding=2 cellspacing=0
|'''Build Number'''||'''Patches available'''||'''Build description''' || '''[[Trainz-build]]* version No.'''
|-
|'''Build 41491''' ||manual patch to 41615 || [[TS2010| TS2010 SP0]], English Online Release
| Ver: 3.0 
|-
|Build 41615||manual patch to 43434 || [[TS2010 SP1]]
|Ver: 3.1 
|-
|Build 41622||manual patch to 43434 || English Online Release
|
|-
! || ||
|
|-
|'''Build 42203'''||manual patch to 43434||[[TS2010 SP2]] English, Swedish DVD Retail Release
| Ver: 3.2
|-
|Build 42534||-||French Retail
|
|-
|Build 42763||-||German Retail
|
|-
|Build 42831||-||Dutch Retail
|
|-
|Build 42953||-||Russian Retail
|
|-
|Build 43030||-||Czech, Polish Retail
|
|-
|Build 43233||-||Spanish Retail
|
|-
| || || ||
|-
|Build 43434||-||[[TS2010 SP3]]
| Ver: 3.3
|-
|Build 44088||-||[[TS2010 SP3]] Minor revision
|
|-
| || || ||
|-
|Build 45467||auto patch to 46170||[[TS2010 SP4]] (including Trainz Multiplayer Beta)
| Ver: 3.4
|-
|Build 45607||auto patch to 46170||[[TS2010 SP4]] patch 1 (including Trainz Multiplayer Beta)
|
|-
|Build 46170||manual patch to 49938||[[TS2010 SP4]] patch 2 (including Trainz Multiplayer Beta)
|
|-
|Build 49933||-||[[TS2010 SP3]] Minor revision, added support for Aerotrain DLC
|
|-
|Build 49938||-||[[TS2010 SP4]] patch 3 (including Trainz Multiplayer Beta), added support for Aerotrain DLC
|
|-
|}
<big>'''*'''</big> The tag trainz-build assigned value will reflect the tech-level assigned the release or that under which an asset is first made; the version is now listed on the title bar of the [[Content Manager]] screen, and that of individual items is one of the column listings. The trainz-build version is also list on the DLS web page.

==TS12 - Trainz 2012==
:'''Trainz 2012: Anniversary Edition'''</big>
The following builds exist for [[TS12]]. Where patches are available, these are noted beside the build number.

{| border=1 cellpadding=2 cellspacing=0
|'''Build Number'''||'''Patches available'''||'''Build description'''
|-
|Build 46957||auto-patch to 48054||Planet Auran release version
|-
|Build 47059||auto-patch to 48054||Minor revision
|-
|Build 47103||-||Steam release
|-
|Build 47452||auto-patch to 48054||Just Trainz release version
|-
|Build 47772||auto-patch to 48054||Just Trainz release version (minor revision)
|-
|Build 48054||manual patch to 48249||Minor revision
|-
|Build 48249||manual patch to 49922||Minor revision
|-
|Build 49849||-||Czech Release
|-
|Build 49922||-||Minor revision, added support for Aerotrain DLC
|-
|Build 50027||-||German Release
|-
|Build 50406||-||French Release
|-
|Build 51054||-||Dutch Release
|-
|Build 52143||-||Russian, Japanese, Polish Release
|-
|Build 57720||-||TS12 SP1 English
|-
|Build 57825||-||TS12 SP1 Hotfix 1 English
|-
|Build 57898||-||TS12 SP1 Hotfix 2 English
|-
|Build 58414||-||TS12 SP1 Hotfix 3 English
|}

==Trainz Simulator Mac==
:<big>'''Trainz MAC'''</big>
The following builds exist for [[Trainz Simulator Mac]]. Where patches are available, these are noted beside the build number.

{| border=1 cellpadding=2 cellspacing=0
|'''Build Number'''||'''Patches available'''||'''Build description'''
|-
|Build 47652||-||Planet Auran Digital Store release
|-
|Build 47770||-||Third-party Digital Store release
|-
|Build 48159||-||Feral retail release
|}

= Content Builds =

Auran's newer patch technology developed for TRS2009 has the capability of updating the base Trainz version and installed add-on content independently. The following is a list of released content build versions for add-on content since the advent of TRS2009's technology. Legacy versions (Trainz UTC, Trainz TCC discussed below)

{| border=1 cellpadding=2 cellspacing=0
|'''Content Build Number'''||'''Content Patches available'''||'''Build description'''
|-
|Content Build 40355||-||Cabon City English Online Release
|-
|Content Build 40400||-||Cabon City English Online Release
|-
|Content Build 40563||-||Treez English Online Release
|-
|Content Build 40761||-||Murchison English Online Release
|-
|Content Build 40836||-||S&C English Online Release
|-
|Content Build 49210||-||Duchess Online Release
|-
|Content Build 49474||-||Duchess Steam Release
|-
|Content Build 49631||-||Coronation Scot Online Release
|-
|Content Build 49694||-||Coronation Scot Steam Release
|}
==Legacy build versions==
:''This section is being provided by the user community to make as complete a reference as possible, so is currently incomplete and may remain so.''
===Trainz 1.x===
:<big>'''Trainz 1.3'''</big>
{| border=1 cellpadding=2 cellspacing=0
|'''Ver#:'''|| <big>{{center|'''Build Number'''}} || {{center|'''Trainz Retail Release Name'''}} ||'''Patches available''' || {{center|'''Build description'''<big>*</big>}}</big>
|-
|0.9||Build 0009 || {{center|Trainz Beta}} ||<center>wholly replaced by [[Trainz 1.0]] </center>||released in November 2000 for testing purposes to Model Railroaders.
|-
|1.0||Build 0010|| {{center|[[Trainz 1.0]]}} ||{{cdash}} || ''''''Trainz Community Edition'''''', released in December 2001
|-
|1.0||Build 0019? || {{center|[[Trainz 1.0]], non-English}} ||{{cdash}} || Trainz Community Edition 2
|-
|1.1||Build ???? || {{Cdash}} || {{center|[[Trainz 1.0| SP1]]}} || released in 2002 (April ?)
|-
|1.2||Build 0??? || {{cdash}} || {{center|[[Trainz 1.0| SP2]]}} || ''''''Trainz Retail Edition'''''' was released in June 2002 aimed at the North American markets.
|-
|1.3||Build 0263 || {{center|aka '''Trainz 1.3'''}} || {{center|[[Trainz SP3]]}} || First with TrainzScript.exe, and Scenarios, November 2002
|-
|1.0||Build 0277 || {{center|[[Trainz 1.0]], non-English}} ||{{cdash}} || Trainz Community Edition 2
|-
|1.5||Build 0377 || {{center|Trainz UTC 3 CD set}} || {{cdash}} || Ultimate Trainz Collection, released 26 November 2002 w/expanded content
|-
|1.6||Build 0404 || {{cdash}} || {{center|Trainz UTC SP1}} || Ultimate Trainz Collection SP1
|-
|1.6||Build 0033 || {{center|Paintshed}} || {{cdash}} ||1st released as part of Ultimate Trainz Collection SP1
|-
|}
===TRS2004===
'''TRS2004''' had a relatively large number of separate builds as Auran worked out methods for international names handling in various languages, plus went through a related succession of Service Packs.
{| border=1 cellpadding=2 cellspacing=1
|'''Ver#:'''|| <big>{{center|'''Build Number'''}} || {{center|'''Trainz Retail Release Name'''}} ||'''Patches available''' || {{center|'''Build description'''<big>*</big>}}</big>
|-
|2.0||Build 668 || [[TRS2004|Trainz Railroad Simulator 2004]] || || International version (Australia and USA). Released in September 2003.
|-
|2.0||Build 686 || [[TRS2004|Trainz Railway Simulator 2004]] || || Just Trains version (UK). Requires disk in drive.
|-
|2.1||Build ???? || [[TRS2004|Trainz Railroad Simulator 2004]] SP1 || || International (USA/Australia) release
|-
|2.1||Build ???? || [[TRS2004|Trainz Railway Simulator 2004]] SP1 || || Just Trains release (UK). Requires disk in drive.
|-
|2.2||Build ???? || [[TRS2004|Trainz Railroad Simulator 2004]] "Passenger Edition" (SP2)|| || International (USA/Australia) release
|-
|2.2||Build 2285 || [[TRS2004|Trainz Railway Simulator 2004]] "Passenger Edition" (SP2)|| || Just Trains release (UK). Requires disk in drive.
|-
|2.3||Build ???? || [[TRS2004|Trainz Railroad Simulator 2004]] SP3 || || International (USA/Australia) release
|-
|2.3||Build ???? || [[TRS2004|Trainz Railway Simulator 2004]] SP3 || ||
|-
|2.3||Build ???? || [[TRS2004#Deluxe|TRS2004 Deluxe]] || ||Trainz 2004: Deluxe Edition. Includes SP3 and additional content. Different regions received different additional content.
|-
|2.4||Build 2365 || [[TRS2004|Trainz Railroad Simulator 2004]] SP4 || || International (USA/Australia) release
|-
|2.4||Build 2370 || [[TRS2004|Trainz Railway Simulator 2004]] SP4 || || Just Trains release (UK). Requires disk in drive.
|-
|2.4||Build 2370 || [[TRS2004|Trainz Railway Simulator 2004]] SP4 || || Included in ''Trainz Collection'', but ''without'' the requirement for a disk in the drive.
|-
|}

===TRS2006 & etc.===

'''TRS2006''' had a relatively large number of separate builds as Auran worked out methods for international names handling in various languages, plus went into partnership with various 3rd party distributors giving a host of releases in various markets but only one series of related Service Packs.

{| border=1 cellpadding=2 cellspacing=1 width="100%"
|col-width="8%"|'''Ver#:'''|| <big>{{center|'''Build Number'''}} || {{center|'''Trainz Retail Release Name'''}} ||'''Patches available''' || {{center|'''Build description'''<big>*</big>}}</big>
|-
|  2.5||Build 2761 || {{center
|[[TRS2006|TRS2006 GM]] }} ||{{cdash}} ||  Original release for Australia and USA. [[Content Creator Plus]] and [[Content Manager|Content Manager Plus]] first introduced.
|-
|  2.5||colspan="3" |'''Other Builds:''' UK release - 2773; French - 2883; Dutch - 2967;German - 2970; Spanish - 3007 ||German - was also called Pro Train Perfect or PTP
|-
|  2.5|| Build 3096 &Merscom's build 3104|| '''{{center|Trainz Driver Edition (TDE)''' ('demo version')}}|| {{cdash}} || UK release date of Trainz Driver was 24 February 2005. {{bullR}}TDE did not have CMP nor Surveyor, but did include Railyard
|-
|  2.6 || build 3092 || {{cdash}} || {{center|[[TRS2006|TRS2006 SP1]] }} || TRS2006 - Australia and North American markets
|-
|  2.6||colspan="4" |'''Other SP1 Builds:''' United Kingdom-SP1= build 3099; Spanish-SP1= build 3118
|-
|  2.6||Build 3335 || {{cdash}} || {{center|[[TRS2006#SP1|TRS2006 SP1]] }} || Vista support. Released in September 2007. Used for bundle packs - Trainz Railwayz (North American release bundled with TC1) and Trainz Complete Collection (bundled with TRS2004 SP4, UTC and Trainz Routes 1 to 4).
|-
|  2.6||Build ????|| {{center|[[TRS2007]] }} || {{cdash}} ||  French retail, equivalent to TRS2006+SP1, with some additional French content.
|-
|  2.6||Build ????|| {{center|[[TRS2007]] }} || {{cdash}} ||  German retail, equivalent to TRS2006+SP1, with a lot of additional German content.
|-
|}

===Trainz Classics===

'''Trainz Classics''' was series of releases each featuring a single route. New code features were added to each version to support that route.

{| border=1 cellpadding=2 cellspacing=1 width="100%"
|col-width="8%"|'''Ver#:'''|| <big>{{center|'''Build Number'''}} || {{center|'''Trainz Retail Release Name'''}} ||'''Patches available''' || {{center|'''Build description'''<big>*</big>}}</big>
|-
|  2.7||Build 3337|| {{center|[[TC1|'''Trainz Classics''']]}} || {{cdash}} ||  English Retail. Released July 9th, 2007 as a bundle with both [[TC1]] and [[TC2]] content included. Released as '''Trainz Railwayz''' (bundled with an updated TRS2006) in North America.
|-
|  2.7||Build ????|| {{center|[[TRS2008]] }} || {{cdash}} ||  French Retail. Includes both TC1/TC2 and also the French 2007 content in a single build.
|-
|  2.8||Build 3529|| {{center|[[TC3|Trainz Classics 3]]}} || {{cdash}} ||  TC3 English Retail, released on July 23, 2008.
|-
|}

==Notes and references==
<big><big><code>*</code></big></big> Name usages matching information posted on {{wp|Trainz}} and the {{plain link|http://en.wikibooks.org/wiki/Trainz/Version_And_Build_Numbers|Trainz Wikibook}} Version and Build Numbers pages.

{{ORP-bot}}{{TBKr}}

Build Numbers

2013-10-14T23:05:13Z

Fabartus: /* TS2010 - Trainz 2010 */ format, begin xreferencing

{{ORP-top}}
=Code build number=
The '''Code build number''' or '''Trainz build version''' (two names meaning the identical 'tracking number') is the unique software level identifier that increments not only with 'named' main retail releases, but with each release for specific language groups, and by {{wp|Hotfix}}es, as well as by {{wp|Service_pack}} releases. 

Initial Trainz code build versions are not released in initial retail release versions for all world wide languages at the same time, but these are produced as available translations, so typically, non-English releases lag by some months, but may have hot fixes or service packs already installed. As the translation needs are satisfied and an overall ''release stabilizes'', subsequent service pack releases apply to those code build numbers and effectively combine language releases into a merged common product. At the end of the process, the final service pack produces a ''single stable '''code build version''''', creating the final corresponding Trainz (two digit) version number and corresponding identical [["Trainz-build" tag]] level found in assets config.txt.

=Currently Supported Releases=
Trainz versions are known best by their ''''''Retail Release name'''''', after which N3V Games/Auran, following general software industry practices subsequently release bug fixing '''hot fixes''' and usually a succession of service packs. Each

:'''Note:''' ''Legacy version releases and build numbers are listed at the bottom of the page, reserving this area for currently supported versions.''
The following builds exist for [[TS2009]]. Where patches are available, these are noted beside the build number.
==TS2009 - Trainz 2009==
{{anchor|TRS2009|TS2009|Trainz2009|TRS 2009|TS 2009|Trainz 2009}}
:<big>'''Trainz 2009: World Builder Edition'''</big> 
{| border=1 cellpadding=2 cellspacing=0 style="text-align:center; "
|'''Build Number'''||'''Patches available'''||'''Build description'''
|-
|Build 37625||auto-patch to 40040||English Online Release
|-
|Build 38017||auto-patch to 40040||[[TS2009 SP1]]
|-
|Build 38411||auto-patch to 40040||English Retail
|-
|Build 38599||auto-patch to 40040||[[TS2009 SP1]] hotfix
|-
|Build 38610||PROTECTED||Steam English Retail
|-
|Build 38808||auto-patch to 41590||French Retail
|-
|Build 38824||-||Dutch Retail
|-
|Build 38869||PROTECTED||UK Retail
|-
|Build 39176||-||German Retail
|-
|Build 39413||auto-patch to 40040||Czech, Polish, Hungarian Retail
|-
|Build 39561||-||Spanish Retail
|-
|Build 39979||auto-patch to 40040
|[[TS2009 SP2]]
|-
|<big>Build 40040</big>
|<big>{{center|-auto-patch Common version-}}</big>
|<big>[[TS2009 SP2]] + hotfix </big>
|-
|Build 40357||-||Cabon City English Online Release
|-
|Build 40542||-||Russian Retail
|-
|Build 40702||-||Cabon City English Online Release
|-
|Build 40702||-||Treez English Online Release
|-
|Build 40762||-||Murchison English Online Release
|-
|Build 40837||-||S&C English Online Release
|-
|Build 40895||-||Spanish pre-SP3
|-
|Build 41497||-||Dutch, German pre-SP3
|-
|Build 41546||-||Italian Retail
|-
|Build 41590||-||French pre-SP3
|-
|<big>Build 41844</big>
|<big>{{center|-auto-patch Common version-}}</big>
|<big>[[TS2009 SP3]]</big> [[TADDaemon]] ("Trainz Asset Database Daemon") introduced
|-
|<big>Build 44653</big>
|<big>{{center|-auto-patch Common version-}}</big>
|<big>[[TS2009 SP4]]</big>
|}

==TS2010 - Trainz 2010==
:<big>'''Trainz 2010: Engineers Edition'''</big>
The following builds exist for [[TS2010]]. Where patches are available, these are noted beside the build number.

{| border=1 cellpadding=2 cellspacing=0
|'''Build Number'''||'''Patches available'''||'''Build description''' || '''Trainz-build version'''
|-
|'''Build 41491''' ||manual patch to 41615 || [[TS2010| TS2010 SP0]], English Online Release
| Ver: 3.0 
|-
|Build 41615||manual patch to 43434 || [[TS2010 SP1]]
|Ver: 3.1 
|-
|Build 41622||manual patch to 43434 || English Online Release
|
|-
! || ||
|
|-
|'''Build 42203'''||manual patch to 43434||[[TS2010 SP2]] English, Swedish DVD Retail Release
| Ver: 3.2
|-
|Build 42534||-||French Retail
|
|-
|Build 42763||-||German Retail
|
|-
|Build 42831||-||Dutch Retail
|
|-
|Build 42953||-||Russian Retail
|
|-
|Build 43030||-||Czech, Polish Retail
|
|-
|Build 43233||-||Spanish Retail
|
|-
|Build 43434||-||[[TS2010 SP3]]
|
|-
|Build 44088||-||[[TS2010 SP3]] Minor revision
|
|-
|Build 45467||auto patch to 46170||[[TS2010 SP4]] (including Trainz Multiplayer Beta)
|
|-
|Build 45607||auto patch to 46170||[[TS2010 SP4]] patch 1 (including Trainz Multiplayer Beta)
|
|-
|Build 46170||manual patch to 49938||[[TS2010 SP4]] patch 2 (including Trainz Multiplayer Beta)
|
|-
|Build 49933||-||[[TS2010 SP3]] Minor revision, added support for Aerotrain DLC
|
|-
|Build 49938||-||[[TS2010 SP4]] patch 3 (including Trainz Multiplayer Beta), added support for Aerotrain DLC
|
|-
|}

==TS12 - Trainz 2012==
:'''Trainz 2012: Anniversary Edition'''</big>
The following builds exist for [[TS12]]. Where patches are available, these are noted beside the build number.

{| border=1 cellpadding=2 cellspacing=0
|'''Build Number'''||'''Patches available'''||'''Build description'''
|-
|Build 46957||auto-patch to 48054||Planet Auran release version
|-
|Build 47059||auto-patch to 48054||Minor revision
|-
|Build 47103||-||Steam release
|-
|Build 47452||auto-patch to 48054||Just Trainz release version
|-
|Build 47772||auto-patch to 48054||Just Trainz release version (minor revision)
|-
|Build 48054||manual patch to 48249||Minor revision
|-
|Build 48249||manual patch to 49922||Minor revision
|-
|Build 49849||-||Czech Release
|-
|Build 49922||-||Minor revision, added support for Aerotrain DLC
|-
|Build 50027||-||German Release
|-
|Build 50406||-||French Release
|-
|Build 51054||-||Dutch Release
|-
|Build 52143||-||Russian, Japanese, Polish Release
|-
|Build 57720||-||TS12 SP1 English
|-
|Build 57825||-||TS12 SP1 Hotfix 1 English
|-
|Build 57898||-||TS12 SP1 Hotfix 2 English
|-
|Build 58414||-||TS12 SP1 Hotfix 3 English
|}

==Trainz Simulator Mac==
:<big>'''Trainz MAC'''</big>
The following builds exist for [[Trainz Simulator Mac]]. Where patches are available, these are noted beside the build number.

{| border=1 cellpadding=2 cellspacing=0
|'''Build Number'''||'''Patches available'''||'''Build description'''
|-
|Build 47652||-||Planet Auran Digital Store release
|-
|Build 47770||-||Third-party Digital Store release
|-
|Build 48159||-||Feral retail release
|}

= Content Builds =

Auran's newer patch technology developed for TRS2009 has the capability of updating the base Trainz version and installed add-on content independently. The following is a list of released content build versions for add-on content since the advent of TRS2009's technology. Legacy versions (Trainz UTC, Trainz TCC discussed below)

{| border=1 cellpadding=2 cellspacing=0
|'''Content Build Number'''||'''Content Patches available'''||'''Build description'''
|-
|Content Build 40355||-||Cabon City English Online Release
|-
|Content Build 40400||-||Cabon City English Online Release
|-
|Content Build 40563||-||Treez English Online Release
|-
|Content Build 40761||-||Murchison English Online Release
|-
|Content Build 40836||-||S&C English Online Release
|-
|Content Build 49210||-||Duchess Online Release
|-
|Content Build 49474||-||Duchess Steam Release
|-
|Content Build 49631||-||Coronation Scot Online Release
|-
|Content Build 49694||-||Coronation Scot Steam Release
|}
==Legacy build versions==
:''This section is being provided by the user community to make as complete a reference as possible, so is currently incomplete and may remain so.''
===Trainz 1.x===
:<big>'''Trainz 1.3'''</big>
{| border=1 cellpadding=2 cellspacing=0
|'''Ver#:'''|| <big>{{center|'''Build Number'''}} || {{center|'''Trainz Retail Release Name'''}} ||'''Patches available''' || {{center|'''Build description'''<big>*</big>}}</big>
|-
|0.9||Build 0009 || {{center|Trainz Beta}} ||<center>wholly replaced by [[Trainz 1.0]] </center>||released in November 2000 for testing purposes to Model Railroaders.
|-
|1.0||Build 0010|| {{center|[[Trainz 1.0]]}} ||{{cdash}} || ''''''Trainz Community Edition'''''', released in December 2001
|-
|1.0||Build 0019? || {{center|[[Trainz 1.0]], non-English}} ||{{cdash}} || Trainz Community Edition 2
|-
|1.1||Build ???? || {{Cdash}} || {{center|[[Trainz 1.0| SP1]]}} || released in 2002 (April ?)
|-
|1.2||Build 0??? || {{cdash}} || {{center|[[Trainz 1.0| SP2]]}} || ''''''Trainz Retail Edition'''''' was released in June 2002 aimed at the North American markets.
|-
|1.3||Build 0263 || {{center|aka '''Trainz 1.3'''}} || {{center|[[Trainz SP3]]}} || First with TrainzScript.exe, and Scenarios, November 2002
|-
|1.0||Build 0277 || {{center|[[Trainz 1.0]], non-English}} ||{{cdash}} || Trainz Community Edition 2
|-
|1.5||Build 0377 || {{center|Trainz UTC 3 CD set}} || {{cdash}} || Ultimate Trainz Collection, released 26 November 2002 w/expanded content
|-
|1.6||Build 0404 || {{cdash}} || {{center|Trainz UTC SP1}} || Ultimate Trainz Collection SP1
|-
|1.6||Build 0033 || {{center|Paintshed}} || {{cdash}} ||1st released as part of Ultimate Trainz Collection SP1
|-
|}
===TRS2004===
'''TRS2004''' had a relatively large number of separate builds as Auran worked out methods for international names handling in various languages, plus went through a related succession of Service Packs.
{| border=1 cellpadding=2 cellspacing=1
|'''Ver#:'''|| <big>{{center|'''Build Number'''}} || {{center|'''Trainz Retail Release Name'''}} ||'''Patches available''' || {{center|'''Build description'''<big>*</big>}}</big>
|-
|2.0||Build 668 || [[TRS2004|Trainz Railroad Simulator 2004]] || || International version (Australia and USA). Released in September 2003.
|-
|2.0||Build 686 || [[TRS2004|Trainz Railway Simulator 2004]] || || Just Trains version (UK). Requires disk in drive.
|-
|2.1||Build ???? || [[TRS2004|Trainz Railroad Simulator 2004]] SP1 || || International (USA/Australia) release
|-
|2.1||Build ???? || [[TRS2004|Trainz Railway Simulator 2004]] SP1 || || Just Trains release (UK). Requires disk in drive.
|-
|2.2||Build ???? || [[TRS2004|Trainz Railroad Simulator 2004]] "Passenger Edition" (SP2)|| || International (USA/Australia) release
|-
|2.2||Build 2285 || [[TRS2004|Trainz Railway Simulator 2004]] "Passenger Edition" (SP2)|| || Just Trains release (UK). Requires disk in drive.
|-
|2.3||Build ???? || [[TRS2004|Trainz Railroad Simulator 2004]] SP3 || || International (USA/Australia) release
|-
|2.3||Build ???? || [[TRS2004|Trainz Railway Simulator 2004]] SP3 || ||
|-
|2.3||Build ???? || [[TRS2004#Deluxe|TRS2004 Deluxe]] || ||Trainz 2004: Deluxe Edition. Includes SP3 and additional content. Different regions received different additional content.
|-
|2.4||Build 2365 || [[TRS2004|Trainz Railroad Simulator 2004]] SP4 || || International (USA/Australia) release
|-
|2.4||Build 2370 || [[TRS2004|Trainz Railway Simulator 2004]] SP4 || || Just Trains release (UK). Requires disk in drive.
|-
|2.4||Build 2370 || [[TRS2004|Trainz Railway Simulator 2004]] SP4 || || Included in ''Trainz Collection'', but ''without'' the requirement for a disk in the drive.
|-
|}

===TRS2006 & etc.===

'''TRS2006''' had a relatively large number of separate builds as Auran worked out methods for international names handling in various languages, plus went into partnership with various 3rd party distributors giving a host of releases in various markets but only one series of related Service Packs.

{| border=1 cellpadding=2 cellspacing=1 width="100%"
|col-width="8%"|'''Ver#:'''|| <big>{{center|'''Build Number'''}} || {{center|'''Trainz Retail Release Name'''}} ||'''Patches available''' || {{center|'''Build description'''<big>*</big>}}</big>
|-
|  2.5||Build 2761 || {{center
|[[TRS2006|TRS2006 GM]] }} ||{{cdash}} ||  Original release for Australia and USA. [[Content Creator Plus]] and [[Content Manager|Content Manager Plus]] first introduced.
|-
|  2.5||colspan="3" |'''Other Builds:''' UK release - 2773; French - 2883; Dutch - 2967;German - 2970; Spanish - 3007 ||German - was also called Pro Train Perfect or PTP
|-
|  2.5|| Build 3096 &Merscom's build 3104|| '''{{center|Trainz Driver Edition (TDE)''' ('demo version')}}|| {{cdash}} || UK release date of Trainz Driver was 24 February 2005. {{bullR}}TDE did not have CMP nor Surveyor, but did include Railyard
|-
|  2.6 || build 3092 || {{cdash}} || {{center|[[TRS2006|TRS2006 SP1]] }} || TRS2006 - Australia and North American markets
|-
|  2.6||colspan="4" |'''Other SP1 Builds:''' United Kingdom-SP1= build 3099; Spanish-SP1= build 3118
|-
|  2.6||Build 3335 || {{cdash}} || {{center|[[TRS2006#SP1|TRS2006 SP1]] }} || Vista support. Released in September 2007. Used for bundle packs - Trainz Railwayz (North American release bundled with TC1) and Trainz Complete Collection (bundled with TRS2004 SP4, UTC and Trainz Routes 1 to 4).
|-
|  2.6||Build ????|| {{center|[[TRS2007]] }} || {{cdash}} ||  French retail, equivalent to TRS2006+SP1, with some additional French content.
|-
|  2.6||Build ????|| {{center|[[TRS2007]] }} || {{cdash}} ||  German retail, equivalent to TRS2006+SP1, with a lot of additional German content.
|-
|}

===Trainz Classics===

'''Trainz Classics''' was series of releases each featuring a single route. New code features were added to each version to support that route.

{| border=1 cellpadding=2 cellspacing=1 width="100%"
|col-width="8%"|'''Ver#:'''|| <big>{{center|'''Build Number'''}} || {{center|'''Trainz Retail Release Name'''}} ||'''Patches available''' || {{center|'''Build description'''<big>*</big>}}</big>
|-
|  2.7||Build 3337|| {{center|[[TC1|'''Trainz Classics''']]}} || {{cdash}} ||  English Retail. Released July 9th, 2007 as a bundle with both [[TC1]] and [[TC2]] content included. Released as '''Trainz Railwayz''' (bundled with an updated TRS2006) in North America.
|-
|  2.7||Build ????|| {{center|[[TRS2008]] }} || {{cdash}} ||  French Retail. Includes both TC1/TC2 and also the French 2007 content in a single build.
|-
|  2.8||Build 3529|| {{center|[[TC3|Trainz Classics 3]]}} || {{cdash}} ||  TC3 English Retail, released on July 23, 2008.
|-
|}

==Notes and references==
<big><big><code>*</code></big></big> Name usages matching information posted on {{wp|Trainz}} and the {{plain link|http://en.wikibooks.org/wiki/Trainz/Version_And_Build_Numbers|Trainz Wikibook}} Version and Build Numbers pages.

{{ORP-bot}}{{TBKr}}

"mesh-table" container

2013-10-14T01:36:09Z

Fabartus: /* Mesh subcontainer */ +details

{{ORP-top}}
==KIND Heirarchy==
The "mesh-table" container is a top-level [[config.txt file]] entry used by various [[Content_Configuration#Content_Types|Content Types]].

The mesh-table is a list of mesh subcontainers with no standalone tags. Each mesh subcontainer uses the following format. Tags are parsed in a standardised format, but not all [[Content_Configuration#Content_Types|Content Types]] support the full range of tags listed below. Each mesh derives its name from the subcontainer's tag name. These names are used to refer to specific meshes from within the mesh-table and also from script.

==Known Dependent Parent Types==
:''Main article, see: [[KIND Mesh]]''
The Content Types listed here use the mesh-table container as part of their definition.

* [[KIND Industry]]
* [[KIND MOJunction]]
* [[KIND Pantograph]]
* [[KIND Scenery]]
* [[KIND Track]]
* [[KIND Traincar]]

The following config containers also reference back to their Asset's mesh-table container in some fashion:
* [["junction-vertices" container]]
* [["track-lod-tree" container]]

'''See also'''{{bullR}} [[Modeling Guidelines]] {{bull}} [[Modeling Scenery]]
==Mesh subcontainer==
Each mesh subcontainer supports the following tags. Each tag is shown here with its default value. {{FAB-todo| Use Pseudo-table to recast as a real wikitable.}}
* The term 'filenamespec' is meant to convey the local pathspec (folder and subfolders) below the base folder of the asset (i.e. when opened for edit in Windows Explorer).
mesh-asset <NULLKUID>
mesh "text=path and name/ident"
anim "text=path and name/ident"
lod-level 255
mesh-season 255
att "text=a.some-attachment"
att-parent "text=filenamespec: some-mesh.im" *
opacity 1.0
position 0,0,0
orientation 0,0,0
auto-create 0
use-parent-bounds 0
animation-loop-speed 0
critical-animation 1
effects {
}
night-mesh-base "text=filenamespec of ..."

<big>*</big> The att-parent defaults to "default" which is the parent mesh. The att-parent tag can include a path.

==Supported Tags==
Each mesh subcontainer supports the following tags.

===mesh-asset===
Allows assets to be used as 'mesh libraries', the following container specifies that the mesh required (and its optional animation) is located relative to ''''''the root folder'''''' of <kuid:1234:5678>. CMP does not auto-check for the existence of these'' 'externally referenced files' ''when processing so you must ensure that they are present in the referenced kuid before using this tag. Subfolder paths within the asset can be used; folder names should be prefixed to the path with a forward slash ("/") separator in the usual fashion.

===mesh===
The ‘main’ mesh name. This may include a sub-path;
ie: mesh nightwindows/nightwindows.im, where the file nightwindows.im has been placed in the subdirectory nightwindows.

Use .im files exported from 3dsmax (as opposed to .pm.) or reference an .lm file if you wish your asset to have ‘Level of Detail’ mesh reduction.

Level of detail is a process of using different model meshes, depending on how far the viewer is from the model. A finer mesh is used for close up viewing in Trainz.

===anim===
The animation file (.kin) exported from 3dsmax. This may include a sub-path.

===lod-level===
The object LOD level at which this mesh is displayed. The default value (255) indicates that this mesh is visible at all detail levels. See also [[KIND Mesh]] for the 'mesh-detail-level' tag.

===mesh-season===
The season index for which this mesh is displayed. The default value (255) indicates that this mesh is visible in all seasons. See also [["Season-selector" container]].

===att===
The mesh (and animation if present) is inserted at a mesh attachment point rather than the origin (without this line the mesh is placed relative to the origin of the parent model).

===att-parent===
The tag tells Trainz in which mesh the attachment point is located. The insertion attachment point is located within the mesh ‘name’ , as listed in the config.txt.

===opacity===
opacity x (float 0.0 - 1.0 default 1.0)

Specifies the overall transparency of a mesh. Values other than 0.0 or 1.0 employ alpha blending and a value of 0.0 has the same effect as hiding the mesh.

Note that this tag is buggy in TS2009 prior to SP4.

===mesh-scale===
This tag defines a minimum and maximum scaling value for the mesh, where 1.0 is the size as modelled. Each instance of the mesh that exists in the world will randomise within this range. Randomisation will not change between runs or between Trainz editions, but may change based on factors such as the position of the mesh in the world. This tag is currently only supported on SpeedTree assets; attempts to use this tag on other assets results in undefined behaviour.

===position===
position X,Y,Z (in metres, default 0,0,0)

Specifies the location of a mesh relative to its insertion point.

===orientation===
orientation X,Y,Z (radians default 0,0,0)

Allows a submesh to be rotated relative to its insertion point. To reverse a mesh by 180 degrees about the Z axis, add the tag:

orientation 0,0,3.14159

===auto-create===
The model is generated automatically when placed, or when you load a map which includes the model. In some instances you don’t want the mesh visible (as this may be controlled through script). If auto-create is 0 the mesh will not be visible when placed.

===use-parent-bounds===
When enabled, this tag indicates that render culling should occur using the whole object's bounding box rather than this mesh's bounding box. Bounding boxes on individual meshes may not update correctly when animation moves the object's geometry any significant distance from the bind position. This flag can help mitigate such effects, at a tiny performance penalty.

===animation-loop-speed===
This tag must be here if the asset is to animate when placed. If this tag is not here when placed the animation will not play by default, but may play if controlled by script. A different value (e.g. 0.5, 2.0) may be used in the tag to play the animation at a different speed from that created in 3dsmax.

===light===
If set (which it is by default), this tag causes the non-stitched mesh to be linked into the Trainz lighting model. This causes the mesh to respond to directional lighting changes, such as the angle of the sun or train headlights. This is also necessary for normal maps to work correctly. Zeroing this tag will remove the mesh from the Trainz lighting model. Generally speaking, you should never zero this tag- almost every effect that can be achieved through this approach can be better served by using an appropriate normal map or appropriate geometry detail.

This tag has no effect on stitched meshes, which are always affected by the Trainz lighting. Since the content creator has no direct influence over which meshes are subject to [[Mesh Stitching]], and all indirect influences are subject to change between Trainz editions, it is strongly recommended that this tag is avoided to ensure that results are consistent.

===critical-animation===
"critical-animation" indicates that this mesh's animation generates events which are critical to the script system's behavior. If your asset is not scripted, does not use scripted animation events, or only uses the events for display purposes and will not break if the occasional event is missed, this tag should be set to ''false''. Leaving this flag set to ''true'' is a '''significant''' performance penalty.

===night-mesh-base===
This night mesh is linked to the specified mesh and is visible only at night. It is invisible if the specified mesh is invisible, (if the auto-create 0 line were used so the specified mesh can be controlled by script).

==Effects Container==
The effects container also contains a list of effect subcontainers. The effect subcontainers support the following generic tags.

kind ""
name ""

The effect subcontainers support additional tags depending on the effect kind. The following effect kinds are supported:

* [[Corona Effect]]
* [[Name Effect]]
* [[Attachment Effect]]
* [[Animation Effect]]
* [[Texture-Replacement Effect]]

==Mesh-Table Example==
The following is an example of a simple mesh-table which implements two levels of detail.

mesh-table
{
default-lod0
{
mesh "example-lod0.im"
auto-create 1
lod-level 0
}
default-lod1
{
mesh "example-lod1.im"
auto-create 1
lod-level 1
}
}

[[Category:Config Container|mesh-table container]]
{{ORP-bot|mesh-table container}}

User talk:Jamesmoody

2013-10-13T01:18:59Z

Fabartus: /* Please verify conclusion */ new section

Please do not leave comments here. I am unlikely to spot them.

If you need to contact me, please send me an email. If you do not have my address, send a forum Private Message.

Note: Do not contact me directly for technical support. Technical support requests should be sent to the Helpdesk.

== See {{wp|Wikipedia:Etiquette}} ==

:: Please note that this isn't wikipedia. We might use the same software, but don't assume that their rules and conventions apply here. [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]]) 12:27, 21 August 2013 (EST)
:: In particular note that we are not "NPOV". Documents on this wiki should reflect N3V Games point of view. [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]]) 12:39, 21 August 2013 (EST)

* Sorry we seem to have a different definition of profanity and the appropriate. S***ty is a rather apt term when things don't work right. For example, I'll address wiki business on the wiki, and expect the same—wiki's are about collaborative efforts, it's fairly plain something you guys have done failed in that respect... things never took off. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
:: No, we don't have a different definition of profanity. You may see it as acceptable to use such words, but we don't. This includes "bleeping" words out; you're obviously aware of the words you're using, so just don't use them. If you feel the need to use such words, go outside and take a break instead of replying. Keep it up and you'll be banned. It's that simple. [[User:Windwalkr|Windwalkr]] ([[User talk:Windwalkr|talk]]) 09:54, 21 August 2013 (EST)
::
:: Also, we used a wiki initially because it was easy for us to edit - I can come back and add a page whenever I have new information to publish. If we get some community assistance, that's great - but it really is a secondary consideration. [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]])

: I think it embarrassing that a wiki started so long ago is in such a P*** Poor state, it wasn't even initialized with Public Domain standard help pages, and even ParserFunctions (which I badly need, I couldn't even begin to write [[Template:N3V-Help-Image]] and [[Template:Help-Image]] a while ago as I can't test conditions, files, parameters, so have a Sh***th temporary placeholder workaround... NOT HAPPY FACE MAKING! {{Tl|Tlx}} is not yet useable, which is pretty much needed for any smart template exposition and help... all that TAKES UP AND WASTES my freely donated TIME... So stop that!). // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
:: We're not trying to be wikipedia. We welcome collaboration, but this is NOT a community-owned site. This is a corporate site, with corporate goals. Where our goals align with your goals, that's great. If your goals work against our goals, then our goals take precedence. That may be a harsh way to put it, but I don't want you to misunderstand the reality of the situation here. [[User:Windwalkr|Windwalkr]] ([[User talk:Windwalkr|talk]]) 09:54, 21 August 2013 (EST)

: Think Chris is or has gotten the picture that I only mean well, and if I wanted to be confrontational, I could really roast the company on the forum, and the Wikibook. I'm only trying to make you all look better, but ''that certainly means changing the status quo''. For starters, if someone comes out with a browser that requires HTML 5, the whole site is non-compliant. There's no Common.css and Common.js files in place. No classes to call, only HTML 4, which have been obsolescent now for what, five or six years?
: Coming in this spring after years of casual browsing to see in detail how little Trainz has progressed, how few changes and how dead this wiki is (Hasn't really progressed much since I first saw it back in late 2009, iirc) has been an eye opener. Not sure what you guys actually do, but I guess you can be proud you don't use coarse language. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
:: Thankfully, all common browsers work fine on our site, so it's not something that we're remotely concerned about at the current time. [[User:Windwalkr|Windwalkr]] ([[User talk:Windwalkr|talk]]) 09:54, 21 August 2013 (EST)

On the other commentary/responses... [[Talk:TADDaemon]], I have to parse what you changed to understand all your answers. Wikiquette when interleaving is to indent in between 'voices' (responses). Numerous people can then address a paragraph's point... or just the two. Taking things out of order to change the original text makes it rather difficult to see the conversational flow. Breaking the context seems to be a bad thought habit in N4V group think. Sign each para/post with four tildes, that adds a date stamp and your sig, which you can customize under preferences. (See mine)
:: You're quite correct, but nobody here really cares. We don't see the wiki as a workable chat tool. The software is not built with that in mind, and while some conventions have developed on other wikis to make it work "as best possible" we have better tools at our disposal and thus have minimal interest in learning the hacks that people have come up with for dealing with communication in a wiki. James has already suggested you use our forums. If you choose to use a backwards chat process such as this rather than the better tools which we have available, then don't complain when it's hard to use. [[User:Windwalkr|Windwalkr]] ([[User talk:Windwalkr|talk]]) 09:54, 21 August 2013 (EST)
::: I have gone back and fixed that chat page (with indenting and tildes). Please note though that what you posted is still purely a personal rant, and is still not welcome on a corporate site. You may wish to edit it... [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]]) 12:27, 21 August 2013 (EST)

I have to reconstruct the original text to make sense of your rebuttal. Again... a time investment for me. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
: ... and a time investment for me to learn a new way of formatting text when writing using a tool for what appears to be /obviously/ the wrong purpose, and also by someone elses fairly arbitrary rules. And when I could have been working on something productive instead.

Regardless, as Chris understands, I'm here to help, and TADDaemon with all it's time wasting is [http://forums.auran.com/trainz/showthread.php?102671-Insight-into-periodic-pauses-in-Surveyor&p=1192261#post1192261 NOT something which is working well or properly] in the real user world. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
: I'm a real world Trainz user too. My first version of Trainz was 1.1.1. I became a betatester for UTC, a content creator for TRS2004, and joined Auran around the time of TC3. I see TADDaemon as an immense improvement over the problems we had previously - particularly from a content creator workflow. As an end user, I /vehemently disagree/ with your apparent viewpoint that TADDaemon is the spawn of satan and should be killed with fire, and that doing so would fix all problems ever. It saves me countless hours waiting for Trainz or CM to start up. I can run multiple CM windows in parallel, and even Trainz at the same time as well, none of which was even remotely practical before TADDaemon. [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]]) 12:27, 21 August 2013 (EST)

I'm like Chris there, what counts is what I see, the trouble for you guys is we have thousands of times the number of eyes, time on the job and places where we're seeing insufficient progress, or worse, a [http://forums.auran.com/trainz/showthread.php?102671-Insight-into-periodic-pauses-in-Surveyor&p=1192261#post1192261 lack of attention or acknowledgement] that there are serious issues. I know of three long time content creators, people with hundreds of DLS assets created between them that won't use [[TS2009 SP3]] and beyond because of all the time TADDaemon wastes reconnecting when it should be connected (assuming it's needed at all), why it's active at all when we're in surveyor is a mystery. Makes no sense. You go with the local data base, no one is upgrading or downloading from in surveyor. [http://commons.wikimedia.org/wiki/File:Collected-Trianz-Releases-2013-0727,about_half_the_EnglishLang_Releases.jpg As you can see], I've got a few Trainz versions to choose from, and TS12 is not one anyone should be happy with as an operator given all it's pauses and time wastes. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
: TADDaemon *is* the local database. It existed in pretty much the same form before we split it into it's own process, and we did that because:
: * A Trainz crash used to reliably require a DB repair afterwards. Trainz would do it during the loading process. Just a black screen, no progress report. User reports at the time often suggested that Trainz needed a reinstall after crashing because it was "broken". I personally experienced this in TRS2006.
: * Multiple processes can use the database at once - e.g. CM and Trainz in parallel, multiple CM windows, etc.
: * It frees up process space for Trainz to use for other things. Just "maintaining the database listings" was starting to be a significant drain on process space for people with large installs.
: * People *can* and *do* download within the game - the content updates menu, when getting DLC packs, and when joining multiplayer sessions, to name the obvious ones.
:
: To address some other points: TADDaemon is continually necessary because it provides asset listings. When you use the tabs in surveyor, or the filter dialog, or in fact /anything that asks for a list of assets/ (which is way more common than you think as asset scripts can do it), TADDaemon is what gives you that list back. And Trainz can use the process space (i.e. RAM) freed up by using TADDaemon for other things. [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]]) 12:27, 21 August 2013 (EST)

So sorry if you're offended by my casual choice in language, but do credit that we are from different societies. That language doesn't raise anyone's eyebrows over here. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
: That kind of language doesn't raise eyebrows in "general society" here either - particularly the more, ummm, bogan parts of society. But it does a lot more than raise eyebrows in some of our critical markets, so we obviously don't want it easily visible in our end user documentation. [[User:Jamesmoody|Jamesmoody]] ([[User talk:Jamesmoody|talk]]) 12:27, 21 August 2013 (EST)

But do get used to having other computer professionals taking a serious look at your work, for as far as I'm concerned if I did my job as you guys have seemed to have done yours, the F-22 Raptor would crash every 99th flight, the Patriot missile would turn around and blast it's launcher or control vans, Laser eye surgery would burn through into peoples' cornea, and the Trident missile wouldn't ever threaten to launch from Ohio class submarines... so you'd likely be forcibly learning Chinese or Russian there down under. Those are only a fraction of the complex things I've been part of in my career, and when something runs worse than the version three releases before, something smells.

BTW, Given the ridiculously annoying wait for Parserfunctions, interwikis and so forth, I'm perfectly happy to wait for a talk response here. If you turn on email notification (since you are a site bureaucrat, that's in your toolkit) you can then see when pages change without using a watchlist tab.

The N3V staff admin seems to have trouble changing a boolean value when given a link to the how-to, don't you know. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)
:: You're making the assumption that he's remotely interested in taking advice on configuration from someone outside the company. Again, we work to our goals, not yours. [[User:Windwalkr|Windwalkr]] ([[User talk:Windwalkr|talk]]) 09:54, 21 August 2013 (EST)

Perhaps you can help him appear competent in that little thing. Like much of N3V's visible output, it's leaving a bad taste at the moment. Chris wants me to put up new user pages, in the Help namespace, but I'm not about to start that without further cleanup and having things straight first. I've already tagged too much using {{tl|FAB-todo}}, and for [http://online.ts2009.com/mediaWiki/index.php/Special:WhatLinksHere/Template:FAB-todo every page there], there are three that don't have an overt tag that are dependent upon ParserFunctions.

Best regards // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 09:11, 21 August 2013 (EST)

== Small words and big pictures ==

If you can use some small words and big pictures to explain to me why N3V wouldn't want the power of parserfunctions I'd really appreciate it. Having one template do ten things is much preferable than ten doing ten when the same branching and testing logic that allows that, can allow things like having pop-open collapsed elements like the table {{Tl|TBS}}. I'd like to make that and other such table structures where it makes sense so people can expand them or not as it suits them, allowing them to see a big picture in the context. // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 14:22, 12 October 2013 (EST)

== Please verify conclusion ==

Please verify the tag region is obsolescent as I inferred from config.txt entries whilst fixing errors. I made an appropriate [http://online.ts2009.com/mediaWiki/index.php/Index_of_Tags_%26_Containers#qu-rz annotation here] which should be verified. Thanks // [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 12:18, 13 October 2013 (EST)

Index of Tags & Containers

2013-10-13T01:15:33Z

Fabartus: /* qu-rz */ depreciate note

{{FUN-beg}}
===About this page===
This is a comprehensive list of tags and containers, where possible linked to the TrainzOnline detail page which covers the data element.
__NOTOC__
{| style="verticle-align:top; border: 2px solid grey; float:center;padding:1ex; align:center; margin-left:2.5%;margin-right:2.5%;"
! Navigable Click-table as Table of Contents
|-
|<hr/>Words beginning with strings between...
|-
|<big>
;{{void
}}[[{{PAGENAME}}#aa-ar|aa-ar]] {{void
}}[[{{PAGENAME}}#as-at|as-at]] {{void
}}[[{{PAGENAME}}#au-az|au-az]] {{void
}}[[{{PAGENAME}}#ba-bo|ba-bo]] {{void
}}[[{{PAGENAME}}#br-cg|br-cg]] {{void

}}[[{{PAGENAME}}#ch-cz|ch-cz]] {{void
}}[[{{PAGENAME}}#da-dz|da-dz]] {{void
}}[[{{PAGENAME}}#ea-ez|ea-ez]] {{void
}}[[{{PAGENAME}}#fa-gz|fa-gz]] {{void
}}[[{{PAGENAME}}#ha-hz|ha-hz]] {{void

}}[[{{PAGENAME}}#ia-iz|ia-iz]]
;{{void

}}[[{{PAGENAME}}#ka-kz|ka-kz]] {{void
}}[[{{PAGENAME}}#la-lz|la-lz]] {{void
}}[[{{PAGENAME}}#ma-mz|ma-mz]] {{void
}}[[{{PAGENAME}}#na-nz|na-nz]] {{void
}}[[{{PAGENAME}}#oa-oz|oa-oz]] {{void

}}[[{{PAGENAME}}#pa-pz|pa-pz]] {{void
}}[[{{PAGENAME}}#qu-rz|qu-rz]] {{void
}}[[{{PAGENAME}}#sa-sz|sa-sz]] {{void
}}[[{{PAGENAME}}#ta-tz|ta-tz]] {{void
}}[[{{PAGENAME}}#ua-vz|ua-vz]] {{void

}}[[{{PAGENAME}}#wa-zz|wa-zz]] 
</big>
|}
{{-}}

==aa-ar==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|accel
|float,float
|smoke {
|smoke block
|Acceleration. First number is Gravity effect, second is wind effect. Default is 0,0.
|-
|adhesion
|?
|motor {
|engine
|?
|-
|air-drag-coefficient
|?
|motor {
|engine
|?
|-
|alias
|kuid
|config.txt
|general
|Kuid of the asset to be referenced as a basis for the new asset. For example TRS Traincars can reference archived locomotive mesh assets for use with custom textures. This process is done by aliasing the KUID of the archived traincars.
|-
|alias
|kuid
|config.txt
|paintshed-skin
|the kuid of the paintshed template the paintshed reskin is based on
|-
|allowed-categories {
|subcontainer
|queues-ID {
|industry
|The allowed product categories in this queue.
|-
|allowed-products {
|subcontainer
|queues-ID {
|industry
|The allowed products in this queue.
|-
|allows-mixing
|boolean
|config.txt
|product
|Products with this tag may be combined in a single queue along with other products of the same category. Eg. Lumber and 20ft Container on a flatcar. By default, allows-mixing is set to 0. Therefore by default, a queue will only allow one product-category at a time. To look at allows-mixing from another angle, liquid products should never have allows-mixing enabled. Otherwise you have the potential to mix petrol with oil within the same tanker.
|-
|altitude
|?
|config.txt
|region
|altitude of this region
|-
|ambient
|boolean
|soundscript-ID {
|mesh object
|0 or 1, default 0 is off. Ambient sounds have no 3D “position” and may be stereo. Non-ambient (positional) sounds are positioned on the object and must be mono - see attachment above
|-
|amount
|float
|inputs-ID {
|industry
|Amount required as input.
|-
|amount
|float
|outputs-ID {
|industry
|Amount to output.
|-
|angle
|float list degrees
|config.txt
|turntable
|Specifies the angles at which the turntable stops. Not used if the turntable is set up as animation.
|-
|angles
|float list
|mesh-table-ID {
|interior
|Rotational boundaries in radians relative to its attachment point.
|-
|anim
|[path/]filename.kin
|config.txt
|pantograph
|The “anim.kin” animation file for the pantograph
|-
|anim
|[path/]filename.kin
|effects-ID {
|animation effect
|Reference to the animation file (.kin)
|-
|anim
|[path/]filename.kin
|mesh-table-ID {
|mesh object
|The animation file (.kin) exported from 3dsmax.
|-
|animated-mesh
|mesh-table-ID {
|queues-ID {
|industry
|Animated mesh which changes as the queue becomes full.
|-
|animation-loop-speed
|float
|mesh-table-ID {
|mesh object
|This tag must be here if the asset is to animate when placed. If this tag is not here when placed the animation will not play by default, but may play if controlled by script. A different value (e.g. 0.5, 2.0) may be used in the tag to play the animation at a different speed from that created in 3dsmax.
|-
|animdist
|float
|config.txt
|bogey
|Leave this tag out if the bogey is not animated. The distance traveled in meters by the bogeys in 1 second (30 frames) of animation. Bogey animations (exported from 3ds Max) are called “anim.kin”.
|-
|}
==as-at==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|asset-filename
|string
|config.txt
|general
|Obsolete
|-
|att
|helper
|attached-trigger-ID {
|industry
|Attachment point (stored in the mesh file)
|-
|att
|helper
|effects-ID {
|effects-ID {
|The effect insertion point. The attachment point must be orientated correctly in 3dsmax.
|-
|att
|helper
|mesh-table-ID {
|mesh object
|The mesh (and animation if present) is inserted at a mesh attachment point rather than the origin (without this line the mesh is placed relative to the origin of the parent model).
|-
|attached-track {
|container
|config.txt
|scenery with track
|Auto-generated spline track. Generated through attachment points located within the default mesh. Attached-tracks update automatically to the spline track connected to it. You may over-ride this auto-update feature by adding useadjoiningtracktype 0 Note. Correct track end attachment orientation is essential. The Y axis must point ‘out’ at the correct angle. The Z axis must point ‘up’.
|-
|attached-track-ID {
|subcontainer
|attached-track {
|scenery with track
|User supplied identifier
|-
|attached-trigger {
|container
|config.txt
|industry
|A Trigger is a point along an attached track with a specified radius. When a compatible rollingstock item enters this radius it triggers a set of commands,controlled through its script.
|-
|attached-trigger-ID {
|User supplied identifier
|attached-trigger {
|industry
|User supplied identifier
|-
|attachment
|helper
|smoke# {
|smoke block
|The attachment point (stored in the mesh file) to place the smoke effect.
|-
|attachment
|helper
|soundscript-ID {
|mesh object
|Attachment point on the object to which the sound is attached. Default: The sound will attach to the origin of parent object (not used for ambient sound)
|-
|attachment-points {
|subcontainer
|queues-ID {
|industry
|List of attachment points for this queue on which products are visualised. (Use this, OR animated-mesh)
|-
|att-parent
|mesh-table-ID {
|mesh-table-ID {
|mesh object
|The tag tells Trainz in which mesh the attachment point is located. The insertion attachment point is located within the mesh ‘name’ , as listed in the config.txt.
|-
|}
==au-az==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|author
|string
|config.txt
|general
|Author, contact-email and contact-website are useful information, particularly if a user has a question on your models or would like to offer help or suggestions.
|-
|autobrakecylinder
|?
|volume {
|engine
|?
|-
|autobrakecylinder_start
|?
|pressure {
|engine
|?
|-
|autobrakecylindervent
|?
|flowsize {
|engine
|?
|-
|auto-create
|boolean
|mesh-table-ID {
|mesh object
|The model is generated automatically when placed, or when you load a map which includes the model. In some instances you don’t want the mesh visible (as this may be controlled through script). If auto-create is 0 the mesh will not be visible when placed.
|-
|autoname
|boolean
|config.txt
|general
|When enabled, automatically assigns a unique name to this object as it is placed.
|-
|autopilotmode
|boolean
|driver-settings {
|activity
|AI driver setting. (off, on)
|-
|auxreservoir
|?
|volume {
|engine
|?
|-
|auxreservoir_autobrakecylinder
|?
|flowsize {
|engine
|?
|-
|auxreservoir_no3
|?
|flowsize {
|engine
|?
|-
|auxreservoir_start
|decimal
|pressure {
|engine
|Auxiliary reservoir pressure on loading the game.
|-
|auxreservoir_trainbrakepipe
|?
|flowsize {
|engine
|?
|-
|auxreservoirvent
|?
|flowsize {
|engine
|?
|-
|axle-count
|?
|motor {
|engine
|?
|-
|-
|}
==ba-bo==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|backdrop
|boolean
|config.txt
|scenery
|Specifies whether the object is treated as a backdrop or not. (stays visible even when far from the camera)
|-
|bendy
|boolean
|config.txt
|splines
|Switches how track is bent on corners, set as 1 allows the mesh to be deformed as the spline is bend around corners.
|-
|bogey
|kuid
|bogeys-ID {
|traincar
|Kuid of bogey asset.
|-
|bogey
|kuid
|config.txt
|traincar
|The bogey KUID number (default for a.bog0 and a.bog1)
|-
|bogey
|kuid
|tracksound {
|Tracksound
|The bogey to which this sound will apply.
|-
|bogey-#
|kuid
|config.txt
|traincar
|The bogey KUID number for a.bog# (Used only if different to a.bog0)
|-
|bogey-#-r
|kuid
|config.txt
|traincar
|Used instead of ‘bogey’ and bogey-1. The bogey will have reversed orientation. Note: This will cause bogey animation to play in reverse unless the attachment point for the bogey is also rotated 180 degrees in 3dmax.
|-
|bogey-r
|kuid
|config.txt
|traincar
|Used instead of ‘bogey’ and bogey-1. The bogey will have reversed orientation. Note: This will cause bogey animation to play in reverse unless the attachment point for the bogey is also rotated 180 degrees in 3dmax.
|-
|bogeys {
|container
|config.txt
|traincar
|The bogey container stores the bogeys used for the loco\rollingstock item.
|-
|bogeys-ID {
|subcontainer
|bogeys {
|traincar
|User supplied identifier
|-
|boiler-to-piston-flow
|?
|steam {
|steam-engine
|?
|-
|boiler-volume
|?
|steam {
|steam-engine
|?
|}
==br-cg==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|brakefull
|decimal
|pressure {
|engine
|Brake pipe pressure in grams/m³ after full service reduction (for self lapping brakes).
|-
|brakeinitial
|decimal
|pressure {
|engine
|Brake pipe pressure in grams/m³ after initial service reduction (for self lapping brakes).
|-
|brakepipe
|decimal
|pressure {
|engine
|Brake pipe pressure in grams/m³ when fully charged.
|-
|brakeratio
|?
|motor {
|engine
|?
|-
|bridgetrack
|kuid
|config.txt
|splines
|Kuid of the track type to be used.
|-
|buffer-speed
|float metres/second
|config.txt
|trackside
|Used for buffers; specifies the maximum speed up to which the buffer will stop a train.
|-
|burn-rate
|decimal
|steam {
|steam-engine
|How much coal in kg/s is consumed when the loco is operating at the test parameters
|-
|burn-rate-idle
|decimal
|steam {
|steam-engine
|How much coal in kg/s is consumed when the loco is idle, purely to keep the fire burning
|-
|cabinsway
|float
|config.txt
|traincar
|Cabin sway multiplier. Eg -2.
|-
|camera#
|float list
|cameralist {
|interior
|A camera contains 5 numeric coordinates that determine the placement and orientation of the camera. These are: 0,0,0,0,0 =left/right, front/back, up/down, yaw, pitch To determine these variables add -freeintcam to the trainzoptions.txt. Pan around the interior using arrow keys and mouse. Co-ordinates are displayed at bottom-left of screen. industry asset’s script file.
|-
|cameradefault
|integer
|config.txt
|interior
|The in-cab camera view Trainz defaults to when entering the cab.
|-
|cameralist {
|container
|config.txt
|interior
|List of camera viewpoints
|-
|car#
|kuid
|config.txt
|map
|Each of these tags stores the kuid of a car to be used on the roads.
|-
|car#
|kuid
|config.txt
|region
|Each of these tags stores the kuid of a car to be used on the roads.
|-
|carrate
|float seconds
|config.txt
|splines
|Defines traffic density on road (minimum seconds between each car generated). 0 = No traffic. Number must be greater than 3.
|-
|casts_shadows
|boolean
|config.txt
|splines
|Toggles whether the shadow model is displayed.
|-
|category-class
|class code
|config.txt
|general
|The class code for this asset.
|-
|category-era
|era code
|config.txt
|general
|Era code list.
|-
|category-era-#
|era list
|config.txt
|general
|Era code.
|-
|category-keywords
|keyword list
|config.txt
|general
|Keyword list
|-
|category-region
|region list
|config.txt
|general
|A list of REGION codes or REGION GROUP codes,
|-
|category-region-#
|region code
|config.txt
|general
|A REGION code or REGION GROUP code.
|}
==ch-cz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|changeability
|0/1/2
|driver-settings {
|activity
|Propensity for weather to change. (none, periodic, extreme)
|-
|chunky_info
|float list
|config.txt
|splines
|These values (in metres) define the shape of the mesh created for the track.
|-
|chunky_mesh
|folder
|config.txt
|splines
|Name of texture to apply to rail. The texture must be within a directory of the same name (ie. “textureName\textureName.texture.txt”). The chunky_mesh value will simply be the name of this directory (ie. “textureName”).
|-
|class
|string
|config.txt
|general
|This refers to the class of asset within the script file (the class must match that stated in the script).
|-
|clutter-mesh
|kuid
|config.txt
|groundtexture
|Ground textures can now reference a mesh and insert the mesh automatically as the ground is painted. Painting over a clutter-mesh ground texture effectively deletes clutter meshes and texture. The mesh it refers to is can be standard scenery object kind mesh. Clutter-meshes must have only one Max material assigned to it only. Polycounts must be very low.
|-
|collate-meshes
|?
|config.txt
|trackside
|Enables clutter-mesh support (eg. fast trees)
|-
|collision-parent
|mesh-table-ID {
|mesh-table-ID {
|interior
|For collision-proxy meshes in an interior mesh-table, this specifies the parent object to be proxied. is 3.
|-
|color
|rgb value
|smoke# {
|smoke block
|The R,G,B color value of the effect.
|-
|company
|string
|config.txt
|traincar
|The Locomotive or car owner
|-
|compressor
|integer
|flowsize {
|engine
|Flowsize of the compressor
|-
|compressor
|decimal
|pressure {
|engine
|Compressor maximum pressure in grams/m³
|-
|conesize
|?
|smoke# {
|smoke block
|?
|-
|conflicts-with queues {
|subcontainer
|queues-ID {
|industry
|This queue and the conflicting queue(s) cannot be used simultaneously.
|-
|consists {
|container
|config.txt
|industry
|The consists tag stores information on consists that can be generated by the industry.
|-
|consists-ID {
|subcontainer
|consists {
|industry
|User supplied identifier
|-
|consists-vehicle-ID {
|subcontainer
|consists-ID {
|industry
|User supplied identifier
|-
|contact-email
|string
|config.txt
|general
|Author, contact-email and contact-website are useful information, particularly if a user has a question on your models or would like to offer help or suggestions.
|-
|contact-website
|string
|config.txt
|general
|Author, contact-email and contact-website are useful information, particularly if a user has a question on your models or would like to offer help or suggestions.
|-
|controlmethod
|0/1
|driver-settings {
|activity
|Driver control setting. (dcc, cabin)
|-
|coupling-mask
|boolean
|consists-ID {
|industry
|Coupling mask that applies to the consist. 0 will block off all coupling activity while “1” will mean you can couple with a vehicle.
|-
|critical-animation
|boolean
|mesh-table-ID {
|mesh object
|When enabled, this forces the animation to continue playing when off screen. Impacts performance when enabled.
|-
|custom-attachments
|?
|queues-ID {
|industry
|Not used.
|}
==da-dz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|decoupling-mask
|boolean
|consists-ID {
|industry
|Coupling mask that applies to the consist. 0 will mean you can’t decouple vehicles in the train while 1 means you can decouple vehicles.
|-
|default {
|subcontainer
|mesh-table {
|mesh object
|Main mesh of the asset
|-
|defaultjunction
|kuid
|config.txt
|region
|Default type of junction in this region.
|-
|default-mesh
|kuid
|effects-ID {
|attachment effect
|The KUID of the attached mesh.
|-
|default-night {
|subcontainer
|mesh-table {
|mesh object
|‘Main’ night window mesh on scenery and industry and traincar assets. Modeled to the same 3d space as the default mesh and is inserted at the default mesh origin.
|-
|default-night-forward {
|subcontainer
|mesh-table {
|mesh object
|The name for a submesh attached to a locomotive, to show a beam of light for example, in the direction of movement of the locomotive. Trainz recognises the name and turns on the correct mesh depending on the running direction.
|-
|default-night-reverse {
|subcontainer
|mesh-table {
|mesh object
|The name for a submesh attached to a locomotive, to show a beam of light for example, in the direction of movement of the locomotive. Trainz recognises the name and turns on the correct mesh depending on the running direction.
|-
|deraillevel
|0/1/2
|driver-settings {
|activity
|Derail setting. (none, arcade, realistic)
|-
|description
|string
|config.txt
|general
|Description of the asset.
|-
|description-##
|string
|config.txt
|general
|Translated description of the asset.
|-
|dighole
|float length, width
|config.txt
|scenery
|Specifies the number of grid segments (length, width) to be removed from the surveyor grid to accommodate the turntable pit.
|-
|direct-drive
|boolean
|config.txt
|bogey
|When direct-drive is present, the bogey animation is linked to the steam piston and physics system. If this tag is not included the piston and steam sounds will not work!
|-
|direction
|vector
|smoke# {
|smoke block
|The vector at which the smoke travels.
|-
|directional
|boolean
|effects-ID {
|corona effect
|The default for coronas is to be aligned to the attachment point to face the NEGATIVE Z direction. This is especially useful for Traincars.
|-
|disable-extra-track-sounds
|boolean
|config.txt
|traincar
|Disables the “click-clack” tracksounds. (0, 1)
|-
|distance
|min, max metres
|soundscript-ID {
|mesh object
|2 numbers (meters) 1st number is the distance at which the sound is played 100% 2nd number is the cut-off distance. Doesn’t affect the volume of the sound (Default: 50m, 150m)
|-
|ditch_color
|rgb value
|config.txt
|traincar
|RGB ditch light color. Eg. 255,255,255.
|-
|divider
|folder
|config.txt
|splines
|Name of the model to use as the middle bridge section. Placed in subfolder with same name.
|-
|don’t-flip-terminator
|boolean
|config.txt
|splines
|Terminator model isn’t mirrored on one side.
|-
|driver-settings {
|container
|config.txt
|activity
|Specify the settings of this scenario, similar to Driver’s settings screen
|-
|duration
|float
|process-ID {
|industry
|Length of time (in seconds) that the process runs for.
|-
|dynamic-brake {
|container
|dynamic-brake container
|engine
|A sequence of numeric subcontainer data structures referring to a specific throttle notch and specifying the speed (m/s) and a braking force (kN) value which together define a braking force graph for that throttle notch
|}
==ea-ez==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|effects {
|subcontainer
|mesh-table-ID {
|mesh-table-ID {
|Optional mesh-table variations
|-
|effects {
|subcontainer
|mesh-table-ID {
|mesh object
|Optional mesh-table variations
|-
|effects-ID {
|subcontainer
|effects {
|effects {
|User supplied identifier
|-
|enabled
|boolean
|smoke# {
|smoke block
|Specifies whether the effect is enabled.
|-
|endcolor
|rgb value
|smoke# {
|smoke block
|The final color the smoke effect shifts to.
|-
|endlength
|float metres
|config.txt
|splines
|Length in meters of the initiator and terminator models.
|-
|engine
|boolean
|config.txt
|traincar
|States type of traincar. 0 for Rolling stock, 1 for Locomotive.
|-
|enginesound
|kuid
|config.txt
|traincar
|References the KUID number for the traincar’s sound.
|-
|enginespec
|kuid
|config.txt
|traincar
|References the engine KUID number. This specifies the driver physics boundaries for the traincar.
|-
|epreservoirpipe
|decimal
|flowsize {
|engine
|Flowsize of the electric pneumatic braking
|-
|epreservoirpipe
|decimal
|volume {
|engine
|For electro pneumatic braking. Not currently in use, generally leave this setting
|-
|epreservoirpipe_autobrakecylinder
|decimal
|flowsize {
|engine
|Flowsize of the electro pneumatic automatic brake cylinder reservoir.
|-
|epreservoirpipe_start
|?
|pressure {
|engine
|For electro pneumatic braking. Not currently in use, generally leave this setting.
|-
|equaliser
|decimal
|volume {
|engine
|Equalising reservoir volume.
|-
|equaliser_mainreservoir
|decimal
|flowsize {
|engine
|Flowsize of the equaliser main reservoir
|-
|equaliser_start
|decimal
|pressure {
|engine
|Equalising Reservoir pressure on loading Trainz
|-
|equaliservent
|decimal
|flowsize {
|engine
|Flowsize of the equaliser vent
|-
|equaliserventemergency
|decimal
|flowsize {
|engine
|Flowsize of the emergency equaliser vent
|-
|equaliserventhandleoff
|decimal
|flowsize {
|engine
|Flowsize of the equaliser to the atmosphere when in the "handle off" position
|-
|extensions {
|container
|config.txt
|all
|Asset specific data.
|}
==fa-gz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|faces
|camera/motion/down
|smoke# {
|smoke block
|The direction the smoke effect faces.
|-
|face-texture
|[path/]filename.texture
|config.txt
|drivercharacter
|This is the driver icon used in TRS. Must be 64x64 pixels
|-
|facing
|boolean
|consists-vehicle-ID {
|industry
|Indicates the direction of the vehicle.
|-
|file
|[path/]filename.tfx
|smoke# {
|smoke block
|The twinkle file to be used (optional).
|-
|firebox-efficiency
|decimal (0.0 -> 1.0)
|steam {
|steam-engine
|Efficiency of the firebox (higher is more efficient)
|-
|firebox-to-boiler-heat-flow
|decimal
|steam {
|steam-engine
|Rate of heat flow from firebox to boiler
|-
|firebox-to-boiler-heat-flow-idle
|decimal
|steam {
|steam-engine
|Rate of heat flow from firebox to boiler when idle
|-
|firebox-volume
|
|steam {
|steam-engine
|Physical volume of firebox in litres
|-
|flowsize {
|container
|config.txt
|engine
|Flowsize settings specify the rate of flow through the pipes.
|-
|fontcolor
|rgb value
|effects-ID {
|corona effect
|The color of the sign text in r.g.b.
|-
|fonts
|integer
|config.txt
|traincar
|Indicates how many types of numbering fonts used.
|-
|fontsize
|float metres
|effects-ID {
|corona effect
|The size of the sign text
|-
|fonts-path
|folder
|config.txt
|traincar
|Replaces asset-filename usage for ‘fonts’.
|-
|frame-rate
|float frames/second
|config.txt
|turntable
|Generally make this 30 (frames per second)
|-
|frequency
|float
|effects-ID {
|corona effect
|This variable specifies the flash frequency in Hz, e.g. 1 for once per second, 0.5 for once every 2 seconds, 2 for twice per second.
|-
|fuel
|decimal
|mass {
|engine
|Fuel level, not currently in use
|-
|fuel-energy
|decimal
|steam {
|steam-engine
|Relative energy in kilojoules per kilogram of coal
|-
|function
|'TrackSignal'
|config.txt
|trackside
|Must be set to 'TrackSignal'
|-
|grounded
|float metres
|config.txt
|splines
|Height in meters for the road to be offset from terrain.
|}
==ha-hz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|height
|float metres
|config.txt
|splines
|Height from the track level to the base. Must be a negative value in order to raise the bridge above the ground.
|-
|height
|integer
|thumbnails-ID {
|all
|Image height
|-
|height
|negative metres
|config.txt
|scenery
|Height from the track level to the base. Should be negative.
|-
|height-range
|min,max metres
|config.txt
|scenery
|height-range min, max eg: height-range –10, 100. Where min and max are values in meters.
|-
|hidden
|boolean
|config.txt
|splines
|Prevents the spline from being rendered.
|-
|highspeedexhauster
|decimal
|pressure {
|engine
|For vacuum braking - not currently in use
|-
|highspeedexhauster_vacuumbrakepipe
|decimal
|flowsize {
|engine
|For vacuum braking
|-
|hornsound
|kuid
|config.txt
|traincar
|References the KUID number for the traincar horn sound.
|}
==ia-iz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|icon0
|kuid
|config.txt
|general
|Deprecated. Use thumbnails container
|-
|icon1
|kuid
|config.txt
|general
|Deprecated. Use thumbnails container
|-
|icon2
|kuid
|config.txt
|general
|Deprecated. Use thumbnails container
|-
|icon3
|kuid
|config.txt
|general
|Deprecated. Use thumbnails container
|-
|icon-texture
|[path/]filename.texture
|config.txt
|product
|The in-game representation of the product when specifying the load type for a compatible rollingstock item (driver) Should be a 64x64 TGA.
|-
|image
|[path/]filename
|thumbnails-ID {
|all
|Image filename
|-
|indbrakefull
|?
|pressure {
|engine
|?
|-
|independantbrakecylinder
|?
|volume {
|engine
|?
|-
|independantbrakecylinder_start
|?
|pressure {
|engine
|?
|-
|info-page
|[path/]filename.html
|config.txt
|profile
|Filename of the HTML information page for the session.
|-
|inherit-velocity
|?
|smoke# {
|smoke block
|?
|-
|initial-boiler-temperature
|?
|steam {
|steam-engine
|?
|-
|initial-count
|integer
|queues-ID {
|industry
|The initial number of items in the queue.
|-
|initiator
|folder
|config.txt
|splines
|Name of model to use at start of bridge, placed in subfolder with same name.
|-
|inputs {
|subcontainer
|processID {
|industry
|Input process list
|-
|inputs-ID {
|subcontainer
|inputs {
|industry
|User supplied identifier
|-
|instance-type
|'instance'/'resource'
|config.txt
|product
|Instance-type: 'resource' is used when there is no mesh, or one only mesh is referenced in the mesh table (Ie Liquids, Bulk loads etc). 'instance' is used when more than one mesh is in the mesh table Ie: Passengers, General Goods. 200 max.‘size’ per Asset.
|-
|interior
|kuid
|config.txt
|traincar
|References the KUID number for the traincar interior cab view.
|-
|interpolate
|?
|smoke# {
|smoke block
|?
|-
|invisible
|boolean
|config.txt
|splines
|Specifies whether the object is invisible.
|-
|isroad
|boolean
|config.txt
|splines
|Isroad/Istrack. Two boolean tags detailing the behavior of the bridge. If the isroad is set to true, then cars are placed on the bridge. Both values should not be set to true.
|-
|istrack
|boolean
|config.txt
|splines
|Isroad/Istrack. Two boolean tags detailing the behavior of the bridge. If the isroad is set to true, then cars are placed on the bridge. Both values should not be set to true.
|-
|istunnel
|boolean
|config.txt
|splines
|Disables smoke effects for trains on track with this tag set. Useful for tunnels, engine houses, snow sheds - anywhere you don't want smoke going through the roof of a structure.
|-
|junction-lever-mesh
|subcontainer
|junction-vertices-ID {
|fixed track
|The mesh (selected from the mesh table) to be used as a junction lever.
|-
|junction-vertex
|helper
|junction-vertices-ID {
|fixed track
|The attachment point (located in mesh file) at which to place the lever.
|-
|junction-vertices {
|container
|config.txt
|fixed track
|The Junction-Vertices Container contains the tags needed to handle the lever portions of a fixed track.
|-
|junction-vertices-ID {
|container
|junction-vertices {
|fixed track
|User supplied identifier
|}
==ka-kz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|keyframes
|integer list
|config.txt
|turntable
|Specifies where on the animation the turntable is to stop.
|-
|kind
|'animation'
|effects-ID {
|effects-ID {
|This effect is used when a mesh has a variety of animations. Usually the animations will be controlled by a script related to the asset.
|-
|kind
|'attachment'
|effects-ID {
|effects-ID {
|In TRS we now have the ability to attach a mesh into another mesh by referencing it’s KUID through a meshtable.
|-
|kind
|'corona'
|effects-ID {
|effects-ID {
|A corona is a ‘glow’ light effect. It is a simple texture that is inserted at an attachment point within the mesh. Coronas can be added to any asset that uses a meshtable.
|-
|kind
|interior object kind
|mesh-table-ID {
|interior
|The type of interior object the particular mesh is. Affects the behavior of the mesh in game. Kinds: lever (Levers, switches, dials etc), animated-lever (Animated Levers etc Eg. in steam cabs), collision-proxy (Mouse collisions for animated levers), needle (Gauge needles, Speedo, brake pres.), pullrope (Pull rope horn as in the F7), light (Wheelslip light)
|-
|kind
|kind
|config.txt
|general
|Asset kind.
|-
|kind
|'name'
|effects-ID {
|effects-ID {
|Some assets may have editable signs. When you set an asset’s name in surveyor through the Edit Properties icon (‘?’ icon) the signage can be set-up to automatically update. The variables can be set for each sign.
|-
|kind
|'texture-replacement'
|effects-ID {
|effects-ID {
|This effect was created for rolling stock items to swap the visible texture of bulk loads (such as coal or woodchips).
|-
|kuid
|kuid
|config.txt
|general
|Asset kuid
|-
|kuid-table {
|container
|config.txt
|all
|List of all required dependencies.
|-
|kuid-table-ID {
|kuid
|kuid-table {
|all
|User supplied identifier
|}
==la-lz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|latitude
|?
|config.txt
|region
|latitude of this region
|-
|left-passenger-door {
|subcontainer
|mesh-table {
|mesh object
|Predefined submesh identifier. Left side passenger doors.
|-
|length
|float metres
|config.txt
|splines
|Length of track segment in meters
|-
|levels {
|subcontainer
|tracksound {
|Tracksound
|Relative sound levels. The sound is silent until 0.1 m/s, ramping up in volume until 10.0 m/s, constant maximum after that. Note, a value below 0.1 will not play a sound.
|-
|licence
|string
|config.txt
|general
|User licence details
|-
|lifetime
|float
|smoke# {
|smoke block
|Time in seconds that smoke particles exist for. Default is 3.
|-
|light
|boolean
|config.txt
|scenery
|Sets lighting to be used for object to be ambient or directional. 0 sets ambient lighting and object is light by general light value, 1 sets directional light which is affected by the position of the sun.
|-
|light
|boolean
|mesh-table-ID {
|mesh object
|Sets lighting to be used for object to be ambient or directional. 0 sets ambient lighting and object is light by general light value, 1 sets directional light which is affected by the position of the sun.
|-
|light_color
|rgb value
|config.txt
|traincar
|RGB headlight color. Eg. 255,255,255.
|-
|lights {
|container
|config.txt
|mosignal
|Signal lighting container. A list of coronas attached to each light point. Coronas are stored in each signal object’s directory alongside it’s textures.
|-
|lights-ID {
|subcontainer
|lights {
|mosignal
|Light point identifier.
|-
|limits
|float list
|mesh-table-ID {
|interior
|Mathematical boundaries Trainz uses determine the objects function. These values vary as different objects use different mathematical units.
|-
|longitude
|?
|config.txt
|region
|longitude of this region
|-
|loop
|float seconds
|smoke# {
|smoke block
|Time in seconds to loop the smoke sequence. Only valid if mode is set to time.
|-
|loopdelay
|float seconds
|smoke# {
|smoke block
|Delay (in seconds) before the effect is played again.
|-
|looped
|boolean
|effects-ID {
|animation effect
|Looped 1 (optional) Use only if the animation is looping (repeating). Default 0 (i.e. not looped).
|-
|looping
|boolean
|config.txt
|turntable
|specifies that the turntable can go all the way around, rather than stopping at a certain point.
|}
==ma-mz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|mainreservoir
|?
|pressure {
|engine
|?
|-
|mainreservoir
|?
|volume {
|engine
|?
|-
|mainreservoir_ep
|?
|flowsize {
|engine
|?
|-
|mainreservoir_start
|?
|pressure {
|engine
|?
|-
|main-reservoir-volume
|?
|steam {
|steam-engine
|?
|-
|map-kuid
|kuid
|config.txt
|profile
|Kuid of the map attached to this session.
|-
|mass
|float kg
|config.txt
|product
|The physical mass of the product. For Containers and Passengers this is calculated in kilograms/unit, while for Liquid and Bulk loads this is calculated in kilograms/litre.
|-
|mass
|integer kg
|config.txt
|traincar
|Mass in kilograms
|-
|mass {
|container
|config.txt
|engine
|?
|-
|max-accel
|?
|motor {
|engine
|?
|-
|max-coupler-gap
|float metres
|config.txt
|traincar
|maximum gap expected between couplers of this type
|-
|max-decel
|?
|motor {
|engine
|?
|-
|max-distance
|float
|tracksound {
|Tracksound
|Maximum distance at which the sound is played. Eg 1000
|-
|max-fire-coal-mass
|?
|steam {
|steam-engine
|?
|-
|max-fire-temperature
|?
|steam {
|steam-engine
|?
|-
|maximum-volume
|?
|steam {
|steam-engine
|?
|-
|maxrate
|float
|smoke# {
|smoke block
|The maximum rate at which particles are emitted.
|-
|maxsize
|float
|smoke# {
|smoke block
|?
|-
|maxspeed
|?
|motor {
|engine
|?
|-
|maxspeedkph
|float
|smoke# {
|smoke block
|?
|-
|maxvoltage
|?
|motor {
|engine
|?
|-
|mesh
|[path/]filename.im
|mesh-table-ID {
|mesh object
|The mesh name. This may include a sub-path. ie: mesh nightwindows/nightwindows.im, where the file nightwindows.im has been placed in the subdirectory nightwindows.
|-
|mesh
|[path/]filename.lm
|mesh-table-ID {
|mesh object
|The mesh name. This may include a sub-path. ie: mesh nightwindows/nightwindows.im, where the file nightwindows.im has been placed in the subdirectory nightwindows.
|-
|mesh
|[path/]filename.pm
|mesh-table-ID {
|mesh object
|The mesh name. This may include a sub-path. ie: mesh nightwindows/nightwindows.im, where the file nightwindows.im has been placed in the subdirectory nightwindows.
|-
|mesh
|kuid
|config.txt
|drivercharacter
|This refers to the kuid of the mesh asset inserted in to the locomotive mesh at a.driver0 (when in the Driver Module).
|-
|mesh-table {
|container
|config.txt
|mesh object
|This is the new and preferred method of asset mesh placement for most mesh asset types. It gives huge control over mesh placement and animations. There are some asset types that cannot use a meshtable. These include all Bridges, Tunnels, Rails, Pantographs and other Spline Objects (eg. Fences or Catenaries).
|-
|mesh-table-ID {
|subcontainer
|mesh-table {
|mesh object
|User supplied identifier
|-
|mesh-table-ID {
|subcontainer
|mesh-table {
|interior
|User supplied identifier
|-
|min-distance
|float
|tracksound {
|Tracksound
|Minimum distance at which the sound is played. Eg 0.
|-
|minimum-volume
|?
|steam {
|steam-engine
|?
|-
|minrate
|float
|smoke# {
|smoke block
|The minimum rate at which particles are emitted.
|-
|minsize
|float
|smoke# {
|smoke block
|?
|-
|mode
|speed/anim/timeofday/time
|smoke# {
|smoke block
|Describes the mode or type of this smoke effect. This affects how start and period are interpreted. (time | speed | anim | timeofday).
|-
|mode0 {
|subcontainer
|mesh-table {
|trackside
|Mesh showing lever in first position
|-
|mode0 {
|subcontainer
|mesh-table {
|mesh object
|Predefined submesh identifier. Mesh showing lever in first position
|-
|mode1 {
|subcontainer
|mesh-table {
|trackside
|Mesh showing lever in second position
|-
|mode1 {
|subcontainer
|mesh-table {
|mesh object
|Predefined submesh identifier. Mesh showing lever in second position
|-
|motor {
|container
|config.txt
|engine
|?
|-
|mousespeed
|float
|mesh-table-ID {
|interior
|This controls the use of the mouse on screen. Use this to control the mouse speed and push/pull direction for levers and dials. • mousespeed -1 Inverts mouse direction. • mousespeed 2 Doubles mouse speed in default direction. • mousespeed -0.5 Inverts mouse direction and halves the speed.
|-
|moving-friction-coefficient
|?
|motor {
|engine
|?
|}
==na-nz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|name
|<blank>
|effects-ID {
|name effect
|Leave blank to allow the name to be inserted by script without an initial default.
|-
|name
|'name'
|effects-ID {
|name effect
|When name name is specified, it uses the asset’s changeable name. Changed through the Edit Properties icon (the ‘?’ icon) in Surveyor.
|-
|name
|string
|effects-ID {
|name effect
|The default text when placed. If name Graceland (for example) was used, the sign would never be able to be changed even though the user may have changed the asset’s name in Surveyor.
|-
|night
|[path/]filename.tga
|config.txt
|environment
|Name of image file for night sky. File should be 256 x 256 pixel 24bit tga. The file extension should be excluded here, ie “QLD_Sky” rather than "qLD_Sky.texture.txt”.
|-
|night-mesh-base
|mesh-table-ID {
|mesh-table-ID {
|mesh object
|The mesh to which 'default-night' is linked. If the 'night-mesh-base' is hidden then 'default-night' will not be displayed.
|-
|nightmode
|home/lamp/constant
|config.txt
|scenery
|Only add this tag if you reference a default-night mesh in the mesh-table. Values: home, lamp or constant.
|-
|no3pipe
|?
|flowsize {
|engine
|?
|-
|no3pipe
|?
|volume {
|engine
|?
|-
|no3pipe_autobrakecylinder
|?
|flowsize {
|engine
|?
|-
|no3pipe_mainreservoir
|?
|flowsize {
|engine
|?
|-
|no3pipe_start
|?
|pressure {
|engine
|?
|-
|no3pipevent
|?
|flowsize {
|engine
|?
|-
|no4pipe
|?
|flowsize {
|engine
|?
|-
|no4pipe
|?
|volume {
|engine
|?
|-
|no4pipe_start
|?
|pressure {
|engine
|?
|-
|normal
|[path/]filename.tga
|config.txt
|environment
|Name of image file for normal sky. File should be 256 x 256 pixel 24bit tga. The file extension should be excluded here, ie “QLD_Sky” rather than "qLD_Sky.texture.txt”.
|-
|nostartdelay
|boolean
|soundscript-ID {
|mesh object
|0 or 1, default 0 If not set, the sound will have a short delay before playing, this stops flanging (flanging is a really nasty sound caused when several copies of the same sound are played at once).
|-
|notches
|float list
|mesh-table-ID {
|interior
|The position of notches within the angle boundaries. These are represented as decimal points between and including 0 and 1.
|-
|notchheight
|float list
|mesh-table-ID {
|interior
|The size of the notches specified.
|}
==oa-oz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|object-size
|float metres
|effects-ID {
|corona effect
|Size of the corona on the object when viewed up close Defaults to 0.15 (i.e. 0.15m)
|-
|obsolete-table {
|container
|config.txt
|all
|The obsolete-table describes the asset’s revision history.
|-
|ontheright
|boolean
|config.txt
|region
|Cars drive on the right side of the road.
|-
|opacity
|0..1
|mesh-table-ID {
|mesh object
|Controls the opacity of the mesh. Zero (invisible, not recommended) or one (solid).
|-
|opacity
|0..1
|mesh-table-ID {
|interior
|Usually used for the window mesh to give transparency (and the impression of reflection).
|-
|organisation
|string
|config.txt
|general
|Organisation name will show in Trainz in Railyard as the organisation for the model, for instance if you use Joe’s Trainz or Cripple Creek Logging Company.
|-
|origin
|string
|config.txt
|traincar
|The Country Abbreviation.
|-
|outputs {
|subcontainer
|process-ID {
|industry
|Output process list
|-
|outputs-ID {
|subcontainer
|outputs {
|industry
|User supplied identifier
|}
==pa-pz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|paintshed-skin-used
|kuid
|config.txt
|paintshed-skin
|Kuid of the paintshed skin used. (if applicable)
|-
|paintshed-skin-used
|kuid
|config.txt
|paintshed-template
|Kuid of the paintshed skin to be used for this template.
|-
|paintshed-template-used
|kuid
|config.txt
|paintshed-skin
|Kuid of the paintshed template used. (if applicable)
|-
|pantograph
|kuid
|config.txt
|traincar
|The pantograph kuid number inserted at a.pant0, a.pant1, etc. Use this tag only when needed.
|-
|passenger-height
|float metres
|config.txt
|industry
|This value sets the height of the passenger asset in metres, to suit the platform model height. (Doesn't work)
|-
|passenger-queue
|boolean
|queues-ID {
|industry
|Defines this as a passenger station queue.
|-
|period
|?
|smoke# {
|smoke block
|The usage of period depends on the value of the mode tag. If the mode is set to time, period is the duration of time this effect will remain active.
|-
|permit-commit
|boolean
|privileges {
|all
|Allows the end-user to commit changes to this asset.
|-
|permit-edit
|boolean
|privileges {
|all
|Allows the end-user to open this asset for editing
|-
|permit-listing
|boolean
|privileges {
|all
|Allows the end-user to view this object in the surveyor pickers (if it is of an appropriate kind.) Does not affect the visibility of the asset within the CMP asset list.
|-
|piston-angular-offsets
|?
|steam {
|steam-engine
|?
|-
|piston-area
|?
|steam {
|steam-engine
|?
|-
|piston-to-atmosphere-flow
|?
|steam {
|steam-engine
|?
|-
|piston-volume-max
|?
|steam {
|steam-engine
|?
|-
|piston-volume-min
|?
|steam {
|steam-engine
|?
|-
|pressure {
|container
|config.txt
|engine
|?
|-
|preview-mesh-kuid
|kuid
|mesh-table-ID {
|mesh object
|The mesh to be used in the surveyor preview area. This is useful when an asset has a large bounding box. Ie the "Airport” with it’s jet animation.
|-
|preview-scale
|float
|mesh-table-ID {
|mesh object
|Scale of the preview mesh.
|-
|priority
|float, 0 = highest
|tracksound {
|Tracksound
|The priority of the sound versus other sounds to be played. Lower values indicate a higher priority.
|-
|privileges {
|container
|config.txt
|all
|Limited content protection applies only to built-in (JArchived) assets.
|-
|processes {
|container
|config.txt
|industry
|Processes (required) The input and output settings of the industry. You can specify the amount of input and output for each queue referenced product as well as the duration (or rate) in seconds for that process to take place. All queues and processes are linked through the industry asset’s script file.
|-
|process-ID {
|subcontainer
|processes {
|industry
|User supplied identifier
|-
|product-category
|kuid
|config.txt
|product
|Kuid of applicable category for this product
|-
|product-id
|?
|config.txt
|paintshed-skin
|For paintshed support.
|-
|product-kuid
|kuid
|queues-ID {
|industry
|The product type used to fill ‘initial-count’
|-
|product-texture
|[path/]filename.texture
|config.txt
|product
|The texture to be used with load ‘texture-replacement’. Ie When a hopper loads woodchips instead of it’s default load of coal.
|-
|product-type
|?
|config.txt
|paintshed-skin
|For paintshed support.
|-
|product-version
|?
|config.txt
|paintshed-skin
|For paintshed support.
|}
==qu-rz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|queue
|queues-ID {
|inputs-ID {
|industry
|queue from which to take input.
|-
|queue
|queues-ID {
|outputs-ID {
|industry
|queue in which to place output.
|-
|queues {
|container
|config.txt
|industry
|The queues container states which product or products the industry can use. It contains the size of each product, the initial count when placed, and can refer to it’s visual load state whether through a load animation or attachment.
|-
|queues-ID {
|subcontainer
|queues {
|industry
|User supplied identifier
|-
|radius
|float
|attached-trigger-ID {
|industry
|Radius (in meters) of the trigger.
|-
|radius
|float
|mesh-table-ID {
|interior
|The notch position relative to the attachment point.
|-
|random-color-high-hsb
|hsb value
|config.txt
|scenery
|For clutter-mesh objects, specifies a color range for tinting purposes. HSB color space.
|-
|random-color-low-hsb
|hsb value
|config.txt
|scenery
|For clutter-mesh objects, specifies a color range for tinting purposes. HSB color space.
|-
|rate
|float particles/second
|smoke# {
|smoke block
|The rate of emission in particles per second for modes time, speed, and timeofday, or the number of particles to emit over the animation period for anim mode. Default is 4.
|- style="color:navy; background:lightyellow;"
|[[region]] (depreciated)
|region code
|config.txt
|general (obsolescent)
|Trainz 1.x legacy tag; the country region to which this asset belongs. This should be one of the Auran-supplied region names, but older content has shown full names.
|-
|repeat-delay
|random [min,max] seconds
|soundscript-ID {
|mesh object
|1 or 2 numbers (min, max, in sec) time to delay between the end of the sound playing, and playing it again randomised between(min .. max) default min is 0, default max is equal to min Notes: Repeat-delay now has two values rather than one. When upgrading old assets, make sure there is a repeat delay for both values or the sound will loop endlessly when triggered.
|-
|repeats
|integer
|config.txt
|splines
|The number of times the mesh is placed between spline points
|-
|resistance
|?
|motor {
|engine
|?
|-
|reversed
|boolean
|bogeys-ID {
|traincar
|Affects the direction of the bogey.
|-
|rgb
|rgb value
|config.txt
|splines
|This value should be left as default.
|-
|right-passenger-door {
|subcontainer
|mesh-table {
|mesh object
|Predefined submesh identifier. Right side passenger doors.
|-
|rollstep
|float degrees
|config.txt
|scenery
|Where n is a value in degrees. Used in conjunction with rotate-yz-range, rollstep lets you specify the step size of roll angles for this object. Other example values are 1, 5, 20 etc. The default rollstep is 1.0.
|-
|rotate
|boolean
|config.txt
|scenery
|Where n is 0 or 1 (default). This lets you disable rotation on a scenery object. 0 to disable, 1 to enable (default).
|-
|rotate-yz-range
|min,max degrees
|config.txt
|scenery
|Where min and max are values in degrees. This tag lets you set the roll / yz rotation range (normal object rotation is an xy rotation). If you want your scenery object to support rolling then use this tag to set the minimum and maximum roll range. By default, objects have a min/max roll range of 0 to 0.
|-
|rotstep
|float degrees
|config.txt
|general
|Where n is a value in degrees. This lets you specify the step size of rotation angles for this object. Other example values are 1, 10, 20, 90, 180 etc. The default rotstep is 1.0
|-
|running-number
|string
|consists-vehicle-ID {
|industry
|Running number of the vehicle.
|}

==sa-sz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|safety-valve-high-flow
|?
|steam {
|steam-engine
|?
|-
|safety-valve-high-pressure
|?
|steam {
|steam-engine
|?
|-
|safety-valve-low-flow
|?
|steam {
|steam-engine
|?
|-
|safety-valve-low-pressure
|?
|steam {
|steam-engine
|?
|-
|scale
|?
|smoke# {
|smoke block
|?
|-
|scale
|?
|mass {
|engine
|?
|-
|scale
|?
|pressure {
|engine
|?
|-
|scale
|?
|volume {
|engine
|?
|-
|script
|[path/]filename.gs
|config.txt
|general
|This refers to the name of the script file.
|-
|search-limit
|?
|config.txt
|trackside
|Not required. For internal use only.
|-
|shadow {
|subcontainer
|mesh-table {
|mesh object
|Predefined submesh identifier. Shadow mesh.
|-
|shadows
|?
|config.txt
|splines
|Undocumented
|-
|shift
|?
|smoke# {
|smoke block
|?
|-
|shovel-coal-mass
|?
|steam {
|steam-engine
|?
|-
|showhelp
|boolean
|driver-settings {
|activity
|Show Driver Help. (off, on)
|-
|show-in-consist-menu
|boolean
|consists-ID {
|industry
|Boolean flag that dictates whether this train appears in the consist menu (0 - false, 1 - true). The consist menu was along the bottom of the screen in the original Trainz and UTC but is no longer present. It effectively stopped a user from getting access to an AI train. Redundant for most uses except for legacy/scenario usage.
|-
|signals {
|container
|config.txt
|mosignal
|Sets out which aspects the signal is capable of displaying, and also which light points are activated when each state is displayed.
|-
|signals-ID {
|subcontainer
|lights {
|mosignal
|Signal point identifier.
|-
|size
|integer
|queues-ID {
|industry
|Size of queue.
|-
|smoke_fastlife
|float
|config.txt
|traincar
|Longevity of smoke particles at normal speed.
|-
|smoke_fastspeed
|?
|config.txt
|traincar
|?
|-
|smoke_height
|float
|config.txt
|traincar
|How hard particles are pushed out of the stack.
|-
|smoke_random
|float
|config.txt
|traincar
|Level of particle excitation.
|-
|smoke_shade
|float
|config.txt
|traincar
|Smoke opacity. (0 - 1)
|-
|smoke_slowlife
|float
|config.txt
|traincar
|Longevity of smoke particles at low speed.
|-
|smoken {
|container
|config.txt
|smoke block
|?
|-
|snapgrid
|float metres
|config.txt
|scenery
|Where n is a value in meters. This lets you specify the size of the grid the object snaps to. We recommend factors/fractions of 720 as this is the size of a base board and the positioning may do funny things across section borders. e.g. 1, 2, 5, 10, 20, 30, 40, 45, 60, 80, 90, 120, 180, 240, 360, 720. The default snapgrid is 10.
|-
|snapmode
|0/1/2
|config.txt
|scenery
|Where n is either 0 (default) , 1 or 2. Use snapmode to enable snapping of a scenery object to the snap grid. 0 will disable grid snapping (default), 1 will enable grid snapping, 2 will enable an offset grid snapping. Offset grid snapping will cause objects to be snapped to the grid but will also offset the object’s position by ½ the grid size – essentially positioning the object in between the normal grid lines.
|-
|sound {
|subcontainer
|soundscript-ID {
|mesh object
|List of .wav files to play (randomly picked)
|-
|soundscript {
|container
|config.txt
|mesh object
|Controls the looping sound made by the object.
|-
|soundscript-ID {
|subcontainer
|soundscript {
|mesh object
|User supplied identifier
|-
|speed
|float
|effects-ID {
|animation effect
|Speed factor of the animation. Default 1, 2 for double speed, 0.5 for half speed
|-
|speedlimit
|float metres/second
|config.txt
|trackside
|This value is the maximum speed allowed in meters per second
|-
|start
|?
|smoke# {
|smoke block
|The usage of stard depends on the value of the mode tag. If the mode is set to time, start is a set of time values in seconds after the creation of this effect’s parent object when this phase of the effect will start. If the mode is set to speed, start is a speed in meters per second (m/s) and period is not used. (Note: 1 m/s = 3.6 km/hr.) All other sequence attributes (rate, velocity, lifetime, minsize, maxsize) are interpolated so there are smooth transitions between phases. If the mode is set to anim, start is a value from 0.0 to 1.0 which describes the start time into the object’s animation cycle. If the mode is set to timeofday, start is a value from 0.0 to 1.0 which describes the time of day when this effect will start. Values range as follow: 0 - midnight, 0.25 - 6am, 0.5 - midday, 0.75 6pm, 1.0 - midnight.
|-
|start-enabled
|boolean
|process-ID {
|industry
|Specifies whether the process starts enabled.
|-
|startingtime
|0..1
|driver-settings {
|activity
|Time of day. Range is from 0 to 1 (0.5 - midday).
|-
|steam {
|container
|config.txt
|steam-engine
|?
|-
|storm
|[path/]filename.tga
|config.txt
|environment
|Name of image file for stormy sky. File should be 256 x 256 pixel 24bit tga. The file extension should be excluded here, ie “QLD_Sky” rather than "qLD_Sky.texture.txt”.
|-
|string-table {
|container
|config.txt
|all
|The string table stores a list of text strings to be used by the industry script.
|-
|string-table-## {
|container
|config.txt
|all
|These alternative string tables store translated strings
|-
|supports-null-driver-character
|boolean
|config.txt
|drivercommand
|Command can be executed without a driver present in the selected loco.
|-
|surface-area
|?
|motor {
|engine
|?
|-
|surveyor-name-label
|boolean
|config.txt
|general
|Specifies whether this item has floating name label text.
|-
|surveyor-only
|boolean
|config.txt
|general
|Adding this means the attached mesh will only be visible in Surveyor and not Driver.
|-
|surveyor-only
|boolean
|effects-ID {
|attachment effect
|Adding this means the attached mesh will only be visible in Surveyor and not Driver.
|}
==ta-tz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|tender
|boolean
|config.txt
|traincar
|Specifies that the traincar is a tender.
|-
|terminator
|folder
|config.txt
|splines
|Name of model to use at end of bridge, placed in subfolder with same name.
|-
|test-collisions
|boolean
|mesh-table-ID {
|interior
|Mouse cannot be used for this mesh. Collision mesh used instead. Ie animated-levers.
|-
|texture
|[path/]filename.texture
|config.txt
|general
|An image texture file.
|-
|texture
|[path]/filename.texture
|effects-ID {
|texture-replacement effect
|Texture reference denoting the texture file to be swapped by this effect.
|-
|texture
|kuid
|smoke# {
|smoke block
|Kuid of the texture to be used for the effect.
|-
|texture-kuid
|<blank>
|effects-ID {
|corona effect
|If the texture-kuid tag is not present the corona will use the default yellow/orange texture in TRS.
|-
|texture-kuid
|kuid
|effects-ID {
|corona effect
|Add this tag only when you want to specify your own texture for the corona. It specifies the KUID of a kind texture asset. See KIND TEXTURE.
|-
|textures {
|container
|config.txt
|texturegroup
|The textures container stores a list of additional textures to be used in the texture group.
|-
|three-part
|boolean
|config.txt
|hornsound
|Specifies that the hornsound has a beginning, middle and ending sound.
|-
|throttle-notches
|?
|motor {
|engine
|?
|-
|throttle-power {
|container
|config.txt
|engine
|?
|-
|thumbnails {
|container
|config.txt
|all
|Any asset may specify a thumbnail or preview image.
|-
|thumbnails-ID {
|subcontainer
|thumbnails {
|all
|User supplied identifier
|-
|timerate
|float
|driver-settings {
|activity
|Time progression. (1 - real-time, 2 - double speed etc.)
|-
|track
|kuid
|attached-track-ID {
|scenery with track
|Kuid of the track to be used.
|-
|track
|kuid
|tracksound {
|Tracksound
|The track type to which this sound will apply
|-
|track
|trackID
|attached-trigger-ID {
|industry
|The track name which the train must be on to trigger.
|-
|trackmark
|boolean
|config.txt
|trackside
|Specifies that the object is a trackmark.
|-
|trackoffsets
|float list, metres
|config.txt
|splines
|Distance in meters the rail/s are attached to the center of the spline. Any number of tracks can be attached to the spline, only splines with the same track offsets can be connected together.
|-
|track-parent
|kuid
|tracksound {
|Tracksound
|The parent (eg. bridge/industry/tunnel) of the track to which this sound will apply.
|-
|trackdirections
|float metres
|config.txt
|splines
|?
|-
|trackside
|float metres
|config.txt
|trackside
|This is a value that is the distance in meters the object is placed relative to the center of the track. Negative values will put the object on the left side of the track, and positive values will appear on the right.
|-
|track-sound
|kuid
|tracksound {
|Tracksound
|The kuid of the tracksound object to be used.
|-
|tracksound {
|container
|config.txt
|Tracksound
|A sound asset that is referenced by track or bogeys to play a different sound from the default track/train sound (for example when a train travels over a bridge or through a tunnel).
|-
|trainbrakepipe
|?
|flowsize {
|engine
|?
|-
|trainbrakepipe
|?
|volume {
|engine
|?
|-
|trainbrakepipe_reservoir
|?
|flowsize {
|engine
|?
|-
|trainbrakepipe_start
|?
|pressure {
|engine
|?
|-
|trainbrakepipevent
|?
|flowsize {
|engine
|?
|-
|trainz-build
|build code
|config.txt
|general
|The Trainz build is the version number for which this asset was created.
|-
|trigger
|boolean
|config.txt
|trackside
|Specifies that the object is a trigger.
|-
|trigger
|string
|soundscript-ID {
|mesh object
|A trigger may be used in an event file (.evt) associated with an animation. It plays at selected key frames of animation as defined in the event file. Sound files may triggered in this manner, and from scripting. Used in the mojunction example (switch lever) the “toggle” action is automatically triggered when the lever is operated and the sound plays.
|-
|turntable {
|mesh-table-ID {
|mesh-table {
|turntable
|Predefined submesh identifier
|-
|turntable {
|subcontainer
|mesh-table {
|mesh object
|Predefined submesh identifier.
|-
|two-part
|boolean
|config.txt
|hornsound
|Indicates that the Railyard and Driver hornsounds are different. The Driver hornsound is looping. If this tag is not present, the hornsound defauts to UTC equivalent non-looping format.
|-
|type
|string
|config.txt
|scenery
|Specify a type for the model that will be used in the Surveyor menu drop down menu for Track or Object type.
|}
==ua-vz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|uncached_alphas
|boolean
|config.txt
|splines
|This is used in certain situations to improve alpha sorting. This should only be set to 1 for tracks that use an alpha texture and are always placed flat
|-
|unit_mesh
|folder
|config.txt
|splines
|For mesh-reducing track, the filename of the long mesh, which must be placed in a subdirectory of the same name as the mesh. Only the file name is entered, not the directory name nor the file extension. For example, the full pathname and extension is “rockwall/rockwall.im”. Enter only “rockwall” in the text input box.
|-
|upright
|boolean
|config.txt
|splines
|Specifies whether the bridge “legs” point vertically, or perpendicular to the spline.
|-
|useadjoiningtracktype
|boolean
|attached-track-ID {
|scenery with track
|Indicates whether the track type should change to match that of the first track joined to the object.
|-
|use-gradient-track
|boolean
|config.txt
|scenery
|This means to use the spline gradient rather than following the ground height.
|-
|use-parent-bounds
|boolean
|mesh-table {
|mesh object
|Specifies that the mesh should use the bounds of the parent object for visibility culling. Use with caution.
|-
|username
|string
|config.txt
|general
|The human-readable English name of this asset.
|-
|username-##
|string
|config.txt
|general
|The human-readable translated name of this asset.
|-
|vacuumbrakecylinder
|?
|volume {
|engine
|?
|-
|vacuumbrakecylinder_start
|?
|pressure {
|engine
|?
|-
|vacuumbrakecylinder_vacuumbrakepipe
|?
|flowsize {
|engine
|?
|-
|vacuumbrakepipe
|?
|volume {
|engine
|?
|-
|vacuumbrakepipe
|?
|flowsize {
|engine
|?
|-
|vacuumbrakepipe_start
|?
|pressure {
|engine
|?
|-
|vacuumbrakepipereleasevent
|?
|flowsize {
|engine
|?
|-
|vacuumbrakepipevent
|?
|flowsize {
|engine
|?
|-
|vacuumbrakereservoir
|?
|volume {
|engine
|?
|-
|vacuumbrakereservoir_start
|?
|pressure {
|engine
|?
|-
|vacuumbrakereservoir_vacuumbrakepipe
|?
|flowsize {
|engine
|?
|-
|value-range
|min,max time of day
|soundscript-ID {
|mesh object
|2 numbers, currently used only for day/night sound effects. Midnight is 0.5, midday = 0.0 or 1.0 Where the numbers are not the same, this sets the start and end times for the sound to play. Default 0,0 (off)
|-
|vehicle
|kuid
|consists-vehicle-ID {
|industry
|The kuid of the vehicle to be used.
|-
|velocity
|float
|smoke# {
|smoke block
|The initial speed of emitted smoke particles. Default is 1.
|-
|vertices {
|subcontainer
|attached-track-ID {
|scenery with track
|Attachment points at which to place track.
|-
|visible-on-minimap
|boolean
|config.txt
|splines
|Specifies whether the object\track is displayed on the minimap.
|-
|volume
|0..1
|soundscript-ID {
|mesh object
|Gain of the sound Default 1.0 = 100%
|-
|volume {
|container
|config.txt
|engine
|?
|}
==wa-zz==
{| cellpadding="5" cellspacing="0" border="1"
|- style="background-color:#ffffcc;"
|width=15%|Tag or Container
|width=15%|Data Type
|width=15%|Parent
|width=15%|Applies to
|width=40%|Description
|-
|water
|kuid
|config.txt
|map
|Undocumented
|-
|watercolor
|rgb value
|config.txt
|region
|RGB color value of the water for the region.
|-
|water-injector-rate
|?
|steam {
|steam-engine
|?
|-
|wave-shift
|?
|effects-ID {
|corona effect
|Affects the flashing intensity pattren on the corona.
|-
|weather
|0..7
|driver-settings {
|activity
|Weather setting. (clear, cloudy, drizzle, rain, stormy, light snow, medium snow, heavy snow)
|-
|westinghouse-volume
|?
|steam {
|steam-engine
|?
|-
|width
|float metres
|config.txt
|splines
|Width of track mesh in meters.
|-
|width
|integer
|thumbnails-ID {
|all
|Image width
|-
|workingscale
|?
|config.txt
|map
|Undocumented
|-
|workingunits
|?
|config.txt
|map
|Undocumented
|-
|[["world-origin" container|world-origin]]
|container
|config.txt
|map
|Undocumented, latitude, longitude, and altitude
|-
|}
==Notes==
 

;TBDL - should have something here about things discarded, moved and used differently version to version.

==Categories==
{{ORP-bot}}<div> {{FUN-bot}}

"mesh-table" container

2013-10-12T15:49:04Z

Fabartus: /* Mesh subcontainer */ format, stub in values for strings.

{{ORP-top}}
==KIND Heirarchy==
The "mesh-table" container is a top-level [[config.txt file]] entry used by various [[Content_Configuration#Content_Types|Content Types]].

The mesh-table is a list of mesh subcontainers with no standalone tags. Each mesh subcontainer uses the following format. Tags are parsed in a standardised format, but not all [[Content_Configuration#Content_Types|Content Types]] support the full range of tags listed below. Each mesh derives its name from the subcontainer's tag name. These names are used to refer to specific meshes from within the mesh-table and also from script.

==Known Dependent Parent Types==
:''Main article, see: [[KIND Mesh]]''
The Content Types listed here use the mesh-table container as part of their definition.

* [[KIND Industry]]
* [[KIND MOJunction]]
* [[KIND Pantograph]]
* [[KIND Scenery]]
* [[KIND Track]]
* [[KIND Traincar]]

The following config containers also reference back to their Asset's mesh-table container in some fashion:
* [["junction-vertices" container]]
* [["track-lod-tree" container]]

'''See also'''{{bullR}} [[Modeling Guidelines]] {{bull}} [[Modeling Scenery]]
==Mesh subcontainer==
Each mesh subcontainer supports the following tags. Each tag is shown here with its default value. {{FAB-todo| Use Pseudo-table to recast as a real wikitable.}}
* The term 'filenamespec' is meant to convey the local pathspec (folder and subfolders) below the base folder of the asset (i.e. when opened for edit in Windows Explorer).
mesh-asset <NULLKUID>
mesh "text=path and name/ident"
anim "text=path and name/ident"
lod-level 255
mesh-season 255
att "text=filenamespec of attachment points"
att-parent "text=filenamespec of tbdl, unknown"
opacity 1.0
position 0,0,0
orientation 0,0,0
auto-create 0
use-parent-bounds 0
animation-loop-speed 0
critical-animation 1
effects {
}
night-mesh-base "text=filenamespec of ..."

==Supported Tags==
Each mesh subcontainer supports the following tags.

===mesh-asset===
Allows assets to be used as 'mesh libraries', the following container specifies that the mesh required (and its optional animation) is located relative to ''''''the root folder'''''' of <kuid:1234:5678>. CMP does not auto-check for the existence of these'' 'externally referenced files' ''when processing so you must ensure that they are present in the referenced kuid before using this tag. Subfolder paths within the asset can be used; folder names should be prefixed to the path with a forward slash ("/") separator in the usual fashion.

===mesh===
The ‘main’ mesh name. This may include a sub-path;
ie: mesh nightwindows/nightwindows.im, where the file nightwindows.im has been placed in the subdirectory nightwindows.

Use .im files exported from 3dsmax (as opposed to .pm.) or reference an .lm file if you wish your asset to have ‘Level of Detail’ mesh reduction.

Level of detail is a process of using different model meshes, depending on how far the viewer is from the model. A finer mesh is used for close up viewing in Trainz.

===anim===
The animation file (.kin) exported from 3dsmax. This may include a sub-path.

===lod-level===
The object LOD level at which this mesh is displayed. The default value (255) indicates that this mesh is visible at all detail levels. See also [[KIND Mesh]] for the 'mesh-detail-level' tag.

===mesh-season===
The season index for which this mesh is displayed. The default value (255) indicates that this mesh is visible in all seasons. See also [["Season-selector" container]].

===att===
The mesh (and animation if present) is inserted at a mesh attachment point rather than the origin (without this line the mesh is placed relative to the origin of the parent model).

===att-parent===
The tag tells Trainz in which mesh the attachment point is located. The insertion attachment point is located within the mesh ‘name’ , as listed in the config.txt.

===opacity===
opacity x (float 0.0 - 1.0 default 1.0)

Specifies the overall transparency of a mesh. Values other than 0.0 or 1.0 employ alpha blending and a value of 0.0 has the same effect as hiding the mesh.

Note that this tag is buggy in TS2009 prior to SP4.

===mesh-scale===
This tag defines a minimum and maximum scaling value for the mesh, where 1.0 is the size as modelled. Each instance of the mesh that exists in the world will randomise within this range. Randomisation will not change between runs or between Trainz editions, but may change based on factors such as the position of the mesh in the world. This tag is currently only supported on SpeedTree assets; attempts to use this tag on other assets results in undefined behaviour.

===position===
position X,Y,Z (in metres, default 0,0,0)

Specifies the location of a mesh relative to its insertion point.

===orientation===
orientation X,Y,Z (radians default 0,0,0)

Allows a submesh to be rotated relative to its insertion point. To reverse a mesh by 180 degrees about the Z axis, add the tag:

orientation 0,0,3.14159

===auto-create===
The model is generated automatically when placed, or when you load a map which includes the model. In some instances you don’t want the mesh visible (as this may be controlled through script). If auto-create is 0 the mesh will not be visible when placed.

===use-parent-bounds===
When enabled, this tag indicates that render culling should occur using the whole object's bounding box rather than this mesh's bounding box. Bounding boxes on individual meshes may not update correctly when animation moves the object's geometry any significant distance from the bind position. This flag can help mitigate such effects, at a tiny performance penalty.

===animation-loop-speed===
This tag must be here if the asset is to animate when placed. If this tag is not here when placed the animation will not play by default, but may play if controlled by script. A different value (e.g. 0.5, 2.0) may be used in the tag to play the animation at a different speed from that created in 3dsmax.

===light===
If set (which it is by default), this tag causes the non-stitched mesh to be linked into the Trainz lighting model. This causes the mesh to respond to directional lighting changes, such as the angle of the sun or train headlights. This is also necessary for normal maps to work correctly. Zeroing this tag will remove the mesh from the Trainz lighting model. Generally speaking, you should never zero this tag- almost every effect that can be achieved through this approach can be better served by using an appropriate normal map or appropriate geometry detail.

This tag has no effect on stitched meshes, which are always affected by the Trainz lighting. Since the content creator has no direct influence over which meshes are subject to [[Mesh Stitching]], and all indirect influences are subject to change between Trainz editions, it is strongly recommended that this tag is avoided to ensure that results are consistent.

===critical-animation===
"critical-animation" indicates that this mesh's animation generates events which are critical to the script system's behavior. If your asset is not scripted, does not use scripted animation events, or only uses the events for display purposes and will not break if the occasional event is missed, this tag should be set to ''false''. Leaving this flag set to ''true'' is a '''significant''' performance penalty.

===night-mesh-base===
This night mesh is linked to the specified mesh and is visible only at night. It is invisible if the specified mesh is invisible, (if the auto-create 0 line were used so the specified mesh can be controlled by script).

==Effects Container==
The effects container also contains a list of effect subcontainers. The effect subcontainers support the following generic tags.

kind ""
name ""

The effect subcontainers support additional tags depending on the effect kind. The following effect kinds are supported:

* [[Corona Effect]]
* [[Name Effect]]
* [[Attachment Effect]]
* [[Animation Effect]]
* [[Texture-Replacement Effect]]

==Mesh-Table Example==
The following is an example of a simple mesh-table which implements two levels of detail.

mesh-table
{
default-lod0
{
mesh "example-lod0.im"
auto-create 1
lod-level 0
}
default-lod1
{
mesh "example-lod1.im"
auto-create 1
lod-level 1
}
}

[[Category:Config Container|mesh-table container]]
{{ORP-bot|mesh-table container}}

Template:Pseudo-table

2013-10-12T15:45:11Z

Fabartus: +purpose statement and {{{other}}} parameter

"padding: 1em; border: 1px dashed rgb(47, 111, 171);color: black; background: rgb(249, 249, 249); width:{{{width|68%}}}; {{{other}}}"<noinclude>{{Doc-page-head}}

[[Category:Formatting templates|{{PAGENAME}}]]
{{SelfTdoc}}{{TypeTaid}}
;Purpose
This template provides compatible formatting to duplicate the appearance of the monospace tables the N3V staff used when building pages for Kinds, containers and so forth. Using this template to set the style allows a wikitable to neaten up the staffs ragged efforts, and make things more readable.

;usage
*This template is meant to be used after the <{{...}} style= {{tl|Pseudo-table}} > and forms the pre-quoted string above.
* The default width is shown above, but the template call can be given an alternative width as follows:
::form the call: '''<code><nowiki>{| style={{pseudo-table|width=XX%}}</nowiki></code> '''''versus the default''''' <code><nowiki>{| style={{pseudo-table}}</nowiki></code>'''
* The format also provides for other format parameters to be included in the style block by defining the parameter ''''other''''.
** for example: '''|other=color:blue; would assert the table contents as a blue font. Other HTML/CSS formatting elements are equally valid.
 
 
;for other examples...
:Use the {{plain link|http://online.ts2009.com/mediaWiki/index.php5/Special:WhatLinksHere/Template:Pseudo-table|What links here}} wiki feature to examin a use inclusion.

 
 
</noinclude>

"mesh-table" container

2013-10-12T15:23:40Z

Fabartus: /* Supported Tags */ refactor, fmt fixups

{{ORP-top}}
==KIND Heirarchy==
The "mesh-table" container is a top-level [[config.txt file]] entry used by various [[Content_Configuration#Content_Types|Content Types]].

The mesh-table is a list of mesh subcontainers with no standalone tags. Each mesh subcontainer uses the following format. Tags are parsed in a standardised format, but not all [[Content_Configuration#Content_Types|Content Types]] support the full range of tags listed below. Each mesh derives its name from the subcontainer's tag name. These names are used to refer to specific meshes from within the mesh-table and also from script.

==Known Dependent Parent Types==
:''Main article, see: [[KIND Mesh]]''
The Content Types listed here use the mesh-table container as part of their definition.

* [[KIND Industry]]
* [[KIND MOJunction]]
* [[KIND Pantograph]]
* [[KIND Scenery]]
* [[KIND Track]]
* [[KIND Traincar]]

The following config containers also reference back to their Asset's mesh-table container in some fashion:
* [["junction-vertices" container]]
* [["track-lod-tree" container]]

'''See also'''{{bullR}} [[Modeling Guidelines]] {{bull}} [[Modeling Scenery]]
==Mesh subcontainer==
Each mesh subcontainer supports the following tags. Each tag is shown here with its default value.

mesh-asset <NULLKUID>
mesh "text=path and name/ident"
anim ""
lod-level 255
mesh-season 255
att ""
att-parent ""
opacity 1.0
position 0,0,0
orientation 0,0,0
auto-create 0
use-parent-bounds 0
animation-loop-speed 0
critical-animation 1
effects
{
}
night-mesh-base ""

==Supported Tags==
Each mesh subcontainer supports the following tags.

===mesh-asset===
Allows assets to be used as 'mesh libraries', the following container specifies that the mesh required (and its optional animation) is located relative to ''''''the root folder'''''' of <kuid:1234:5678>. CMP does not auto-check for the existence of these'' 'externally referenced files' ''when processing so you must ensure that they are present in the referenced kuid before using this tag. Subfolder paths within the asset can be used; folder names should be prefixed to the path with a forward slash ("/") separator in the usual fashion.

===mesh===
The ‘main’ mesh name. This may include a sub-path;
ie: mesh nightwindows/nightwindows.im, where the file nightwindows.im has been placed in the subdirectory nightwindows.

Use .im files exported from 3dsmax (as opposed to .pm.) or reference an .lm file if you wish your asset to have ‘Level of Detail’ mesh reduction.

Level of detail is a process of using different model meshes, depending on how far the viewer is from the model. A finer mesh is used for close up viewing in Trainz.

===anim===
The animation file (.kin) exported from 3dsmax. This may include a sub-path.

===lod-level===
The object LOD level at which this mesh is displayed. The default value (255) indicates that this mesh is visible at all detail levels. See also [[KIND Mesh]] for the 'mesh-detail-level' tag.

===mesh-season===
The season index for which this mesh is displayed. The default value (255) indicates that this mesh is visible in all seasons. See also [["Season-selector" container]].

===att===
The mesh (and animation if present) is inserted at a mesh attachment point rather than the origin (without this line the mesh is placed relative to the origin of the parent model).

===att-parent===
The tag tells Trainz in which mesh the attachment point is located. The insertion attachment point is located within the mesh ‘name’ , as listed in the config.txt.

===opacity===
opacity x (float 0.0 - 1.0 default 1.0)

Specifies the overall transparency of a mesh. Values other than 0.0 or 1.0 employ alpha blending and a value of 0.0 has the same effect as hiding the mesh.

Note that this tag is buggy in TS2009 prior to SP4.

===mesh-scale===
This tag defines a minimum and maximum scaling value for the mesh, where 1.0 is the size as modelled. Each instance of the mesh that exists in the world will randomise within this range. Randomisation will not change between runs or between Trainz editions, but may change based on factors such as the position of the mesh in the world. This tag is currently only supported on SpeedTree assets; attempts to use this tag on other assets results in undefined behaviour.

===position===
position X,Y,Z (in metres, default 0,0,0)

Specifies the location of a mesh relative to its insertion point.

===orientation===
orientation X,Y,Z (radians default 0,0,0)

Allows a submesh to be rotated relative to its insertion point. To reverse a mesh by 180 degrees about the Z axis, add the tag:

orientation 0,0,3.14159

===auto-create===
The model is generated automatically when placed, or when you load a map which includes the model. In some instances you don’t want the mesh visible (as this may be controlled through script). If auto-create is 0 the mesh will not be visible when placed.

===use-parent-bounds===
When enabled, this tag indicates that render culling should occur using the whole object's bounding box rather than this mesh's bounding box. Bounding boxes on individual meshes may not update correctly when animation moves the object's geometry any significant distance from the bind position. This flag can help mitigate such effects, at a tiny performance penalty.

===animation-loop-speed===
This tag must be here if the asset is to animate when placed. If this tag is not here when placed the animation will not play by default, but may play if controlled by script. A different value (e.g. 0.5, 2.0) may be used in the tag to play the animation at a different speed from that created in 3dsmax.

===light===
If set (which it is by default), this tag causes the non-stitched mesh to be linked into the Trainz lighting model. This causes the mesh to respond to directional lighting changes, such as the angle of the sun or train headlights. This is also necessary for normal maps to work correctly. Zeroing this tag will remove the mesh from the Trainz lighting model. Generally speaking, you should never zero this tag- almost every effect that can be achieved through this approach can be better served by using an appropriate normal map or appropriate geometry detail.

This tag has no effect on stitched meshes, which are always affected by the Trainz lighting. Since the content creator has no direct influence over which meshes are subject to [[Mesh Stitching]], and all indirect influences are subject to change between Trainz editions, it is strongly recommended that this tag is avoided to ensure that results are consistent.

===critical-animation===
"critical-animation" indicates that this mesh's animation generates events which are critical to the script system's behavior. If your asset is not scripted, does not use scripted animation events, or only uses the events for display purposes and will not break if the occasional event is missed, this tag should be set to ''false''. Leaving this flag set to ''true'' is a '''significant''' performance penalty.

===night-mesh-base===
This night mesh is linked to the specified mesh and is visible only at night. It is invisible if the specified mesh is invisible, (if the auto-create 0 line were used so the specified mesh can be controlled by script).

==Effects Container==
The effects container also contains a list of effect subcontainers. The effect subcontainers support the following generic tags.

kind ""
name ""

The effect subcontainers support additional tags depending on the effect kind. The following effect kinds are supported:

* [[Corona Effect]]
* [[Name Effect]]
* [[Attachment Effect]]
* [[Animation Effect]]
* [[Texture-Replacement Effect]]

==Mesh-Table Example==
The following is an example of a simple mesh-table which implements two levels of detail.

mesh-table
{
default-lod0
{
mesh "example-lod0.im"
auto-create 1
lod-level 0
}
default-lod1
{
mesh "example-lod1.im"
auto-create 1
lod-level 1
}
}

[[Category:Config Container|mesh-table container]]
{{ORP-bot|mesh-table container}}

"Throttle-power" container

2013-10-12T15:12:59Z

Fabartus: /* Example throttle-power container */ resize pic off right data column

{{ORP-top}}
==Parent Class==
The Throttle-power container is a top-level Enginespec [[config.txt file]] entry used by [[KIND Engine]] assets.

==Supported Tags==
{{Related value|"Motor" container|sect=#throttle-notches|throttle-notches}}
The Throttle-power container has 'nn elements' defining a sequence of paired numeric data sets grouped into subcontainers ({{wp|Array data structure|data array}}s) that depend on the type of motive power at each throttle setting. Each subcontainer or array refers to a specific throttle notch of a particular engine's performance curves, points on a graph to incorporate into the simulation dynamic models.
# The first (index of zero) value(s) correspond to zero power or neutral and have neither thrust nor speed values (both are zero factors).
# The majority of the Throttle-power container then has a sequence of numeric subcontainers matching in numbers the integer count define in the [["Motor"_container#throttle-notches|"Motor" container]]'s 'throttle-notches' tag value.
# The Throttle-power containers last listed index of subcontainers must match the number of the integer defined by the value given the '''[["Motor"_container#throttle-notches|"Motor" container's 'throttle-notches' tag]]'''. This value will generally be 8, or 32.
:*'''{the set: 0, 1, 2, {{...}}, 6, 7, 8} for diesels ''' and {{...}}
:*'''{the set: 0, 1, {{...}}, 30, 31, 32} for electric or diesel-electric powered locos.'''
# A unit with dynamic brakes will have a double array of 8 or 32 values, corresponding to dynamic braking engaged (deceleration or braking mode) or not engaged (acceleration).

Within each subcontainer, there are a series of numeric named lines. Each line specifies a speed (m/s) and a {{wp|Tractive force|tractive effort}} ({{wp|Newton (unit)|kiloNewtons (kN)}}) value. Together, these points define a tractive effort graph for a specific throttle notch.

==Example throttle-power container==

Here is an example throttle-power container. (Several notches have been omitted for brevity - the format is identical throughout).
[[File:Three-loco-styles.jpg|thumb|right|400px|Three loco styles shown together in Victoria, Australia.]]
throttle-power
{
0
{
0 0
}

1
{
0 165
2.2 83
4.4 55
6.6 41
8.8 33
13.0 0
}
...
...
...
8
{
0 1320
2.2 800
4.4 750
5.5 700
6.6 480
8.8 250
11.25 200
13.3 195
28.5 190
30.0 26
31.0 0
}
}
[[file:Inclined Normal Force.png|thumb|right|350px|Weight is a force which depends on the part of the mass bearing straight down in a gravitational field. When the surface is inclined, that part of the weight at right angles to the track/surface, called the normal component or force diminishes as some of it now acts downhill which we sometimes call ''dead-weight'', and ''that component'' now has to be lifted while friction, declines as the normal force declines.]]
*Note that ''in the example's figures'' the high notch thrust values are way beyond what the loco can actually thrust against the track at low speeds - in other words, this loco cannot be opened up to full throttle at very low speeds, otherwise it's wheels will slip.
* The maximum tractive effort a {{wp|locomotive engine}} can put onto the rails before slipping is configured in the loco config file—the reason for this is that the weight of the loco (''also set in the loco config file'') will affect this value since {{wp|Friction|frictional force}} opposes slippage and friction is directly dependent upon the '{{wp|Normal Force}}' exerted by a mass on a surface.
* As the slope of a grade increases it affects (diminishes) the component of the normal force producing friction against the rails. With a diminished frictional coefficient the tendency to slip increases proportionally to the {{wp|sine}} of the angle of pitch of the grade.
* It is a well known factor of pragmatic rail operations that traincars have less braking ability or can only apply reduced tractive effort on grades. The decline in the Normal Force with an increase in grade is why friction is commensurately reduced, and wheel slippage commensurately is more likely. Similarly, lubrication of the rails reduces frictional forces in a foul weather situation, again reducing braking ability and allowable pre-slip traction.
* See also: {{wp|Tractive_force#Defining_tractive_effort|Defining Tractive Effort}} on Wikipedia.

[[Category:Config Container|throttle-power]]
{{Cont-Engine|throttle-power}}
{{ORP-bot|throttle-power}}

User talk:Jamesmoody

2013-10-12T03:22:50Z

Fabartus: /* Small words and big pictures */ new section

Template:TL-Obsolete-tag

2013-10-10T01:10:46Z

Fabartus: update

[[Category:Container tags, obsolete|{{PAGENAME}}]]<noinclude>
{{autoTcat}}{{SelfTdoc}}
This template. '''TL-Obsolete-tag''', is used on brief pseudo-article pages discussing '''obsolete container tags''', the last version when their inclusion was valid and when / if they were replaced by what more modern KIND data type.
* It does not categorize the same as using {{tl|DIS-top}} and {{tl|DIS-bot}} which should also be used on pages covering the history of discontinued tags / data types.
 
*Such pages are akin to soft redirects in Wikipedia, requiring the user to clink on a link to get to the current data type whilst providing both a '''search name''' and a bit of ''version information'' about the obsolete tag.
<div>{{DIS-bot|*{{PAGENAME}} }}
[[Category:Container tags, obsolete|*{{PAGENAME}}]]
</noinclude>

Epbrakes

2013-10-10T01:03:48Z

Fabartus: ++{{DIS-top}}+{{DIS-bot}} and update with date/ver data

{{DIS-top}}
The config.txt tag '''Epbrakes''' once part of [[KIND_Engine#epbrakes|KIND Engine]] is an obsolete Steam Engine single value tag that generates an error in Trainz versions after release of TS2009-SP0 and prior to that was an entry listed in [[KIND_Engine#epbrakes|KIND Engine]].

{{TL-Obsolete-tag
|kind=KIND_Engine|ver=|* To correct CM Errors of this kind }}
{{DIS-bot|}{{PAGENAME}} }}

KIND Engine

2013-10-10T01:00:10Z

Fabartus: /* epbrakes */ link

{{ORP-top}}
[[KIND Engine]] assets contain diesel or electric loco engine performance characteristics.
==Historical==
{{MainCCG|CCG/Kind:_Engine|Kind: Engine}}

==KIND Hierarchy==
===Parent Classes===
* [[KIND TrainzBaseSpec]]
{{TBS}}
===Child Classes===
The engine child {{wp|data structure}}s are termed containers in Trainz and each defines the parameters and variables the simulator software needs to produce a dynamic working 3D asset.
# [[throttle-power container]]
# [[dynamic-brake container]]
# [[pressure container]]
# [[mass container]]
# [[motor container]]
# [[flowsize container]]
# [[volume container]]

==Supported Tags==

kind "engine"
[[throttle-power_container|throttle-power]]
{
}
[[dynamic-brake_container|dynamic-brake]]
{
}
[[pressure_container|pressure]]
{
}
[[mass_container|mass]]
{
}
[[motor_container|motor]]
{
}
[[flowsize_container|flowsize]]
{
}
[[volume_container|volume]]
{
}
scale ""
epbrakes ""
autopilot-stop-distance 5.0
autopilot-crawl-distance 20.0
autopilot-caution-speed-multiplier 0.5
throttle-adjustment-rate 0.01

====throttle-power====
:Type: [[throttle-power_container|throttle-power Container]]
:Desc: Acceleration variables in cabin mode.

====dynamic-brake====
:Type: [[dynamic-brake_container|dynamic-brake Container]]
:Desc: Deceleration variables while dynamic braking in cabin mode.

====pressure====
:Type: [[pressure_container|pressure Container]]
:Desc: TBD

====mass====
:Type: [[mass_container|mass Container]]
:Desc: TBD

====motor====
:Type: [[motor_container|motor Container]]
:Desc: TBD

====flowsize====
:Type: [[flowsize_container|flowsize Container]]
:Desc: TBD

====volume====
:Type: [[volume_container|volume Container]]
:Desc: TBD

====scale====
:Type: Obsolete
:Desc: Obsolete

====[[epbrakes]]====
:Type: Obsolete single value
:Desc: Obsoleted in release of TS2009

====autopilot-stop-distance====
:Type: float
:Desc: How far (in meters) in front of a typical obstruction (red light, etc.) the AI will attempt to stop the train. Changing this value can help fine-tune the accuracy of the AI's movement, however attempting to make the train stop too close to a target may result in overruns in some cases. This tag is intended for special-case usage only.

====autopilot-crawl-distance====
:Type: float
:Desc: Once this distance (in meters) from the intended stopping position has been reached, the AI will 'crawl' rather than attempt to speed up to reach its destination. Changing this value can help fine-tune the accuracy of the AI's movement, however attempting to make the train stop too close to a target may result in overruns in some cases. This tag is intended for special-case usage only.

====autopilot-caution-speed-multiplier====
:Type: float
:Desc: The AI will slow to this multiple of the speed limit when operating under caution conditions. This can be set to 1.0 in order to effectively remove caution-speed driving, however this can increase the risk of overruns in some cases

====throttle-adjustment-rate====
:Type: float
:Desc: Defines the adjustment rate at which the engine's throttle will adjust to match the train's throttle. Increasing this rate will make the engine more responsive at the possible cost of audio or driving realism. In DCC mode, a minimum value of 0.1 is used.

==Example Config.txt==
Sample [[config.txt file]] for an enginespec asset, with the Standard Tags excluded for brevity:

''TBD''

==Downloads==
''Attach sample files here?''

==Categories==
[[Category:Asset KIND|Engine]]

[[Category:TBD|Engine]]
{{ORP-bot|Engine}}

KIND Engine

2013-10-10T00:59:41Z

Fabartus: /* epbrakes */ Obsoleted in release of TS2009

{{ORP-top}}
[[KIND Engine]] assets contain diesel or electric loco engine performance characteristics.
==Historical==
{{MainCCG|CCG/Kind:_Engine|Kind: Engine}}

==KIND Hierarchy==
===Parent Classes===
* [[KIND TrainzBaseSpec]]
{{TBS}}
===Child Classes===
The engine child {{wp|data structure}}s are termed containers in Trainz and each defines the parameters and variables the simulator software needs to produce a dynamic working 3D asset.
# [[throttle-power container]]
# [[dynamic-brake container]]
# [[pressure container]]
# [[mass container]]
# [[motor container]]
# [[flowsize container]]
# [[volume container]]

==Supported Tags==

kind "engine"
[[throttle-power_container|throttle-power]]
{
}
[[dynamic-brake_container|dynamic-brake]]
{
}
[[pressure_container|pressure]]
{
}
[[mass_container|mass]]
{
}
[[motor_container|motor]]
{
}
[[flowsize_container|flowsize]]
{
}
[[volume_container|volume]]
{
}
scale ""
epbrakes ""
autopilot-stop-distance 5.0
autopilot-crawl-distance 20.0
autopilot-caution-speed-multiplier 0.5
throttle-adjustment-rate 0.01

====throttle-power====
:Type: [[throttle-power_container|throttle-power Container]]
:Desc: Acceleration variables in cabin mode.

====dynamic-brake====
:Type: [[dynamic-brake_container|dynamic-brake Container]]
:Desc: Deceleration variables while dynamic braking in cabin mode.

====pressure====
:Type: [[pressure_container|pressure Container]]
:Desc: TBD

====mass====
:Type: [[mass_container|mass Container]]
:Desc: TBD

====motor====
:Type: [[motor_container|motor Container]]
:Desc: TBD

====flowsize====
:Type: [[flowsize_container|flowsize Container]]
:Desc: TBD

====volume====
:Type: [[volume_container|volume Container]]
:Desc: TBD

====scale====
:Type: Obsolete
:Desc: Obsolete

====epbrakes====
:Type: Obsolete single value
:Desc: Obsoleted in release of TS2009

====autopilot-stop-distance====
:Type: float
:Desc: How far (in meters) in front of a typical obstruction (red light, etc.) the AI will attempt to stop the train. Changing this value can help fine-tune the accuracy of the AI's movement, however attempting to make the train stop too close to a target may result in overruns in some cases. This tag is intended for special-case usage only.

====autopilot-crawl-distance====
:Type: float
:Desc: Once this distance (in meters) from the intended stopping position has been reached, the AI will 'crawl' rather than attempt to speed up to reach its destination. Changing this value can help fine-tune the accuracy of the AI's movement, however attempting to make the train stop too close to a target may result in overruns in some cases. This tag is intended for special-case usage only.

====autopilot-caution-speed-multiplier====
:Type: float
:Desc: The AI will slow to this multiple of the speed limit when operating under caution conditions. This can be set to 1.0 in order to effectively remove caution-speed driving, however this can increase the risk of overruns in some cases

====throttle-adjustment-rate====
:Type: float
:Desc: Defines the adjustment rate at which the engine's throttle will adjust to match the train's throttle. Increasing this rate will make the engine more responsive at the possible cost of audio or driving realism. In DCC mode, a minimum value of 0.1 is used.

==Example Config.txt==
Sample [[config.txt file]] for an enginespec asset, with the Standard Tags excluded for brevity:

''TBD''

==Downloads==
''Attach sample files here?''

==Categories==
[[Category:Asset KIND|Engine]]

[[Category:TBD|Engine]]
{{ORP-bot|Engine}}

Region

2013-10-10T00:45:18Z

Fabartus: genesis

{{DIS-top}}
 
{{-}}
The '''region''' tag is a legacy tag valid when defined in pre-TRS2006 Trainz versions, but depending upon the [[Trainz-build]] version will be obsolescent (may give a warning or just be ignored) or obsolete (will generate an error) in newer releases of Trainz.
{{-}}
 
{{DIS-bot}}

Template:DIS-top

2013-10-10T00:21:59Z

Fabartus: genesis

<div style="width:100%; font-face:Verdana, Garamond,Times,Serif,Arial; font-size:11pt;">
<table style="width:100%; border:2px solid grey; align:center; text-align:center; padding:1px; margin:0; max-height:40px; " >
<tr>
<td style="align:left; margin: 1px 5px 1px 1px; vertical-align:center; max-height:40px; width:10%; ">[[image:wikilogo.png|45x45px|left|alt=]]</td>
<td style="width:80%; background:#C61236; color: yellow; ">'''{{{1|Discontinued data type - N3V TrainzOnline}}}''' official reference page</td>
<td style="width:10%; ">
[[File:TRAINZ Original^ footer Logo w-reflections (src=Auran!com~trainz~faq!php^FaqID=258 and 'footer Logo').jpg|101x35px|right|alt=]]
</td>
</tr>

</table>
<noinclude>
;Purpose
:This template is used to set off N3V Wiki reference pages denoting data types officially discontinued and documented as such on the N3V TrainzOnline Wiki.
* {{tl|DIS-bot}} will ''also auto-categorize the page'' to the [[:category:Trainz reference pages]].

[[Category:Mbox templates|{{PAGENAME}}]]
[[Category:Self-documenting templates|{{PAGENAME}}]]
[[Category:Auto-categorizing templates|{{PAGENAME}}]]
[[Category:Discontinued Trainz data types|*{{PAGENAME}} ]]</noinclude>

Template:DIS-bot

2013-10-10T00:20:32Z

Fabartus: genesis

<noinclude>
<div style="width:100%;background:#F5FFFA; font-face:Verdana, Garamond,Times,Serif,Arial; font-size:10pt;">

;Purpose
:This template is used with {{Tl|DIS-top}} to set off official N3V Wiki reference pages delineating 'discontinued data types' be they obsolescent or obsolete tag and container names,

[[Category:Self-documenting templates|{{PAGENAME}}]]
[[Category:Trainz reference pages|*{{PAGENAME}}]]
[[Category:Auto-categorizing templates|{{PAGENAME}}]]</noinclude>
</div><includeonly>
[[Category:Discontinued Trainz data types|{{{1|{{PAGENAME}}}}}]]
[[Category:Trainz reference pages|{{{1|{{PAGENAME}}}}}]]</includeonly>

"Category-region" tag

2013-10-09T23:48:45Z

Fabartus: complete format tweaks

{{FUN-beg}}{{ORP-top}}
==About Category-region codes==
'''Category-region codes''' are a single ("UK") or multiple codes ("AUS;DE;UK;USA") in a quoted string that is included in the config.txt file for user defined filters.
* Assets with narrow single country scope would contain a single code after the tagname.
* Assets which were widely found in many regions (e.g. ''''Caterpillar D7 bulldozer'''', will list the series of country codes of the region.)
** The codes have only a minor importance in TRAINZ and are primarily used in Trainz as a sort and selection criteria in user defined filters.
* For content that exists in multiple areas, when creating new assets, select appropriate codes in [[Content Creator Plus]] (CCP).
** For example, a locomotive that was available in the United States and Canada would be specified as follows:

category-region "US;CA"

==Tables of codes==
<big>'''The category-region codes below are in alphabetical order by sort criteria.

Legal codes that are recognized by Trainz are as follows:'''</big>

===by region code order===
{|
|-
! AD-EE || EG-LI || LK-SC || SD-ZZ
|-valign="top"
|
# AD Andorra
# AE United Arab Emirates
# AF Afghanistan
# AG Antigua and Barbuda
# AI Anguilla
# AL Albania
# AM Armenia
# AN Netherland Antilles
# AO Angola
# AQ Antarctica
# AR Argentina
# AS American Samoa
# AT Austria
# AU Australia
# AW Aruba
# AZ Azerbaidjan
# BA Bosnia-Herzegovina
# BB Barbados
# BD Bangladesh
# BE Belgium
# BF Burkina Faso
# BG Bulgaria
# BH Bahrain
# BI Burundi
# BJ Benin
# BM Bermuda
# BN Brunei Darussalam
# BO Bolivia
# BR Brazil
# BS Bahamas
# BT Buthan
# BV Bouvet Island
# BW Botswana
# BY Belarus
# BZ Belize
# CA Canada
# CC Cocos (Keeling) Isl.
# CF Central African Rep.
# CG Congo
# CH Switzerland
# CI Ivory Coast
# CK Cook Islands
# CL Chile
# CM Cameroon
# CN China
# CO Colombia
# CR Costa Rica
# CS Czechoslovakia
# CU Cuba
# CV Christmas Island
# CY Cyprus
# CZ Czech Republic
# DE Germany
# DJ Djibouti
# DK Denmark
# DM Dominica
# DO Dominican Republic
# DZ Algeria
# EC Ecuador
# EE Estonia
|
# EG Egypt
# EH Western Sahara
# ES Spain
# ET Ethiopia
# FI Finland
# FJ Fiji
# FK Falkland Isl.(Malvinas)
# FM Micronesia
# FO Faroe Islands
# FR France
# GA Gabon
# GB Great Britain
# GD Grenada
# GE Georgia
# GH Ghana
# GI Gibraltar
# GL Greenland
# GP Guadeloupe (Fr.)
# GQ Equatorial Guinea
# GF Guyana (Fr.)
# GM Gambia
# GN Guinea
# GR Greece
# GT Guatemala
# GU Guam (US)
# GW Guinea Bissau
# GY Guyana
# HK Hong Kong
# HM Heard & McDonald Isl.
# HN Honduras
# HR Croatia
# HT Haiti
# HU Hungary
# ID Indonesia
# IE Ireland
# IL Israel
# IN India
# IO British Indian O. Terr.
# IQ Iraq
# IR Iran
# IS Iceland
# IT Italy
# JM Jamaica
# JO Jordan
# JP Japan
# KE Kenya
# KG Kirgistan Ex-USSR
# KH Cambodia
# KI Kiribati
# KM Comoros
# KN St.Kitts Nevis Anguilla
# KP Korea (North)
# KR Korea (South)
# KW Kuwait
# KY Cayman Islands
# KZ Kazachstan
# LA Laos
# LB Lebanon
# LC Saint Lucia
# LI Liechtenstein
|
# LK Sri Lanka
# LR Liberia
# LS Lesotho
# LT Lithuania
# LU Luxembourg
# LV Latvia
# LY Libya
# MA Morocco
# MC Monaco
# MD Moldavia Ex-USSR
# MG Madagascar
# MH Marshall Islands
# ML Mali
# MM Myanmar
# MN Mongolia
# MO Martinique (Fr.)
# MR Mauritania
# MS Montserrat
# MT Malta
# MU Mauritius
# MV Maldives
# MW Malawi
# MX Mexico
# MY Malaysia
# MZ Mozambique
# NA Namibia
# NC New Caledonia (Fr.)
# NE Niger
# NF Norfolk Island
# NG Nigeria
# NI Nicaragua
# NL Netherlands
# NO Norway
# NP Nepal
# NR Nauru
# NT Neutral Zone
# NU Niue
# NZ New Zealand
# OM Oman
# PA Panama
# PE Peru
# PF Polynesia (Fr.)
# PG Papua New Guinea
# PH Philippines
# PK Pakistan
# PL Poland
# PM St. Pierre & Miquelon
# PN Pitcairn
# PT Portugal
# PR Puerto Rico (US)
# PW Palau
# PY Paraguay
# QA Qatar
# RE Reunion (Fr.)
# RO Romania
# RU Russian Federation Ex-USSR
# RW Rwanda
# SA Saudi Arabia
# SB Solomon Islands
# SC Seychelles
|
# SD Sudan
# SE Sweden
# SG Singapore
# SH St. Helena
# SI Slovenia
# SJ Svalbard & Jan Mayen Is
# SK Slovak Republic
# SL Sierra Leone
# SM San Marino
# SN Senegal
# SO Somalia
# SR Suriname
# ST St. Tome and Principe
# SU Soviet Union
# SV El Salvador
# SY Syria
# SZ Swaziland
# TC Turks & Caicos Islands
# TD Chad
# TF French Southern Terr.
# TG Togo
# TH Thailand
# TJ Tadjikistan Ex-USSR
# TK Tokelau
# TL East Timor
# TM Turkmenistan Ex-USSR
# TN Tunisia
# TO Tonga
# TR Turkey
# TT Trinidad & Tobago
# TV Tuvalu
# TW Taiwan
# TZ Tanzania
# UA Ukraine
# UG Uganda
# UK United Kingdom
# UM US Minor outlying Isl.
# US United States
# UY Uruguay
# UZ Uzbekistan Ex-USSR
# VA Vatican City State
# VC St.Vincent & Grenadines
# VE Venezuela
# VG Virgin Islands (British)
# VI Virgin Islands (US)
# VN Vietnam
# VU Vanuatu
# WF Wallis & Futuna Islands
# WS Samoa
# YE Yemen
# YU Yugoslavia
# ZA South Africa
# ZM Zambia
# ZR Zaire
# ZW Zimbabwe
|}

===by country name order===

{|
|''' Aa—Ear || Eas— Ecu || Les—Lib || San—Sau'''
|- valign="top"
|
# Afghanistan AF
# Albania AL
# Algeria DZ
# American Samoa AS
# Andorra AD
# Angola AO
# Anguilla AI
# Antarctica AQ
# Antigua and Barbuda AG
# Argentina AR
# Armenia AM
# Aruba AW
# Australia AU
# Austria AT
# Azerbaidjan AZ
# Bahamas BS
# Bahrain BH
# Bangladesh BD
# Barbados BB
# Belarus BY
# Belgium BE
# Belize BZ
# Benin BJ
# Bermuda BM
# Bolivia BO
# Bosnia-Herzegovina BA
# Botswana BW
# Bouvet Island BV
# Brazil BR
# British Indian O. Terr. IO
# Brunei Darussalam BN
# Bulgaria BG
# Burkina Faso BF
# Burundi BI
# Buthan BT
# Cambodia KH
# Cameroon CM
# Canada CA
# Cayman Islands KY
# Central African Rep. CF
# Chad TD
# Chile CL
# China CN
# Christmas Island CV
# Cocos (Keeling) Is CC
# Colombia CO
# Comoros KM
# Congo CG
# Cook Islands CK
# Costa Rica CR
# Croatia HR
# Cuba CU
# Cyprus CY
# Czech Republic CZ
# Czechoslovakia CS
# Denmark DK
# Djibouti DJ
# Dominica DM
# Dominican Republic DO
# East Timor TL
|
# Ecuador EC
# Egypt EG
# El Salvador SV
# Equatorial Guinea GQ
# Estonia EE
# Ethiopia ET
# Falkland Isl.(Malvinas) FK
# Faroe Islands FO
# Fiji FJ
# Finland FI
# France FR
# French Southern Terr. TF
# Gabon GA
# Gambia GM
# Georgia GE
# Germany DE
# Ghana GH
# Gibraltar GI
# Great Britain GB
# Greece GR
# Greenland GL
# Grenada GD
# Guadeloupe (Fr.) GP
# Guam (US) GU
# Guatemala GT
# Guinea GN
# Guinea Bissau GW
# Guyana GY
# Guyana (Fr.) GF
# Haiti HT
# Heard & McDonald Isl. HM
# Honduras HN
# Hong Kong HK
# Hungary HU
# Iceland IS
# India IN
# Indonesia ID
# Iran IR
# Iraq IQ
# Ireland IE
# Israel IL
# Italy IT
# Ivory Coast CI
# Jamaica JM
# Japan JP
# Jordan JO
# Kazachstan KZ
# Kenya KE
# Kirgistan Ex-USSR KG
# Kiribati KI
# Korea (North) KP
# Korea (South) KR
# Kuwait KW
# Laos LA
# Latvia LV
# Lebanon LB
# Lesotho LS
|
# Liberia LR
# Libya LY
# Liechtenstein LI
# Lithuania LT
# Luxembourg LU
# Madagascar MG
# Malawi MW
# Malaysia MY
# Maldives MV
# Mali ML
# Malta MT
# Marshall Islands MH
# Martinique (Fr.) MO
# Mauritania MR
# Mauritius MU
# Mexico MX
# Micronesia FM
# Moldavia Ex-USSR MD
# Monaco MC
# Mongolia MN
# Montserrat MS
# Morocco MA
# Mozambique MZ
# Myanmar MM
# Namibia NA
# Nauru NR
# Nepal NP
# Netherland Antilles AN
# Netherlands NL
# Neutral Zone NT
# New Caledonia (Fr.) NC
# New Zealand NZ
# Nicaragua NI
# Niger NE
# Nigeria NG
# Niue NU
# Norfolk Island NF
# Norway NO
# Oman OM
# Pakistan PK
# Palau PW
# Panama PA
# Papua New Guinea PG
# Paraguay PY
# Peru PE
# Philippines PH
# Pitcairn PN
# Poland PL
# Polynesia (Fr.) PF
# Portugal PT
# Puerto Rico (US) PR
# Qatar QA
# Reunion (Fr.) RE
# Romania RO
# Russian Federation Ex-USSR RU
# Rwanda RW
# Saint Lucia LC
# Samoa WS
# San Marino SM
|
# Saudi Arabia SA
# Senegal SN
# Seychelles SC
# Sierra Leone SL
# Singapore SG
# Slovak Republic SK
# Slovenia SI
# Solomon Islands SB
# Somalia SO
# South Africa ZA
# Soviet Union SU
# Spain ES
# Sri Lanka LK
# St. Helena SH
# St. Pierre & Miquelon PM
# St. Tome and Principe ST
# St.Kitts Nevis Anguilla KN
# St.Vincent & Grenadines VC
# Sudan SD
# Suriname SR
# Svalbard & Jan Mayen Is SJ
# Swaziland SZ
# Sweden SE
# Switzerland CH
# Syria SY
# Tadjikistan Ex-USSR TJ
# Taiwan TW
# Tanzania TZ
# Thailand TH
# Togo TG
# Tokelau TK
# Tonga TO
# Trinidad & Tobago TT
# Tunisia TN
# Turkey TR
# Turkmenistan Ex-USSR TM
# Turks & Caicos Islands TC
# Tuvalu TV
# Uganda UG
# Ukraine UA
# United Arab Emirates AE
# United Kingdom UK
# United States US
# Uruguay UY
# US Minor outlying Isl. UM
# Uzbekistan Ex-USSR UZ
# Vanuatu VU
# Vatican City State VA
# Venezuela VE
# Vietnam VN
# Virgin Islands (British) VG
# Virgin Islands (US) VI
# Wallis & Futuna Islands WF
# Western Sahara EH
# Yemen YE
# Yugoslavia YU
# Zaire ZR
# Zambia ZM
# Zimbabwe ZW
|}
==Notes==
==Categories==
[[Category:Config Tag]]
{{ORP-bot}}<div>{{FUN-bot}}

KIND TrainzBaseSpec

2013-10-09T23:46:35Z

Fabartus: /* Supported Tags */ obsolete & obsolescent tags

{{FUN-beg}}
{{ORP-top}}
==KIND Hierarchy==
[[KIND TrainzBaseSpec]] provides the basis for all Trainz asset types. It provides for a number of "Standard Tags" which are common to (or at least, can legally be defined) for any and all Trainz assets. Some of these are mandatory, most are optional and a defining line using the tag may be omitted in most sub-assets.

===Parent Classes===
* Config.txt files, All elements of the TrainzBaseSpec are contained in Config.txt files. Each of the TrainzBaseSpec file elements can be specified in any asset that has a defining [[Config.txt file]].

===Table of KIND Child Classes===
{|
|-valign="top"
|
*  [[KIND Achievement-category]]
*  [[KIND Achievement-group]]
*  [[KIND Activity]]
*  [[KIND Asset-group]]
*  [[KIND Behavior]]
*  [[KIND Bogey]]
*  [[KIND Buildable]]
*  [[KIND Controlset]]
*  [[KIND Consist]]
*  [[KIND Drivercharacter]]
*  [[KIND Drivercommand]]
*  [[KIND Engine]]
*  [[KIND Enginesound]]
*  [[KIND Environment]]
*  [[KIND Fixedtrack]]
*  [[KIND Gameplaymenu]]
|
*  [[KIND Groundbrush]]
*  [[KIND Groundtexture]]
*  [[KIND Hornsound]]
*  [[KIND HTML-asset]]
*  [[KIND Industry]]
*  [[KIND Interior]]
*  [[KIND Library]]
*  [[Class Library]]
*  [[KIND Map]]
*  [[KIND Mesh]]
*  [[KIND Module]]
*  [[KIND MOCrossing]]
*  [[KIND MOJunction]]
*  [[KIND MOSignal]]
*  [[KIND MOSpeedboard]]
*  [[KIND Pantograph]]
|
*  [[KIND Product]]
*  [[KIND Product-category]]
*  [[KIND Profile]]
*  [[KIND Region]]
*  [[KIND Scenariobehavior]]
*  [[KIND Scenery]]
*  [[KIND Scenery-trackside]]
*  [[KIND SceneryWithTrack]]
*  [[KIND Servlet]]
*  [[KIND Steam-engine]]
*  [[KIND Texture]]
*  [[KIND Texture-group]]
*  [[KIND Track]]
*  [[KIND Tracksound]]
*  [[KIND Traincar]]
*  [[KIND Turntable]]
*  [[KIND Water2]]
|}

 
==Obsolescent tags==
These tag names will occur in older content, and newer conventions have replaced their usages. They are listed here to delineate the discouragement of their use.
*tag: region
:example: region "England"
:era: Obsoleted in TRS2006 as this quote CCP: "The country region to which this asset belongs, not used for TRS2006 - ''[[category-region]]''' is used instead"
notes: This tag antedates TRS2006's introduction of [[Content Manager Plus]] with the capability to set up selection and grouping filters; the older form was a simple string without any real bounds, so could be defined as just about anything.

 

==Obsolete Containers and tags==
These data type names will be seen in older content, and newer conventions have replaced their usages. They are listed here to delineate their replacement is mandantory as errors will be generated on the occasion of their use.

 
==Supported Tags==
The [[KIND TrainzBaseSpec]] [[config.txt file]] supports the following tags. Each tag is show here with its ''default value'':

kind ""
kuid <NULL>
trainz-build ?
script ""
class ""
script-include-table
{
}
username ""
username-XX ""
description ""
description-XX ""
kuid-table
{
}
obsolete-table
{
}
string-table
{
}
string-table-XX
{
}
category-region ""
category-class ""
category-era ""
category-keyword ""
custom-category-list ""
must-have-product-rights ""
must-not-have-product-rights ""
privileges
{
}
thumbnails
{
}
extensions
{
}
license ""
author ""
organisation ""
contact-email ""
contact-website ""
member-of-groups
{
}

 
{{UserTip|1=The [[Template:TBS]] can be placed on any of the terse KIND pages in this Wiki to enable a local viewing of the following table.
*Once N3V turns on WikiMedia ParserFunctions and installs a suitable [[:MetaWiki:Common.css]] and [[:MetaWiki:Common.js]] pages, these local versions will stay small but pop-up when clicked-on in the appropriate place. [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 17:49, 1 July 2013 (EST)
}}

 
===kind===
:''type:'' string.
:''desc:'' The asset type which this [[config.txt file]] represents. See the list: [[KIND_TrainzBaseSpec#Table_of_KIND_Child_Classes|here (above)]]

===kuid===
:''type:'' [[KUID]]
:''desc:'' The unique asset ID referencing this asset.

===[[trainz-build]]===
:''type:'' floating point number (must exactly match a released Trainz version number.)
:''desc:'' The file format version to which this asset is built. This number should generally be set to the trainz version number of the Trainz installation on which the asset is being created and tested. Some asset kinds are parsed significantly differently depending on their ''trainz-build'' version tag. NOTE: The ''trainz-build'' tag is compulsory. If not specified, Trainz will make a primitive attempt to guess at a legacy Trainz version based on the contents of the [[config.txt file]].

===script===
:''type:'' string.
:''desc:'' Indicates the filepath of the primary script file for this asset, if any. This filepath should always end in a ".gs" extension - the runtime will attempt to add or substitute a ".gs" extension if the filepath has an alternative extension.

===class===
:''type:'' string.
:''desc:'' Indicates the script class name to load as the primary class for this asset, if any. This class is loaded from the primary script file for this asset.

===script-include-table===
:''type:'' The [["script-include-table" container]].
:''desc:'' A key-value table of scripted assets which are searched for script includes when compiling this asset's script file(s). The key is currently unused but must be unique; the value indicates the KUID of the asset to include.

===username===
:''type:'' UTF-8 string, [["Username" tag]].
:''desc:'' The '''English''' human-visible name for this asset. This field should never contain non-English text, except where the asset name is a Proper Noun (eg. a place name) with no English localized variant.

===username-XX===
:''type:'' UTF-8 string, [["Username" tag]].
:''desc:'' (Where ''XX'' is replaced with the appropriate [[localization code]] for the language being represented.) The localized human-visible name for this asset. This field is similar to the ''username'' field except representing a non-English locale. Multiple ''username-XX'' tags may be present in an asset, once for each supported locale. If the appropriate 'username-XX' tag is not present to represent this asset on a given end-user system, the English ''username'' tag is used instead.

===description===
:''type:'' UTF-8 multi-line string, [["Description" tag]].
:''desc:'' The '''English''' human-visible descriptive summary for this asset. This field should be kept to a short (1-2 paragraph) blurb describing the asset. Extended details should be provided via an ''info-url'' page. This field must be comprised of English descriptive text, although the text may reference non-English Proper Nouns as explained above.

===description-XX===
:''type:'' UTF-8 multi-line string, [["Description" tag]].
:''desc:'' (Where ''XX'' is replaced with the appropriate [[localization code]] for the language being represented.) The localized human-visible descriptive summary for this asset. This field is similar to the ''description'' field except representing a non-English locale. Multiple ''description-XX'' tags may be present in an asset, once for each supported locale. If the appropriate 'description-XX' tag is not present to represent this asset on a given end-user system, the English ''description'' tag is used instead.

===string-table===
:''type:'' UTF-8 string list container, the [["String-table" container]].
:''desc:'' A key-value list of '''English''' strings. Each key is a meaningful script identifier. Each value is an '''English''' string. As described above, an English string may comprise of or reference a non-English Proper Noun.

===string-table-XX===
:''type:'' UTF-8 string list container, the [["String-table" container]].
:''desc:'' (Where ''XX'' is replaced with the appropriate [[localization code]] for the language being represented.) This field is similar to the ''string-table'' field except representing a non-English locale. Multiple ''string-table-XX'' tags may be present in an asset, once for each supported locale. Each should contain a list of strings with the same Keys as in the ''string-table'' list, but with different Values. If the appropriate 'string-table-XX' tag is not present to represent this asset on a given end-user system, or the appropriate string is missing from the that list, the English ''string-table'' container is referenced instead.

===kuid-table===
:''type:'' KUID list container, the [["Kuid-table" container]].
:''desc:'' A key-value list of assets upon which this asset is dependent. The keys may be any unique value (typically, sequential integers if the keys are meaningless, or script identifiers if the asset is to be referenced from script.) Entries in this table serve two purposes - firstly, to ensure that the game systems are aware of the dependency such that installing and loading this asset will successfully install and load any dependencies, and secondly to allow scripts to locate relevant child assets. Only first-level dependencies are included. Circular dependencies are legal. An asset cannot be listed as a dependency if it is also marked as an obsolete version of this asset. An asset cannot be listed as its own dependency.

===obsolete-table===
:''type:'' KUID list container, the [["Kuid-table" container]].
:''desc:'' A key-value list of assets which are made obsolete by this asset. Any attempt to load an asset referenced in this list will result in this asset being loaded instead. The assets referenced in this list must have the same creator as this asset. It is illegal for two assets to both mark a third asset obsolete, unless one of the two also marks the other as obsolete. Circular obsolete references are illegal. All lower-numbered KUID2 versions of this asset are implied as obsolete and need not be included in this list. It is illegal to mark a higher-numbered KUID2 version of this asset as obsolete as that creates an implicit circular reference.

===category-region===
:''type:'' string.
:''desc:'' A list of two-character [[Category Region]] codes, separated by semi-colons (';'). No other characters (including whitespace, etc.) should be present in the string. This asset is considered relevant to each of the specified regions - this is most relevant for [[KIND Traincar]] and [[KIND MOSignal]] assets, but may be supplied for any asset.

===category-class===
:''type:'' string.
:''desc:'' A single 2-3 character [[Category Class]] code which describes this content item. The ''category-class'' tag is used to provide additional human sub-categorization beyond what is implicit from the Asset Kind. Note that many category-class codes are only relevant to specific Asset Kinds - category-class codes must not be applied to assets of an inappropriate Kind.

===category-era===
:''type:'' string.
:''desc:'' A list of five-character [[era code]]s, separated by semi-colons (';'). Each era code token must be an exact match for one of the specified legal [[era code]]s. No other characters (including whitespace, etc.) should be present in the string. This asset is considered relevant to the specified era range.

===category-keyword===
:''type:'' UTF-8 string.
:''desc:'' A list of natural-language keywords, separated by semi-colons (';'). No other characters (including whitespace or irrelevant punctuation) should be present in the string. These keywords form the basis for asset keyword searching. The asset's name need not be repeated in the ''category-keyword'' list. Various [[default search keywords]] are supplied automatically based on the asset type.

===custom-category-list===
:''type:'' ascii string.
:''desc:'' A list of custom category identifiers, separated by semi-colons (';'). Each [[custom category identifier]] should be a short (eg. 3-6 character) alphanumeric token. No other characters (including whitespace) should be present in the string. These custom categories are used to enable scripts to rapidly locate certain classes of asset. It is strongly recommended that new custom category identifiers are introduced sparingly. The ''custom-category-list'' tag value may have no more than 64 characters total. This tag should be left blank unless there is an existing specific script requirement that can only be fulfilled via the custom-category-list approach.

===must-have-product-rights===
:''type:'' ascii string.
:''desc:'' A list of required product rights, separated by semi-colons (';'). If the local installation does not have the required product rights then the asset may not be loaded by certain game systems.

===must-not-have-product-rights===
:''type:'' ascii string.
:''desc:'' A list of conflicting product rights, separated by semi-colons (';'). If the local installation has one of the listed product rights then the asset may not be loaded by certain game systems.

===privileges===
:''type:'' The [["privileges" container]].
:''desc:'' A set of privileges set by the asset creator to control how this asset can be used.

===thumbnails===
:''type:'' The [["Thumbnails" container]].
:''desc:'' The thumbnail(s) which are used to represent this asset in 2D preview boxes, lists, and icon form throughout the game environment (including in-game, in [[Content Manager]], and on the [[Download Station]].)

===extensions===
:''type:'' The [["Extensions" container]].
:''desc:'' A set of extended attributes which provide additional information to scripts beyond the [[Config.txt file]] specifications defined for this asset type. Care should be taken to abide by the extensions naming guidelines when creating a new extension, and to abide by the extension-creator's guidelines when providing data for an existing extension. Auran reserves the right to add validation for specific entries in the [["Extensions" container]] at a later date, based on the extension-creator's guidelines.

===license===
:''type:'' UTF-8 multi-line string.
:''desc:'' A license describing how the asset creator would like this asset to be used. The meaning of the ''license'' tag is ambiguous and its usage is not recommended. Content uploaded to the [[Download Station]] or provided for inclusion into the game may be under a specific redistribution contract or license agreement which supersedes any text in this field. The license field does not provide for localization support. The text of the license field is not validated or enforced by Auran and may or may not be legally binding to end users.

===author===
:''type:'' UTF-8 string.
:''desc:'' The author's name or mark. The use of this field is not recommended as attribution can be determined programmatically.

===organisation===
:''type:'' UTF-8 string.
:''desc:'' The name or mark of the organization responsible for the creation of this asset. The use of this field is not recommended as attribution can be determined programmatically.

===contact-email===
:''type:'' email address string.
:''desc:'' The contact email address for the creator of this asset. The use of this field is not recommended as attribution can be determined programmatically and contact details can be registered against the creator's [[Planet Auran account]] where they can be limited or updated as necessary.

===contact-website===
:''type:'' URL string.
:''desc:'' The contact website for the creator of this asset. The use of this field is not recommended as attribution can be determined programmatically and contact details can be registered against the creator's [[Planet Auran account]] where they can be limited or updated as necessary.

===info-url===
:''type:'' URL string.
:''desc:'' A link to an online description of this asset. The URL must resolve to a site within the [[Trainz Online Security Zone]]. The use of custom [[Trainz Short URL]] formats is recommended to future-proof the URL against possible future site layout changes. Where this tag is present, in-game buttons are provided to allow the user to view the asset description without leaving the game environment. It is recommended that generic group pages are used for entire classes of asset in any case where the assets provide similar functionality but minor differences in appearance. This reduces the time-expense of creating, maintaining and localizing such documentation.

===member-of-groups===
:''type:'' [["Member-of-groups" container]].
:''desc:'' A list of [[KIND Asset-group]] assets to which this asset belongs. See the [[KIND Asset-group]] documentation for details on how and when this is used.
{{void|
===Downloads===
''Attach sample files here''
}}

==Categories==
[[Category:Asset KIND|$BaseSpec]]
{{ORP-bot|$BaseSpec}}
<div>{{FUN-bot|$BaseSpec}}

KIND TrainzBaseSpec

2013-10-09T23:26:38Z

Fabartus: /* trainz-build */ link section

{{FUN-beg}}
{{ORP-top}}
==KIND Hierarchy==
[[KIND TrainzBaseSpec]] provides the basis for all Trainz asset types. It provides for a number of "Standard Tags" which are common to (or at least, can legally be defined) for any and all Trainz assets. Some of these are mandatory, most are optional and a defining line using the tag may be omitted in most sub-assets.

===Parent Classes===
* Config.txt files, All elements of the TrainzBaseSpec are contained in Config.txt files. Each of the TrainzBaseSpec file elements can be specified in any asset that has a defining [[Config.txt file]].

===Table of KIND Child Classes===
{|
|-valign="top"
|
*  [[KIND Achievement-category]]
*  [[KIND Achievement-group]]
*  [[KIND Activity]]
*  [[KIND Asset-group]]
*  [[KIND Behavior]]
*  [[KIND Bogey]]
*  [[KIND Buildable]]
*  [[KIND Controlset]]
*  [[KIND Consist]]
*  [[KIND Drivercharacter]]
*  [[KIND Drivercommand]]
*  [[KIND Engine]]
*  [[KIND Enginesound]]
*  [[KIND Environment]]
*  [[KIND Fixedtrack]]
*  [[KIND Gameplaymenu]]
|
*  [[KIND Groundbrush]]
*  [[KIND Groundtexture]]
*  [[KIND Hornsound]]
*  [[KIND HTML-asset]]
*  [[KIND Industry]]
*  [[KIND Interior]]
*  [[KIND Library]]
*  [[Class Library]]
*  [[KIND Map]]
*  [[KIND Mesh]]
*  [[KIND Module]]
*  [[KIND MOCrossing]]
*  [[KIND MOJunction]]
*  [[KIND MOSignal]]
*  [[KIND MOSpeedboard]]
*  [[KIND Pantograph]]
|
*  [[KIND Product]]
*  [[KIND Product-category]]
*  [[KIND Profile]]
*  [[KIND Region]]
*  [[KIND Scenariobehavior]]
*  [[KIND Scenery]]
*  [[KIND Scenery-trackside]]
*  [[KIND SceneryWithTrack]]
*  [[KIND Servlet]]
*  [[KIND Steam-engine]]
*  [[KIND Texture]]
*  [[KIND Texture-group]]
*  [[KIND Track]]
*  [[KIND Tracksound]]
*  [[KIND Traincar]]
*  [[KIND Turntable]]
*  [[KIND Water2]]
|}

==Supported Tags==
The [[KIND TrainzBaseSpec]] [[config.txt file]] supports the following tags. Each tag is show here with its ''default value'':

kind ""
kuid <NULL>
trainz-build ?
script ""
class ""
script-include-table
{
}
username ""
username-XX ""
description ""
description-XX ""
kuid-table
{
}
obsolete-table
{
}
string-table
{
}
string-table-XX
{
}
category-region ""
category-class ""
category-era ""
category-keyword ""
custom-category-list ""
must-have-product-rights ""
must-not-have-product-rights ""
privileges
{
}
thumbnails
{
}
extensions
{
}
license ""
author ""
organisation ""
contact-email ""
contact-website ""
member-of-groups
{
}

{{UserTip|1=The [[Template:TBS]] can be placed on any of the terse KIND pages in this Wiki to enable a local viewing of the following table.
*Once N3V turns on WikiMedia ParserFunctions and installs a suitable [[:MetaWiki:Common.css]] and [[:MetaWiki:Common.js]] pages, these local versions will stay small but pop-up when clicked-on in the appropriate place. [[User:Fabartus|Fra]][[User talk:Fabartus|nkB]] 17:49, 1 July 2013 (EST)
}}

====kind====
:''type:'' string.
:''desc:'' The asset type which this [[config.txt file]] represents. See the list: [[KIND_TrainzBaseSpec#Table_of_KIND_Child_Classes|here (above)]]

====kuid====
:''type:'' [[KUID]]
:''desc:'' The unique asset ID referencing this asset.

====[[trainz-build]]====
:''type:'' floating point number (must exactly match a released Trainz version number.)
:''desc:'' The file format version to which this asset is built. This number should generally be set to the trainz version number of the Trainz installation on which the asset is being created and tested. Some asset kinds are parsed significantly differently depending on their ''trainz-build'' version tag. NOTE: The ''trainz-build'' tag is compulsory. If not specified, Trainz will make a primitive attempt to guess at a legacy Trainz version based on the contents of the [[config.txt file]].

====script====
:''type:'' string.
:''desc:'' Indicates the filepath of the primary script file for this asset, if any. This filepath should always end in a ".gs" extension - the runtime will attempt to add or substitute a ".gs" extension if the filepath has an alternative extension.

====class====
:''type:'' string.
:''desc:'' Indicates the script class name to load as the primary class for this asset, if any. This class is loaded from the primary script file for this asset.

====script-include-table====
:''type:'' The [["script-include-table" container]].
:''desc:'' A key-value table of scripted assets which are searched for script includes when compiling this asset's script file(s). The key is currently unused but must be unique; the value indicates the KUID of the asset to include.

====username====
:''type:'' UTF-8 string, [["Username" tag]].
:''desc:'' The '''English''' human-visible name for this asset. This field should never contain non-English text, except where the asset name is a Proper Noun (eg. a place name) with no English localized variant.

====username-XX====
:''type:'' UTF-8 string, [["Username" tag]].
:''desc:'' (Where ''XX'' is replaced with the appropriate [[localization code]] for the language being represented.) The localized human-visible name for this asset. This field is similar to the ''username'' field except representing a non-English locale. Multiple ''username-XX'' tags may be present in an asset, once for each supported locale. If the appropriate 'username-XX' tag is not present to represent this asset on a given end-user system, the English ''username'' tag is used instead.

====description====
:''type:'' UTF-8 multi-line string, [["Description" tag]].
:''desc:'' The '''English''' human-visible descriptive summary for this asset. This field should be kept to a short (1-2 paragraph) blurb describing the asset. Extended details should be provided via an ''info-url'' page. This field must be comprised of English descriptive text, although the text may reference non-English Proper Nouns as explained above.

====description-XX====
:''type:'' UTF-8 multi-line string, [["Description" tag]].
:''desc:'' (Where ''XX'' is replaced with the appropriate [[localization code]] for the language being represented.) The localized human-visible descriptive summary for this asset. This field is similar to the ''description'' field except representing a non-English locale. Multiple ''description-XX'' tags may be present in an asset, once for each supported locale. If the appropriate 'description-XX' tag is not present to represent this asset on a given end-user system, the English ''description'' tag is used instead.

====string-table====
:''type:'' UTF-8 string list container, the [["String-table" container]].
:''desc:'' A key-value list of '''English''' strings. Each key is a meaningful script identifier. Each value is an '''English''' string. As described above, an English string may comprise of or reference a non-English Proper Noun.

====string-table-XX====
:''type:'' UTF-8 string list container, the [["String-table" container]].
:''desc:'' (Where ''XX'' is replaced with the appropriate [[localization code]] for the language being represented.) This field is similar to the ''string-table'' field except representing a non-English locale. Multiple ''string-table-XX'' tags may be present in an asset, once for each supported locale. Each should contain a list of strings with the same Keys as in the ''string-table'' list, but with different Values. If the appropriate 'string-table-XX' tag is not present to represent this asset on a given end-user system, or the appropriate string is missing from the that list, the English ''string-table'' container is referenced instead.

====kuid-table====
:''type:'' KUID list container, the [["Kuid-table" container]].
:''desc:'' A key-value list of assets upon which this asset is dependent. The keys may be any unique value (typically, sequential integers if the keys are meaningless, or script identifiers if the asset is to be referenced from script.) Entries in this table serve two purposes - firstly, to ensure that the game systems are aware of the dependency such that installing and loading this asset will successfully install and load any dependencies, and secondly to allow scripts to locate relevant child assets. Only first-level dependencies are included. Circular dependencies are legal. An asset cannot be listed as a dependency if it is also marked as an obsolete version of this asset. An asset cannot be listed as its own dependency.

====obsolete-table====
:''type:'' KUID list container, the [["Kuid-table" container]].
:''desc:'' A key-value list of assets which are made obsolete by this asset. Any attempt to load an asset referenced in this list will result in this asset being loaded instead. The assets referenced in this list must have the same creator as this asset. It is illegal for two assets to both mark a third asset obsolete, unless one of the two also marks the other as obsolete. Circular obsolete references are illegal. All lower-numbered KUID2 versions of this asset are implied as obsolete and need not be included in this list. It is illegal to mark a higher-numbered KUID2 version of this asset as obsolete as that creates an implicit circular reference.

====category-region====
:''type:'' string.
:''desc:'' A list of two-character [[Category Region]] codes, separated by semi-colons (';'). No other characters (including whitespace, etc.) should be present in the string. This asset is considered relevant to each of the specified regions - this is most relevant for [[KIND Traincar]] and [[KIND MOSignal]] assets, but may be supplied for any asset.

====category-class====
:''type:'' string.
:''desc:'' A single 2-3 character [[Category Class]] code which describes this content item. The ''category-class'' tag is used to provide additional human sub-categorization beyond what is implicit from the Asset Kind. Note that many category-class codes are only relevant to specific Asset Kinds - category-class codes must not be applied to assets of an inappropriate Kind.

====category-era====
:''type:'' string.
:''desc:'' A list of five-character [[era code]]s, separated by semi-colons (';'). Each era code token must be an exact match for one of the specified legal [[era code]]s. No other characters (including whitespace, etc.) should be present in the string. This asset is considered relevant to the specified era range.

====category-keyword====
:''type:'' UTF-8 string.
:''desc:'' A list of natural-language keywords, separated by semi-colons (';'). No other characters (including whitespace or irrelevant punctuation) should be present in the string. These keywords form the basis for asset keyword searching. The asset's name need not be repeated in the ''category-keyword'' list. Various [[default search keywords]] are supplied automatically based on the asset type.

====custom-category-list====
:''type:'' ascii string.
:''desc:'' A list of custom category identifiers, separated by semi-colons (';'). Each [[custom category identifier]] should be a short (eg. 3-6 character) alphanumeric token. No other characters (including whitespace) should be present in the string. These custom categories are used to enable scripts to rapidly locate certain classes of asset. It is strongly recommended that new custom category identifiers are introduced sparingly. The ''custom-category-list'' tag value may have no more than 64 characters total. This tag should be left blank unless there is an existing specific script requirement that can only be fulfilled via the custom-category-list approach.

====must-have-product-rights====
:''type:'' ascii string.
:''desc:'' A list of required product rights, separated by semi-colons (';'). If the local installation does not have the required product rights then the asset may not be loaded by certain game systems.

====must-not-have-product-rights====
:''type:'' ascii string.
:''desc:'' A list of conflicting product rights, separated by semi-colons (';'). If the local installation has one of the listed product rights then the asset may not be loaded by certain game systems.

====privileges====
:''type:'' The [["privileges" container]].
:''desc:'' A set of privileges set by the asset creator to control how this asset can be used.

====thumbnails====
:''type:'' The [["Thumbnails" container]].
:''desc:'' The thumbnail(s) which are used to represent this asset in 2D preview boxes, lists, and icon form throughout the game environment (including in-game, in [[Content Manager]], and on the [[Download Station]].)

====extensions====
:''type:'' The [["Extensions" container]].
:''desc:'' A set of extended attributes which provide additional information to scripts beyond the [[Config.txt file]] specifications defined for this asset type. Care should be taken to abide by the extensions naming guidelines when creating a new extension, and to abide by the extension-creator's guidelines when providing data for an existing extension. Auran reserves the right to add validation for specific entries in the [["Extensions" container]] at a later date, based on the extension-creator's guidelines.

====license====
:''type:'' UTF-8 multi-line string.
:''desc:'' A license describing how the asset creator would like this asset to be used. The meaning of the ''license'' tag is ambiguous and its usage is not recommended. Content uploaded to the [[Download Station]] or provided for inclusion into the game may be under a specific redistribution contract or license agreement which supersedes any text in this field. The license field does not provide for localization support. The text of the license field is not validated or enforced by Auran and may or may not be legally binding to end users.

====author====
:''type:'' UTF-8 string.
:''desc:'' The author's name or mark. The use of this field is not recommended as attribution can be determined programmatically.

====organisation====
:''type:'' UTF-8 string.
:''desc:'' The name or mark of the organization responsible for the creation of this asset. The use of this field is not recommended as attribution can be determined programmatically.

====contact-email====
:''type:'' email address string.
:''desc:'' The contact email address for the creator of this asset. The use of this field is not recommended as attribution can be determined programmatically and contact details can be registered against the creator's [[Planet Auran account]] where they can be limited or updated as necessary.

====contact-website====
:''type:'' URL string.
:''desc:'' The contact website for the creator of this asset. The use of this field is not recommended as attribution can be determined programmatically and contact details can be registered against the creator's [[Planet Auran account]] where they can be limited or updated as necessary.

====info-url====
:''type:'' URL string.
:''desc:'' A link to an online description of this asset. The URL must resolve to a site within the [[Trainz Online Security Zone]]. The use of custom [[Trainz Short URL]] formats is recommended to future-proof the URL against possible future site layout changes. Where this tag is present, in-game buttons are provided to allow the user to view the asset description without leaving the game environment. It is recommended that generic group pages are used for entire classes of asset in any case where the assets provide similar functionality but minor differences in appearance. This reduces the time-expense of creating, maintaining and localizing such documentation.

====member-of-groups====
:''type:'' [["Member-of-groups" container]].
:''desc:'' A list of [[KIND Asset-group]] assets to which this asset belongs. See the [[KIND Asset-group]] documentation for details on how and when this is used.
{{void|
===Downloads===
''Attach sample files here''
}}

==Categories==
[[Category:Asset KIND|$BaseSpec]]
{{ORP-bot|$BaseSpec}}
<div>{{FUN-bot|$BaseSpec}}

"Trainz-build" tag

2013-10-09T18:12:33Z

Fabartus: rv vandalism, statements of error never justified

{{ORP-top}}
==Trainz-build tag number==
A '''Trainz-build tag''' number or '''version number''' is the number assigned in an asset's [[Config.txt file|Config.txt]] {{wp|source code}} {{wp|INI file}} as part of the technology tracking and matching system in Trainz. It indicates the asset (or content's) '''tech-level''' for an asset built to the specifications of a '''[[Trainz build versions|Trainz code build version]]'''. As Trainz has grown and changed, the data models needed to impliment improvements changed, and the Trainz-build tag level system was installed to group the correct data type with the correct software version of Trainz releases. Exactly what makes up legal fields in a '''trainz-build tag''' ''level'' has evolved over the years, and is the source of some of the errors in the download of older content. Some required {{wp|data type}}s have been eliminated, some added, and some moved to other [[Trainz Containers]]—the data structures that are used by the trainz data KIND types as sub-data types.
 
{{UserTip|The word version has an inexact technical meaning. The meaning of ''''Trainz Retail version'''', and ''''Trainz version'''' are not identical, for the first refers to a product release, a ''''base named retail version'''' such as TRS2006 which was given when it was released into the massed market somewhere at some time. The latter, '''Trainz version''' may mean the same initially, but when that product release needs a software {{wp|Patch (computing)|bug-fix patch}} or has a {{wp|service pack}} installed the ''''''code build version'''''' and the tech-level tracking '''''software version/Trainz-build tag''''' version may both change to other code numbers. Any type of {{wp|software update}} creates a new code build number. It is how the programmer staff keeps what version has which software code inside. If the change does not change the technology of the release, if it is a {{wp|Hotfix}} the'' 'Trainz build-version' does not increment'', so the Trainz-build tag number is the same as before, whilst the code build has evolved. Service packs are considered product advancements, so both tracking code numbers will be larger. A retail release may have multiple service packs, so in it's final version—before N3V Games coins a new Retail release name— the service packs will change to reflect different technologies added with each service pack. Each such release upgrades the base named product some, so at that time, the Trainz-build version also increments—because the later indicates a different Code build of the software. }}

{| border=2 cellpadding=5 cellspacing=2 style="align=right; float:right; margin: 10px 0 10px 10px;"
|'''trainz-build''' tech-level version or tag# || '''First Trainz product versions to support the listed content tech-level (buiild-tag) version'''
|-
| {{center|1.0 }} || [[Trainz SP3|Trainz SP3]]
|-
| {{center|1.1 }} || [[Trainz SP3|Trainz SP1]]
|-
| {{center|1.2 }} || [[Trainz SP3|Trainz SP2]]
|-
| {{center|1.3 }} || [[Trainz SP3|Trainz SP3]]
|-
| {{center|1.5 }} || Ultimate Trainz Collection
|-
| {{center|1.6 }} || Ultimate Trainz Collection SP1
|-
| {{center|2.0 }} || [[TRS2004]]
|-
| {{center|2.1 }} || [[TRS2004]] SP1
|-
| {{center|2.2 }} || [[TRS2004]] SP2 - Passenger Pack
|-
| {{center|2.3 }} || [[TRS2004]] SP3
|-
| {{center|2.4 }} || [[TRS2004]] SP4
|-
| {{center|2.5 }} || [[TRS2006]]
|-
| {{center|2.6 }} || [[TRS2006]] SP1
|-
| {{center|2.7 }} || Trainz Classics 1&2
|-
| {{center|2.8 }} || Trainz Classics 3
|-
| {{center|2.9 }} || [[TS2009]]
|-
| {{center|3.0 }} || [[TS2009 SP1]]
|-
| {{center|3.1 }} || [[TS2009 SP2]]
|-
| {{center|3.2 }} || [[TS2009 SP3]] / [[TS2010]]
|-
| {{center|3.3 }} || [[TS2010 SP3]] / [[TS2009 SP4]]
|-
| {{center|3.4 }} || [[TS2010 SP4]]
|-
| {{center|3.5 }} || [[TS12]]
|-
| {{center|3.6 }} || [[TS12]] and [[Trainz Simulator Mac]]
|-
| {{center|3.7 }} || [[TS12 SP1]]
|}

==Trainz build versions==
'''[[Trainz build versions|Trainz code build]]''' or version numbers are assigned first to each released ''''''retail version/retail release'''''' of Trainz, then change by application of {{wp|Hot fix}}es and {{wp|Service packs}}, but while the hot fixes change the code build number, they do not advance the Trainz-build version number, which nowadays will be displayed on the title bar of {{h|ContentManager.exe}} (this is a recent improvement). Content may be created for different versions, making use of the newer functions in a more recent release, when it does so, it must be assigned the corresponding Trainz-build tag tech-level or version number. Consequently, some new-generation assets will not function in earlier versions of the simulator. Some older one's need tweaked, so called {{h|Error fixing}} to comply with the three newer {{wp|Graphical_user_interface|GUI run time}} modules typically affected by service pack releases: {{H|Surveyor}}, {{H|Railyard}} and {{H|Driver}}.
 
==Asset compatibility==
It is important ''for assets'' [[config.txt file]]s to list the version of Trainz with which they are compatible. For older Trainz builds, this is done by entering a Trainz-Build number in the model config.txt file. If used (many content creators hand create assets) the utility program [[Content Creator Plus]] will automatically add the correct trainz-build level version to the config.txt file. Manually edited asset creation frequently copies working materials from another similar asset, and in such cases the asset creator will elect to add a lower build tag version to the asset, for such levels if correctly applied, open the new asset up for use and exploitation by more people; many choose not to move on to a newer Trainz release, particularly now that later versions of TS2010 and TS2012 are needing more advanced computer architectures and high performance video cards.
 
==Older vs Newer build versions==
A correctly-constructed asset built for an older version will usually function in a newer version of Trainz, but this is not always guaranteed, as there have been amendments made to subsequent versions. An article [[List of known breaking changes]] has been in the works for some time by chief programmer [[User talk:Windwalkr|Windwalkr]]. A model using the latest graphical functions will not work in an earlier version. Assets with older technologies sometimes fail in the new data model and processing, despite the effort to fix such content items entering a users data base.

There have been recent changes to vett assets uploaded to the [[Download Station]]. Uploaded content items now are validated against the new data requirements in force for that version. The Trainz-build tag is found in all Trainz config.txt files, an {{wp|INI file|asset's INI file}}—a type of source code provided by content creators, an that number identifies which version of Trainz you have installed and when you use the [[Content Manager]], it will not allow the download of a more advanced/recent asset with a data model that is incompatible with your version. Happily, a lower build-tag most often means the asset can still be used in newer Trainz releases.
 
The approved Trainz-Build version numbers and their mapping to official Trainz release versions are as follows:

==Assigning asset build levels==
Trainz-build numbers up to and including 2.8 are considered by N3V programmers as obsolete as of September 2012 and they believe they should no longer be used.

{{TBKR|trainz-build tag}}
[[Category:Config Tag|trainz-build tag]]
[[Category:Trainz fundamentals pages|trainz-build tag]]
{{ORP-bot|trainz-build tag}}