Steam Spad Failure In Random Location Without Signal Birmingham - Crewe

I have just been on Birmingham - Crewe but it seems I can't get an end to end run in without something going wrong. The first run the crashed and the second run now ended with this happening. I was running on a STP service/free roam with a 801/1 from Crewe approaching Wolverhampton about to pass over Fox's Lane bridge (RBS2/119), the previous signal was double yellow and I was doing 30.68 MPH according to Thirdrails, I could see the next signal was single yellow, I had not yet reached it but I got kicked (SPAD).

This is the precise location:


This is the service record:
https://rentor.nl/Ride/0384b32b0dd44493a5dd5362161ef8ec

Why is this happening?

 

There's a bug with AI trains SPAD-ing which causes the player to be kicked out as if they were the culprit

 

Yes it’s a known issue as being documented in the official feedback thread.

What’s less certain is when or even if it will be fixed as last I heard the route developers seemed to be struggling with how to debug the problem.

So once more, definitely a case to be made for a code change that means an AI SPAD does not result in the player run being terminated.

 

I don't think I have encountered AI misbehaving before, that is a weird issue.

 

Happened on Spirit Of Steam where it took over a year to identify and fix the cause. Prevented Journey mode from being completed until fixed.

 

hey I faced the same issue today as well .... was doing an evening service on the voyager 220 from stafford to birmingham new street ..... and somewhere after dudley port I got SPAD error and my service ended abruptly even though all signals were green for my line and I was strictly under the speed limit.... so playing this dlc I cannot even complete a full service ... whats the point of even releasing dlcs in this state ... If anyone from dovetails game and all aboard studios are reading this ... please please have some kindness for the buyers of this dlc and fix the issues !

 

From what I've seen of the patch notes this doesn't seem to have been addressed and no indication it's an easy one to fix.

The only real solution, as I've mentioned before, is for DTG to remove the algorithm that causes an AI SPAD to fail the player service, if need be auto deleting the train(s) involved.