Activity log for bug #1348980

Date Who What changed Old value New value Message
2014-07-26 19:00:50 Rippstein bug added bug
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
2014-08-02 14:45:40 James Ross or: status New In Progress
2014-08-02 14:45:42 James Ross or: importance Undecided Low
2014-08-02 14:45:43 James Ross or: assignee James Ross (twpol)
2014-08-02 14:50:44 James Ross or: status In Progress Fix Committed
2014-08-02 14:50:46 James Ross or: milestone 1.0
2014-08-02 14:51:16 James Ross summary Change-time semaphorearms Semaphore signals ignore SemaphoreInfo() change time
2015-05-25 11:09:40 James Ross or: status Fix Committed Fix Released