Changing Build Number

[sfinlay]

Hi

I've been fooling around, fixing some errors on some downloaded content (not as difficult as you might at first think).
I'm looking for some advice on the following :

It's possible to change the build number in the config.txt file of an asset from e.g. 2.4 to 2.8. so that the warning about older build numbers no longer being supported, doesn't appear. I know this is merely a warning that doesn't seem to impact on using the asset but it does get rid of alot of warnings in many assets.

If I do this, will it cause any unforseen problems in the game or is it best to just leave well alone ?

 

[oknotsen]

If you manually edit the build number, the asset will become "locally modified". This will result in it no longer available for multiplayer.
Changing the number will kill the warning itself but not the reason the warning was there in the first place: To make you aware of these items not being guaranteed to work in the latest version of Trainz. The change of the number does not change the way the asset is build up internally.

 

[fran1]

If the warning is only about the build number and nothing else (pm's instead of im's for eg) change it using edit in explorer.
I'd clone the asset first then change the number and commit. If all's ok change the original asset and delete the clone.

 

[tomurban]

You can use open with CCP. It will update the build number to 2.9 and fix some other warnings as well.

 

[shaneturner12]

A couple of warnings relating to updating assets to a newer trainz-build:

1. Most of the time, this will cause extra warnings/errors due to obsolete config.txt entries and new required entries not present in earlier versions.
2. If the asset uses ARN, this will be affected as the entry that controls it in TRS2004/TRS2006 is obsolete in later versions and will need to be updated to the new tags.

Shane

 

[sfinlay]

Thanks folks.
Think i'll probably leave well alone, at least until I know a bit more about changing assets.

 

[fran1]

Thanks folks.
Think i'll probably leave well alone, at least until I know a bit more about changing assets.

Clone the original, fiddle with that. If it goes wrong it doesn't matter, delete it and start again. Don't touch built in assets.

 

[sfinlay]

Good idea. Thanks.