[mauried]

Many signals in a typical MSTS sigcfg.dat file have lines like this.

SignalAspect ( STOP "Red" SpeedMPH ( 0 ) )
SignalAspect ( RESTRICTING "Flashing Red" SpeedMPH ( 15 ) )
SignalAspect ( APPROACH_1 "Yellow" SpeedMPH ( 40 ) SignalFlags ( ASAP ) )
SignalAspect ( APPROACH_2 "Flashing Yellow" )
SignalAspect ( APPROACH_3 "Flashing Yellow" )
SignalAspect ( CLEAR_1 "Green" )
SignalAspect ( CLEAR_2 "Green"
)

All fairly straightforward except the line with
SignalFlags ( ASAP ) in it , which Ive never understood its function.
How does OR interpret this line , and how does the signal behave differantly
if the SignalFlags ( ASAP ) is not there, in so far as defining train speed limits?
Reason for asking is that Im getting some odd AI train behaviour where AI trains are
running slowly for no obvious reason, and the F5 dispatcher window shows the AI train as being subject
to a low maximum speed limit, and I cant work out whats causing it,but appears to be signal related.

Thanks

[roeter]

The "ASAP" flag indicates that the train should reach that speed sometime after passing that signal - which means there is no actual speed limit at the signal itself.
That is how this flag is used in OR : if set, the defined speed limit is simply ignored.
What exactly happens to the AI trains I clearly cannot tell. It might be related to the mode you're running and the selected options (especially enhanced activity compatibility), but if you want anybody to look into this you will have to provide a lot more details.

Regards,
Rob Roeterdink

[Csantucci]

The compatibility flag shouldn't change the behavior there, but of course, as Rob said, more details are needed to try to understand what happens. So as a first proposal I would suggest: try with and without the compatibility flag to see if something different happens referring to AI train speed; try deleting the speed limit and the ASAP from the line of the sigcfg.dat file and check if something different happens.

[mauried]

Thanks.
Ive done some more tests, and there appears to be some conflict between the speed limits being set by signals and the speed limits
which are set by speed boards, but the problem is only apparent if the Enhanced Compatability with MSTS Activities box is checked.
If unchecked everything works as it should.
What actually does this checkbox do?
Ill put together a simple route and activity to try and make the problem reproducable.