Trainz/tags/trainz-build tags

From Wikibooks, open books for an open world
< Trainz‎ | tags(Redirected from Trainz/tags/trainz-build tag)
Jump to: navigation, search
logo
Fundamentals for Trainz Trainees

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

Trainz-build tag number[edit]

The trainz-build tag number indicates the minimum 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 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.  

P train grey.png

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.

 

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.
trainz-build values or 'version numbers' and their mapping to official Trainz release versions are as follows:
'trainz-build' Trainz product for which the asset was designed
1.3
Trainz SP3
1.4
a non-Trainz utility (PaintShed)
1.5
Ultimate Trainz Collection
1.6
Ultimate Trainz Collection SP1
1.7–1.9
Unused, skipped
2.0
TRS2004 initial release
2.1
TRS2004 SP1
2.2
TRS2004 SP2 - Passenger Pack
2.3
TRS2004 SP3
2.4
TRS2004 SP4
2.5
TRS2006
2.6
TRS2006 SP1
2.7
Trainz Classics 1&2
2.8
Trainz Classics 3
2.9
TS2009
3.0
TS2009 SP1
3.1
TS2009 SP2 / TS2009 SP3
3.2
TS2010 / TS2010 SP1
3.3
TS2010 SP2 / TS2010 SP3 / TS2009 SP4
3.4
TS2010 SP4
3.5
TS12
3.6
TS12 and Trainz Simulator Mac
3.7
TS12 SP1

Asset compatibility[edit]

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, while Trainz content validation has improved over time, and newer versions of Trainz detect errors that older versions did not pick up on, many errors are useless make work caused by callous and rapacious programmer and management practices. Often, content may be detected as 'faulty' in a current Trainz version that was missed in the version it was originally created for, but the most frequent issues are missing thumbnail images which have nothing to do with the functionality of the asset, or obsoleted tag names.

Or that is the official party line per N3V, which ignores the fact there are errors they could just fix in parsing, such as ignoring legacy tag names like type, region, asset-filename, or name-xx, etc. and similarly could convert in situ older forms to newer container forms of data, then test for faults. They do neither putting the time cost of their unprofessionalism onto the customers who must one by one correct errors their software should be handling.  

It should be noted that content that is uploaded to the Download Station is validated for faults by the most recent version of Trainz—and may be rejected if an more stringent newer fault or error test has been put in place.[1]

This depends on the version of Trainz that you are running, and if we've updated the DLS error checking. I can make content that shows no errors in TS2009, but will be rejected from the DLS under the current error checking due to issues that TS2009 could not detect. This is essentially the same here. The DLS error checking is updated regularly, and may be more strict than the error checking in TS12 SP1. OTOH, TS:Mac2 is a newer release and will have most of the updates to the error checking.

We have stated many, many, many, many, many, times over the last 12 months that the error checking on the DLS is generally ahead of that in Trainz. Hence, if you are given a rejection notice with actual errors in it, you'll need to correct these.
—N3V spokesman ZecMurphy at forums.auran.com/trainz#post1289419, May 11th, 2014.[1]

Assets generated under a perfectly valid currently supported version of Trains, using the validation compatibility for the trainz-build specified by the asset, may still be rejected by the Download Station Software.

 

If Content Creator Plus CCP is used to modify an asset, it will automatically update the trainz-build version in the config.txt file to the current Trainz version it came with. This is problematic and contrary to the greatest interests of the most members in the Trainz community, as the lowest trainz-build code is desired from the standpoint of giving the asset the most Trainz users access to the new product (asset). Prior to V3.2, such codes could then be manually back-dated to a lower trainz-build, but the error checking in versions since requires exporting the asset-open-for-edit by copying the folder, reverting it, deleting it, editing the trainz-build code change in the copy, then re-importing it—a discourteous number of extra steps-in-the-dance for content creators, and yet another friction point with Trainz programmers. If Using CCP to fault fix and update, often this version with the invincibility of naive programmers forcing others to toe their line and if the asset specs have changed significantly, many other changes to the config.txt file will probably be required, as CCP wants to promote the asset to the current Trainz-build version.

P train grey.png
If you don't want to spend all of your Trainz time patching assets with the user unfriendly interface of CCP and it's demands on your entries, learn to master manually editing and committing to keep the edits down to only those actually necessary.

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[edit]

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. 

  1. a b [Can-a-new-tag-be-made-for-Trainz ], ZecMurphy, Auran Community Assistant, May 11th, 2014, 09:02 PM