Signalling problem

Have you given it a go? Post your experiences, particularly things that worked well. Let the team know what works and doesn't work as they cannot test the software with every combination of routes, activities and content available for MSTS. OpenRails is actively being improved and is quickly approaching v1.0. This is a great place to discuss what you can do with OpenRails.

Moderator: Moderators

Locked
User avatar
docmartin
Very Active Forum Member
Posts: 1031
Joined: Mon Dec 29, 2003 10:44 pm
Location: Obviously in the wrong sim but also Louisiana, USA

Signalling problem

Post by docmartin »

Image

The screenshot shows a scene from a test activity for my forthcoming Chiltern line route. Can anyone explain why the signals on the track adjacent to the player train are showing green when there are no AI trains in the activity?

The screenie is taken in Open Rails, though the same thing happens when the activity is run in MSTS. In MSTS, however and despite using MSBin, some of the signals do not light up at all.

The signals are the London Transport colour light signals developed by Jimi Ibett and his team for their District line route and used with permission. The signal scripts are contained in sigscr-LUL-signals.dat

Here are relevant lines extracted from the OR log file (the full log file is attached), which I am not knowledgeable enough to interpret:

Information: Duplicate SignalDrawState name 'amber', using name 'DST1' instead in C:\1MSTS\ROUTES\Chiltern\sigcfg.dat:line 194

Information: Skipped unknown signal aspect APPROACH in C:\1MSTS\ROUTES\Chiltern\sigcfg.dat:line 1641

Information: Skipped unknown signal aspect GREEN_1 in C:\1MSTS\ROUTES\Chiltern\sigcfg.dat:line 2640

Warning: Skipped duplicate SignalType gw_tubdistant in C:\1MSTS\ROUTES\Chiltern\sigcfg.dat:line 2768

Warning: Skipped duplicate SignalType lq/uq_headshunt in C:\1MSTS\ROUTES\Chiltern\sigcfg.dat:line 4357

Warning: 3 missing SignalType(s) in C:\1MSTS\ROUTES\Chiltern\sigcfg.dat:line 8707

Information: Skipped unknown SignalSubObj flag OPTIONAL_DEFAULT in C:\1MSTS\ROUTES\Chiltern\sigcfg.dat:line 11498

Warning: 4 missing SignalShape(s) in C:\1MSTS\ROUTES\Chiltern\sigcfg.dat:line 20265

Warning: sigscr-file line 1713 : Unknown parameter in statement : LMS_LOFS_BOARDEXTERN FLOAT STATE

Warning: Signal referenced in .w file -6075 14918 as TrItem 1124 not present in .tdb file
(a very large number of these errors flagged)

Any help that can be given with these issues will be gratefully received.

Martin
coolhand101
Very Active Forum Member
Posts: 1200
Joined: Tue Mar 06, 2007 2:20 pm

Re: Signalling problem

Post by coolhand101 »

This will happen if the signal is set to automatic( controlled by the passing of trains and not by the signalbox ) in the signal script, if so, the signal will always show a proceed aspect until any train passes it. This is a real life event.

However if it a controlled signal, ie point work front/back, junctions, manual level crossings,etc. Then these signals must show red.

I haven't seen many automatic scripts in freeware routes, however there are plenty in EB and MT route( providing they are set to automatic in the first place ).

Thanks

EDIT
Just seen your ET post and OR log. The errors in the signal files could be causing it. However from my experience, the signals are normally unlit, if aspects are not recognized by OR.
User avatar
DarwinS
Very Active Forum Member
Posts: 1335
Joined: Fri May 28, 2004 10:08 am
Location: York

Re: Signalling problem

Post by DarwinS »

I am pretty sure the London Underground signals are automatic - therefore should show green unless the section ahead is occupied or they are protecting something.

Anyway as posted on ET it is worth checking the signal script and signal placement.
Regards

Darwin
ozziedriver
Been on the forums for a while
Posts: 282
Joined: Sat Jul 02, 2005 11:52 pm
Location: Pakenham,victoria, Australia

Re: Signalling problem

Post by ozziedriver »

Information: Skipped unknown signal aspect APPROACH in C:\1MSTS\ROUTES\Chiltern\sigcfg.dat:line 1641
You can't have a signal aspect as just APPROACH...……..It must be APPRACH_! or APPRACH_2

Information: Skipped unknown signal aspect GREEN_1 in C:\1MSTS\ROUTES\Chiltern\sigcfg.dat:line 2640
There is no such aspect as GREEN_!...….Should be CLEAR_!

Information: Skipped unknown SignalSubObj flag OPTIONAL_DEFAULT in C:\1MSTS\ROUTES\Chiltern\sigcfg.dat:line 11498
Signal flags can only be OPTIONAL or DEFAULT ...can't be both ,,one is an "Option" the other is "Has to be present"

In the screenshot the signal your train is facing has a white board under it with a black line....this indicates the signal is AUTOMATIc
The other signal doesn't have this but still could be Automatic depending on how it is scripted
Locked

Return to “[OR] General OpenRails Discussion”