1C11 05:31 Sheffield-London St Pancras
11th June 2023On a misty morning in May 2019 you’re in charge of East Midlands Trains’ 1C11 the 05:31 Sheffield-St Pancras service. You join the train just north of Bedford where you will call at additionally this morning due to the failure of 222101 & 102 on 1P01 the 06:03 service from Melton Mowbray to London. Upon departure from Bedford, you’ll call at Luton Airport Parkway and London St Pancras. It’s a busy weekday morning but no disruption has been reported.
Duration: 35 Minutes.
Requirements:
DTG
*European Loco & Asset Pack*
*Midland Mainline: London-Bedford*
London-Faversham High Speed
North London Line (Or any route containing the Class 387)
Thameslink Class 700
DB Class 407 ‘New ICE 3’
Class 66 EWS v2.0
Class 66 Freightliner v2.0
AP
*Class 43 HST VP185 Enhancement Pack*
Class 66 Enhancement Pack
Class 700/707/717 Enhancement Pack
HKA/JMA Wagon Pack
Class 220/221/222 Sound Pack
Sky & Weather Enhancement Pack 2.0
JT
Class 222 Advanced
Class 153 Advanced
ATS
JT Class 153 West Midlands Rail (Ex London Midland)
Class 222 Destination Upgrade
MJW
*Class 43 Revamp Pack*
Class 153 Revamp Pack
Eurostar Class 374 Reskin
Semaphore Simulations
Meridian/Voyager Advanced 2019 Overhaul
The DLC marked with asterisks (*) are required for the basic functionality of the scenario. Other DLC adds to the realism and intended experience in the scenario.
To start the installation of the scenario, unzip the .7z file.
An excellent scenario thank you
hi, loved the scenario and the really interesting stock. Just one question, are you sure that the scenario is enabled for ap weather v2.0? I normally find that if a scenario has ap weather v.2.0 it collapses to desktop on loading as I use full screen mode. It didn’t and I wouldnt say that the scenario looked misty either. Loved it anyway, thanks
Sorry, but I’m getting many errors upon loading this scenario. Route is blocked, Can’t find destination, etc… for many services. Any ideas? Have tried re-downloading the route.
Not too sure sorry this wasn’t an error that was occurring during testing. If you run the scenario from the editor this may help.