I have been trying to play the MBTA #915 service to Stoughton there is always a crash between 2.6 and 2.4 mi from Route 128. I tried it 4 times now. I have always started it from the journey mode
Same here - on PC Steam version. Same location, repeated 3 times. Sent a support ticket, will try a run the other way.
I crashed 300 yards from last station, same service. And it is the first after tutorial in Journey :lol:
I tried now many ways passing thru that point: I tried to start the service from the timetable and not the journey, I tried playing as the passanger it never worked now I made around 15 tries and I always had a crash around that same point (between 2.4 and 2.6 mi before Route 128 going from Boston towards Route 128)
I deleted the whole thing in the end including the core files by chucking the whole Train sim world 2 folder from steamapps into the recycle bin, and let Steam reinstall it. It worked ok after doing this. Don't understand why the original Steam 'overwriting' process caused a problem but it did for me.
I tried it too but for me it doesn't work. If i approach Route 168 from any directions it crashes for me. I have redownloaded the whole game twice now
Same issues for me in similar location. Always around Rt 128. I have verified files multiple times in Steam, even deleted everything and re-downloaded. Still crashing more often than not and usually around (within a couple miles) Route 128 station.
Happened to me today as well, about 10 miles out from 128 from the south on #174 Providence - Boston service. Crashed me out to windows.
I have also had problems at back bay twice at the same place on the same service. Will get the service number and get it reported
At these locations I don't get crashes but freezes instead lasting no longer than a minute. I use a NVIDIA GTX 970. Could it be a memory issue and loading of scenary?
I don't think so, I have 8GB of VRAM and 16 GB RAM, that shoulde be enough on ultra setting. For me it seems that my game only crashes if the Route 128 station is being loaded or unloaded. The only way currently I can reach that station if I spawn on foot from the menu
Just had my first mid-play crash. Before I had experienced crashes only if exiting the game from the pause menu (other than that, there's been no issues). This time, I was driving the "Cold as Ice" scenario, approaching Canton Junction about 1 mile away from Boston direction, when the game threw me back to the desktop with UE4 crash report screen. No mods, no custom liveries or scenarios, No engine.ini or other tweaks. Steam file verification done few days ago after the update and purchasing the season ticket, no problems were found. I'm running the game on i7-7700, 16GB of RAM and GTX1070.
If you have no mod pak files installed and no engine ini tweaks, please PM me if you're willing to send me crash dump files via email. Thanks! Matt.
Tried the "Cold as Ice" scenario again. This time the crash happened shortly after departing Canton Junction, heading towards Stoughton on the outbound leg from Boston. I had just gotten the train up to the max allowed speed when it happened. Slightly different message on the crash log this time, though, and seems to point to Nvidia? I'm running driver version 471.68 (08/10/2021), updated via Geforce Experience. I have about 500 hrs of playing time on TSW2, and it has been very stable and trouble free until now. P.S. I could not locate the crash dump files, I would be happy to send them over in case I keep experiencing these crashes in the future.
PS5 user and experiencing the same issue. I then started the "Ice Night" scenario on HHL and it crashed in similar fashion shortly before Bad Oldesloe. Never had an issue like this before.
Everyone with an AMD graphics card (and no installed mods or engine.ini tweaks) who experiences ongoing mid-game Unreal Engine crashes while driving can try the following workaround: 1. Install or downgrade to the latest (recommended) Adrenalin driver Version 21.6.1 2. Go to the in-game Settings > Screen > and change the Window Mode from “Fullscreen” to “Window”. At least this seems to work perfectly for my system and I’ve experienced no more game-crashes since applying these changes. Edit after a few more hours: The following error messages seems to be gone for now: 1. LowLevelFatalError [File:Unknown] [Line: 198] Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - 'HUNG&apos 2. LowLevelFatalError [File:Unknown] [Line: 1241] FMallocBinned2 Attempt to realloc an unrecognized block 0000000002150000 canary == 0x96 != 0xe3 The following error messages still occur occasionally: 1. Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffffffffffff All in all, it is much better but not fixed.
In reference to my earlier post #25, I was able to successfully complete the scenario on the third attempt. Only change I made was to reduce texture quality from "Ultra" to "High" from my graphic settings. I had no issues running with "Ultra" before, but maybe GTX1070 (8GB) does not have enough memory for this particular scenario? I had another issue on this third run, though. Only one of the doors on the train would open when pressing "u" or selecting "Unlock Right" form the TAB-menu. I ran into similar issue with an Amtrak service later, so I'll make another post with more details for that.
Thanks! I will give it a try with lower settings later this day. Wasn't able to complete "Cold as Ice" until now (4th try). Either I got game-crashes or I was blocked by other locomotives or signals don't turned green. Slightly bit annoying.
You can find crash dump files here: ..\Documents\My Games\TrainSimWorld2\Saved\Crashes Each crash dump is in a folder, you should zip this folder and then send it. Please make sure to have all Mods removed before play, not use DX12 and not use any engine.ini tweaks if you really want to help.
That was the solution! Just tried it once again on "high" graphics settings and without saving, reloading, contacting the signaller and passing signals at danger and it worked perfect now. Thanks for your help!