# Trainz/refs/Trainz build versions

Back to the Top
* Trainz Annotated Reference Pages Trainz Asset Maintenance and Creation
* TOC | Beginnings | Fun | AM&C | Creation | InBook Refs | ORP Refs:  • Index • Containers • Kinds • Tags | Appendixes  • Vers
Glossary :
HKeys-CM :
HKeys-DVR :
HKeys-SUR :
HKeys-WIN :
Mouse use :
Notations :

## Code build number

    The main enhanced Wikibook data tables corresponding to the N3V source page Trainz_build_versions page is found at Version And Build Numbers, which includes release dates, and citations.
The Code build number or Trainz build version (two names meaning the identical 'tracking number') is a type of model number of the software, a unique software specific identifier that in Trainz practices— increments not only with 'named' main retail releases, but with each release for specific language groups, and by Hotfixes, as well as by Service_pack releases. As described in the Notes section below, it also changes in-house with software under development
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 file.

## 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. The below table is for the most recent Windows release.
    For detailed code build version increments in various versions, Click to see table:

### TS2009

   * TS09 see Versions/TS09-Ver Table; or

### TS2010

   * for TS10 see Versions/TS10-Ver Table; or

### TS2012

   * and for TS12 see Versions/TS12-Ver Table.

## Notes and references

Additional information and release tables for all other versions, see the combined Versions And Build Numbers appendix.
* The term 'build' or 'build code' or 'code build' is a computing industries term of art, and is in fact a software serial number identifying a unique combination of software component files, 'built' or 'made' into a particular software package of resultant files. It derives directly from 'making' a 'build' with a script asset generally known as a 'make file' which lists out component parts, instructions on how they are to be processed into intermediate binary files (with specific names) and in what order, and additional instructions on linking the binary object files into specific modules. Make files also have the capability of tracking dependencies and if a component file changes, re-building the dependent software module. IDE's or Integrated Development Environments may layer another interface above the Make level, but in effect, those merely auto-edit the make scripts, then execute the build or make. The IDE thus provides data management automation relieving some of the responsibility of updating the make or build specification from the developers.
* The make or build can be partial or all up, so that the 'full' make process generates a suite of finished Library assets, executables, and dynamic link libraries whose integration can then be tested and evaluated for further development, or adjudged as 'finalized' and stable, at all times then ready for a supporting role in testing related dependent code which may not be so ready. The partial make can rebuild only a part of the software, which has had further development and changes. The auto-dependency sensing of source file changes, protects the developers from forgetting a change by another member of the team; ensuring all the coder are on the same page evaluating the same build and symptoms.
* A 'final build' might also specify copying such retail release boilerplate support files (e.g. keyboard hotkeys mapping files, initial user specific files) into a single installation—the build, which is released to publication.
* On the release of a version for Q&A testing or publication for retail release, the build might then be compressed and distributed, so the end user Installs them, which mostly involves a bit of bookkeeping in the computer's registry and uncompressing the ready to use files from the DVD or internet source. In the later case, the local installer's generally consist of a FTP download manager combined with the file extraction (uncompressing) software.
* Obviously, in modularize software such as Trainz, software update builds would only need to replace run-time software and libraries which have been updated since the last stable 'base' version. Some require processing local data and perhaps incorporate a patching or translation stage for certain assets, such as defaulting a problematic kind engine parameter if and when a ..\local (from 3rd party or the DLS sources) asset or JA asset hadn't defined the data. Such a stage often incurs an extremely long processing cycle of many hours such as several that occurred in several Service Packs during TS2009 and TS2010's evolution.

## Notes, Footnotes & References

Config.txt files are endemic and ever present in Trainz assets, for no asset can be defined without this type of Computer Science container. The keyword-value_of_key pairing must always be kept in mind in editing or creating Trainz content. The TrainzBaseSpec contains values and containers which are most common in asset defining config.txt files.

### Notes

* ↑ In a December 2013 email, Trainz Version Manager James Moody stated that at times he did as many as five or six builds and related Trainz Installs a day.

### Footnotes

* 1 2 Thread: TS12 Patch 1 (47059) is live., shadowarrior, N3V Games Sys-Op; This patch turned out to be corrupted and was taken off the web and replaced by patch 2
* 1 2 3 4 fake cite
* 1 2 3 4 5 6 7 8 9 TS12 SP1 Hotfix 3 and Auto-patch Now Available, by WindWalkr, Published on June 6th, 2013 02:00 AM.
* ↑ Sequence confirmed by Author ed. Fabartus with successive careful installs of TS10, keeping different versions on different drives as installed to new computer. Hotfix from build 43434 inferred from patching method. Manual patch directly skipped.
* 1 2 3 Trainz TS10 and TS12 Hot-fix Patches released,sub-titled: "Patch for TS10 SP3 build 44088 will take the build to version 49933.", by N2V's Shadowarrior
* 1 2
* ↑ Trainz TS10 and TS12 Hot-fix Patches released,Later annotated: "Note: To be able to install Aerotrain and any future DLC packs, you will need to install this patch for your Trainz build.", Last edited by shadowarrior; November 17th, 2011 at 08:27 PM.
* ↑ Trainz TS10 and TS12 Hot-fix Patches released,sub-titled: "Patch for TS12 build 48249 will take the build to version 49922", by N2V's Shadowarrior
* ↑ Trainz 12 Service Pack 1, by aronc, Published on April 10th, 2013 12:47 AM
* ↑ TS12 SP1 Hotfix 2 now available, by GPavlich, Published on April 30th, 2013 07:38 AM
* 1 2 TS12 SP1 Hotfix 1 now available, by GPavlich, Published on April 18th, 2013 02:00 AM

### References

* Trainz printed or pdf file Manuals, applicable version - usually in the ..\extras or ..\extras\manuals folder
* TrainzOnline Wiki Config.txt file page and various other pages
* TrainzOnline Wiki: Content Creator's Guide pages (various)
* Various CCG and Auran websites