[markus_GE]

Using X1744, I get an alerter (finally), but still not the way, as in MSTS: It seems like the time Limit when the alerter should start going off after the last time pressed / controls moved that OR interprets as such is the one that in MSTS is the time Limit when the alerter stops sounding and the Train goes into emergecy.

At least, using this code...

 VigilanceMonitor(
  MonitoringDeviceMonitorTimeLimit( 59 )
  MonitoringDeviceAlarmTimeLimit( 45 )

... the alerter sounded after 59 seconds, instead 45, and I only went into emergency 45 seconds later, making for 104 seconds between the last alerter reset and the final emergency Trigger. I´ve heard about one Minute still being OK somehow (nalthough not necessarily prototypical), which is what i´d be using with this Setup. And in MSTS it works that way: Audible and visible warnings 45 seconds, emergency 59 secs after the last reset (14 secs in between warning start and emergency). Looks like OR somehow missinterprets These values...

Otherwise, finally everything works as it should - Keep up the great work! ;)

Cheers, Markus

[Gary54]

Good afternoon,

I would add to the above that in my case (using X1744), the alerter is sounding, yet the movement of controls using RailDriver is not acknowledging the alerter. In other words, the only way I can acknowledge the alerter while using RailDriver is by pressing "Z".

Gary

[BillC]

Gary54, on 07 September 2013 - 11:11 AM, said:

Good afternoon,

I would add to the above that in my case (using X1744), the alerter is sounding, yet the movement of controls using RailDriver is not acknowledging the alerter. In other words, the only way I can acknowledge the alerter while using RailDriver is by pressing "Z".

Gary

Fix for RailDriver alerter acknowledgement committed X1747. Gear fix should be also corrected in the future.

[Gary54]

Thanks very much for the fix. It's much appreciated.

Gary

[gpz]

markus_GE, on 07 September 2013 - 09:41 AM, said:

Using X1744, I get an alerter (finally), but still not the way, as in MSTS

Markus, I corrected the timing in r1746 as you described here. Thank you very much for the clarification, the docs I found were not so clear in this aspect. :)

[markus_GE]

Just been playing ´round with it, as all the different Defaults were - let´s say, a bit odd to become acquainted to when playing.

First tested them in MSTS, of which I know it works like MSTS (despite all the "Features" :D ), and then went to OR - the difference could not be overlooked :)

Cheers, and thanks for Fixing ;)

Markus