2014-07-27 07:08:28 |
Rippstein |
description |
In MSTS the change-time of a semaphorearm is defined in the sigcfg.dat in the SIGNALTYPE-definition by the parameter:
SemaphoreInfo ( 0 )
in this case the change-time is 0 s, extremely short
The OR seems to have a fix change time for all semaphores and does not look at this definition Semaphoreinfo ( )
But there exist many signals, they use animated colored round pieces (like a semaphore) instead of lights, because the MSTS has had at a time not enough light-points. This lights should change much quicker then the fixed change time of the OR. |
In MSTS the change-time of a semaphorearm is defined in the sigcfg.dat in the SIGNALTYPE-definition by the parameter:
SemaphoreInfo ( 0 )
in this case the change-time is 0 s, extremely short
The OR seems to have a fix change time for all semaphores and does not look at this definition Semaphoreinfo ( )
But there exist many signals, they use animated colored round pieces (like a semaphore) instead of lights, because the MSTS has had at a time not enough light-points. This lights should change much quicker then the fixed change time of the OR.
correction:
if SemaphoreInfo ( 0 ) OR works correct, but for all other change-times
OR use a unified fix change-time of about 0.5 seconds
instead of the time in semaphoreInfo (...)
shorter or longer change-times are not possible |
|