What assets are ACTUALLY TS12?

[frogpipe]

Obviously as time has gone by, the specifications for Trainz assents has changed. The programmers have seen fit to retain backward compatibility, however not without penalty.

These penalties seem to vary, depending on how old the asset is, however they do carry a penalty.

My question is, when did the current TS12 specification come into effect? v 2.7 (aka TS2009)? Or later?

I want to know because I want to make sure NOT to use older assets in my own route. I want to make sure it's all TS12 level and not encumbered by outdated models/configs/textures/etc.

 

[GP30Fan]

The current TS12 spec came with TS12. Some TS12 assets are a bit problematic in earlier version.
Not all... just some. Especially scripted assets.

In CM... place your cursor on the little arrow next to the title "Name" in the sort bar. Right click and
make sure there is a check mark next to "Build Version".

This will allow you to sort by build version in CM.

Piece of cake...

=AL

 

[shaneturner12]

For TS12, it's best to use 2.9 and higher (2.9 is TS2009), due to changes between 2.9 and earlier versions.

As for routes, 3.5 or 3.6 are best, but lower builds can be used (bear in mind though that anything below 2.7 (Trainz Classics 1+2) will show a warning in Content Manager).

Another tool in Content Manager and in-game is the Minimum Build Version search term.

Shane

 

[frogpipe]

Ok, thanks!

 

[johnwhelan]

For simple scenery objects the build doesn't matter that much as long as they are error free.

Cheerio John

 

[mraven9]

For simple scenery objects the build doesn't matter that much as long as they are error free.

Cheerio John

We are having trouble with american grade crossings, buildings, trees, etc and engines and rolling stock showing up in red, and when we click on them we can't use them

I tried re-downloading the files and it didn't seem to help

Is this the same problem?

 

[BuilderBob]

I tried re-downloading the files and it didn't seem to help

Is this the same problem?

No. There is no problem using assets created for earlier versions, except for issues common to all assets - if they are built incorrectly then they might have errors that prevent them being used. However, the standards enforced on content creators got tighter with each release, so it is likely that newer assets have less errors. You need to right-click each faulty asset and examine the errrors in order to discover the cause of the problem.

The reason for the error is probably using assets with build numbers later than that supported by your version of Trainz. For instance, TS12 will not be able to use assets with a build number of 4 or greater. See:
http://online.ts2009.com/mediaWiki/index.php/"trainz-build"_number

 

[JCitron]

We are having trouble with american grade crossings, buildings, trees, etc and engines and rolling stock showing up in red, and when we click on them we can't use them

I tried re-downloading the files and it didn't seem to help

Is this the same problem?

Welcome to the forums.

Without seeing the actual assets, it's difficult to tell. It could be that the assets are much older than TS12.

What assets are you having difficulties with?

Post the KUID and the asset name so we can take a look.

For the most part, older assets will work fine in T:ANE as along as they meet the standards that they were created for at the time. This means that if the content creator followed the rules for TS12, then that asset will work fine as it followed the specification. With older assets prior to TS12, this is a bit more difficult because the specifications weren't always verified - we have better error checking today so, therefore, more errors are caught beforehand and not during runtime, which meant in the old days severe crashes. With older assets, such as those from TRS2004 and below, the content creator would include things not part of the specs in their config.txt files, for example, which are not part of the rules. The problem then is the program, at the time, would then parse through the content, looking for the correct information, causing bad performance, and even crashes.