ORTS - Signals disappear when using ORTSUserPreferenceForestClearDistance (2)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ttjjj
    Member
    • Sep 2004
    • 39
    • Stokke, Norway.
    • English

    #1

    ORTS - Signals disappear when using ORTSUserPreferenceForestClearDistance (2)

    Hi everybody!

    I tried to implement the new feature in many of my routes, have annoying trees in the midlle of the roadbed.

    Implementing the small program lines in a OpenRails folder in your favorite route get rid of the trees OK, but
    all the signals both in the route ifself, and the track-monitor gets black, no signals are shown. I have tested many routes,
    but they all seems to loose all their signals when I try to implement this rather new feature.

    Is there a way around this ?

    I am using ORTS version X3854.

    Below are the text in the little program, used lately in the CIMA-route. It works OK in this route but here there is not many trees to get rid of either.

    include ( ../Buffalo.trk )

    ORTSUserPreferenceForestClearDistance ( 2 )


    All the best from John in Norway
  • csantucci
    Senior Member
    • Nov 1999
    • 856
    • Torino, Italy.

    #2
    Have you inserted a blank line as the first line of this file?
    Is Buffalo.trk the name of the .trk file you find in the root directory of your route?
    sigpic

    Comment

    • ttjjj
      Member
      • Sep 2004
      • 39
      • Stokke, Norway.
      • English

      #3
      Dear mr. Santucci,

      I have tested many of my routes with following results:

      If you leave out the blank line in the beginning, I get a "load error: ConnRiv" and the route will not load at all.

      The same name are used both in the OpenRails directory as in the main directory of the route.

      The only route which actually works OK , is the new Cima route, when I first started on this route I got a load error, then inserted the extra line in the start of the small trk-file in the OpenRails directory.
      In this route all signals is actually working. I have just copied all the other files from from the OpenRails directory in this route to other routes and have only renamed the *.trk file.

      So it may be something in the other files which creates the signal error??

      All the best from John in Norway

      Comment

      • ttjjj
        Member
        • Sep 2004
        • 39
        • Stokke, Norway.
        • English

        #4
        Dear mr. Santucci and all:

        I think I found the solution.

        Make a OpenRails directory in the root of your favorite route

        Make a small 4 line file into the Openrails directory:

        It must start with a blank line, here example from the Buffalo route, name the file Buffalo.trk
        1:
        2: include ( ../Buffalo.trk )
        3:
        4: ORTSUserPreferenceForestClearDistance ( 2 )

        Now you have only one file in the OpenRails directory, but there is more..

        Copy the sigcfg.dat and sigscr.dat files from the route root directory to the OpenRails directory.
        I there are more sgscr.dat files with various endings like the Cima-route they have to be copied as well.

        This is it, - I now enjoy both the removed threes from the roadbed and got my signals back.

        Am I doing it the wight way ?

        Alle the best from John

        Comment

        Working...