[markus_GE]

A customizeable alerter is a great Addition to OR, especially as 30 seconds are a short interval - at least IMHO. Also being able to make it shut down when the Train is halted is good.

But what´s not so good is, that I don´t hear the alerter at all :) I let a Train using my customized "VigilanceMonitoringDevice" (see below) for 10 minutes - no alerter sounds, no visual warning from the CVF file used, no emergency braking. What´s wrong, either with OR or with my Setup of the Alerter / Vigilance Monitor?

Yours, Markus

PS: My "VigilanceMonitor"

 VigilanceMonitor(
  MonitoringDeviceMonitorTimeLimit( 59 )
  MonitoringDeviceAlarmTimeLimit( 45 )
  MonitoringDevicePenaltyTimeLimit( 0 )
  MonitoringDeviceCriticalLevel( 0 )
  MonitoringDeviceResetLevel( 0 )
  MonitoringDeviceResetOnZeroSpeed( 1 )
  MonitoringDeviceAppliesFullBrake( 1 )
  MonitoringDeviceAppliesEmergencyBrake( 0 )
  MonitoringDeviceAppliesCutsPower( 1 )
  MonitoringDeviceAppliesShutsDownEngine( 0 )
  )

[gpz]

Are you driving from cabview? Because I set alerter to clear automatically when not in cabview. I remembered it works this way in MSTS, but I will have to check.

[markus_GE]

Starting outside cab (Default for OR on Startup, as in MSTS - AFAIK) and then usually in-cab, sometimes out for taking screenies or whatever.

Also another question to the graphics-department: I fiddled around with OR´s registry a bit again to try and improve the shadow Settings I use. I found that "ShadowMaplur" was turned off (obviously did so myself) and turned it on - whew, 1 meter or even more distance between full sunlight and real shadow (= 1 meter blurred area) eats a lot of small-detail shadows, like from signs. My question, could this blurred area be narrowed down to, let´s say a third of a meter? Without blur shadows do have edges where there are None in the model they are cast off, with blur there are no edged at all. A bit unrealistic, isn´t it?

Cheers, Markus

[gpz]

 markus_GE, on 18 August 2013 - 06:38 AM, said:

Starting outside cab (Default for OR on Startup, as in MSTS - AFAIK) and then usually in-cab, sometimes out for taking screenies or whatever.

It should work this way, so I don't know what could be the problem. Where can I download the locomotive?

(There might be a problem when using multiple locomotives of the same type, depending of the internal loading order, as the Clone() function is not implemented yet, so internal copying of a locomotive doesn't copy the vigilance monitor yet.)

[markus_GE]

As far as I experienced it yet, it occurs on any loco I use the above vigilance Monitor Settings on.
(tested on 5 so far)

Also, this one loco I first experienced the Problem with only occurs once in this activity.

At the latest, after 1 Minute it should go into emergency that way (does so in MSTS - works all fine there), but in OR you can run 10 minutes, 15 mins, ... hours without any sign. (tested 10 mins without touching anything on my Keyboard or mouse)

Could it be some interference with some of the other Monitoring devices?

Cheers, Markus

[markus_GE]

Took another look at the Settings I use: Might it have to do with the following two lines?

  MonitoringDeviceCriticalLevel ( 0 )
  MonitoringDeviceResetLevel ( 0 )

[gpz]

No, those ones are not used for anything for vigilance monitor. I will check what the problem is. (I will have very limited time for programming in the following 2 weeks.)

[markus_GE]

Don´t hurry, it´s by no means as distracting as going into emergency every two or three seconds would be :clapping: (had that once on MSTS... Praise to OR as it is much more tolerant!)

If I finf a loco that DOES work, I´ll post the working and a non-working one here (thought to have found one that works, but later found out it used MSTS Default alerter Settings :/ . The Defaults are without the switched off on 0 Speed, so might it be that one? )

Cheers, Markus

[gpz]

Fixed in r1730.

[markus_GE]

Sounds great, thanks :drinks:

Cheers, markus