Signalling problem

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • docmartin
    Member

    • Dec 2004
    • 99
    • Bossier City, LA, USA

    #1

    Signalling problem

    The attached 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
    Attached Files
  • mnowosad
    Senior Member

    • May 2010
    • 126

    #2
    Errors - Warning: Signal referenced in .w file

    Good morning Martin.
    I had a similar problem with errors in Open Rails. Corrected type errors - Warning: Signal referenced in .w file -6076 14920 as TrItem 1532 not present in .tdb file using TSRE5. For example, I was looking for the TrItem 1532 signal in the w-6076 14920.w file from the WORLD folder. I determined his position and entered it into the Position & Rotation window, marking the red good signal marker probably placed closest to the faulty signal, which consisted only of shape and did not have a red marker. The signals listed in the log were not added to the TDB and after selecting and deleting the shape with the Del button the error from the log disappeared. In the OR Track Viewer program you can first check the Route - Menu - File - Search by index - Search TrackItem - trackItem index = 1532. You have to do it with maximum zoom and probably the signal with this number will be of a different type and at a different location on the route. I only had a few warnings of this type, but before, I made a copy of the route and took screenshots of places on the route of correct and incorrect signals with the same TrItem numbers (I deleted the correct one temporarily). By the way, I corrected the "incorect crossover" error in TSRE5, which I checked a few years ago on the Polish CMK Route, in which this error caused a malfunction of the signaling and the inability to create correct paths for the Timetable mode. Regards Marek - written in the translator

    Rebusz W5n.jpg

    Choszczno Tm k.jpg

    Poznan W24.jpg

    Dobiegniew Tm K.jpg

    Stary Klukom W24.jpg

    # Old log during correcting signaling errors:
    Loading TRK TDB SIGCFG_OR DAT ACT RDB CARSPAWN SIGSCR WWW

    Warning: Signal referenced in .w file -5452 14971 as TrItem 2639 not present in .tdb file

    W(repeats) W(repeats) W(repeats) W(repeats) W(repeats) WWWWWWWWWWWWW

    Warning: Signal referenced in .w file -5490 14999 as TrItem 1011 not present in .tdb file

    W(repeats) WWWWWWWWW

    Warning: Signal referenced in .w file -5499 15007 as TrItem 2637 not present in .tdb file

    W

    Warning: Signal referenced in .w file -5500 15007 as TrItem 1012 not present in .tdb file

    W(repeats) WWWWWWWWWW

    Warning: Signal referenced in .w file -5510 15013 as TrItem 1391 not present in .tdb file

    W(repeats) W(repeats) W(repeats) WWWWW

    Warning: Incomplete crossover : indices 1389 and 147

    ENV SIGCFG SIGCFG_OR TTYPE

    # New Log :

    Route = Poznan-Szczecin
    Path = test-Choszczno_P-S (F:\Train Simulator Poland-351-Test\ROUTES\Poland-351\PATHS\test-Choszczno_P-S.pat)


    Warning: Found a suffix 'nan' which could not be parsed as a Speed unit in F:\Train Simulator Poland-351-Test\TRAINS\CONSISTS\EP07-198.con:line 7

    Consist = EP07-198 (F:\Train Simulator Poland-351-Test\TRAINS\CONSISTS\EP07-198.con)
    Time = 12:00:00 (12:00)
    Season = Summer (1)
    Weather = Clear (0)
    ------------ ---------- ------------ ---------- ------------ ---------- --------
    Loading TRK TDB SIGCFG_OR DAT ACT RDB CARSPAWN SIGSCR W(repeats) W(repeats) W(repeats) W(repeats) W(repeats) W(repeats) W(repeats) W(repeats) W(repeats) W(repeats) W(repeats) W(repeats) WWWWWWWWW

    Warning: Found a suffix 'nan' which could not be parsed as a Speed unit in F:\Train Simulator Poland-351-Test\TRAINS\CONSISTS\EP07-198.CON:line 7

    ENV SIGCFG SIGCFG_OR TTYPE

    Information: Allocation for 87 500 particles:

    16 800 000 B RAM vertex data
    2 100 000 B RAM index data (temporary)
    16 800 000 B VRAM DynamicVertexBuffer
    2 100 000 B VRAM IndexBuffer

    TTTTTTTTWWSSSSSSSSSSSSSSSSSS TRP(default)SSSSSSSSSSSSSSSSSSS
    https://www.youtube.com/playlist?lis...SIYbL4sRM-VMd7

    Comment

    Working...