New build for TRS

[peeet2005]

Is it possible to find out what were the important reasons that the new build 5.2 was introduced? The effect of this is the lack of compatibility with the TRS19 version. Is this another push to buy the TRS22?

 

[Forester1]

Each new release is always a new build. So yes, you might say so, but version numbers also have to change when they make changes and improvements under the hood that won't work with the older versions. That is why we can't back-version things, as they won't work.

 

[pware]

I did attempt a search for an answer on that but I was unable to find anything definite - but that is not to say that a "conspiracy" to purchase TRS22 is the cause.

In general, looking back at the build number wiki page confirms that every new version of Trainz has also seen an increase in the minimum build number of routes created with that version. Each new version has introduced changes to the map structures, file formats, etc, used in each version. This "up-versioning" also occurred with the release of many of the Service Packs for each version.

TRS19, for example, has had 4 SPs released and each one has an increase in the build number.

TRS19 SP5 set the minimum build number to 5.0
TRS22 set it at 5.1
TRS22 SP1 and Trainz Plus SP1 set it to 5.2 - possibly because of a significant increase in the file compression level used.

The latest beta for Trainz Plus sets the minimum build number to 5.3 - no doubt because of the introduction of HD Terrain.

 

[JCitron]

The latest beta for Trainz Plus sets the minimum build number to 5.3 - no doubt because of the introduction of HD Terrain.

The reason for this is to prevent beta-created routes from being uploaded to the DLS. Once the version is released, build 5.3 will become the standard or may be some other version. Tony mentioned this some time ago in a forum post.