Trainz/Version And Build Numbers

From Wikibooks, open books for an open world
Jump to navigation Jump to search

Trainz Versions[edit]

logo
Fundamentals for Trainz Trainees

Versions and Their Respective Build Numbers
TOC | BeginningsFun | AM&C | Creation | InBook Refs ORP Refs:  • Index • Containers • Kinds • Tags | Appendixes  • Vers
Loupe light.svg
 Glossary
 HKeys-CM
 HKeys-DVR
 HKeys-SUR
 HKeys-WIN
 Mouse use
 Notations
Example of an TS2010 built-in route asset showing a vertices alignment and end-caps bounds problem with the new mesh-stitching technology introduced in TS09 and TS10. Modeled software misbehaving under the run time GUI's is one type of problem fixed by hotfixes or service packs.

Trainz Versions Overview[edit]

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

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.

File:TS2009 Launcher screen.jpg
N3V Games Windows releases Launcher Screens all look pretty much the same as this TS2009 example, and is similar (excepting color) to TRS2004's, TRS2006's and all its spin-offs like the TC's...
 • Since TS2009-SP2 V3.1 and TS2010, N3V has been putting the code build onto the Launcher Screen and the trainz-build version number onto the title bar of CM.
File:TS2004 Launcher screen.jpg
v2.0--v2.4 Launcher Screens have mostly the same choices and a different style.
File:TS2006 Launcher screen.jpg
V2.5 and up Launcher Screens look prettier since TRS2006 and all its spin-offs like the TC's, and TRS2009–TS2012's, but since they use the same layouts for the same buttons all look pretty much the same.

 

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.

P train grey.png
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 TRS19Trainz 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[edit]

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.

P train grey.png
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[edit]

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

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.

Trainz[edit]

  • Trainz, the original version, with no service packs applied is assigned a trainz-build of 1.0 (V1.0) and is known as the 'Trainz Community Edition'. The boxed Trainz 1.0 was transferred from Auran Development and released by Auran Games, Pty. Ltd in November 2001 in a self-published regionally distributed version after an initial 24 September 2001 software download only version[6] Generally, each applied service pack increments the version by +0.1, so with application of the third service Pack (SP3) the cumulative version code value becomes Trainz V1.3; the first fully stable software release of the series also dubbed as the 'Trainz Passenger Edition'.</ref> The release also included a licensed version of the three dimensional (3D) model building tool w:GMAX, which is responsible for the huge numbers of user created 3D assets[note 5] available on the Trainz Download Station (DLS) web site[7].

Early Trainz Mininum & Suggested Requirements[edit]

System Requirements[8]
Minimum
   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

Recommended

   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

 

  • The first widespread international release was in February 2002 and included SP1.
  • With SP3, this is sometimes called the "Community Edition", and by some is considered a totally separate release and product so different was the operability and reliability in V1.3.
    • Trainz Community Edition (retail version or UK Edition, SP1.3 unpatched): build 263
    • Trainz Community Edition (retail version or UK Edition, SP1.3 patched): build 277

Trainz 1.1 (SP1)[edit]

Trainz 1.0 with SP1 for Trainz applied is promoted to Trainz V1.1, code build TBDL

Trainz 1.2 (SP2)[edit]

Trainz Version 1.1 with SP2 for Trainz applied promotes to Trainz V1.2, code build TBDL

Trainz 1.3 (SP3)[edit]

Trainz 1.2 with SP3 for Trainz applied promotes to Trains V1.3, code build TBDL, and because of the functionality enhancements—is widely considered a major product release on it's own, despite being free to acquire[9]. This was the most widely distributed and longest lasting of the versions of the original Trainz product family, not replaced except for language updates and patches until the release of Trainz 2004 with several major user friendly resources added, including Trainscript,[6] a facility that enabled scenario creation.[10] A few years later Trainzscript was generalized, libraryized, and the game engine modified to assemble and run the conglomerate rules of a session 'on-the-fly', so Scenarios were soon replaced by the (scriptlet based) sessions Rules facility in TRS2004/06. This version was still being sold in the USA, with an additional Service Pack 3 CD included in the summer of 2013[11].  

Trainz V1.4 (SP4, Spanish)[edit]

Trainz 1.x implemented multilingual languages support by installation of different service packs. There was no French or Eastern European languages versions marketed.

Trainz UTC, V1.5[edit]

Trainz: the Ultimate Trainz Collection
Main article: Trainz UTC with no service packs applied V1.5

This was called the Ultimate Trainz Collection, a November 26th, 2002 release including four groups of routes expanding the options for the user.

  • UTC - English - no service packs applied: build 327
  • UTC - English - SP1,. code build 404
  • UTC - English with SP1 pre-installed as part of the 2008 Trainz: The Complete Collection Omnibus edition.


TRS2004 series[edit]

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.



TRS2006 series[edit]

The TRS2006 technology was leveraged into a large series of releases with targeted regional content, much of it formerly payware routes now shipped in partnership with Auran and N3V Games, which took over management of the franchise early in the era.

Trainz/Versions/TR06-Ver Table

Trainz Driver Edition (TDE)[edit]

This is a Trainz Driver GUI only (a game only or demo) version of TRS2006 with some features omitted; it lacked both the Content Manager and Surveyor modules, so has no expandability nor extendability (self-built routes and sessions). Like TRS2006, it is Trainz-build version level 2.5, Build number 3096 — UK release date of Trainz Driver was 24 February 2005.

  • TDE - US (Merscom) edition: build 3104 also appears to be a version of Trainz Driver Edition.[12]

TRS2006-SP0 v2.5[edit]

Main: Trainz Railroad Simulator 2006 (or TRS2006) with no service packs applied V2.5 TRS2006 - Australia and USA - no service pack applied: build 2761

TRS2006 - UK - no service pack applied: build 2773

TRS2006 - French - no service pack applied: build 2883

TRS2006 - Dutch - no service pack applied: build 2967

TRS2006 - German - no service pack applied - also called Pro Train Perfect or PTP: build 2970

TRS2006 - Spanish - no service pack applied: build 3007

 

Trainz Routes[edit]

The 'Trainz Routes' release was an add-on pack containing twenty additional layouts and dependencies for TRS2004/TRS2006 and not a program release. The DVD has an installer interface which directly patches the content into either version's data structure, but is biased to install to TRS2004 and must be given a hand-edited directory to install into TRS2006. The loader, once initialized, then presents four buttons, so requires four additional clicks, plus finishing acknowledgement clicks to completely install.

Build number (if any) and original publication date not known. Paradox Interactive re-published Trainz Routes as 3rd DVD part of 'Trainz: The Complete Collection' with cover art copyright date of 2008[13]. The release takes nearly an hour to install.

 

TRS2006-SP1[edit]

Trainz 2006 with Service Pack 1 (which was notoriously hard to install) was perhaps the most stable version of Trainz released before the latter service packs of TS2009 and TS2010, which each had four. On the other hand, the game itself was the game engine for TRS2004 with few improvements, with the main changes being the introduction of the unified utility suite Content Manager Plus.

  • TS12's CM is only slightly improved over TR06's original, and that kind of longevity and stability is an ovation all its own. TR06 would spawn numerous regional releases and until TS2009, these were clones of TR06 with a different batch of content, aside from slight changes to data models begun in TC3.
TRS2006 with SP1 for TRS2006 applied V2.6

TRS2006 - Australia and USA - SP1: build 3092

TRS2006 - UK - SP1: build 3099

TRS2006 - Spanish - SP1: build 3118

TRS2006 - as included in Trainz: The Complete Collection (aka Trainz TCC Pack, includes SP1 pre-loaded): build 3335[14]

  • A three DVD omnibus release and the first Trainz franchise release published by N3VRF41L Software (Now N3V Games); North American version distributed by Paradox Interactive. Release includes
     • TRS2006 (with SP1 pre-installed), as one third on 2nd DVD;
     • UTC and TRS2004 on 1st DVD,
     • Trainz Routes on third DVD.

TRS2006 - as included with Trainz Railwayz (includes SP1), distributed by Merscom with a Steam Loco on the cover art. (aka possibly 'Trainz Classics' in the USA): build 3337 with 2nd CD containing TC1&2[15]

Trainz TCC[edit]

'Trainz: The Complete Collection' was a 2008 Omnibus release distributed by Paradox Interactive bundling UTC, TRS2004, and TRS2006 with pre-installed service packs on a 3 CDROM single box set. Build 3335[note 6] The edition also included Trainz Routes, a collection of mainly 'Basement Railroad Empire' sized routes without sessions.  

Trainz 2007[edit]

'Trainz Railroad Simulator 2007', several Europe only releases

French Edition[edit]

  • The French TRS2006 standard edition release (includes SP1) is known as TRS2007: Build number not known.

'Trainz Railroad Simulator 2007' (abbreviated as TRS2007) was the second release targeting a regional market distributed by Anuman Interactive for sale in France, Belgium and Switzerland. There were initially two versions: the standard version which consisted of Trainz Railroad Simulator 2006 with Service Pack 1 applied, and the Gold edition, which included French regional add-on items.

Trainz 2008[edit]

Halycon Media later distributed Trainz Railroad Simulator 2007 with German region-specific content for the British, Austrian, and Swiss market.[16] This is colloquially sometimes called TRS2008.

German edition[edit]

The German edition of TRS2006, published by Auran/N3V partner Blue Sky Interactive is also known by its release name: Pro Train Perfect (PTP).
TRS2007 - German (includes SP1): build 3325
  • The German edition of TRS2006 is sometimes referred to as both TRS2007 or TRS2008, and neither has any official standing.

 

Trainz Classics[edit]

Three TRS2006 special content joint-venture production releases were put together by Auran and N3V Games with professional for pay Trainz content developers after the release of the content only add-on release Trainz Routes in 2007. In the era, Auran had over extended in developing other video games and had severe financial troubles. They subsequently laid off most of their staff, entered the Australian version of bankruptcy seeking protection from their creditors, and ended up selling (licensing) development and distribution rights for their most solid asset, The Trainz Franchise to Tony Hilliam, a software publisher with family money who ran what is now known as N3V Games. Auran Development was reorganized as a holding company Auran Holdings LLC, much as DanJaq LLC owns the rights to the James Bond franchise and licenses it to Eon Films. N3V Games now develops and markets Trainz releases, manages the Auran forums, servers, and Simulator Central online store with Hilliam as CEO.

 

Trainz Classics 1&2[edit]

'Trainz Classics 1' (TC1) and 'Trainz Classics 2' (TC2) were both distributed initially (and briefly) as separate releases in a joint venture with Merscomm as DVD producer/software distributor a couple of months apart in early 2007 and soon after as a bundled set.

Released as Trainz Classics 1; TBV V2.7
Released as Trainz Classics 2; TBV V2.7
United Kingdom released as: Trainz Railways/Trainz Railwayz2; TBV V2.7 Build 3337

 

Trainz Classics 3[edit]

The 'Trainz Classics 3' or TC3 release version and is "Trainz-build tag v2.8" and assets with that level, notably locomotives and textures using other than default AlphaHint processing as specified in their *.texture.txt ini files, were the first big group of assets that one had to fiddle with to take back to the TRS2006 standard, or make work with the new 2.8 data structures—depending upon which way one was porting assets.

  • Tag "'epbrakes' not allowed" errors were a common resultant error requiring users to delete the defunct spec line.
  • The new 'AlphaHint=' specification gives a 'path not found error' when ported into earlier versions of Content Manager Plus, specifically TRS2006-SP1's CMP.

This 'new-status-quo', with additional new data adaptation problems when porting between versions now holds true for TS09T:ANE assets builds as well.

  • Trainz Classics 3 original release - UK: build 3517
  • Trainz Classics 3 SP1 - UK: build 3529

 

Trainz Railwayz[edit]

Trainz Classics 1&2 was marketed and packaged as Trainz Railwayz in the USA and Trainz Railways in the UK. Trainz Railwayz (mainly USA) includes the full TRS2006 but the other regional editions do not.

  • Trainz Railways 1&2 - UK: build 3355

 

 

TS2009 WBE TS09[edit]

TS2009
World Builder Edition
Main coverage: 'Trainz Simulator 2009: World Builder Edition'

The following builds exist for TS2009, called the 'World Building Edition' because of upgrades of Surveyor with several new tools such as replace all and the 'Pick List' and tool extensions such as the combined modes of terrain shaping tools with a selected region. Where patches are available, these are noted beside the build number. TS2009-SP4 lacks only multiplayer capabilities and 'Native Mode' (64 bit data handling) relative to TS2010-SP4's improvements, both co-introducing and strategically adopting the major dependence on TadDaemon, Route and Session Layers, SpeedTrees, and allowing compatibility mode or native mode.

Trainz Simulator 2009: World Builder Edition
Build Number Patches Available Now[note 7] Build description Release dates R: / U:
Nexus, or 'Common' builds across languages and regional releases are highlighted in bold. [17]
Build 37??? New Installation downloads had manual patch series to 37625, and, eventual later, to 41615[note 8]   TS2009 (SP0) or TS09 ;1st English Language Release 'Only Online by N3V'[note 9] Common Code start plateau[note 10]
Build 37625 1st stable code plateau[note 11],
auto-patch sequence to 40040[note 12]
TS2009-SP0+patch; Subsequent English Online Release; Wide Distribution (e.g. Amazon.com, etc.)[note 13]   auto-patch to 38017
Build 38017 auto-patch to 40040
via auto-patch to 38599
TS2009-SP1  
Build 38411 auto-patch to 40040 English Retail  
Build 38599 auto-patch to 40040 TS2009-SP1+Hot Fix 1  
Build 38610 PROTECTED
(Just Trainz*)
Steam website's English Retail version[note 14]  
Build 38808 auto-patch to 41590 1st French Retail,  
Build 38824  
--
 
1st Dutch Retail,  
Build 38869 PROTECTED UK Retail  
Build 39176  
--
 
1st German Retail,  
Build 39413 auto-patch to 40040 Czech, Polish, Hungarian Retail  
Build 39561  
--
 
1st Spanish Retail: TS2009-SP2+hf  
Build 39979 auto-patch to 40040 TS2009 SP2  
Build 41615 manual-patch 'common code' prior to 40040 Plateau TS2009 SP2+hf1  
Build 40040  
code Hot Fix 2
 
TS2009-SP2+hot fix 2  
Build 40357  
--
 
Cabon City English Online Release  
Build 40542  
--
 
1st Russian Retail, active code produced as TS2009-SP2+hf  
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 Hot Fix: TS2009-SP2+hf  
Build 41497  
--
 
Dutch, German pre-SP3:TS2009-SP2+hot fix  
Build 41546  
--
 
1st Italian Retail, active code produced as TS2009-SP2+hf  
Build 41590  
--
 
French pre-SP3 Hot Fix, to TS2009-SP2+hf  
Build 41844 Auto update from Build 40040[18] TS09-SP3+sole Hotfix
(Common Patch results)
TS2009 SP3
 Build 44653  
--
 
TS2009 SP4 Common & Last Version, All languages
tbdl
* Just Trainz versions under UK anti-Software piracy laws require a CDROM in the drive.

 

TS2010 - TS10[edit]

Main coverage: Trainz Simulator 2010: Engineer's Edition
sometimes, TS2010 EE

With the issuance of Trainz 2010: Engineer's Edition, N3V Games continued the user-unfriendly practice of not giving unique names to their Trainz.exe files, which would minimize registry confusion. This is even worse because both launcher and loader are Trainz.exe, one in the installations' root, one in the \bin directory. TS10 introduced newer speedtrees tech and multiplayer, as well as somewhat more advanced graphics rendering and was accompanied by a new group of canned routes and tutorials, finally abandoning many stalwart routes found from TRS2004 through TS2009. At the same time, TS2009-SP4 and TS2010-SP3 and SP4 all generate Trainz-build v3.3 tech level assets.

The following builds exist for TS2010. Where patches are available, these are noted beside the build number. N3V's auto-patching capabilities were inconsistent and unreliable until late in the TS09/TS10 product update series.



 

Trainz Simulator Mac[edit]

Main coverage: Trainz Simulator Mac-1
Mac versions of Trainz and on Android and iOS on PAD computers are currently only TS2009 or TS2010 special releases.

The following builds exist for Trainz Simulator Mac. Where patches are available, these are noted beside the build number.

Build Number Patches available Build description  Release Date
Build 47652 - Planet Auran Digital Store release  
Build 47770 - Third-party Digital Store release  
Build 48159 - Feral retail release  
Build 50281 - Mac App Store Release  

TS2012[edit]

Formally, the releases title is: 'Trainz Simulator 12'.

Main coverage: Trainz Simulator 12

The following builds exist for TS12. Where patches are available, these are noted beside the build number. From TS2009 mid-releases, auto-patching of upgrades became more and more reliable as bug fixes to the patching suite of software were unearthed and fixed, so auto-patching since has been the norm.[note 15]

TS2012 - TS12[edit]

The patch will work for the following TS12 builds: 46957, 47059, 47452, and 47772[21] giving promotions: 47059 > 48249, 46957 > 48249, 47452 > 48249 and 47772 > 48249.  

Known build numbers for TS12
July 31st, 2012, 04:05 PM
  1. Build 46957 - Planet Auran release version, new trainz-build V3.4
  2. Build 47059 - Planet Auran release version (minor revision), trainz-build V3.5
  3. Build 47103 - Steam release, trainz-build V3.5 cap.
  4. Build 47452 - Just Trainz release version
  5. Build 47772 - Just Trainz release version (minor revision)
  6. Build 48054 - Defunct due to corrupt patch file
  7. Build 48249 - First SP1 hotfix, established trainz-build V3.6
  8. Build 49922 - Second SP1 hotfix, Added support for Aerotrain DLC - build July 31st, 2012
  9. Build 58414 - Third SP1 hotfix, Hotfix 3 - build Spring/Summer, 2013, established trainz-build V3.7 (TODO - Search for date, make citations)
  10. Build 6xxxx - Hotfix 4 & current build, Classed as a 'Quick bugfix' of hf3, out approximately last August trainz-build V3.7, while Trainz Mac 2 is trainz-build V3.8, the end for 32 bit CPU compatible pre-TANE Trainz versions. (Status update note on August 28th, 2014)

 

  • If you have any of the boldfaced build numbers, you can patch up to 48249. Assets with trainz-build 3.6 will then become available.
  • If you have 48249, you can patch up to 49922. The Aerotrain DLC will then become available.
  • If you have 47103, the initial Steam release, you can neither patch nor use Multiplayer. Also, assets with trainz-build 3.6 must be obtained via FTP, then back-dated to 3.5.
  • If you have any other build, you may have a pirated copy of the game.[22]


 

Content Builds[edit]

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.

Build Number Patches available Build description Release dates R: / U:
  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

Trainz: A New Era[edit]

TANE CE[edit]

Trainz: A New Era, often seen as TANE or T:ANE in forum mentions was built around a new 64 bit computing game engine written from scratch. The initial releases had over optimistic fund raising hopes and expected results too soon for the funding levels obtained. About half-way into development, major staff changes rocked N3V games as long time programmer and asset creator James Moody departed N3V leaving less user oriented programmer's in uncontested control of the software development. Unsurprisingly, it missed nearly all of the deadlines promised during crowd source funding efforts.

Trainz: A New Era, Community Editions

Trainz: A New Era, Community Edition or TANE CE were the expected benchmark partial product releases that were mainly sold by advanced subscription or as a benefit to bigger donors in the internet crowd source funding drives of late 2014.

Beta test and teething troubles plagued each of the three formally released versions of the troubled and Crowd Funded Community Editions — each released to comply with 'developmental benchmarks by deadlines' promised during raising the crowd sourced funding on the internet. The Community Editions were download-only software only available through internet subscriptions. A departure for Auran/N3V inasmuch as previous versions, excepting the Steam.com special versions of TS12 each were also offered by CDROM or DVD with printed manuals.[note 16]   The formal Beta test version was repeatedly reset and put off over the fall of 2015 and finally released for people who preordered TANE on December 10, 2015.  

  1. Trainz A New Era: Community Edition 1.0 - Trainz-build version 3.9[30]
  2. Trainz A New Era: Community Edition 1.1 - Trainz-build version 4.0
  3. Trainz A New Era: Community Edition 1.2 - Trainz-build version 4.1

 

TANE[edit]

Trainz: A New Era (TANE or T:ANE), the full release...

Trainz: A New Era was officially released on May 14, 2015[31] as an alleged full version overcoming lacks of TANE CE. TANE's Driver, Surveyor, and Content Manager modules each had their issues. Most lacked operational hotkeys users were used to having. Its CM user interface has many more powerful pluses, but wastes search specification screen space needlessly, and its overall implementation mysteriously changes terminology in the oddest places (Common Trainz operational terms, most with hotkeys before hand which were in place and well known in the community since Trainz 0.9 Beta release, and other operational menus, and especially the important mini-maps in Driver and Surveyor operated very differently. As of the SP3 release (TBV 4.5), many of these shortcomings are still disgruntling the community.

Various 'finishing touches' have been added through a succession of hotfixes, patches, and service packs with a rumored fourth service pack supposed to be nearly finished as of 12 March 2019, even while the program is being supplanted by TRS19, a new release of TANE, without the New Era tagline. One major improvement instantly popular with users was the facility allows the user to directly control where local content is kept, and to change it as desired, allowing content creators and users to customize their experience and sequester data—say separating British routes and assets from North American, enabling both less clutter in selecting and managing content in CM and Surveyor.[note 17] There have been numerous upgrades, starting from the original zip downloaded installer (Code build: 78667), SP1 (Code build: 80201), SP1 Hotfix 1: 81190, SP1 Hotfix 2: 82149 to TANE SP3 (Code build: 94916)  

TANE MAC[edit]

The Mac version of TANE was also released on May 14, 2015 as an alleged full version overcoming lacks of TANE CE. The MAC user interface from Trainz Mac is alleged to be used for CM and Surveyor screens, giving the Trainz software an alien look, see, and feel for the first time since Trainz 1.0 on the one hand, and TRS2006's CM on the other.

Notes, Footnotes & References[edit]

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.  

Notes[edit]

  1. Worse, it's evident sloppy programming and validating practices have proliferated because software companies count on such a safety net and place less emphasis on quality control—all but discounting the damage to company reputation such instability did once create. Once anti-viral software required periodic updates, the flood gates were open allowing any software to be updated automatically.
  2. Auran Holdings, Pty Ltd, The Gold Coast, Queensland, Australia is the holding company with all the Trainz rights and their partner N3V Games, Pty Ltd who bought in (2007) during Auran Games and Auran Developments' bankruptcies in 2007-2009 currently manages the development and marketing of the properties
  3. The upload filter is enforcing the latest 'supported' versions TBV number, even when the technology of the asset does not need such a level.
  4. One tendency has been Content Creator's are revisiting older content source files and upgrading them, thereafter, promoting their TBV#s on the DLS and so making the asset conformal to the DLS upload filter then in-effect[note 3] for any changes, including minor cosmetic texture replacement, since the whole file needs re-edited from tags and data structures which work perfectly well since Trainz 0.9 to a more complicated generalized structure (Sets of parameters and tags) unneeded by most common assets—in effect, the fancy feature used in a few places is placing a time charge on all content creators (unpaid volunteers donating time, knowledge, and expertise whilst giving up their intellectual copy rights!) and the casual user. Hence less and less is backwards compatible for those of us who keep up multiple Trainz releases that might also want to bring in that new cool looking bridge, unless one locally edits the asset from the DLS. Together, the DLS software and N3V originated (newer Trainz releases) also jointly have prevented downloading assets with a more advanced TBV automatically, so the user may need to manually download such an asset before adapting a updated asset in-retrograde fashion to an older Trainz release
  5. With the introduction of version creep discussed elsewhere, this figure is impossible to keep up to date as it changes daily as revised upgraded assets are improved to current TANE & TRS19 (TBV of 3.6) standards.
  6. Build 3335: 'The Complete Collection' TCC release build as noted above in TRS2006.
  7. Patches are managed and updated from a server which takes current code build information from the \bin\TrainzUtil.exe data manager and passes back a proper code updater. The code passed back includes updates which incorporate several intervening hotfixes and minor patches, and usually terminate at a plateau version — a stable Service Pack and it's few update needs.
  8. Part of build 41491's (and other early TS09 'bug fix' code builds was they were attempting to patch the 'new auto-patch software' capabilities.
     • As the first release with the TADdaemon offloading the CM code functionality, there was an understandable amount of teething troubles to iron out duties, responsibilities, function calls and other communications between the Daemon and the run-time interface modules (CM 2.0, Driver and Surveyor).
  9. The TS09/TS2009 Online Only release can be considered as a pre-release release version — effectively a Beta Test version before resources are committed to making DVD/CDROM versions, or 3rd party distribution (e.g. Amazon.com) begins. N3V management and the loyal user community play a regular wink-wink, nudge-nudge game pretending (mostly silently, with a few exceptions) the release offered as a special advanced peek release to the early purchasers isn't really just a Beta Test, we in the community agreed to be victimized by.
  10. Trainz biggest market is English speaking countries of the British Commonwealth of Nations. Consequently English speaking programmers keep the base code in English. Producing Menu labels, documentation, and asset string-table translations for the releases built-in assets tends to lag as a consequence. Any base code change affecting displayed text, is also generally delayed, sometimes only a few hours; other times several weeks. See the Language lags in TS09-SP1's to TS09-SP3's above; but also note it is quite normal for retail release progressions to be released in separate 'as up to date as is possible' as a release's code stabilizes and bugs are reported and sterilized. The final versions generally reflect all cultural/language versions merging into the final code build.
  11. The progression of changes to a new retail release can seem bewildering. First reactions generate 'quick fixes', in response to bug reports by the widespread and deep user community. These are normally called 'patches' (Small, quick fixes-generally only to a code module) by N3V Games — and like Hot Fixes (Medium large fixes: more widespread changes with combinations of various bug-fix updates; both will be incorporated in subsequent software updates either as part of plateau to plateau progression of updates, or as the original manual patch or hot fix or Service Pack release. Manual patching generally involves self-extracting code downloads, as .exe files which often have to be run as administrator, with security software (Firewalls, system protection defender, and anti-virus software protections suspended or disabled for a brief period.)
     • These, like many software installers, generate a install shield take over of the system, and generally update code modules in the installation quickly and efficiently, terminating operations in a matter of moments.
     • In contrast, while manual service pack updates are initially released in a manual self-extracting file as well (The Trainzer community can be a bit testy about waiting, esp. waiting for a bug-fix handicapping the way one wants to use the programs!) within a short while, existing auto-update software is outfitted with a modified update file incorporating all relevant changes from build plateau to build plateau. Subsequent installs will use the new combined files and skip over individual hot fixes and patches. In other words, these plateau-to-plateau updates include major patches, medium patches and minor fix patches all-in-one go. Subsequent re-installs of the software, will thus skip a lot of update steps humans experienced one by one over time. During such re-installs or moves, we humans are given the choice at each plateau to continue onto the next grouped series of updates, or stay and operate the software at that plateau (e.g. TS2009-SP2).
  12. re: 'auto-patch sequence to 40040' - Any new install will auto-patch in a succession, lowest code build to next stable plateau version, possibly passing through several upgrade stages. 'SPx upgrades' with any relevant patches and hot fixes are automatically applied as the upgrades reach from one plateau to the next. The 'SP3 to SP4 patch' (41844_to_44653.exe -- renamed to '41844_to_44653 TS09-SP3 to TS2009-SP4 (Final, common).exe' local hard drive) seems to have remained manual, based on a fresh install of TS2009 in 2019-03-29; two days prior to this edit. The other upgrades prior to this last step (i.e. previous auto-upgrades) were offers to auto-update with my intervention at each plateau, beginning with a fresh download from Amazon.com's software library. In short, I'd kept and started with the original download manager from Amazon, and ended with TS2009-SP3, and apparently need to use the manual update to reach TS09-SP4 --ed.
  13. The patches or Hot Fixes needed by the 'Online Release Only by N3V' (Beta test, in fact) are incorporated in the SP0 release distributed to 3rd Party re-sellers. These have adequate auto-patching and updating abilities, and did not have other bugs detected by the community testing the Beta release.
  14. Steam versions have restrictions on content and capabilities due to copyright constrictions. Much better to own rights to a stand alone normal PC install, finances permitting.
  15. The patching messages still leave much to be desired for one doesn't know whether a change will take moments or hours. An occasional upgrade sometimes goes alarmingly slow as the software transitioned to harness multi-core CPUs, better Graphical cards and Coprocessors, better graphics models and with the last release of TS10 and the entirety of TS12 fully utilize and embrace 64 bit operating system memory addressing mode capabilitiess and move into the 32-bit product one-step further into the future.
  16. TS2009 was the first offering via Online middleman retailers such as Amazon, though N3V had offered web download releases via their online store with the Trainz Classics 3 British Themed slightly improved version of TRS2006.
  17. Deleting all BI assets is not recommended, but disabling the asset set is quite achievable, hence eliminating the asset from new surveying.

Footnotes[edit]

  1. Trainz-build Tag table
  2. Revision as of 10:22, 2010 March 4 by Windwalkr, [ ]—1st draft to present, all immediately discussing code build number, Chief programmer Chris Bergman (aka Windwalkr)
  3. Used by chief programmer Windwalkr himself in Trainz_build_versions / code build number
  4. Auran forum post: Trainz Railroad Simulator 2019 has arrived!, Published on December 18th, 2018 09:16 PM by N3V CEO Tony_Hilliam.
  5. TrainzOnline trainz-build number encyclopedia page.
  6. a b c d Lear, Charlie. "A Brief History of Trainz". http://railsimpro.com/charlie/trainzchron/. Retrieved 02 March 2015. 
  7. At the time of this composition, there were well over 250,000 assets listed as separate DLS assets on the TRS2009 Content Manager, a number which increases almost daily.
  8. D:/Auran/Trainz/Readme.htm#1, Section 1 of the install Readme file on the CDROM.
  9. [online.ts2009.com/mediaWiki/index.php5/Trainz_SP3 Trainz SP3]
  10. Trainz SP3, apart from bugfixes, saw the introduction of the Trainzscript programming language and scripted user activities called "Scenarios"., Charlie Lear (cjlear), former Auran developer.
  11. My copy, purchased in May is shown on the introduction collage of Trainz versions. IIRC, as recently as Aug 2015 I saw 'new' & unregistered CDROM versions on the internet. - Fabartus
  12. Mercom games url: [1], various distributed TRS2006 releases in North American markets. URL valid on 2015-0815
     • Trainz Railroad Simulator 2006 on PC February 2, 2006
     • Trainz Railwayz on PCs October 8, 2007
     • Trainz: Driver Edition on PC September 19, 2006
     • source and dates by Merscom at url given.
  13. Paradox Interactive, 'Trainz Routes' bundled as 3rd DVD part of 'Trainz: The Complete Collection' with cover art copyright date of 2008.
  14. Trainz: The Complete Collection (Trainz TCC) a three DVD omnibus release and the first Trainz franchise release published by N3VRF41L Software (Now N3V Games), distributed by Paradox Interactive. verified 2013-1018 by box and build code of installed version.
  15. Cover Art, publisher, title, and TBV v2.6 of USA's BC Version 3337 all confirmed verbally via Skype with RRSignal, 2015-0815.
  16. "Trainz TRS 2007 Service Bereich" (in de). Halycon Media GmbH Co.KG. http://www.halycon.de/TRS2007/index.php. 
  17. TS2009 Original builds:
     • TS2009 - English: 37625
     • TS2009 - Polish - build:39413
     • TS2009 - Russian(Akella Games) - build:40542
     • TS2009 SP1 build: 38017
     • TS2009 SP2 build: 40040
     • TS2009 SP3 build: 41844
     • TS2009 SP4 build: 44653
  18. Just carefully tested with new install.
  19. 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 from build 43434 inferred from patching method. Manual patch directly skipped.
  20. a b c 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
  21. a b c d Thread: TS12 Patch 2 (48249) is live., July 28th, 2011, 02:42 AM, Shadowarrior, N3V IT staff.
  22. a b c Known build numbers for TS12: July 31st, 2012, 04:05 PM Scottbe8
  23. 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
  24. 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.
  25. 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
  26. Trainz 12 Service Pack 1, by aronc, Published on April 10th, 2013 12:47 AM
  27. a b c d e f TS12 SP1 Hotfix 3 and Auto-patch Now Available, by WindWalkr, Published on June 6th, 2013 02:00 AM.
  28. TS12 SP1 Hotfix 2 now available, by GPavlich, Published on April 30th, 2013 07:38 AM
  29. a b TS12 SP1 Hotfix 1 now available, by GPavlich, Published on April 18th, 2013 02:00 AM
  30. TrainzOnline Trainz-build number (list page).
  31. TrainzOnline article: T:ANE "Release Version", which also lists features improved since pre-release Beta testing releases.

Sources[edit]

  1. www.auran.com auran store links (historical 'release' names, albeit, ephemeral)
  2. TrainzOnline Trainz-build tag wiki page
  3. TrainzOnline Trainz Code build version wiki page