Approaching Back Bay from the South is a true nightmare. It's hard for me to count all the crashes in this place. Probably the game loads all those scenery trains then. Who knows. I hope DTG will know. This is not just for my PC. I had the "pleasure" of watching YouTubers end their broadcast for the same reason, in the same place. I can really forgive bad DoStos and other shortcomings, but when the game doesn't work I get nervous. TSW 2 was a better premiere in technical terms. 4.26 and Rush Hour updates, that's a bad joke. I am omitting the epic entitled 'preservation' in this comparison. As a sweetness I would like to add - Boston Sprinter is a very good DLC (I skip technical issues).
Sorry to hear you're having issues. I approached Back Bay from the south in an MBTA train and haven't experienced any crashes, FWIW. If there is a specific scenario or service that is causing an issue let us know and we can run it ourselves and see.
This is random & applies to all services. It definitely has to do with PC memory. The phenomenon is common. Citing specific cases gets you nowhere. This is a core issue. Before '4.26', this problem was not present on the PC. It was at this point that you were informed. BR o7
Is anyone else experiencing this crash? I've driven countless times up and down the route and not had any crashes at all to be honest. I'd like to get some more data on this to help the engineers investigate it.
Not this, but there was a crash on Boston exit, random crash on approaching station, a crash 200 yards before the final station, all this in the first non tutorial service of journey (#915). And the most epic was a crash at the end of "Foundations" scenario, just after completing final objective, and it was 90 minutes long scenario . Also, crashes on exiting the game, all the time, no exception. I forced DirectX 11 usage via -DX11 and it stopped crashing on exit, will now retry Foundations...
I did not have any crashes approaching back bay, or any other station. However, since the update the game crashes EVERY time I exit to windows - with an unreal engine error dialog. It doesn't affect my gameplay at all, because, well, it happens after I'm done I've sent the report from the dialog, but I'm guessing that sends it to the developers of Unreal rather than to DTG... I'll try to fish out the crash report from the folder and send it to DTG support directly
My conclusions are as follows: 1. The F40PH-3C is a model with lower hardware requirements than the ACS-64. You can see it by the number of fps in similar situations. This mainly happens with the ACS-64. // hardware dependent? 2. Lowering the graphics settings reduces the occurrence of this phenomenon. On ultra, it happens every time. High - not, etc. // hardware dependent? 3. In most cases I am forced to restart my computer. If any message appears - it concerns video memory. 4. My configuration is 8 GB RAM and GTX 1050. 5. I am currently experimenting with a page file (8 GB > 16 GB). 32 GB solves similar problems for me, e.g. with DCS World. 6. Other games on UEngine do not cause such problems (eg Assetto Corsa Competizione). 7. I haven't tested any other demanding routes yet, but I'm about to test the HMA. 8. Some of my friends who play TSW (not all) have the same problem, in the same place, but on better configurations (PC). I understand, of course, my configuration is archaic, but this has not happened before. BR o7
A GTX 1050 is, if even close, at the lowest end of the specs. It is basically not a gaming card, more a office card. Only 2 or newer ones 3 GB of VRAM. That is simply not enough for such a game. This will cause continuous problems i believe. Especially on higher settings. Lower your settings to XBox One / PS4 (the entry level versions) standards and you might be good. On PC and high settings you need more VRAM.
You are probably right, but the previous version ran on the ultra without any problems. 20-30 fps. München Hbf < 20 fps
Remember, it is a new engine version. That may have changed things as this version in more than a year newer then the last one. UE4 is not standing still in terms of hardware requirements. On high settings you need better hardware with newer versions.
These are not fps drops but hard-reset crashes. There is something wrong with the code. PS I'm checking the HMA now. If nothing happens - Boston Sprinter. I will repeat again - my friends have a similar problem on very gaming PCs. NB services, approaching Back Bay, less than half a mile away from
Missing VRAM does not impact FPS. It just crashes a game engine. That is exactly what you experiencing.
I had the same issue i7-3700x gtx 3060ti (8Gb Vram)..I found these crashes only relate to Boston Sprinter. I (think) I solved it by deleting the whole install and starting from scratch..Is there something in the Steam update that leaves some.old files behind perhaps, and is Epic having the same problem?.
Just after writing my previous post I started a service (#174 Providence - Boston) and the game crashed smack down in the middle of it, when I was about 13 miles from route 128. I saved the dump. Indeed, not very stable it seems.
Yeah, today I had a crash approaching Providence on the Foundations scenario. Then gave it a second run and it was all fine.
It's not good to be childishly frustrated, but after two days of continuous reboots, I was out of patience. Probably more efficient configurations are more resilient. I also understand it is impossible to play new games on the calculator. However, something is wrong in my opinion (now I am calm). Let me tell you a story: in DCS World, after one of the updates, the multiplayer servers constantly crashed. It turned out that the use of taxi lights on the F-16 caused these problems. It's no malice on my part, but maybe there is something wrong with the ACS? Maybe just another tree has 8K shadows? Unfortunately, as it turns out, not all of it happens in the same place. I'll throw in a little joke. I finally made it to Boston, but the price was high. I feel indistinct I'm delighted with Boston Sprinter and want to believe it's a little technical problem with 4.26! PS I will add one more - I just made a round on HMA - Ultra, 200% screen percentage, all layers, no problems. Stable ~ 10 fps.
The area around 128 is definitely suspect. I experienced 3 crashes in a row 2.6 miles north of there while travelling from Boston, and just north of Readville going the other way.
Yes. It happens that there is such a variant. I usually wait for the GPU fan to go silent. Then I restart Windows /o\
The last few services went smoothly for me. What have I changed: Windows Page File 8 >> 16 GB (8 GB RAM) Ultra settings, 1920x1080, 100% screen percentage, but with antialiasing turned OFF I don't even want to wonder if it's a matter of luck.
Me neither. Maybe some micro stuttering but not full freezes like Redrev described. No edited engine.ini, no fresh install, with mods installed. Maxed out settings and running @ 4k. My specs; I9 9900K 32 GB RAM (3000 Mhz) RTX 2080 Windows on (M.2)SSD Steam installed on HDD TSW2 on separate (M.2)SSD.
I thought nothing would surprise me anymore. I was wrong. DTG, please fix it, because today it's a 'shame' to recommend this game to someone. https://forums.dovetailgames.com/threads/train-sim-world-of-madness-66-boston-depot.44140/ I'm so dumbfounded that I'm going to run over this service with AI in a moment - I'm so curious to see what's going to happen. o m Lord EDIT Now I see. I was unnecessarily trying to be so rational https://forums.dovetailgames.com/threads/northeast-corridor-feedback-thread.42656/page-6#post-360031
I mentioned in another thread that there are huge amounts of stutters. Has anyone thought that it might just be the new compression level on these dlcs? It makes sense if larger swap files are helping the issue - ie, it's RAM related. Maybe less than 32GB leads to issues?
I have 16GB of RAM and it seems to run fine for me. Didn't notice much stuttering and only had one crash so far - if we don't count the game "crashing" when quiting it.
I have had zero crashes, neither random nor when quitting the game, since updating. I am still using all my old .ini files, but I do not have any custom liveries installed (unsupported on DX12). And, at least from my experience, stuttering has been drastically reduced compared to the DX12 experience in 4.23. Cheers
TrainSim-Matt, there's a suggestion that having repaints causes these crashes for whatever reason. A few of us who were having big problems seem to have no crashes in game since removing them. Whether these are CSX repaints (which would probably load in the Boston route) or *any* repaints I couldn't say. Over to your DTG engineers!
I am back on ultra now. 100% screen percentage, AntiAliasing ON & Razer Cortex because I want to believe \o/ 24 GB PageFile + 8 GB RAM + 4 GB VRAM The average fps is ~30 (Razer Cortex info) The game is using a max of 4 GB of VRAM and 5 GB of RAM *. So, if there is a problem somewhere, it is with GPU or with the route itself. It's been stable since yesterday. Unfortunately, I have to dye my hair. I went gray * unofficial information from testers unrelated to DTG
If you have ANY community mod's that are not specifically stating they are built for 4.26 then you MUST uninstall them, 4.23 pak files WILL crash your game if the game touches them. Confirm talking to someone else who was getting a consistent repeatable crash that having uninstalled mods he is now stable. You will need to wait for the relevant authors to make available 4.26 versions of their work before you can use it again i'm afraid. Note: Internal livery editor creations are fine, this is just external mods downloaded as PAK files.
So I have no mods or changes to my engine.ini and up until yesterday everything was good. Then when I exited the game I got my first crash when exiting the game yesterday.
Calm down red. Rush Hour is freshly released and it is totally normal for bugs and issues to be present. I am sure they are working on fixes especially for the crashes because CTDs are always very annoying. I personally drove NEC for like 17 times now and never had a crashes, nevertheless I get UE 4 crash reports when quitting the game. CPU: i5-3470 16 GB Ram Nvidia GTX 1050 TI All settings on ultra, 4.26 mods and some ini tweaks. I also noticed that NEC has a much worse performance than older routes in terms of stuttering and freezing.
Dude, calm down and accept the facts. Stop interpreting stuff the way you want. IF you have mods installed being incompatible, it IS your fault. If not, dont feel talked to. And if Sony messed up the account storage system due to the update, well, then it is Sony's fault. DTG exactly knows that the release of Rush Hour didnt go well and there are and have been enough mistakes. But it isnt constructive to start a mob here. If you didnt do anything wrong, dont feel talked to. Release bugs and issues happen and are totally normal. Stop hate on DTG. Thank you.
I think some of this is based on misunderstanding or misinterpreting a few responses from DTG. But constantly deflecting blame? There are more posts (or statements on streams) where they’ve stood up and taken responsibility for their mistakes.
1) The PS rollout really was Sony's fault. Note that Steam and XBox went pretty smoothly. 2) A LOT of PC users did not get the memo that old mods would not work, and so left them installed. Their fault, not DTG's (remember, mods, like DX12, are not supported; i.e. "use 'em at your own risk; it isn't our problem if they screw up")
DX 12 has never been supported for the PC version of the game, neither pre-Rush Hour nor now. If you decide to use DX 12 per starting parameters, then you are not able to play if you have custom liveries because DX 12 and custom liveries are not compatible. And crashes happening for people without mods or tweaks should be reported to the customer support and the technical forums here.
If you dont have mods or ini tweaks, report the crashes to the customer support and the technical forums with a description of when and where it appeared, ideally with the configuration of your PC like CPU and GPU.
Well, if you dont have -DX12 as a starting parameter, you play the game in DX 11 because afaik the game starts natively in DX 11 so there is no point of rolling back.
There have always been graphical issues trying to use DX12, long before Rush Hour or the 4.26 Core update.
Just wanted to clarify a couple of the points of discussion. If you have DX12 on your system (most of you do) thats fine, you dont need to roll back. By default, the game will run in DX11 mode which is perfectly fine and DX12 supports that - that's the backward compatibility. There are many who are using -dx12 command line which forces TSW to initialise and use DX12 mode - *that* is what is not supported. Simply leave it doing what it does by default. For those of you with mods and not having crashes, I salute you. Fantastic. No issues there. Some people are NOT seeing issues and honestly I don't understand it There may be other factors influencing it. If you do NOT have mods installed, and you do NOT have a custom engine ini, and you're NOT using DX12 then there IS something else wrong, and you SHOULD report as much info as possible to support so we can continue to investigate. Matt.
Could the DX12 be the issue on Series X with the texture glitching in cab. Some routes it flickers blurry and returns to normal but SEHS and TGV it stays blurry where you can't even see the writing on the desk as its just blocks and on the TVM you can read it at all. On Boston Sprinter just the ATC panel fickers like crazy and you can't read it either. I watched a Colonel Failure video on the weekend and he did not have the same issue with the flicker on PC. So hopefully can be easy fixes as it is quite immersion breaking for at least the 2 routes that it doesn't just flip back. But the outside scenery is so spectacular and everything else looks fantastic. Look forward to a bug fix in the future after everyone has access to all their DLC.
I don't have any MODS and the system is running fine after the update -- DX12 never has been supported by TSW2 - so why should one expect it to suddenly not cause a problem with an update that still doesn' t support DX12. That logic I do not follow. Obviously you have an axe to grind,,, but we don't agree.
