Route West Coast Main Line: London Euston - Milton Keynes - Feedback

The signal buzzers would be really nice to implement in both modes, both once the doors have shut when driving so you can give 2 back, and on the guard mode in return to your 2 buzzers.

 

Very disappointing route. There is just not enough traffic on the route. Isn't this supposed to be one of the busier routes in the UK? It does not show. Had an LGV dejavu driving this route in the Avanti.

 

I know it probably couldn’t be done as they are only layered, but a shame the 710 didn’t get its own mini Journey mode on the route.

 

Random lighting with no obvious source just north of Tring just at signal TK5178

 

Some services seem to get stuck, because the AI trains can't open the doors properly, blocking the lines for all following trains (those are allowed in the block, though, and stop right behind the "stranded" service).

When I took over the "stranded" service (2T40), closed and reopened the doors, then abandoned the service, the AI would resume as expected (close the doors and proceed).

 

Regeneration

 

Wembley Central platform 6 - re DTG/RG (another hint at the scope of Rivet’s involvement) flags - one of the DTG flags is kind of semi behind but sticking through a poster

 

Also, the 350 is very empty given the football scenario purposes is due to high crowd numbers!

 

Service : 2C49 - 1730 Watford Junction-Euston
Unit: 710
Weather: Custom, Clear, 18th September
Platform: PC/Steam

Issue: AWS ramps as associated signals WS74 AWS horn vice bell on a green. WS66R same as WS74, however maybe the TSW quirk of a horn at a relate signal with a green aspect. WS22 at Willesden Junction no AWS bell at the magnet. All on the up line.

Other issues in general, double AWS ramps on the up leaving Tring, and on the down at Harrow and Wealdstone.

 

There’s numerous issues with AWS set up wrong at multiple locations. Needs someone at DTG who knows what they’re doing with signalling to go through the route and check all the links are set up correctly, or however it’s done in TSW. In fact I would go so far as to say this route is worse for incorrect AWS than MML was on release. Can’t remember where it was exactly but somewhere on the Up Slow, might be Cheddington area there’s a ramp that gives a warning nowhere near a signal or speed reduction advance board.

 

Missing AWS magnet in front of this signal.

In fact there are a whole bunch a missing AWS magnets across the southbound Watford DC line…

 

I'm sure this has been requested before, but I’ve noticed several neutral section signs along the route without any functionality. I’d like to suggest adding fully operational neutral sections. With JT's Class 87 on the way, this would be a great feature to experience—managing the tap changer and cutting power before entering the section, plus the immersive sound of the fans winding down and back up again.

 

There's some real oddities during the hours of darkness at Euston, track appears black before entering the sheltered section of the platform, the train lighting changes as the train hits the platform. See image below.

 

Wembley Central

WM338 on the Up Slow. The theatre box would only display WR (Willesden Relief) and if the route was set for Up Slow it would be blank. In game it displays US which is wrong.
The station footbridge at country end is only used during stadium events, the correct one is the concourse one at the Milton end which in game cannot be accessed.

Harrow & Wealdstone

Down Slow stop car marks are wrong and platform is too short.

 

I will say as a positive for the timetable and one service worth playing - 1Y21 0854 London Euston - Birmingham New Street. Plenty of AI traffic, especially Watford-Euston. First stop Leighton Buzzard so pushing the 350 to 110mph most of the way. And also changing from the fast to the slow line at Ledburn Junction.

Only negative I got a TPWS activation on approach to Milton Keynes, Milton Keynes South Junction, no obvious reason I’d say my speed was 40-50 mph and braking.

 

PS5 keeps crashing on approaching Euston. Usually in the primrose tunnels on the fast line.

 

Same on series S, always at Euston I crash even though my performance is quite fast.

 

• The bodyside indicator lights on the 350 only turn off behind where the guards key is active (so they're all on if dispatching from rear vehicle), despite the doors being locked on all but the vehicle the guard is at.
• No eurobalise antennas along the route, in the four-foot.
• In guard mode, the AI deceleration of the 350 is awful. Between 85-60mph the train slows down sharply in 5mph increments. My virtual character has severe whiplash now!
• 2T19 spawned me at Tring rather than on the train at Euston.
• The final stop doesn't display on the 350 scrolling PIS boards.

 

More bugs to add

- in the timetable selection you find 350 services saying things like early morning and late night despite it being a 15:00 service

- on the PIS the grammar looks like Jeremy Clarkson with AWC services being 'a avanti' service

 

So things I've noticed about WCML South pathing, routing and stock issues.

1. 6V49 in real life is a JNA rake from Northampton Castle Sidings to Acton, not intermodal boxes as it is presently.
2. Bletchley Reliefs not being used to stable intermodal trains, they've been added and routed to the Bletchley carriage sidings.
3. Wembley Central signalling is all wrong when being routed to the reliefs, you will very rarely be routed along the Up Slow to Sudbury Junction (this is for Southern units), freight gets a wR at the end of the Platform and then drops on to the Willesden Relief lines there, and proceed along from there.
4. Trains for Acton need to be routed to WM21 signal at Willesden No7 junction just before Acton Lane Reception lines, 6V49 is set to finish in line with Acton Lane Reception lines and therefore would not be able to get to Acton without a serious shunting and run rounds.
5. The timetable really does need a overhaul on the routing, and I have to agree it feels very rushed

 

It will also display R1-7 or UC for Carriage sidings for freight going into Wembley Yard and the ICD

 

Back again with another...

- After entering photo mode in thick fog i was met with a clear view after exiting

 

I still don't really understand how this got through testing, surely some folks are tasked with checking signalling at some point by driving up and down the route? Skyhook made a bit of a mess with their signalling for MML initially (similar AWS issues), it took an age to get sorted (I'm guessing because fixing it screws up the timetable). Therefore it pays to get it properly sorted before timetable creation.

 

I can give a strange thing.... If i have turend on motion Sway that the cab is strange vibrating..... Its very strange and only on this route. Anybody else who have noticed that? Its after yesterdays update.

 

I can only assume this route was a particular casualty of the beta team breach as most of the leaked content came from it. So they just sacked the whole group and didn't bring anyone else in. They could have asked any one of us on here to take a quick drive up and down the principal lines and we would have reported that back in a heartbeat.

 

At Bletchley on platform one, you forgot to add collision to the overpass, it’s only textures so if I try to go up I’ll end up back on the platform, if I go down no problemo lol:

 

5C00 0440 710 - starts with flashing shoes down button, but this is an OHLE area

 

Same with part two of the service, and there is no power changeover point set up either

 

Same service. Platform indicator just before Watford junction told me I was going into platform 3, but I was actually going into platform 4.

 

Ground signal W762 coming out of Wembley Intercity Depot gives a TPWS brake demand.

 

Absolutely love the route, however the timetable needs seriously addressing for overground and underground services and the TFL map signage has been removed at stations and more passenger information screens need to be added especially at Watford junction. 710 needs passenger information in the train for next stops in the interior of the train "train to Euston" is just a little plain in my eyes but that's just my opinion.

Great route to play however I'm going to wait for updates at the moment

There's so much potential for this route in my opinion I'm sure if there's a way to get DLC extension content people will go mad and I'd probably buy on day 1 immediately the st.albans' line would be great to add for DLC content as the bletchley - Bedford line but I'm sure people would go insane for any type of extension on this route especially north of the line so we get more use out of the 390

Apart from all what's mentioned above and if we're able to get branded livery on the WCML I'd definitely say we'd have endless gameplay! And this would be a triple AAA when everything gets sorted out.

Also when I did route hop to the bakerloo line when one-stop to kilburn park and the signage is all incorrect northbound is on the soundbound platforms and southbound has northbound platforms I think this was an old bug from before but little mistakes like this makes it feel there's no quality control/quality checking - super fun to play but please fix the timetable!

 

DTG should be very proud of how well this ‘flagship’ route for TSW 5 turned out. I’m being sarcastic here, but I’m pretty sure DTG is proud of the way this route turned out, or they wouldn’t have released it.

Soooo glad I cancelled my pre-order and I’m thoroughly enjoying reading about all the issues we knew from the preview stream would be there.

 

8/10 seems awfully high based on all of the issues players are raising. You might be an ambassador before TSW 6 comes out.

 

Why, because I’ve given my honest opinion?

I know you have an axe to grind, I remember when you were leaving the community all together and never buying another piece of TSW DLC, but there you go.

I’ve given my feedback, I’ve said it’s not perfect pointed out the various issues.

I think a timetable makes or breaks a route and it is one of the shortcomings of WCML.

I’ve played 15.3 hours of TSW5 so far all on WCML, and it’s given me all enjoyment with the odd frustration over the timetable and AWS issues, it’s hardly unplayable and as long as I’ve enjoyed myself then that’s all that matters.

 

5.5/10 as it stands. I mean the route is not unplayable and the 390 is a nice bit of kit. But Code 2 AWS faults on numerous signals should not have slipped through QA as a minimum, then all the other issues.

 

Stopping points in Euston seem to be all over the place, some being set quite far back from the buffer stops

 

Playing on Series X:-

• Audio crackling/popping in the cab
• Hazy flickering along the bottom of the cab windscreen in 350 and 377
• Cab instrument labels text flickering and disappearing continuously 350 & 377
• Crashing after an hour+ in the game
• Played the first scenario and got all the way to Euston and didn't see a single piece of AI traffic. Once I got to Euston, the game crashed as I was unloading passengers about to complete the scenario
• In timetable, played the 06:28 350 services from MK to LE and 6 miles from Euston all the signals were at red and no traffic was moving. Tried removing all the services but still no green lights.

 

PC Player - Steam

APSLEY platform vegetation/clutter needs finishing.

 

I'm not sure if this has been reported but service 2T13 (London Euston to Tring at 0752, I think) cannot keep to the timetable because it is following a slower service. I've had this problem on Frankfurt to Fulda as well. Don't get me wrong, I like having services where I have to pay attention to the signalling but the timetable needs to be adjusted so that it is achievable. I wonder if this is a consequence of having multiple layers. People with fewer layers might be able to keep to time.

 

Sorry but have to disagree with you here. This is the way it is in real life. Railroads don't adjust schedules because its congested, they live with being late. I do feel that some of this is due to the AI dispatcher being "kind of dumb" when it comes to setting routes, but that is inherent with the underlying game engine.

 

That's true. I think I expect the "base" timetable to be achievable because that is what has been planned and congestion should have been taken into account. Random events can, of course, disrupt this plan, but those are not available in game. The question is what is the "base" timetable? Particularly on routes with many layers. Some players could struggle to keep to time if they have all the layers while some could be running early if they have only a few. Where should the line be drawn?

Anyway, I think I should stop thinking about timetables for tonight

 

Ran the WCML for three hours today after a session on San Bernardino.
Final run from MK to Euston started the stutters and once completed it had run over 22 GB ram, when I checked afterburner straight after closing.
Could be an issue there.
PC steam,amd 3600 ,2070 super,32 GB ram.
Edit : memory leak:
It's repeatable; the game needs closing and restarting, otherwise it stays with the stutters and higher than usual ram usage.
Visual settings in line with pc performance.
Default high 60 FPS locked.

 

M
Missing part of rail on the map at Harrow where the DC line joins to Bakerloo

 

Performance is fine. But the game crashes at big stations such as Watford Junction. No issue relating to stutters (xbox series s). The crashes are rare, happen very rarely on frankfurt route as well

Edit: just checked now, i turned the layers off and to confirm, the crashes aren't related to the trains

 

Spawned a 484, I can move but I can’t set a destination in free roam, I get the unreachable message. I’m on the 3rd rail tracks.

 

Same issue here. For some reason the dispatcher won’t let some routes get set on the DC lines.

 

I've been out of the country all week, have DTG said anything about a fix coming up?
In particular has DTG Alex or DTG Matt addressed the lighting issues and the god awful 710 timetable?

 

Folks keep mentioning the 710 timetable being awful (it is), but the Bakerloo line timetable is also very poorly represented on this route. Like if you go to Queen’s Park on the Bakerloo Line, you’ll see near constant trains coming in and out of the tunnels and sidings. But then you go to the WCML version of Queen’s Park and it’s… nothing. Transport for London got screwed in this one!

 

Timetable 2J45 Bakerloo on WCML.
Start,Kilburn park the station is pitch black,track is daytime bright.No external camera available till you climb out the tunnel at Queen's park.
Door chime is present but no audio for doors.
Also the flashes seen in several tunnels appear to be caused by holes in topography or missing texture map above.

 

Can't disagree, I guess I'm more focused on the LO timetable because I love driving the 710 and along with some of the 350 services are proper end to end runs which are my preference.