Trying to play this scenario on PlayStation 5 and when choosing the shortest journey available there is a red signal glitch at London Paddington not allow me to leave after setting up the train correctly for the intended journey.
How long did you wait? I have played all 3 of the runs you can choose withing the scenario and they all worked. I'm pretty sure on one of them I had to wait at the red signal for a couple of minutes for the line to clear.
I can confirm (PC), have tried several times because the bug was also reported on Steam today. The Class 166 on platform 14 does not get a green signal, no matter how long you wait.
Don't think so, the problem is that two of the possible services no longer have routes set for them. All you can do at the moment is drive the Reading train.
That's a shame. I really liked this scenario as you could replay it and choose a different service. Wish they'd do more like this.
Same for me, both platform 8 and 14, stuck at reds. Annoying thing is that have played it before and it ran okay. Must be a recent upload causing the problem.
Yes, I was enjoying retrying this when I got ps5. So it was working. Can confirm it is now a festival of waiting.
I have a pc and I have the same problem as the ps4. I can run Down The Line using TSW 2020 and I Do not have a problem, only the TSW2 version.
I can confirm that the red light issue with the services from P8 and P14 is still present. The only way to avoid this issue is to run the P10 service which is around 60 minutes semi-fast to Reading.
Its likely those particular services have something wrong with them then rather than the generic red light issue. I'll check them out on PC and see if they're the same. Edit I see the P numbers are platform numbers - doh Confirmed the P14 service gets stuck on PC too.
There's also another weird bug with this scenario. If you choose the 60 minute service (the only one currently playable), the stop at Ealing Broadway instruction is listed 3 times. The top one listed after the service starts at x time activates a short time after leaving Paddington.
Yep also have the same issue on PC, can't find a solution trying everything that came to my mind. When I checked the route on the map there is like the end of this blue track so maybe something with that is wrong.
Unfortunately this scenario is No.3 in Journey Mode so effectively kills off any further progress along that path.
You can’t on GWE as the Journey is sequential, you need to complete an element to unlock the next one.
Good to know, I'm used to the more modern ones where you can just jump ahead if you want to by selecting the journey you want from the menu.
They seem to have done that when adding in DLC, too. The Baby Bullet and MP15 on SF Corridor are an example.
I've started the PS5 version I ran into this bug last night. I tried the platform 8, 10 and 14 services. 8 and 14 go no-where, I waited until the 166s were queing up to enter Paddington but could not. The only way to complete this at this time is to take the service running from platform 10 and you can complete as normal.
Just to add to my earlier posts about the services, it seems that even if you do run and complete the P10 service in journey mode, it doesn't mark it as done and there's no tick next to it. I completed said scenario last week on the PS5 version and when I went back and checked the list, no tick next to it. You can skip to the next service if you have auto load journeys off as I've run services and scenarios from other journey chapters.
Wish I had seen this sooner. Just sat there in the 166 on Platform 14, watching the window to get to Acton getting smaller and smaller, thinking "There's no way I can make this." Was about to open a thread.
Same issue on PC/Steam. This game is a joke... so many bugs not getting fixed, many of which weren't in the previous version and are so obvious (as in so early in the scenario), yet taking a ridiculous amount of time to be fixed - if they're going to bother at all. And effectively forcing you to buy the new version as new scenarios won't appear for the previous version. I should have just stuck with the older game, as I won't be spending any more on this; no point handing them more money when you never know if you're going to be able to play what you're buying.
Just got this glitch myself on the Xbox Series X version, I don't understand why they don't test their old stuff on the new engine before releasing it publicly for TSW2
I’ve got this problem as well on my Xbox Series X version. Tried the runs leaving from platform 8 and 14 and no matter how long you wait after setting the train up properly the signal remains as a red aspect. I wish they’d fix it but it’s clear from this thread that this glitch has been around for a very long time now, so I’m not confident it’ll ever be fixed.
As a heads up, GWE has been awaiting a preservation crew "sweep" for a long time, indeed the sweep was supposed to have been completed in December last year but for various reasons things were changed around so this release has been delayed... but from what Adam said on the last roadmap stream this is now next in line, so fingers crossed this issue will be fixed as part of that package of fixes and upgrades
