Problems with a map and sessions, meant for Tane (build version 4.5)

[Swordfish]

kilanziom has published a very beautiful map, <kuid:173943:106917> Bystrzycka Railway 1976-SUM, and two sessions for Tane (build version 4.5). All assets of the map are on the download station or easily available. The map and the session with the rolling stock are looking wonderful.

But there are some problems with this map in my Trainz+, Build 129343. I would like to discuss these problems. Perhaps someone has other problems too, or a workaround for one of these problems.

1. The warning "There is missing a lever after junction xyz". The map has no missing levers. Here is the problem, that some junctions are out of order, showing it in surveyor with two red arrows, instead a green and a red one.
The workaround in surveyor is: F4 Tracks/Trackside-Mode/Junction. Klicking on the junction out of order will throwing the switch and the two red arrows will change to a green and a red one. After that you can save.

2. The portal <kuid2:116387:6:3> Re-rail Portal Basic made by maggs. This portal has an extended functionality compared with the built-in one. This functionality is hampered: A train with the order "Enter this portal and return through the other portal" will not enter the main track. It is possible, to change to surveyor and pull the consist manually to the main track. If you give the consist several orders, it will loose these orders if you use the function "repeat". It is possible, to give the order "Enter this portal, return through the other portal and drive to the industry xyz".

3. Sometimes, when you are changing from one AI-driven consist to another, the command-list is not changing. That is, the new consist is showing the list of the old one.

Your comments and ideas are very appreciated.

Regards
Swordfish

 

[JCitron]

I've seen odd issues with other routes built in earlier versions and brought into TRS-Plus and TRS22 relations. My fix is to open the route and session and save in the new version.

The issue with the junctions is a bit different. It could be that they are marginally set up. No fault to Kilanziom because the junctions showed no errors when he built the route. What you might want to try is to wiggle the track and maybe stretch the junction a bit. You might also want to try Delete Missing Assets even though the route has none. This process also resets the object table and may clear up the errors. In the early T: ANE days, we ran into this in between service packs, and Tony mentioned this as a fix and it worked. It's possible that the route needs a bit of a clean-up.

The issue with the Re-rail Portal Basic is related to scripting and this affects all portals. I found that the vanilla Portal Basic works most of the time, and I thought the issue was related only to non-vanilla portals, but it turns out to be a random hit or miss that they'll work or not. Other portals, such as the Re-rail Portal Basic though definitely will not work.

I don't know what to say about the command-list. Is there a delay or pause causing the list not to change when you switch drivers? It could be that Trainz is busy working with other things then forgets to switch the driver commands.

 

[Swordfish]

Thank you very much, John, for the hint with opening the route and session and saving in the new version. After that, the problem with the junctions has disappeared.

I replaced the portals, which are installed in the route (<kuid2:116387:6:3> Re-rail Portal Basic by maggs) by <kuid2:96914:22000:4> Portal Basic Short Classic made by bdaneal. These portals seem to run fine in this moment.
In front of a portal, which is consuming trains, I put in some distance an invisible speed-sign "10km/h" or "5mph".

There is a problem with trains, overshooting signals. This is not with all signals. Does a rule exist, which is triggered by the following if-command: "If (driving over the trigger) the signal in front of the consist is read, then reduce the speed to 10km/h"?

With the command-list I have to make further tests.

Regards
Swordfish

 

[JCitron]

Thank you very much, John, for the hint with opening the route and session and saving in the new version. After that, the problem with the junctions has disappeared.

I replaced the portals, which are installed in the route (<kuid2:116387:6:3> Re-rail Portal Basic by maggs) by <kuid2:96914:22000:4> Portal Basic Short Classic made by bdaneal. These portals seem to run fine in this moment.
In front of a portal, which is consuming trains, I put in some distance an invisible speed-sign "10km/h" or "5mph".

There is a problem with trains, overshooting signals. This is not with all signals. Does a rule exist, which is triggered by the following if-command: "If (driving over the trigger) the signal in front of the consist is read, then reduce the speed to 10km/h"?

With the command-list I have to make further tests.

Regards
Swordfish

You're welcome, I'm glad the other solutions worked for you.

What may be needed is an advance signal further back from the absolute to warn the drivers of an upcoming red. I do that on my own routes and it helps.

 

[Swordfish]

This image is showing the different state of signals. At left, the signal is "not red" and the yellow disk as distant signal is showing, that the next signal, far away, is "not red". On the right side, there is the signal, where AI-trainz are "overshooting", I think, perhaps the distant signal is "blocking" the main signal. I tried it with a invisible-speed signal around 20 meters or 20 yards away with "1kmh" or "2kmh". The consist is getting to a stop, the main signal is changing to "not red" but the train is not moving.

Does a rule with a trigger exist: "Do drive 2 kmh for 5 seconds"? After that time the temporary speed signal would be lifted and because the main-signal would be "not red" the consist could drive.

 

[JCitron]

Ah, that's a scripting issue with the signals. There's a group of European users working on new ones. I don't know the status of the project.

 

[Swordfish]

I tried another Polish map and session with build 5.3 in build 5.6. There the portals are still running fine. The portals made by maggs must be broken by a later build.

Another problem I noticed is, that in build 5.3 and later builds most Polish locomotives are loosing the main steam during driving. Standing is ok with the steam.

Regards
Swordfish

 

[JCitron]

I tried another Polish map and session with build 5.3 in build 5.6. There the portals are still running fine. The portals made by maggs must be broken by a later build.

Another problem I noticed is, that in build 5.3 and later builds most Polish locomotives are loosing the main steam during driving. Standing is ok with the steam.

Regards
Swordfish

Yes, portals are broken. Portal Basic, the one from N3V and built-in, appears to work well most of the time. The others such as the re-rail portal are broken and weird things happen.

The steam issue has to do with engine specs. I don't think anything changed with those in this version. Not being familiar with steam, hopefully someone else who is will chime in here. You could try using one of the newer-updated specs uploaded recently by 2995Valliant.

You can do this right in the session editor without needing to edit the engine in Content Manager. Open the properties (Ctrl-right-click) on the locomotive and choose edit.