Signals won't work with Enhanced Interlocking Tower

I recently got 2022, coming from 2019. As always I check to see how updates and changes effect scripted assets. The scripted signals I've been using these past few years (since TANE SP3 broke my other signals) don't seem to work with enhanced interlocking tower anymore. The path will set, mouse-over on signal states the line is clear but the signals themselves are dark. It's an old script and I figured the day would come so I guess it's back to 2019 build 114800 until Trainz has a unified and reliable signal control system that allows extended states.

Is this all signals or just a few?

Also, ITs and EITs have several control settings that can alter how they work. It has been a while since I experimented with them but one setting that I found troublesome back in TANE switches the signals between manual and automatic control. Try toggling that control to see if it makes a difference.

pware said:

Is this all signals or just a few?

Also, ITs and EITs have several control settings that can alter how they work. It has been a while since I experimented with them but one setting that I found troublesome back in TANE switches the signals between manual and automatic control. Try toggling that control to see if it makes a difference.

Click to expand...

Any signal under control of EIT. Same route and settings in both 2019 and 22, only difference being the EIT assets, MCM ect were giving showing errors in 22 so I downloaded the newest versions (quick portal manager still showing errors).

In that case I would submit a bug report, giving as much detail as you can.

These are some of the assets by pguy and they are all fine in TRS22 118660. All scripted signals I use (sig br (w)) work fine on the automatic settings.

<kuid2:61392:8330:71> SetMCTimeTable (TANE SP4 and later)
<kuid2:61392:8290:85> MissionCodeLibrary (TANE SP4 and later)
<kuid2:61392:8322:74> AutoDriveWithMCTimeTable (TANE SP4 and later)
<kuid2:61392:8130:87> IT Enhanced Manager rule (TANE SP4 and later)
<kuid2:61392:4050:65> Common data library V3 (TANE SP4 and later)
<kuid2:61392:8190:87> EnhancedInterlockingTowers library (TANE SP4 and later)
<kuid2:61392:8200:85> MissionCode manager (TANE SP4 and later)
<kuid2:61392:5013:34> Quick portal manager stack library (SP2 and later)
<kuid2:61392:8193:1> Extended FET Library (TANE SP4 and later)
<kuid2:61392:8321:71> AutoDriveToMCPathStop (TANE SP4 and later)
<kuid2:61392:4007:33> Clipboard library (TANE SP4 and later)
<kuid2:61392:4054:11> Global Locks Library (TANE SP4 and later)
<kuid2:61392:4008:53> Quick CustomHud Library (TRS19 SP4 and later)
<kuid2:61392:5020:48> Quick CustomHud Manager (TRS19 SP4 and later)
<kuid2:61392:4051:1> Icon cdlib
<kuid2:61392:5011:57> Quick Portal Manager with Timetable standard edition (TANE SP4 and later)
<kuid2:61392:8203:80> AddMissionCode (TANE SP4 and later)
<kuid2:61392:8101:78> Enhanced TRC3 invisible Interlocking Tower (TANE SP4 and later)
<kuid2:61392:8114:78> IT CancelEnhancedPath (TANE SP4 and later)
<kuid2:61392:1071:10> mc Custom HUD V2 (SP2 and later)
<kuid2:61392:8111:78> IT SetPath (TANE SP4 and later)
<kuid2:61392:8113:78> IT SetPathAndWaitActive (TANE SP4 and later)
<kuid2:61392:1072:10> mc Display Custom HUD V2 (SP2 and later)
<kuid2:61392:8112:78> IT SetPathAndWaitNotRed (TANE SP4 and later)
<kuid2:61392:8311:80> MC - PathStop (TANE SP4 and later)
<kuid2:61392:8204:80> RemoveMissionCode (TANE SP4 and later)
<kuid2:61392:8201:80> SetMissionCode (TANE SP4 and later)
<kuid2:61392:8121:2> EITPathTrigger
<kuid2:61392:8191:13> TRC 3 InterlockingTower library (SP2 and later)
<kuid2:61392:4003:32> Game date library (SP2 and later)
<kuid2:61392:4000:32> Common data library
<kuid2:61392:4001:22> pglib
<kuid2:61392:4006:20> global session variables library

I'm up to date, using my signals (that use an old script by Grahamsea).

Hi Justinroth.

I am currently running TRS2022 build 118660 and have no problems with EITS and signals used on the routes/session I am working with.

So first thing to check is to see if the problems you encountered are specific to the signals you use or are global to your local Trainz configuration.
Can you download from DLS the EIT DemoRoute - UK 1 <kuid2:61392:8401:6> and one of its session EIT DemoRoute - UK1 - Full session with MCM <kuid2:61392:8402:6> and try to run it (all dependencies are available on DLS) and see if the signals are running fine or not. This should help to confirm if your problem is global to your local Trainz configuration or if it is only specific to the signals you use on your route and session.

If as I hope and expect, the problem is specific to the signals you use, can you post here or send me via PM or email (I will PM you my email address in case you have some files to send me) the KUIDs of the signals you encounter problems. If they are not available on DLS can you package some of them in a cdp and send me the cdp via email. I will then have a look to these signals and to their underlying script and I will then come back to you with my diagnosis and if possible a solution to fix the problem.

Regards.
Pierre.

justinroth said:

I'm up to date, using my signals (that use an old script by Grahamsea).

Click to expand...

Were those the Canadian CROR signals per chance? Were you able to get them working? If so, if you could kindly share the trick Thanks!

Papa_de_05 said:

Were those the Canadian CROR signals per chance? Were you able to get them working? If so, if you could kindly share the trick Thanks!

Click to expand...

I think there is a CROR script done by Jon Roma though I don't ever recall seeing physical signals. I have not yet got the scripts to work in 22 with EIT.

Hello there. The Demo route you are mentioning uses the "Signal Br8" kuid:-25:834 . This Signal has no script. So that demo route proves nothing. Try the packaged "Hl H" signals kuid2:83501:24536:7

Hi Justin,
I am having a same problem. Signal are working fine, but as soon as I create path in IT, signals in that path are not working in driver, they stay dark. Did you find a solution yet?
Rob

The problem might be the SecurityTokens, which are now required for some methods. The old signal scripts don't know these tokens, and a default token is used, when they call the old versions of the method. Probably this default token is invalid, if the signal is controlled by an InterlockingTower.

Peter

Thx Peter, is there any way to check this?

Some signals can be set in the EIT path during setup.

Hi.
Can you post here the kuids of some route/session and signals available on the DLS or in a DLC for which you encounter the problem, so that I can have look to try to find why the signals are not working in driver mode under last TRS22 build (probable cause is some signal script not compliant to what signal scripts must mandatory implement in their script).

Hi Pierre
Some of the signals I use are by chrisaw and it is often the branch signals that fail to show the correct feathers.
<kuid2:218467:24855:3> Sig BR(W) Home junction 2 L loop
<kuid2:218467:24863:3> Sig BR(W) Combined R branch centre loop
<kuid2:218467:24815:4> Sig BR(W) Combined R branch route indicator
<kuid2:218467:25199:1> Sig BR(W) Combined L branch route indicator D&D1
<kuid:234086:100343> Sig BR(W) Home R loop RH
<kuid2:218467:25207:1> Sig BR(W) Home R Branch -7
<kuid2:218467:24860:3> Sig BR(W) Home L Branch L loop
<kuid2:218467:24858:2> Sig BR(W) Home R Branch
<kuid2:218467:24862:2> Sig BR(W) Combined R Branch
<kuid2:218467:24857:3> Sig BR(W) Home L loop
<kuid2:218467:24854:3> Sig BR(W) Home R Branch R Loop
<kuid2:218467:24811:3> Sig BR(W) Combined L Branch
<kuid2:218467:24968:1> sig BR(W) Duchy 2
<kuid2:218467:24580:2> Sig BR(W) Home R Branch R Loop
<kuid2:218467:24527:1> Sig BR(W) Combined L Branch

Sorry I've only just looked at this, but if it's still open, in the above list three of the signals are using the old build version 2.8 script:
<kuid:234086:100343> Sig BR(W) Home R loop RH by paulsw2
<kuid2:218467:24580:2> Sig BR(W) Home R Branch R Loop, replace with <kuid2:218467:24854:3> build version 3.5
<kuid2:218467:24527:1> Sig BR(W) Combined L Branch, replace with <kuid2:218467:24811:3> build version 3.5

Chris.