Why is there a trainz-build line ?

cascaderailroad

New member
If all config files had no trainz-build line whatsoever, would assets show up in all versions ?

I really can not fathom the reason for a config file, trainz-build line ... unless it is put there, deliberately, and updated, so as to sabotage lower trainzbuild versions of trainz, in order to sell higher versions of Trainz ? ? ?

With a little work changing/backdating the trainz-build line ... one can get the TS12 GG1 working in TRS2006, and possibly TRS2004
 
Last edited:
If all config files had no trainz-build line whatsoever, would assets show up in all versions ?

Some would, but a lot won't because of the way that assets are configured for later versions now.
Older builds just can't compute some of the differences, just the same as TS12 can't handle some
of the older stuff.
 
not all trainz builds recognize the same config tags that take advantage of new features or even have the same config structure per version. the build-line lets the game know how to interpret the config, or for lower versions, lets them know they cannot possibly interpret the config. if you have in fact converted a 3.5 asset to work in a lower version you are aware of the differences in config structure.
 
It's there to show what version of Trainz it was made in, for and works properly in without anyone "Hacking" it, need to stop this paranoid line of thinking, not everyone hiding behind that bush is out to get you. :hehe:
 
As I said: It is easily accomplished: With a little work changing/backdating the trainz-build line to 2.6 ... one can get the TS12 GG1 working in TRS2006, and possibly TRS2004

I have edited many version 3.3 assets, and asside from deleting a few config file "Error" lines ... almost ALL TS12 assets can be used in TRS2006
 
well, i can tell you mine wont, at least not without breaking of removing functionality from them. for that reason, the build number is needed.

also, if you try to transplant a ts12 config to trs 06 i know for a fact that you have to restructure the config. the tags are different as are the tables. some old tags were obsoleted and some changed to be more efficient, again, a good reason to have the build numbers.
 
The only reason I change any buildnumber is because I can't run anything higher than 06 with my Craptacular computer.
I hope i'm not doing anything wrong by doing this. :(
 
Is that really true? I find 09 to be far easier on the hardware than 06 was.

IDK why but I can't run it my processor isn't good enough.
I read fter buying my copy that it is 2.2 GHz I have 2.0 GHz and it lags just as bad as my '10 (which I bought before I read the minimum required specs) :/
 
Last edited:
Along the lines of Norfolksouthern37, I have some 2.9 steam locomotives that won't run in anything earlier than TS2009 SP1 due to some of the materials used. The bogeys use tags that were introduced in TC3, and so won't look correct (won't align to the rails on curves) in earlier versions. And, some of the scripting won't run in versions earlier than TRS2006.
Many simple assets are easily backdated, but many others are not.

Curtis
 
Here's an interesting thing related to the trainz-build entry.

If the line is omitted, trainz-build 1.3 (Original Trainz SP3) is assumed.

Shane
 
I made the GG1 and can tell you it may run in TRS6 but it is not running right as it uses the same tages Pencil42 used.
 
As one who has converted may items to run in different version, I can state that you lose functionality of some features, particularly scripted functions. The Trainz Build entry is essential in my way of thinking.
 
I have a question about backdating assets to run in a lower version of Trainz

In TRS2006 when you edit a 09, 10, 12 asset, Trainz still see's the original trainz-build line tag, until you delete the 2 files: assets.bku, and then assts.tdx ... these files must be deleted and sent to your recycle bin ... then when you restart the CM the TAD rebuilds for @ 20 min, then the asset is usually ready to use in TRS2006.

But a 09, 10, 12 route never shows up in 04, 06 (just a blank sky, and no baseboards) I suppose because the mapfile is totally different than 04, 06 ... how can this be corrected to show up in TRS2006 ? I suppose NO ! ?

===============================

And can a 12 route be backdated to run in 09, 10 ?
And do you still use the process of deleting the 2 files: assets.bku, and then assts.tdx files, when backdating TS12 assets for use in TS09, TS10 ?

Lastly: Where is Euphod ?
 
Last edited:
Can a TS12 route be backdated to run in TS09, TS10 ?
And do you still use the process of deleting the 2 files: assets.bku, and then assts.tdx files, when backdating TS12 assets for use in TS09, TS10 ?

Lastly: Where is Euphod ?
 
Can a TS12 route be backdated to run in TS09, TS10 ?
No. Routes generally aren't able to be backdated - sometimes even accross service packs (TS12 SP1 to plain TS12, for example) You might get lucky, though....

And do you still use the process of deleting the 2 files: assets.bku, and then assts.tdx files, when backdating TS12 assets for use in TS09, TS10 ?
Eeek! No!! Just commit the changes.

Lastly: Where is Euphod ?
Not sure, but it would be nice to see him again.

Curtis
 
Back
Top