Signal compatibility with the Enhanced Interlocking Tower.

Hello,


I have some problems with some signals.

The Belgian signals created by Belgafox, for example kuid2:60856:24011:12, work without problems. All lights are on normally.


Others, like the kuid2:343955:29171:4 from Ks_Vorsignal for example, stay off.


Is there a configuration I forgot or a list of signals that are compatible with the Enhanced Interlocking Tower.

Best regards.

Whilst I have only used UK signals, I have found all types of signal work correctly with the Enhanced Interlocking Towers.

Have you checked in your path definition within the EIT that you have set the signal state to "Proceed" or "Automatic"?

As another question, when you say "Others, like the kuid2.... stay off." do you mean they are not illuminated? In UK terminology, when a signal is "off" it means it is showing a proceed aspect, ie.not red.

Not all signals show on as the default position. Some signals will show off as the default position.

Hello davidbird and stagecoach, thank for you reply.

The problem is that some signal do not shown anything. No red, no green, no caution. They are dark, allways dark, no matter they are in "Proceed" or "Automatic" !

I just looked at this signal kuid2:343955:29171:4 from Ks_Vorsignal and it looks like it does not have a yellow state. Only red or green?

And has a lot of dependencies, which yours may be out of date?

<kuid2:489332:23150:1> Dm-LST GaK Typ 2 Indusi KS
<kuid2:343955:99054:4> VSM Hv-Signal Meshes
<kuid2:343955:100006:8> VSM 100 SE DB Signalmodul
<kuid2:343955:100034:2> VSM Gruenlicht
<kuid:124930:8010> Indusi2 KS
<kuid2:343955:100032:2> VSM Gelblicht
<kuid2:343955:70001:3> VSM HTML-Seiten
<kuid2:343955:10033:2> VSM Rotlicht
<kuid2:343955:21001:2> VSM Signal textures
<kuid2:343955:10031:2> VSM Weisslicht
<kuid2:343955:99051:4> VSM Zusatzanzeige 1969

Just some ideas..

Christopher824 said:

I just looked at this signal kuid2:343955:29171:4 from Ks_Vorsignal and it looks like it does not have a yellow state. Only red or green?

And has a lot of dependencies, which yours may be out of date?

<kuid2:489332:23150:1> Dm-LST GaK Typ 2 Indusi KS
<kuid2:343955:99054:4> VSM Hv-Signal Meshes
<kuid2:343955:100006:8> VSM 100 SE DB Signalmodul
<kuid2:343955:100034:2> VSM Gruenlicht
<kuid:124930:8010> Indusi2 KS
<kuid2:343955:100032:2> VSM Gelblicht
<kuid2:343955:70001:3> VSM HTML-Seiten
<kuid2:343955:10033:2> VSM Rotlicht
<kuid2:343955:21001:2> VSM Signal textures
<kuid2:343955:10031:2> VSM Weisslicht
<kuid2:343955:99051:4> VSM Zusatzanzeige 1969

Just some ideas..

Click to expand...

A good idea .

Yes, I've the last version of each asset. Meanwhile I've the kuid2:343955:100006:10 instead of the kuid2:343955:100006:8.

That signal is packaged in "Schwäninger Land", a payware included in TRS+

Since the release of SP5 all scripted signals I tried do not working properly anymore, even the ones that came with TRS19. They show fine in Surveyor but in Driver either don't show any lights or they won't change states (in case of semaphores). I already contacted the Help(less) desk twice about this problem (last year and last month) and nothing has been resolved.

It's a script issue. Older scripts tend to time-out due to a huge number of calls, large tables, and large search areas. In the olden days, the assets would appear to work but in reality, they were causing stutters and bad performance. Starting with T: ANE, N3V put in a time-out to force the scripts to stop in order to free up resources, and this is most likely the reason why the signals are not working.

More recently, N3V has made any older scripts faulty if they don't conform to the rules causing many assets to become faulty. Unfortunately, it's up to the content-creator to repair the assets and update the scripts, however the Content Repair Group, has also been tasked to repair these assets but with the huge number of them needing repair and the small number of volunteers, this is not going happen any time soon.