Trainz Versions Overview

Trainz software releases or equivalently Trainz Retail releases or Trainz retail versions follow the common software industry practices of assigning releases version numbers paired to 'Marketing Names' as Major Releases of Retail base packages (to draw a parallel case, consider another more familiar family of software: {each of Microsoft Windows Operating system Retail Releases: Windows 1.0, Windows 2.0, Windows 3.1, Windows 95, ..., Windows Vista, Windows 7, Windows 8 & Windows 10}), any one of which per industry practices, might also then have applicable bug fix 'Hot fixes' and other less urgent change patches (generally adding capabilities and/or also making operational tweaks or fixing additional lesser serious bugs and those providing additional user feedback generated 'new' features) called Service Packs. To manage a series of such software & dependent (supporting) data files collections, programmers use a serial number system, in Trainz called the code build number, build number, or Code Version number. Note that both each element in a software system (DLL, EXE, supporting data files such as images, scripts) each have some sort of serialization, or their own code build numbers, and the resulting overall distributed collection, a 'build', is given an overall code build identifier for the entire mix.

All the changes to these products' retail releases (retail versions) collectively are known as software upgrades' and it is a side of computing with which the average lay computer user has little experience, sheltered as most are in a business environment by an IT department or an IT consultant. These days, internet based or enabled software often are written expecting to be updated periodically, numbing our sensitivity and inuring the computer user community to such instabilities in software. ^{[note 1]} Home computer packages—including virtually all download obtained software these days, with massive distribution numbers, often have built-in update coding within to check for updates and either update automatically, or when well designed, alert the user, and update when commanded. Auran Holdings^{[note 2]}, the holding company with all the Trainz rights and their partner N3V Games, currently managing the development and marketing of the properties, has only recently in 'Trainz-version timespans' (2011, finally debugged in TS2009 SP3 and TS2010-SP2) mastered the later techniques.

Versions terminology and meanings

Each named product release (retail version) as well as each successive upgrade level (Hot fixes and other patches generally have to be added in order of release) has a multi-digit 'build' number that is definitively unique to the build as defined by the software publisher. In Trainz, these are known formally as the code build numbers or Trainz build versions, and as their own IT department, 'Trainzers' have to keep these things straight, for not all can be done automatically, and every new retail release requires a new Installation step.

In Trainz, until one understands the contextual meaning it seems the word 'version' becomes a bit over used:

1. First, there is the Trainz version (slang: meaning Trainz Retail Version),
   
2. Secondly, the 'code version' and 'Trainz asset version' numbers, formally known as a "Trainz-build tag" values or Trainz-build version' numbers^[1][2]
   
3. which like the code build number or 'Trainz_build_versions' or sometimes 'code build version'^[3] has an exact technical meaning— a final compiler run against a version controlled make file and subsequently released by Quality Control as the next official 'code set' advance.
    • If you have problems with a installation, this code build number is the one N3V customer support want reported. In TS2009-SP4 and later releases it appears in both the bottom right corner of the Launcher Menu and the Main Menu. In prior releases, it appeared only on the Trainz 'Launcher' screen, and was easy to overlook in some.
    • Each of the other types of versions derive from this stable set of software source code; a plateau in the change cycle signifying stability and reliability insofar as such things can be tested.
   
4. When QA testing fails, N3V issues a software upgrade of three sorts:
   

A. patches for really bad bugs or an adjustment to features, usually come out fast after a release event, once the complaint storm hits the help desk and forums.

B. Hotfixes for bugs and adjustments of several things, not usually to make the whole work, but instead to make the whole work better after an interval of additional testing and while the programmer's are fixing one or more other minor bugs or adding an extended feature. Some of these, such as TS12-SP1+hf4 should have incremented the trainz-build or technology version. Auran & N3V's management has seemingly been inconsistent in their rationales and actions. Basically, a new trainz-build represents a technology plateau, wherein some heretofore unavailable capability has been added.
 • Some of this is within the programmer's experiences—the internal changes within the run time packages; others, mainly involving asset capability, features, scripts, or interactivity are obvious to the community and to content creators, inasmuch as new tags, practices and containers in config.txt files or asset source folder grouped data elements (asset parts) are affected.
 • Trainz is a highly cooperative joint development COMMUNITY at its heart. Content Creators often drive software development with requests for a capability. The programmers and/or N3V management approve the notion, prioritize it, and the programmers thence define parameters (data types); at that juncture, the likely first software modifications are to the error testing screening software which vetts uploaded assets before allowing them onto the DLS—and to a TBV step release enabling its software to not burp on the heretofore unfamiliar new data elements. Content Creators behind the features then provide assets with the theoretical capability, the programmers work on getting it into a future package of software updates and eventually — everybody gets to see whether the data and software have the desired effects... or whether alterations in data definitions or the run time software implementation need adjusted. This all takes a lot of people working together.

C. Service packs —these are more extensive and larger changes for bug fixing, feature or behavior upgrades, and involved changes to eliminate some source of complaint.

{{TrainzTip|BG=#f9f9f9|Each code build number (2 to 5 digits) maps onto a corresponding Trainz trainz build version number (a 'TB' or 'TBV' decimal like 2.9: once generally indicating a technological threshold or capability level). The trainz-build 'steps' or plateaus correspond thusly to a targeted set of capabilities, whereas several iterations of debugging and 'code build releases' (Smaller Hot Fixes and Larger] Service Pack(s) releases map into the same trainz-build thresholds. Hence the new user will notice a predominance of certain TBV values, so called major releases or major versions, in asset lists in the Content Manager searches— {1.3, 1.5, 2.2 & 2.4, 2.6, 2.8, 2.9-3.3, 3.5&3.7, 4.0& 4.3 &4.5} generally following directly the longevity of a software system. This formerly only reflected the simple relationship between the length of time a stable software suite release existed before the next retail (new) product release was launched with new technological abilities. Formerly, Content Creators deliberately formed new assets with the lowest possible TBV so the asset would be usable by the widest groups of Trainzers, many who remain faithful to an older Trainz release (and even form clubs with thousands of members, s.a. Trainz Pro Routes et. al.) — in short, if the new tech was using a tag or ability such an asset could care less about and didn't need, making a new bridge, building, business, or traincar that would please the most people makes emminent sense... Hence the wide number of V1.3, V2.6, V3.0, V3.5 assets still in very wide use.

Also, since asset features and those bits of code that can manipulate effects-instructions can be embedded inside the run time software suites are written to comply with or satisfy the particular conceived technological capability, there is a long lag time between request for a capability, and the time it shows up in an release that can exploit it.

Example: Basic traincar data structures and configuration were laid out by the end of Trainz UTC. Someone desired ability to have realistic traincar ID numbers vary automatically, submitted the idea to Auran, and the programmers implemented a set of data elements to control the effects. Which leaves most rolling stock unchanged, yet allows a technology not available in previous code releases.

A similar transition occurred for signalling capabilities regarding realism in yard crossing tracks, sometimes called 'Template:TBN' —a real common need to match prototype places (train yards).
 • Generally in the past, Data conventions increasingly enforced since TS2009 were designed and in place in the lengthy TRS2004-TRS2006 era (and JET II game engine) — yet most asset types were perfectly fine using the older simpler Trainz 1.0 era data structures which are unitary tag based in the main, and don't involve any aggregate data structures Trainz's Containers in the config.txt control files. In 2009 N3V decided to add severe filtering enforcing the newer data structures in subsequent releases. They also added installation software testing, filters, to vett and bless DLS uploads—this is updated as time and versions pass, forcing higher and higher TBV values be submitted—even when an implemented asset has nothing significantly different from the earlier 1.3 or 2.5 era assets, save an more detailed less rough sub-assembly component part (A Trainz 'dependency, like a new bogey, sound, or perhaps a traincar modified to have interactive cargo and doors that animate{{efn,Many older assets used a mix of tech tags and containers to program their manifestation in game, so adding the containers and tags to a config.txt that enabled a box or flat car to handle interactive cargos (introduced in TRS2004, a Trainz strength) required a mere cut and paste alteration. However, script and mesh dependent capabilities such as animated doors, really do warrant a version change, being far more complicated.

   }. This has been controversial and caused many aggregate assets (Routes and Sessions) to be short compatible assets. So until TS2009, older and looser data conventions were tolerated in newly altered and new assets—allowing new assets produced to a lesser capable standard.

 •  The Trainz Version number exactly matches the asset (technology 'level' identifying) Trainz-build tag number.

 •  There can be many code build numbers for a trainz-build code (or technology level); some are for a different group of languages as translations become available, and ...

 •  Each of those also has possible Hot fixes and Service Pack patches—some of which change the trainz-build, and others do not.

Hot fixes do not usually cause a change in version numbers, while Service Packs usually cause an increment of +0.1 to the "Trainz-build" tags and colloquial terms thrown around as the 'Version Number!}}

Managing these improvements in the corporate world is the task of an IT department, but since Trainz is a personal software suite, the task of updating a Trainz release devolves onto private users. This aspect of Trainz is further complicated by Trainz nature, it is at the heart, a data base manager and a huge data base (the greater size in files) with satellite tools programs (especially for example, the GUI run time modules Surveyor, Driver, Railyard, and some others behind the scenes like TrainzUtils.exe) each of which may need patched or replaced with a service pack release or Hot fix. Further, and the most problematic part as it takes some time when a user has a lot of downloaded content, a new update may also scan each item in the database, and where necessary, patch those to compliance with the 'new technology level' being introduced by the patch and corresponding to a new asset build tag number.

Trainz version numbers, the product 'technology level' increments by tenths, with Trainz 1.0 being version 1.0, TRS2009 being version 2.9, so TRS2009 + four service packs reaches Version 3.3, but so is the last Service Pack for TS2010—which was co-developed along side TS2009 as a transitional technology from 32 bit game engine to a 64 bit processing environment—so the two overlap and co-join most technology. The first 'only runs' as a 64 bit release, Trainz Railroad Simulator 2012 (TS2012, no Service Packs) is Version/Build-tag level 3.5, during which in the time it was being developed, N3V decided its old game engine needed totally re-written, spawning the crowd funding financing of Trainz: A New Era with much improved graphics and its added plateaus of both video improvements, and various asset capabilities. Hence, TANE or T:ANE spans six iterative stages of capability as it stabilized TBV 4.0–4.5, with TRS19—Trainz Railroad Simulator 2019 (released Dec 18th, 2018[4] currently topping the list of TBVs at 4.6[5]

Trainz releases are further complicated by servicing an international user base; from the start the product was produced to service different international languages groups and their translation needs. In the later practices, the plethora of internationally different releases was managed down to around four initial

Legacy (unsupported) Versions

The balance of this page is presented in ordinary calendar order, first out, first listed. The first group are the giants of history upon whose shoulders newer versions of today stand. Trainz in all versions and releases was supported for over a decade by Auran, then later by N3V Games — until the adoption and announcement of the unpopular Trainz Life Cycle policy in 2010. In the policy, an arbitrary four years has generally been added to the original retail versions release date, after which the release is magically 'called obsolete' and N3V withdraws support.

Once in a while, it's nice to take a look back and see just how far we've come! LOL - ed.

Trainz Life Cycle policy has its largest negative impact now on asset updates through the creeping rise-in-threshold-difficulty of acceptance-testing-software by the DLS software, and those requirement changes have adversely affected the reliability of the Trainz-build numbers as a tell-tale of the tech level actually needed within any given asset. The whole system now is introducing a upward version creep in assets updated or added into the DLS collection, and requires authors' to donate their time making a lot of unnecessary 'updates' to the data structures in the config.txt file leader every asset has; changes which aren't really functional^{[note 4]}, but making no real change to the assets textures, meshes and other operable guts. In short, such changes are administrative data shufflings, instituting wasted time by thousands with unnecessary work-arounds.) showing up on a users Content Manager module and Main Menu screens.

Trainz

Trainz 1.x series

Cover motto: Trainz Virtual Railroading On Your PC

Main article: Trainz with no service packs applied V1.0

Trainz beta V0.9

“	Perfection is achieved, not where there is nothing more to add, but when there is nothing left to take away.	”
—Antoine de Saint Exupery, Auran

The very rare boxed Trainz: Beta version 0.9 was published in a very small run by Auran Developments in June 2001 after several initial software download versions were made available to collaborating railfans and other involved parties for testing purposes^[6].

A few things have changed in the graphics, haven't they!?!

A brief history of Trainz by an early 'Auran partner', Charlie Lear on the development of this popular software can be read can be read here: 'A Brief History of Trainz', and much of what followed is presented with commentary and cover art up through TRS2006. The Beta release cover art contained a quote from Antoine de Saint Exupery.^[6] (See quote above). Targeted at the model railroading enthusiast's market niche, Trainz was bare of a lot of content, but delivered a Surveyor module much like today's, which is still the best in the business for route building.

   Adjusted details: no shadows, low draw distance,
     low draw detail, low train detail.
   Intel Pentium II 400mhz processor
   128 megs RAM
   Nvidia TNT2 16mb videocard
   usable settings:
   640x480 display resolution
   32 bit color depth

   Adjusted details: shadows enabled, medium draw distance, medium draw detail, high train detail.
   Intel Pentium III 733mhz processor or equivalent
   256 megs RAM
   Nvidia GeForce2 32mb videocard
   usable settings:
   800x600 display resolution
   32 bit color depth

TRS2004 series

TRS2004 with no service packs applied V2.0

Main article: Trainz Railroad Simulator 2004

This version incorporating many technical advances, not least among them the vaunted Trainz interactive industries and interactive rolling stock assets. It also established the Trainz Download Station in the internet searchable version whose descendant is today's Trainz DLS Whitepages edition. Many Trainzers held for year after year that TRS2004 was the best Trainz release ever, but time has occluded the memories that it had many growing pains as evidenced by the four service packs. While many of the new data model features were introduced in Trainz UTC, they weren't fully implemented until in 2004. By the 2005 release of TRS2006, Auran began fault testing to a much greater extent, including warning messages that now obsolescent tags should be removed. So after SP4, trainz-build code value 2.4 (V2.4), Auran finally had the extensible product that made users fans. TRS2004.exe (the Launcher module of the release commonly known as TRS2004) provided no integrated data management module. It has a module called ContentManager.exe, but it left much to be desired; at it's heart, it could only list data with very coarse sorting and display abilities. A third-party utility, TrainzObjects by Terry Franks did the best job at asset management and organization in the era until TRS2006's Content Manager Plus (with similar features) supplanted it. Each Trainz release since has a version of Content Manager; though its appearance and operation changed dramatically with the release of references.

[click for List of TRS2004 releases with Code Build numbers]
Trainz Railroad Simulator 2004, or TRS2004, had 4 service packs and spanned TBVs 2.0-2.4 and created a new data model standard introducing data structures such as the bogeys container, mesh-table container and Thumbnails containers. It should be no surprise that installing those very containers is what is needed to fix over 90% of older fault content downloaded from the DLS. Editor's note: Trainz releases in the UK require different publication and release arrangements than most of the rest of the English speaking world as the UK copyright laws require a CD/DVD 'in-the-drive' verification version. Hence UK releases typically lag Australian and North American versions and always have different code build numbers. TRS2004 v2.0 Versions for TRS2004 with no service pack applied are TBV 2.1: Australia and North American markets - initial no-CD English release: build 668 UK: build 686 Australia and North American markets - pre SP2 (hotfix release logically): build 690 French - pre SP2 (precise service pack level not known): build 745 Australia and North American markets: build 753 - likely CDROM version with hotfixes German: build 756 German: build 761 Spanish: build 835 Czech: build 889 TRS2004 v2.1 Versions with SP1 for TRS2004 applied are TBV 2.1: Australia and North American markets: build 2035 UK: build 2036 French: build 2037 German: build 2038 Australia and North American markets: build 2040, and build 2042 - probable hotfix German: build 2200 United Kingdom: build 2285 TRS2004 v2.2 TRS2004-SP2 versions This is sometimes called "The Passenger Edition", after the boxed jewel-case release CDROM title. Versions with SP2 for TRS2004 applied are TBV 2.2: Australia and North American markets: build 2145 United Kingdom: build 2146 Spanish: build 2161 German: build 2163 French: build 2176 TRS2004 v2.3 Versions with SP3 for TRS2004 applied are TBV 2.3: Australia and North American markets - SP3: build 2283 German: build 2288 French: build 2289 Spanish: build 2290 TRS2004 v2.4 Upgrades by download of pre SP4 releases: Australia and North American markets: build 2350 TRS2004 - Australia and North American markets - pre SP4 (precise service pack level not known): build 2357 Versions with SP4 for TRS2004 applied are TBV 2.4: TBS v2.4 by CDROM boxed sets; also bundled with Trainz: The Complete Collection (Trainz TCC) distributed by Paradox Interactive: Australia and North American markets - SP4: build 2365; "Trainz 2004: Deluxe Edition" Czech - SP4: build 2367 UK - SP4: build 2370 German: build 2388 French: build 2390
Note: Due to the catastrophic loss of the Auran Forum's servers and consequent imposition of a five week hiatus in that service during 2006, back checking and footnoting release announcements and code builds in this data has been sidestepped. Auran and N3V Games have not been able to restore those lost years of forum posts, and we've better things to do with our time than chase references with only academic interest.

Content Builds

Main coverage: Auran DLC: Trainz DRM Content

Auran's patch technology has the capability of updating the base Trainz version and installed addon content independently. The following is a list of released content build versions for add-on content.

Trainz: A New Era

Notes, Footnotes & References

Beginning in August of 2009, Auran/N3V Games began a Technical reference and user interest wiki called TrainzOnline. Most of the data on the site was put up by the official staff of the company.