Feature Tell Us What Stops We're Doing Before We Start The Service

On the page that says drive the passenger service from x to y, include at the end, "calling at: a, b, c, etc"


Say your looking at services on the Riviera line and your thinking you want to do a stopping service and not an express service, this would help a great deal

 

Timetables are mostly repetitive, with maybe slight variations (most of which would occur in rush hour periods).

On any given timetable, the stops are virtually the same.

 

I do support the OP, there are routes with differing service patterns and I’d like to know beforehand if it’s a bus service, so I can avoid it.

Also, while on the subject, why can’t we have the timetable displayed in a, erm, proper timetable tabular form, not just a list of services.

And a further point to tag on this, when driving we should be seeing more than the passenger times. We should be driving to the working timetable. It’s faintly ridiculous on routes like WCMLoS to depart Preston on a non stop run and the next timing point is Carlisle 90 odd miles away. How are we supposed to monitor our progress and punctuality?

 

I believe I had a similar suggestion way back... it had to do with what consist we are getting (obviously cant be done on random consists like in MBTA Commuter), like if we are getting 1x, 2x MU, how many wagons/coaches... and yeah some routes list the stopping pattern kinda, but it would be nice to know that too

 

Exactly. It wouldn't be difficult to include a pdf timetable with each route, considering the devs use real timetables when designing the routes. You can get a rough idea of stops from the journey duration - express v stopping - but it's not perfect.

 

Given the schedules are programmed in the .pak files, no doubt an intrepid hacker/programmer can try to get a timetable in readable format and draw a classic timetable graph from those .pak?

A Vern-O-Meter displaying your actual 'driver' performance would be nice if TSW were a proper simulation. Are there even any data available by some tcp protocol?

However, given TSW is increasingly moving away from a simulation into a train driving game aimed at the console market, the thumbstick warrior looking for a 30 minutes distraction from FPS gaming has to settle with XP points.

 

At a glance, it's usually easy to work out by comparing the time on services between the ends of the line. Significantly shorter times for the same distance mean express services.