Just in case it was a bug in TRS19, I ran a test using one of my sessions that uses the SPAD rule. It worked exactly as expected. It is possible that it may be an issue with individual signals but not with those that I use.
An obvious question. How are you handling the SPAD? Normally a train under AI control will not pass a signal at stop so a SPAD should not occur. AFAIK SPADs only happen with trains under manual control and even then they will not produce any result unless you have the Signal Passed At Danger rule in the session that is setup to handle the event.
Check in lower right hand corner of the screen while in Driver. If you pass the red signal, you'll get a subtle SPAD message. Manually driving won't stop you from proceeding unless you have the SPAD rule in place.
I'm so confused. I deleted the route and re-made it. Now... it's working fine? Thank you John, I have to figure out where I'm screwing up laying track?
I'm so confused. I deleted the route and re-made it. Now... it's working fine? Thank you John, I have to figure out where I'm screwing up laying track?
This is what makes reporting bugs to the QA team becomes a game of cat and mouse. A problem will occur repeatedly during testing. Repeatedly enough to make this annoyance a reportable item. We go through the motions of uploading screenshots, videos, KUIDs, and anything else that causes the problem. The QA Team then loads up the same exact content, sometimes even a sample route exhibiting the problem, and they can't reproduce it!
Whoa! What????
You then test the same exact route again, after they said they couldn't find the issue, and the same issue no longer appears in your sample!
