download and install some custom routes

[lackoo11111]

i need some advice.

I’d like to download and install some custom routes / sessions that were made for TANE into TRS 22.

These routes / sessions are containing assets that were originally created in earlier trainz versions .

My question: do i also have to edit the config file of the routes / sessions if i download the newer versions of those assets from the DLS or the game will automatically replace the obsolete ones with the new one ?

( sorry if this sounds silly , but i’m not a content creator , just a simple user )

Thank you.

 

[marmalade32]

you'll have to find the tag in the config that says trainz build and bring it down from for example 5.1 to 4.2 or below.

 

[johnwhelan]

They should work fine as they are.

Cheerio John

 

[johnwhelan]

you'll have to find the tag in the config that says trainz build and bring it down from for example 5.1 to 4.2 or below.

TANE is not 5.2, and that's where they're starting from.

Cheerio John

 

[marmalade32]

TANE is not 5.2, and that's where they're starting from.

Cheerio John

well, what i was saying was to bring it down from 5.2 or higher to whatever tane's build is. stupid ole marmalade32 doesnt have is brain on t'day, if at all.

 

[JCitron]

well, what i was saying was to bring it down from 5.2 or higher to whatever tane's build is. stupid ole marmalade32 doesnt have is brain on t'day, if at all.

I can commiserate with you on brain farts. They pass by from time to time and we all hope that they do without catching us off guard. ;-)

Down-versioning content doesn't always work and given how much has changed since T:ANE came out a decade ago, this definitely may not work at all except for simple objects. This is definitely true of routes and sessions due to the file-structure changes in TRS19 and up.

 

[oknotsen]

Off-topic:

you'll have to find the tag in the config that says trainz build and bring it down from for example 5.1 to 4.2 or below.

You can't move routes to a lower version. Editing that tag would only help in the process of breaking the route.
Some objects can be edited to move to lower versions (which by the way is NOT the question of this topic) but routes can not. The way the files are stored are different, not just the version number in the config file.
Please do NOT make this wrong suggestion as it will harm those who know even less of how this works.

 

[lackoo11111]

Off-topic:

You can't move routes to a lower version.

I never said that i want to do that .

I want to install routes that were made for TANE and install them into TRS22 . I'd like to know : do i have to manually update the kuid list in the route config file if the CM find and install the updated version of the assets that are part of the route and sessions .

 

[wreeder]

I never said that i want to do that .

I want to install routes that were made for TANE and install them into TRS22 . I'd like to know : do i have to manually update the kuid list in the route config file if the CM find and install the updated version of the assets that are part of the route and sessions .

Yeah, reading is a hard sometimes. No editing of the routes and sessions are required. Content manager always downloads the newer version available on the DLS as long as you are using a compatible version of Trainz which in your case is TRS22. TRS22 will use the newer version automatically.

 

[JCitron]

@lackoo11111 in summary, newer versions of Trainz will import 99.9% of older content just fine. The older content may not always look the best, or may have other issues, but that's another ball of wax to play with. Many of our routes, especially those we started 20 or more years ago contain assets from the earlier Trainz versions. These are usually bridges, buildings or other objects. Many of us with routes like that have been renovating and replacing the old with the new.

T:ANE routes are usually fine when they come into TRS22. The sessions may need updating, so ensure you have the latest versions of any of the rules and driver commands if they are different. Most will work fine, but there are those that are affected by the stricter scripting requirements in the newer versions.

There is one thing I discovered not long ago. After importing the route and sessions, open and save them at the current Trainz version. I found that by doing this they behave a lot better than when running with the older version.

If this is someone else's route and session, use this method here:

Open the Session for editing and make a slight change to force a save. When you save, choose Save route and session. (Or however it's worded). By saving the session and route, this will keep everything intact including rules, drivers, industry configuration, trains, etc., and it beats going through the longer process of editing config.txt files, and it's also a lot easier too.

A few years ago, I imported my very first Trainz route I built in TRS2004 SP1 into TRS19. It came in okay, missing some track that was replaced by white lines, but other than that it came in without any technical issues. Note, technical issues... My landscaping, texturing and track laying skills had a lot to be desired. After putting the old route through a major renovation, I was able to bring portions of it into my current iteration of the old route and there it is living on hopefully for more decades to come.