Built in sessions apparently not updated from previous versions.

mike_hooper

New member
I don't know if it's just me but it seems as though many of these sessions don't run correctly. I have so far only found one "ride" (auto-session) that runs unless I'm missing something. Local Freight seems to have a turntable problem, Railway Festival selects wrong track (siding) on fourth loco, Pick Up Cars seems to have a problem with "run around train", Heidenberger 3, I couldn't start train and so on. Now if I'm right (and not just incompetent!) this is an age old problem of sessions not running correctly in a subsequent version, however this is not a cheap game and the company presumably wants to attract new enthusiasts. Disappointment is not the way to achieve this, is it? I have been with Trainz since UTC, however I'm only a (elderly) dabbler and, with the limited instructions available, I'm certainly open to correction.
 
This sounds like you're missing something because no one else ran into this issue that I am aware of. Believe me if others ran into this issue, there would have been a flood of words here in the forums that would go on for pages and pages, upon pages, of reiterated kvetching forever covering the topic.

Have you tried:

A DBR?

an EDR?

A clean database?

To create a clean database:

1) Create an empty folder in Windows File Explorer.

i.e. folder on D: drive (if you have one) called TRS19_Clean_Data

2) Go into the Launcher Settings.

3) Click on the Install tab.

4) Jot down where your current install is located on a piece of paper and save it. (Important in case this doesn't fix the problem so you can go back to the original location).

5) Click on the three dots on the far right of the path

6) Browse to your TRS19_Clean_Data

7) Click on Select Folder

8) Close any windows afterwards.

You'll see a quick Updating translations run.

9) Restart when prompted.

10) Go into Settings again and put in your username, password, etc.

11) Restart again.

12) Go in and set things up - graphics settings, etc.

13) Restart again.

14) Start and you should be prompted to download DLC and built-in routes that don't come with the install directly, but are downloaded later.
 
This sounds like you're missing something because no one else ran into this issue that I am aware of. Believe me if others ran into this issue, there would have been a flood of words here in the forums that would go on for pages and pages, upon pages, of reiterated kvetching forever covering the topic.

Have you tried:

A DBR?

an EDR?

A clean database?

To create a clean database:

1) Create an empty folder in Windows File Explorer.

i.e. folder on D: drive (if you have one) called TRS19_Clean_Data

2) Go into the Launcher Settings.

3) Click on the Install tab.

4) Jot down where your current install is located on a piece of paper and save it. (Important in case this doesn't fix the problem so you can go back to the original location).

5) Click on the three dots on the far right of the path

6) Browse to your TRS19_Clean_Data

7) Click on Select Folder

8) Close any windows afterwards.

You'll see a quick Updating translations run.

9) Restart when prompted.

10) Go into Settings again and put in your username, password, etc.

11) Restart again.

12) Go in and set things up - graphics settings, etc.

13) Restart again.

14) Start and you should be prompted to download DLC and built-in routes that don't come with the install directly, but are downloaded later.

Thanks, John, I did wonder about that. I will try your suggestion when my friend who is a network engineer is here next Tue. It's a bit strange when every thing else seems so perfect.
 
Mike - the problem with Brazemore Yard sessions are well known and have existed for a long time. (TANE & TRS19) They've been reported. I reported them again when beta testing TRS19.

I no longer report problems with N3V Route Sessions (of which there are many) since they seem to be very far down on the priority list of fixes.
 
I no longer report problems with N3V Route Sessions (of which there are many) since they seem to be very far down on the priority list of fixes.

While I understand that reasoning, I would recommend that everyone continue to report problems with N3V Route Sessions, or anything else for that matter. No matter how far down on the priority list of fixes you think that something might be, if enough reports on the same issue are made then it has a greater chance of rising up that list.
 
Have you tried:

A DBR?

an EDR?

A clean database?

I have noticed that these questions often appear in the forums but there is little official information available to point users to. The Trainz Wiki is sadly lacking (or my searching of it has been poor) so I have created a new Trainz Wiki page detailing the steps and process (as I understand them) involved in each of those three points. The "clean database" I have based on your steps supplied in the post referenced above. Since I am no expert on these I would appreciate it if users could look at the page and provide me with some feedback and constructive criticisms before I add it to the official Trainz Wiki indexes.

The page is at http://online.ts2009.com/mediaWiki/index.php/How_to_Perform_Database_Repairs

Thanks
Peter
 
Did that but no discernible difference. Looks like the "Rides" are wrongly labelled. Cattle to Hawes seems to work fine as a normal session. Now found that Fossil Fuels doesn't work. Cannot couple to empty hoppers as the blue couple sign won't change to the next sequence. It's just "stuck". I don't know how many more errors there are out there but it doesn't look very good. It looks like the sessions were just bundled up and no one thought to check whether they worked properly. Some one needs to take responsibility for this sort of problem and sort it out.
 
Thanks for the interest guys. It will be a big bug report! One thing. As far as I can see nearly all the sessions labelled "ride" i.e. auto-session, are just ordinary sessions that mostly work. So is it simply that these sessions have been mis-labelled or is there some sort of fault preventing them from being auto?
 
Back
Top