Broken signal scripts with the public beta

[aorozco623]

I am not sure if this is only an issue in the beta release, or across all version of TS Classic, but I have noticed that I have been randomly getting 15 and 20 MPH speed restrictions in areas that shouldn't have them. Hopefully someone can look into this problem.

[YoRyan]

Can you give me any information about routes, consists, scenarios, locations?

Try disabling ACSES. It might be incorrectly going into positive stop mode. It checks for upcoming "stop" signals and on some routes they don't clear until just before the train encounters them. That's why the mod checks for the presence of a "restricted" cab signal as well, but there may well be certain situations that defeat this logic.

Another possibility is that Dovetail made some kind of core change that causes cab signal messages to be wrongly delivered. That should affect stock scripting as well.

[YoRyan]

Okay, so this definitely looks like a beta issue. If you run the first New York-New Haven scenario ("66 Northeast Regional to New Haven: Part One"), you'll get a Danger signal at the end of the East River tunnel with the beta build. With the stable build, you'll get a Clear.

Dovetail is aware that this build could have introduced signaling problems, so hopefully they'll sort this out.