Hi there - for future reference I highly recommend checking out: https://forums.dovetailgames.com/threads/how-to-and-how-not-to-make-a-suggestion.72089/ a guide on suggestion making including a link to a template in the replies. Have a good time around here in future.
That is not how to make suggestions. Please click the link posted to make a proper suggestion on why Luton to Brighton via Gatwick is a good route.
Especially as BML already exists in the game with the timetable already a fragile thread. Apart from the technical issues of extending the route adding Luton and all the associated MML services likely to collapse the thing entirely.
Remarkable isn't it? Train Sim Classic is over 15 year old copes perfectly well with a Thameslink run from Brighton to Bedford that someone made in their spare time and thankfully added to the Workshop. TSW first developed 5 years ago ostensibly to replace the older game and it's not robust enough for a busy, long route with lots of AI. How did that happen?
My question for almost every single route in TSW. You can run London to Birmingham, Brighton to Bedford, a sizeable portion of the east coast in like 4-5 different eras on an older engine
It's because TSC vs TSW has a lot of differences- the timetable mode is just non existent in TSC, TSC uses an inbuilt route builder so everything is inhouse. While as TSW uses unreal and has a timetable mode. Imagine a run from brighton to Luton or Bedford on unreal, with timetables, you'd have 2500 atleast. That'd cause serious problems.
Nail on head. Most TSC routes merged or otherwise come with a handful of scenarios. You cannot jump off a train, take over another or decide just to board as a passenger. If you’re into career scoring, most runs are carelessly set up so you start losing 100’s of points as soon as you are running more than a minute or two late.
I appreciate the differences between the two games, in the event of a theoretical Workshop merge of two TSW routes none of the scenarios/timetables from the two routes would port to the merged route. Just as is the case with TSC, it would treated in the library as a new route and therefore would need scenarios and/or a whole timetable to be created by users. The point I'm making is that if TSW can't cope with stutter-less short routes, let alone longer ones and has no functionality that allows for merges then it TSW would appear in many ways to be a backward step. Note the improvements in every other type of simulation games since 2007 and compare. That TSC is still more popular according to Steam stats says so much. Maybe TSW4 will take the step up that's needed.
