I know this has been mentioned previously, but I think it deserves a revisit and, ideally, an explanation from DTG. The TSR layouts in this scenario (possibly others, this is the only one I've checked) are utterly abysmal, and about as far from real life as you can imagine. For the benefit of the devs, the correct sequence for a TSR layout is as follows - 1) Portable AWS magnet 2) TSR warning board 3) - BRAKING DISTANCE - 4) TSR commencement board 5) Termination indicator ('T' board) The first TSR in the mentioned scenario is a 30 mph restriction. There is no AWS magnet, roughly 200 yards of braking distance to brake from 125 mph to 30 mph, and a rogue SPATE board after the termination indicator which appears to serve no purpose whatsoever. I've seen somebody suggest that in real life, a driver will know the locations of the TSRs in advance, which is correct - they're published in the WONs (weekly operating notices). However, the system is designed to be failsafe so, in theory, a driver with route knowledge (which is what the speed map is for in TSW) could still safely drive the network without having checked any of their notices. This is what the AWS magnet and braking distance are for - generally speaking, upon receiving the AWS horn and sighting the TSR warning board, if you apply at least 50% of the train's brake, this will be sufficient to achieve the speed by the commencement board. I get that this is ultimately a 'game', but so much effort has gone into almost all aspects of it that I find it very confusing why something as simple as this has been overlooked. From memory, this is something that has been ongoing in the TSW series for years - I remember multiple occasions in TSW 2/3 scenarios when I've encountered the same problem. This is a very, very simple thing to fix, and I would suggest focusing on this before correcting things such as "Fixed the text on the Groningen Europapark sign, which used to display 'Groningen Europapark Europapark'." Come on guys, this is one of the main scenarios on your poster child route, on your flagship sim.
Think several of us pointed this out at the time in the ECML feedback but ignored by DTG. Along with Emily Turner and the farmer telling the driver it was okay to continue after moving cows off the line, they completely ignore even an attempt to comply with correct operational procedures. Seems unlikely they will fix it at this point and the particular error with TSR's/ESR's was repeated in a scenario on the Goblin Line.
It took a while for them to get approach control signalling nailed, so hopefully this will get sorted as well. Hoping in the next iteration of the sim we get more of this kind of stuff (TSR's - correctly implemented of course, random events, AI delays etc). The diorama thing was a promising push in this direction but inexplicably got the chop - no idea why.
