Elvas Tower: Improving management of Time-of-Day Waiting Points - Elvas Tower

Jump to content

Posting Rules

All new threads will be started by members of the Open Rails team, Staff, and/or Admins. Existing threads started in other forums may get moved here when it makes sense to do so.

Once a thread is started any member may post replies to it.
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Improving management of Time-of-Day Waiting Points Rate Topic: -----

#1 User is offline   Csantucci 

  • Member, Board of Directors
  • Group: Status: Elite Member
  • Posts: 7,000
  • Joined: 31-December 11
  • Gender:Male
  • Country:

Posted 01 May 2016 - 01:24 AM

Absolute waiting points (that is waiting points where you can insert a time of day instead of a time interval) are quite useful to synchronize trains in activity mode. However as of now they have some limitations:
1) even if the train arrives late at the absolute waiting point, when the time of day has already passed, the signal is still red. The train must stop for a very small moment, and only at that moment the signal opens and the train can restart. This is true for both player and AI trains; this should be modified in a way that if the time of day has passed, and the train has already reserved for itself the section before the signal, or is occupying it, and the signal is the first in front of the train, the signal should open (if not closed also because the track further down is not free). This way if the train arrives late at the WP it has the signal open and can proceed. To be clearer, this way as in true railroading, it can occur that if the train is running, and the time of day is reached, the train gets the open signal and can proceed before stop. For AI trains (and of course also for player trains) it may also occur that the train slows down because it is near to the WP and the time has not yet completely passed, and in the mean time the signal opens and the train can accelerate without stopping (already tested).
2) another drawback is that of signals that are after a switch (yes, this can occur), as in following case provided by a German trainsimmer and related to an Austrian route
Attached Image: Absol WP zw Weiche und Signal.jpg
This signal is at the exit of a big terminal station. To have the signal opening at a certain time of day, a WP must be set in the same track section of the signal. This way as of now a train, be it player or AI, cannot wait at the platform that the signal opens and then start; instead it must move until in front of the signal, stop and then restart when the signal opens. Also this case can be solved using the above rule: As the section before the signal is already reserved for the train, be it player or AI, the signal will open at the correct hour and player train and AI train can pass the signal without stopping; to avoid that the AI train starts from the platform too early, either a synchronized WP or a station stop has to be added for the AI train.

A blueprint has been opened here https://blueprints.l...-waiting-points .

I am in the testing phase now.

#2 User is offline   Csantucci 

  • Member, Board of Directors
  • Group: Status: Elite Member
  • Posts: 7,000
  • Joined: 31-December 11
  • Gender:Male
  • Country:

Posted 03 May 2016 - 06:07 AM

A beta version is available, and may be tested replacing in release x.3539 Orts.Simulation.dll with the attached one.

Within this work, one unneeded execution step has been deleted for WPs and the other so-called Auxiliary Actions, reducing code lines.

9/5/16: file deleted as update committed in x.3541.

#3 User is offline   Csantucci 

  • Member, Board of Directors
  • Group: Status: Elite Member
  • Posts: 7,000
  • Joined: 31-December 11
  • Gender:Male
  • Country:

Posted 09 May 2016 - 09:14 AM

Committed in x.3541.
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