Everything was fine till i got to sittingborne. Going along at 15mph as instruced. Saying go via, which i was. Got to the green light at the end of the platform. Up pops next instruction then slams emergency brakes on straight after it. I then reset everything. Brakes off as normal but no power to move the train. Everything was set as normal to move the train. But it wasnt going anywhere. So i couldnt finish the service.
Was it same as this? Glad it’s not just me. I’m on PlayStation https://forums.dovetailgames.com/th...rake-hoo-runaround-service.35683/#post-252656
Like you I also couldn’t get it going after the stop. I even consulted a friendly real life class 66 driver I know but it still didn’t want to go!
I'm currently testing it now TinTin_57, to see if I can get the old girl to move. The issues I have is the 66 is grossly underpowered in the game. One thing I've noticed in the SEHS 66 is that the TPWS Train stop override is active every time the the DSD is active and reset.
So my initial findings half way through the scenario. The Class 66 is drastically underpowered pulling 1600 tonnes on a flat gradient. You seem to be limited to under 30mph. It also only pulls away light engine in Notch 3, something is seriously wrong with the weight of the Class 66 light engine and the weight of the train ingame. It feels more like 2200+ tonnes being hauled. TPWS Train stop override light constantly illuminated when DSD sounds and is reset, doesn't illuminate for AWS alarms in Number 1 cab. No EOTD displayed on last wagon in consist on Xbox Series X, but it then appears on the 66 as you uncouple the wagons and remains on throughout the run round portion of the scenario. When coupled back up EOTD is on the front of the loco. Game seems to think the train is running backwards when selecting an external camera. Applying the automatic brake doesn't actually apply the right brake pressures, one touch of the brake controller should apply the brake controller to 4.6 on the brake indicator gauge, it's not even applying 0.1 bars of pressure. Pipes are not stowed on all DTG built Class 66's. Further notes after leaving Hoo Junction. Why a stop at location at Gillingham? You've got momentum up and doing a decent speed. With a green signal Bringing the train to a stand with the power to weight issues, makes no sense. When braking for Sittingbourne 15mph, the loco is the only thing braking the train, so there's no braking application on the wagons, yes it's downhill, but there's nothing there until full service. I went through EK 4213 at 10mph and DID NOT get a brake application. This is the signal you reported an issue with a Sittingbourne. stevenwalker1985 There was no brake application at Rochester either TinTin_57. There should be flashing yellow's at the end of the route towards Faversham to put you into the end point of the scenario.
I totally agree with what you said. I just did it again with aws only. Still the same at 15mph. Did it just now with aws and dsd off. And went through at 15mph with no issues. So there is something up with it for sure.
Well it could be that the TPWS grid is set to drop the brake at 15mph, do it with it on and go through at 10mph and see if it triggers.
Yes, DSD is bugged in the 66 since it was brought into TSW2 (on ECW at least), I can never hear the DSD alarm and always receive random e. brake applications, I always run with DSD isolated.
I just tried it with aws and dsd at 15mph brakes on. only aws at 15mph brakes on again. Did it again with aws and dsd at 10mph brakes on. Did it again with aws only at 10mph and it was fine.
Probabily people just stopped using the loco controls roughly at the same time, causing DSD to activate near the signal? It would be quite the coincidence, but if that guy said he went past it with AWS but no DSD what else could it be?
Well there is that. But I'm referring to real life 66. DSD and TPWS aren't linked. But like I've said I completed the scenario/job with all safety systems on and no brake applications at either Sittingbourne or Rochester as per two people reporting issues.
No it's not. As I did it with everything active. It could be you're running too early and the game hasn't deactivated it when you go over it. If you're constantly going over 60mph you're gonna be arriving way too early.
Following the speed limits of course. But then again the train is slow so cant reqlly get to the speed limits anyway really.
You may not encounter the bug if you are pressing B/Circle or Q key at that point (for DSD/AWS acknowledgments). For some reason, the Class 66 with blue text on the EM2000, links TPWS Override to this button. If you press Q, you can see it has 2 AWS Acknowledgement notifications pop up (one must be for TPWS Override as it illuminates). This may be why some of us aren't experiencing the bug...assuming it is definitely the TPWS.
Yeah on the PlayStation thread Matt is suggesting some of us could be using the GWE 66 (green text on the Em2000) instead of the ECW 66 which is in blue. In my case I just picked the first that came up and not sure what that was. I’ll try it later and make sure I have the blue
Just run it without an issue making sure I had the 66 that has the blue writing on the EM2000. Worth pinning it somehow because it’s not obvious
I've got a ghost emergency break just after Sittingbourne objective too on this service. I'm sure that was the ECW's 66. On PC.
