Track monitor, Switch and train operations window temporarily losing data

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • csantucci
    Senior Member
    • Nov 1999
    • 856
    • Torino, Italy.

    #1

    Track monitor, Switch and train operations window temporarily losing data

    I've noticed that the track monitor, switch and train operations windows always temporarily lose data when the player train enters a specific new tile and recovers data when it exits a specific tile. On this portion of the route map drawn by Mosaic I have pinpointed with a black dot the point where data disappear and with a yellow dot the point where data appear again. The blue squares are the tile boundaries, and the red line is the track line.
    Map.jpg

    Here

    you can see what appears on the screen. The event may be easily reproduced starting activity 1641_StM_Ti in the freeware Bernina route. The event happens about 5 minutes after start (after first tunnel and small station Celerina Staz).

    I use this thread also for some further comment and request:
    - it would be nice if the "Pick signals" and "Pick switches" checkbox would be available also in Single Player mode. Without such checkboxes sometimes it is impossible to pick a signal that is drawn in the same place where there is a switch;
    - for switches it would be useful to have three possibilities, that is (analogously to signals) "System controlled", "To main route", "To side route"; that would be more similar to reality; linked to this is the fact that up to now it often seems not possible to override the switch position decided by the system; after few seconds the switch returns to the original position.
    - it still happens that the player train gets an AI train in front of it in a single track line, even if the player train engaged the track section between two stations before the AI train; it seems that the automatic AI dispatcher does not check if a single track section is free before entering it from a station or a place where a meet is possible; this check should be performed independently from the fact that the single track was already reserved by the AI train;
    - it would be nice if Ai train track reservation (velvet line on dispatch window) could consider waiting points in front of the train; a solution maybe could be that track reservation does not proceed forwards for a time equal to the waiting point time interval.


    I hope that this may be of some use for the ORTS dev team.

    Carlo
    sigpic
  • csantucci
    Senior Member
    • Nov 1999
    • 856
    • Torino, Italy.

    #2
    Dear ORTS dev team,
    thank you for having provided us today as scheduled the new experimental build 1302. I have downloaded it and have seen that now in the single player mode there is a checkbox to disable picking of signals, as I had required. Thank you. Unfortunately, as can be read from my preceding post, the specific case I had is that it was not possible to pick a signal, because it was in the same place where there was a switch (it seems that switches have priority over signals in picking). So in that case the checkbox to disable picking of signals is not useful, because the checkbox to disable picking of switches is needed. In other words both checkboxes are needed, just as I required and as it is in the MP version. But maybe you are already aware of the fact that with this build you were only at 50% of the result on this issue.

    In the meantime I add here other two points:
    - when you run a push/pull train and reverse direction at end station you are faced with negative speeds. This is different from MSTS, and it is not an issue, but only a problem of becoming accustomed to it; in the track monitor (F4 window) you have the speed limits for running in the opposite direction, shown with positive numbers, and that also could be OK; however ORTS continues to perform speed limit check with positive values, so even if you run -200 kph and have a limit of 30 kph you don't get the two parallel vertical red lines, but continue to have the green ones (because -200 is smaller than 30);
    - when running MP sessions with up to 8 other people on some Italian routes we noticed that the signals perform well on the track monitor, but signal lights are grey in the simulation; I believe that this happens because there is following issue on how ORTS interprets sigcfg.dat files: in such routes there are sigcfg.dat files where for many SignalTypes no SignalAspects block is present, or better said only a SignalAspects ( 0 ) line is present; these sigcfg.dat files work correctly under MSTS because the sigscr.dat file already determines the SignalDrawState for such signals (that often have also more than 8 draw states, which is the maximum for SignalAspects), so the signal state can be drawn correctly. Unfortunately ORTS does not draw states of signals where the related SignalAspect is not defined in sigcfg.dat. So my kind request is that also ORTS draws states of signals if such are defined within sigscr.dat (draw_state variable defined), even if in sigcfg.dat the SignalAspect is not defined. This is also a way to overcome the limit of 8 draw states per signal. If you want to check, you can download as an example the route Tirrenica Meridionale v3 from here http://www.trainsimhobby.net/infusio...61&file_id=572 (check the box before clicking Download). To install download the .rar files, and start extracting the first one. The other ones are extracted automatically and an .exe file is generated. Run it, and at end of istallation the route is ready to run.

    I am every day more aware that the objective of developing a simulator highly compatible with MSTS is a very hard and time-consuming goal. Thank you for you efforts.

    Carlo
    sigpic

    Comment

    • wacampbell
      Senior Member
      • Jun 2002
      • 492
      • BC, Canada

      #3
      Thanks for the feedback.

      Comment

      Working...