Signal Changes to Blocked on Resuming Activity!!??

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • meeshu
    Senior Member
    • May 2010
    • 373

    #1

    Signal Changes to Blocked on Resuming Activity!!??

    Another issue has just appeared for Cajon Pass V4.2 and running under Open Rails V1.4.

    A saved activity shows a nearby signal near MP 56 as being clear (green) as it should. But on actually resuming the saved activity the signal changes to red (block)!? And if my train passes this signal the trains emergency brakes apply, so the red signal is definitely now a block for whatever reason(s)!

    Why does the saved green green change to a red signal on resumption of the activity? It shouldn't change to red as there are no other trains within this activity. Signal scripting error?

    Screenshots of signals from Track Monitor enclosed.

    Cajon Pass V4.2 Saved Activity Clear Signal..PNGCajon Pass V4.2 Resume Saved Activity Now Block Signal..jpg
  • R. Steele
    3500 Post Veteran

    • Feb 2013
    • 3928
    • known universe
    • ORTS

    #2
    I've observed this behavior also, it's nothing new...it has been occurring for quite a few years, in many routes, always upon resuming. Not knowing anything about signal scripts or the OR code --- I can only guess that the state of the signals is not being saved correctly??

    Solution is easy, simply switch to manual mode and back to auto mode -- Control+M, this should reset signals.
    Cheers, Gerry
    "A mind is like a parachute. It doesn't work if it is not open." Frank Zappa
    It's my railroad and I'll do what I want! Historically accurate attitude of US Railroad Barons.
    Forever, ridin' drag in railroad knowledge.
    Audi, Vide, Tace, Si Vis Vivere In Pace​

    https://www.trainsim.com/forums/filedata/fetch?filedataid=79656&type=medium​ https://www.trainsim.com/forums/filedata/fetch?filedataid=79654&type=small

    Comment

    • meeshu
      Senior Member
      • May 2010
      • 373

      #3
      Yes, I've come across this issue before, but forgot about the Ctrl + M key "work around" in the meantime.

      Thanks for the reminder!

      Comment

      Working...