The route is set in the early 2000s so I don''t think it is reasonable to expect great mountains of stock for other eras.trainsmit wrote:I have been´working a few days on a pack of scenarios under the "Default Diesel" brand - for the default Great Western Main Line, for starters. The idea expands to Default Steam/Electric/DMU/EMU on other default routes. The challenge is to compose plausible traffic with only default assets.
On the OxPad the HST and Class 166 in FGW livery seems plausible after 1992, but what about earlier?
You do have the original IC125 livery and Class 47's though, that could be a good start if a bit lacking for local traffic.
This is where you need to do some trial runs in a free roam scenario with some kind of stopwatch-equipped device (including a smartphone or iPod) and base your scenarios on the actual capabilities of the traction you'll be using. Then set the % performance to the value which leads to the timing matching your data, minus a couple of percentage points so that you have a little padding.trainsmit wrote:If you run an all stops 166 down the GWML, then even if you accelerate and brake at 100%, you are unlikely to be able to keep a timetable, that uses the default 75% power and 35 second stopping time. The power setting gives the average speed between calls as a percentage of the line speed. I guess the driving time is computed by dividing the distance with the set average velocity. However, the actual consist - AI or user driven - may not be able to accelerate or run fast enough to keep the timetable. In that case the train will run late.
While 75% is clearly preposterous at times (like the 166 having a maximum speed less than 75% of the GWML's 125mph linespeed) I guess that they had to set the default value to something rather than nothing.
Your passengers must love you! 
