Steam Several Locos Showing 0 Drivable Services In The Timetable Menu/train Depot Service Count Broken

I previously touched upon this subject when I reported that some routes that service counts that were all over the place and far higher than the actual service count in some routes. Well with this report, while that issue was fixed since then, this one has not.
This is more like 2 issues in one, but the first one is that several locos in the timetable selection of some routes are showing 0 drivable services, even though they have services available to drive. Down below are some examples that I was able to find, along with proof that these locos have drivable services on that route.

EMT HST on East Coast Main Line: Peterborough-Doncaster


DB Bnrdzf 463.0 Cab Car on Linke Rheinstrecke


LT 1938 Stock on Bakerloo Line (2021 Timetable)


Flying Scotsman & LMS Jubilee Black on Midland Main Line: Leicester-Derby & Nottingham




DB BR 628.2 on Niddertalbahn


OBB 4024 on S-Bahn Vorarlberg & Semmeringbahn




But that's not all, ever since the update in mid-October, the service count in the Train Depot is completely broken. If you currently click on it to give you the available options, you will see that the service count for timetable is 0, similar to the issues that you see above.

Even if you go into timetable and go through the available trains, none of them have any count of how many services they have across TSW, or even on the route that you have highlighted/selected as seen by the example of the Class 395 from SEHS.


This is really something that needs to be addressed, as right now with certain routes, it's impossible to tell how many services a certain route has if a certain loco read 0 drivable services when it actually does have services available, leading to a count that's far lower than what the route actually provides, and it is possible that are more of these examples out there, as I did some routes with lower services count that what they actually provide, it's just working out what locos are causing it.

It was getting there slowly with a recent patch, but there's still along way to go in order to get the service count back to what it was before that mid-October update.