Elvas Tower: Problem with train held at signal in OR but not in MSTS - Elvas Tower

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Problem with train held at signal in OR but not in MSTS Rate Topic: -----

#1 User is offline   dforrest 

  • Foreman Of Engines
  • Group: Status: Contributing Member
  • Posts: 977
  • Joined: 12-January 12
  • Gender:Male
  • Location:St. Vincent (formally UK)
  • Simulator:MSTS, Open Rails
  • Country:

Posted 21 February 2020 - 03:49 AM

We have an activity which was written in the MSTS Activity Editor and runs perfectly in MSTS. However, when running in OR the train is stopped indefinitely at a signal it passed through in MSTS. Further investigation shows that it is held at that signal because of another train held at a signal further up the line.

Can anyone offer any advice on diagnosing this problem?

#2 User is offline   R H Steele 

  • Executive Vice President
  • PipPipPipPipPipPipPipPipPip
  • Group: ET Admin
  • Posts: 3,433
  • Joined: 14-March 13
  • Gender:Male
  • Location:known universe
  • Simulator:Open Rails
  • Country:

Posted 21 February 2020 - 12:52 PM

Quote

6.10.3 Location-linked passing path processing
When this option is NOT selected, ORTS acts similarly to MSTS. That is, if two trains meet whose paths
share some track section in a station, but are both provided with passing paths as dened with the MSTS
Activity Editor, one of them will run through the passing path, therefore allowing the meet. Passing paths
in this case are only available to the trains whose path has passing paths.
When this option is selected, ORTS makes available to all trains the main and the passing path of the
player train. Moreover, it takes into account the train length in selecting which path to assign to a train in
case of a meet.

Quote

For content developers
A more detailed description of this feature can be found under Location-Linked Passing Path Processing in
the chapter Open Rails Train Operation.

Options/Experimental tab -- check or uncheck the "locations-linked passing path processing" to see if it makes a difference


#3 User is offline   eugenR 

  • Conductor
  • Group: Status: Contributing Member
  • Posts: 472
  • Joined: 15-April 13
  • Gender:Male
  • Simulator:MSTS
  • Country:

Posted 22 February 2020 - 07:31 AM

View Postdforrest, on 21 February 2020 - 03:49 AM, said:

We have an activity which was written in the MSTS Activity Editor and runs perfectly in MSTS. However, when running in OR the train is stopped indefinitely at a signal it passed through in MSTS. Further investigation shows that it is held at that signal because of another train held at a signal further up the line.

Can anyone offer any advice on diagnosing this problem?


MSTS does Interpret the Parameters SignalNumClearAhead() in Sigcfg.dat in an other manner then OR does.
MSTS is taking the highest Value found on all Signalheads on the Route and use it for ALL Signalheads.
OR is using the individual Values for the Signalheads. So sometime there are not enough signals open ahead.

Please read in Manual Chapter 10.14.1 and .2 for this Problem.
The Manual is integrated in the Testing-Version:
http://openrails.org/download/program/

Regards
EugenR

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users