Yet another failure to resume a saved service, again on the 166, requiring a restart of the computer. Plus continuing problems with the 802. Would not start an express service from Reading to Paddington, again requiring a restart. And, as noted by me and others, it does not work with the Raildriver. I think I'll take a break from GWE-R, it's driving me crazy.
Such a shame but it has ruined the remaster. I accept what Liam says that it's outside his control but, still, what is different about the route from the original that now makes this an issue? Doubt I will be spending much time playing it or buying any extra content for the route until the matter is addressed. And I can't understand how this wasn't picked up during testing or did everyone just complete all the runs in a straight shot, no testing with the save/load on a variety of services?
I'm at a lose currently with it. It's not something that was reported once during months of QA nor something I have been able to replicate on PC yet which is adding to the frustration of it. One suspicion is perhaps loading a save from such a large timetable causes issues. I don't suppose anyone has had this crash on the original timetable since the remaster?
Can’t say on that, but there’s another thread opened on Trainsim World Community FB page this morning from people having the same issue. All I can say is the only other route giving issues (for me) is Frankfurt S Bahn but that is a soft CTD with a UE error after trying to load, not the complete hardware lock up either during loading or within a couple of minutes of running. I may give that a test later, maybe disable the LUL or the Connect layers (we know the 350 is a bit of a dark horse from WCMLS and B2C), see if that makes a difference.
I wonder if it’s a legacy issue with the route as always used to have this issue on the scenario where you have to drag a HST with the 66 - saving the game would render it unfinishable, even if you never left the session. That being said I’ve not had the save issue on any timetabled service in the remaster, albeit I rarely use the save as they’re mostly short services.
That does work as does a simpler method - sometimes. I've been able to swap to diesel from electric purely by pressing the diesel button until it's lit (PC). Doing so starts the engines and drops the pan. Trouble is any method seems to be inconsistent and possibly depends on the state of the unit when it loads. The TMS traction screen can't be relied on for trouble shooting as it can report a pan as up when it's visibly down. The fact that nobody from DTG has seen fit to offer any assistance on this issue, and it's been raised in other threads, speaks volumes for the support their paying customers can expect once they've got your cash.
Why is there so many different many different locos list to choose from it hurts my brain figuring out witch one to pick.
Well, I can only emphasize that what's happening on GWE-R is a completely new experience for me. I've never had lockups or CTD's on any route before this, certainly not on the original GWE. Add to this the fact that at least one train does not work with the Raildriver and it's making the remaster unplayable for me right now. I fully respect the effort that DTG Liam has made with the route and realize that these issues are not down to him. I can only assume that the problems are due to poor Q&A and a failure to fully test the route and layers before publication and release. I mean it's not like this is the first time we've seen routes with launch issues. Sign me " Very disappointed ".
OK, dal#7945, I ran it from the tt and as soon as it started, the train rolled onto its left side, which ended it. I then spawned on foot at Reading and went looking for 5R21. When I found it, I took it over from the AI driver and was able to successfully complete it. Why the difference, no idea.
Derailment rolling seems to happen now and again. Have had it on the PS5 with BML and various routes randomly on PC, since TSW6 came out. Just like the spawning away from your train, it’s very hard to replicate as it doesn’t necessarily happen next time. Possibly more of a core issue, or the core’s response to a set of conditions in the route that it cannot resolve, so it tips the player train over like a checkmated chess Queen.
DTG Liam found a weired issue with the 165 unit on 1P06, on PC basically the cab indicators are not working properly, it doesent show that you have enabled TPWS and oddly the TPWS brake demand light is lit, also the door interlock light is lit even when the doors are closed, and also the proving lights are not working for the headlights, they dont change when you switch between tail lights and headlights. The AWS, lights and i assume TPWS are working as they should just the cab doesent say so.....
Testing now to see if knocking out the 350's cures the game loading issue. Edit: It's not the 350's, or the West London layer which I also disabled. Started a Class 166 run from Reading to Paddington and saved after departing Twyford. Exited game and restarted. Save game loaded and ran for about two minutes before hard video lock up requiring PC reboot on the button. Edit 2: Going to see if removing the LUL layer (which must be a heck of a lot of trains) makes a difference.
This ones got a fix ready for an update. The FGB 166s have a swapped material ID in one of the cabs which was missed.
Further to mine above... nope, taking out all the LUL layers including the 1938 stock, still got a lock up exactly two minutes after resuming the run. So I don't think it can be a layer issue or the timetable overwhelming the RAM. Anyhow that's enough PC hard reboots for one evening, think this one definitely has to be thrown back in DTG's lap to debug and fix.
Sorry to hear it's still happening. I've asked the beta team to try and replicate it as I'm clueless myself on what could be the cause, but I'm hoping someone who understands the core game better than myself can shed some light on the issue.
Yes. I know DTG Liam has taken this issue on board, but would be nice to get some acknowledgment from one of the mods that they're aware and looking into it. Of course whether they're actually following the feedback threads is an open question, since we don't get any responses for the most part. I suppose they're all over on Discord Q&A these days. We could just be whistling Dixie here on the forgotten forums.
Hi DTG Liam , just want to let you know that the issue regarding gwe on series s is fine. I have a controller that has a bit of stick drift which could have resulted in it being disable without me knowing
Announcements issue: I’m at London Paddington announcement says the next train to arrive is to London Paddington calling at London Paddington only. Should be the next train to arrive at platform __ is the __ service from __ this train will terminate here.
About to test the save game with a DLOGW run. More to follow... Okay, so far loaded game from DLOGW timetable is holding up so it does look as if the issue with saves not loading sits somewhere firmly inside the new timetable. Well, we know it's not the 350 or 484 layers so maybe something with the 166's or even HST's that needs to be debugged?
Xbox Series X Started 1K21 Bedwyn - London Paddington. GWE 166 - 3 car Left Reading and saved as I went through Twyford at 06:27. Exited to menu, quite game and reloaded. 06:30 Game running smoothly. 06:34 - passed through Maidenhead with no crashes or performance issues. Made it into Slough at 06:40 and completed loading cycle before coming off the game as hadn't got time to finish the run. Again no crashes or performance issues.
DTG Liam Hi Liam job 5P55 166 3 car in green instant derailment on xbox series x. Sharon E hello would give that one a try for us.
dal#7945 I started with 5P55 from Reading TCD to Reading station. When coming in via the tt, the train immediately starts wobbling and the run crashes. Spawned on foot at Reading TCD and took over the train. At 1404 I got a "Wait a Moment" with a new start time of 1405. I waited until 1410 and it never showed an "Objective Complete" so I could begin. Further, when I moved anyway and approached the red dwarf signal, contacting the signaler did not get any response. So would have to think this one is broke.
1. Can report another successful load into a saved run with the DLOGW Timetable. 2. Mentioned a couple of days ago there shouldn't really be passengers on the Main Line platforms at stations where trains are not booked to call. Crawling (!) along the Relief Lines with a Class 31 hauled stopper also revealed a number of stations where the centre platform suicide deterrent fencing is incomplete. It was possibly like that on the original and maybe when the route was surveyed was still in the process of being erected. Particularly noticed at Southall and Hayes which, sadly, were (are) fatality hotspots IRL. So it might be an idea to go back in and close the gaps...
dal#7945 Have now run the 1P41. As soon as I started it from tt mode, the screen went black and I was presented with the menu you get after a crash. Spawned on foot at Reading station at 1220, found out 1P41 was booked into platform 10, so went over there. Now I see and issue, which I have seen before. In the tt the train is booked for a 1224 departure, but in the pis screen it shows a 1226 departure time. This difference of 2 minutes maybe what is causing it to crash when loaded from the tt. I took over the train once it arrived in Reading and ran without issue to Paddington.
On PS5 I got through the Class 66 intro using the “I’m Stuck Reset Train Physics” option. The “Aggregate Supply” is impossible to get through without derailing. i thought I could at least get through it by having the slow speed set to 0.2 and make multiple passes if necessary (vs start/stop for each hopper unload) but even that derailed before the first hopper was unloaded.
Just tried it for the first time on PS5. Very good job Liam! Some notes: I was especially overjoyed to find out that the Flying Scotsman shows up on the route for me, even though Liam announced back in early 2025 that the very expensive WCMLoS route would be required for the Class 47 loco in that layer. I wrote a lengthy comment asking him to reconsider the route choice for the 47 to make the layer more accessible to players — as I now found out, he did! Thank you On that note… I actually don’t know which content unlocks which layers. Is there a big list floating around that lists all the DLC requirements for each layer? I have tons of HST variants to select from in the timetable menu. Except for the obvious new blue livery, what are the differences? There are about 4-5 HSTs which look exactly identical and have the same services. Roaming around on foot for about an hour, I haven’t seen a single mixed HST consist (green and blue wagons) yet. Is there a special requirement to make these appear on PS5? I did have a unique camera bug with the Class 484 (switched to external cam and back, suddenly had an “out of body” experience and was sitting in the secondman’s seat in the cab). Using the “change interior view feature” (camera shift + left d-pad), I was able to switch back to my original seat and regain control.
I’ve seen one on PS5. I think it’s just a rare occurrence as it has only happened the once (maybe twice but I can’t swear to that) for me after several runs and a couple of hours on foot. They are almost always uniform blue or green sets. I prefer it that way as it’s the other way on WCML over Shap. After driving for over 18,000 miles on that route, plus many hours on foot, I’ve never seen a ‘not mixed’ set of coaches behind a Class 87.
I don't know if this has been reported yet for the PC - Steam version but the DB 66 cab 2 has no illuminations on the dials when turning them on and the screen buttons don't show up, thought it might have been a mod causing the issue but it also happened with no mods installed so I think it might be a baking/TOD lighting issue. Please can this be added to the list of fixes.
