The new TRS2022 routes

Well that was/is a disaster!

Deleted all the caches, extended database repair, no difference. Deleted prod people 19,extended dB repair, o difference

Deleted TRS22, reinstalled from scratch, no difference.
That's TRS 22 broken!

I'll check a few more routes, but this doesn't look good.

Colin


Yes, I'm seeing some issues too. It is Beta after all!

For example, DLS route Stockton Terminal works fine in '19 (though I have 3 unknown assets). In '22 I have same 3 unknown assets but I also have a bunch of "invisible" cars in consists. Some of them are there, the just don't render. My train has a large "gap" after the loco but cars behind the space faithfully stay coupled to the train and stay with the loco. About halfway back there is a 2 or 3 car gaps and the last half of the consist remains, obviously, uncoupled.
 
There will be an update coming to fix the passenger issue. Finding faults is what a beta is all about. 97 of 98 routes I have installed have no problems caused by TRS22.

Cheers Graeme
 
There will be an update coming to fix the passenger issue. Finding faults is what a beta is all about. 97 of 98 routes I have installed have no problems caused by TRS22.

Cheers Graeme

Well, how about Ai's not working? Created a new "test" route. I set up 3 trains and created a set of commands for them. Then I went into driver mode in the session and..... 2 trains worked and the other one just stood there without the driver commands showing. Deleted all the consists and tried again. Same thing. Maybe in this version I can only "program" 2 trains to run as AI. :confused:
 
As far as I know there is one missing dependency in West from Denver. You can still explore the route in surveyor and/or create your own sessions.

I'm running a test route with 60+ AI drivers. I suggest you re-check the commands, the pathing, the track, any track direction markers. Also turn driver messages on to see what the problem is.
 
When I first downloaded TRS22 Beta and the WfD route I tried to test the two Amtrak sessions because I created the originals and I sent several Bug reports relating to the issues I found:-
1. The install package includes an HTML file that the release session does not require.
2. The "driver schedule rule" is broken and shows drivers as missing and hence the AI trains are never triggered to start and pass the player train as they should.
3. The Locomotives used are modified Jointed Rail locomotives and I have the originals from JR. The originals work perfectly. The N3V cab view flickers and flashes constantly making it virtually unusable.
4 This is a common problem not limited to the two Amtrak session and it is the inability to set different locomotive numbers on the locomotives of a given type.

I hope all of those as well as the missing dependency are being addressed.

I made several other sessions not adopted by N3V and when I imported them into the TRS22 Beta they all suffered from the driver schedule issue and one also had two locomotives and an invisible speed signal displaced off the map. This may be the same issue reported where the player locomotives appear off the map in the Amtrak sessions. My solution was to recreate the session and replace the same assets where they should have been and that worked.
 
Thanks DennR for this post.
Issue #2 ("driver schedule rule" is broken) is exactly what is happening in my test route. I am glad to hear that someone else has had this problem. I have been working with Trainz for a long time and I do know what the possible problems could be, as in "I suggest you re-check the commands, the pathing, the track, any track direction markers. Also turn driver messages on to see what the problem is."
Anyhow, I will send in a bug report.
 
Issue #2 ("driver schedule rule" is broken) is exactly what is happening in my test route. I am glad to hear that someone else has had this problem. I have been working with Trainz for a long time and I do know what the possible problems could be, as in "I suggest you re-check the commands, the pathing, the track, any track direction markers. Also turn driver messages on to see what the problem is."
Anyhow, I will send in a bug report.

You are correct, before I sent the Bug report I made all the checks I could but all the (#2. #3. & #4.) errors were 100% repeatable and I found #2 & #4 in multiple DLC sessions.
 
The ad for TRS22 says it includes 5 new routes:

1 • West from Denver - Moffat Route
2 • Schwäninger Land
3 • Liskeard to Looe
4 • Bairnsdale to Orbost Line
5 • Beloreck - South Ural Mountains

And there are 9 engines on the roundhouse:

Amtrak P42DC (1)
DB ICE (2)
Class 47 and 153, BR Switcher (3)
VR T Class (4)
VL82 (5)
Class A1 Tornado
BR Inter-City

What route will the last two run on?
 
Last edited:
The ad for TRS22 says it includes 5 new routes:

1 • West from Denver - Moffat Route
2 • Schwäninger Land
3 • Liskeard to Looe
4 • Bairnsdale to Orbost Line
5 • Beloreck - South Ural Mountains

And there are 8 engines on the roundhouse:

Amtrak P42DC (1)
DB ICE (2)
Class 47 and Class 153 (3)
VR T Class (4)
VL82 (5)
Class A1 Tornado
BR InterCity

What route will the last two run on?
Technically, they could run on Liskeard to Looe, but that would be a long shot. More likely future DLC?
** I just watched the video for Liskeard to Looe again and the Tornado is shown towards the end, I am not sure about the BR Intercity but it may have been on there too.

Cheers Graeme
 
Last edited:
Thanks, but the question was about TRS22 in-game routes.

If I am not mistaken the map show intercity routes Kings Cross Edinburgh and Edinburgh Aberdeen via Dundee and those the DLC routes "ECML Kings Cross - Edinburgh" and "ECML Edinburgh - Dundee" Both are TRS19 routes available in TRS22. They are Intercity routes and would by applicable for the Tornado as an express passenger locomotive of it's day.

The Loco Trust website shows typical consist builds that the Tornado would have hauled when in mainline passenger service. I hope that clarifies what I posted.
 
Back
Top