Midland Main Line - still a TPWS nightmare on PC/ Steam. A new route that has obviously been rushed out with very obvious and very irritating bugs. HST 125 services arriving at Nottingham are effected by AWS automatically and for no reaon stopping the train. You are not telling me that this basic fault, which was also effecting PS5 users until a patch was rushed out today for PS5 users, was not spotted during testing of this route. When can Steam users (Windows 11 PC) expect a fix for this nonsensical situation? €35 for a badly tested, rushed out of the door route. As ever, what a disappointing disgrace from Dovetail/ Focus Entertainment. Get it fixed and stop insulting your customers with badly tested and bug ridden DLC's on release.
Are you sure it's not a TPWS overspeed? There are a couple grids approaching Nottingham that got me before i realized they were there
Sticking within the speed limits I've so far had no problem with AWS or TPWS. As noted above it sounds more like a TPWS-related stop. I think this is only the second route to include TPWS properly after Birmingham Cross-City. The only issue I've had with AWS so far is there are a (very) few locations where the magnet is triggering bi-directionally at the moment (for signals behind the player on bi-directional track) but it sounds the alarm and can be cancelled as usual so it's not game-breaking, although it should be fixed.
I have had no issues at all with AWS. On the approach to Nottingham there are several signal sets very close together so if you do not begin to slow down very quickly after a double yellow you will be stopped by TPWS as you do not have time to stop for the red.
I think there are legit TPWS issues, but I actually don't think I have been able to reproduce any (in around 5-10 full service journeys). I've been caught once but that was me approaching a red signal at like 50 mph
This is from the BCC manual if people would like more info on TPWS: "It's not a drivers job to know the speed that TPWS grids are set at, only to drive sensibly enough to avoid triggering the system, therefore we recommend, with the Class 323, passing double yellow signals at no more than 75mph , and single yellow signals at no more than 50mph, reducing your speed after the single yellow down to 30mph, aiming to be at 15mph at the AWS magnet before the signal. Approaching bufferstops you will find if you are travelling faster than 10mph you are likely going to trigger the system." Not sure if these exact limits apply on MML, but probably a decent reference point.
Yes, I've been caught out approaching Nottingham for the 25mph I think - way before it actually whilst travelling slow enough, so I think it needs tweaking. There are a few missing AWS ramps however and also quite a few directional AWS issues on the reversible line around Leicester - i.e they ping for the reverse direction signal. I also think there are a few speed signs missing, although that may be as per reality, not sure. I think someone from Skyhook or a beta tester needs to drive the various routes and note down the few anomolies. There are also some inadeqaute approach control issues at a couple of junctions and a couple of signals with wrong feather directions. That's for another thread though. The good news is Skyhook seem to be listening and actioning feedback.
i have had more so issues of the shut downs with the 158 heading into Nottingham not so on HST i have founded slowing down more before hand on the HST works on im on PC Steam yeah there is issues but at least they working on a patch god knows when that is
I've been tripped (I'm guessing by TPWS) on the approach to not just Nottingham, but Derby as well, I don't think it's AWS-related but instead TPWS-related (this is on Xbox)
I'm having TPWS activations on every journey at speeds/locations at which they should not occur. Today's two: 1. Tripped by the TPWS at the signal after Long Eaton in the Up direction, passing over the TPWS overspeed loops (well before the AWS magnet) at 28mph. In reality you can go over TPWS overspeed loops that far from the signal at up to around 35mph (the precise speed varies based on a number of factors which are included in the calculation, but 28mph would never be too fast so far from the signal). 2. Tripped (as others have reported) on approach to the 25mph PSR on approach to Nottingham. I was doing 31mph, with a considerable distance to go before the commencement of the 25mph restriction. Again, this would not be close to triggering a TPWS activation in real life. I've looked to see whether you can isolate the TPWS while keeping the AWS active (as you can on the 323 on Cross City) but can't see a way of doing it on either the 158 or HST. You can isolate AWS and TPWS together, but not having AWS is too much of an immersion-killer for me. This makes the route unplayable for me at the moment, unfortunately. Hopefully the upcoming patch will fix it.
For those who want to isolate TPWS but keep AWS operational this can be done by moving the Temporary Isolation rocker switch to "Isolate" above the desk on the non-driver side. The Temp Isolation/Fault light above the desk on the drivers side will illuminate indicating that TPWS is isolated. To re-enable TPWS simply move the rocker switch to "Normal". More details in this great thread.
I think that's where mine tripped too but I am happy to continue driving I haven't had too many issues..... Other routes can't even finish but MML you can. Even sometimes with a few issues....
Luckily I drive with safety systems off but even from casual observation the signalling and speed limits, both in terms of signage and placement of ramps/grids needs a complete rework. We have speed limit commencements in the HUD with no signage on the ground. A rogue 20 MPH speed limit at Syston on the Down Slow which momentarily pops up in the HUD. AWS magnets and TPWS grids in the middle of nowhere, also missing advance speed triangular warning boards. Where AWS ramps are placed for signals these are rather further back than they should be. The route itself actually isn’t that bad and both the 158 and VP185 are great. But the signalling and speed restrictions plus signage needs rebuilding from the ground up by someone competent in how UK infrastructure works.
Frankly that is incredibly poor. To find this out, a beta tester would simply have to drive the route. Oh wait! You early adopters are doing that for free…
