The claim that 3 requires no more computing horsepower than 2 is nonsense- I have yet to be able to complete a single service or scenario in any of the new TSW 3 routes (not counting training modules). And this is a vanilla game, no mods, no .ini tweaks (whereas under 2 I ran boatloads of both). In every case the same thing happens: at the start the game runs smooth as butter, no issues at all, but as the service progresses, stutters and hitches become more and more frequent until (frustratingly, close to the end) the almighty lockup, a hitch that never clears itself: either a game shutdown with an OOM alert, or a game freeze and a manual force-quit, or (most often) a complete computer freeze with no way out but a reboot* I don't have the zippiest of computers, but it's not chipped out of flint, it has 16 GB of RAM and 8 of VRAM - and never gave me any crashing problems or OOM warnings running TSW2. Whereas 3, at least as regards the new routes, is literally unplayable. ______________________________________________ *This is especially annoying because it turns back on all those background processes I have to quit manually before I launch TSW if I want it to run at all.
What hardware you using? Apart from the crash on exit, I've had one crash from a dodgy mod since early access.
I5 7400 3 GHz RX 580 16 GB RAM, 8 GB VRAM Same rig that ran TSW2 just fine, and which continues to run legacy TSW2 routes in TSW3 just fine (except for lower framerates)
Not the best no but it should still run the game. I don't know what settings to suggest for that setup. I've got a rtx 3070 and can have everything turned right up playing @1080. Any res above that and performance does start to suffer. What resolution and graphics settings are you using?
I am running on I5 6400 @2.7 GHz AMD RX 570 w/8 Gig Ram 16 Gig Ram Not having any issues only crashed once upon exiting the game other that than the game runs better than I expected.
Yup, I've had game freezes and manual shutdowns I had to do sometimes. This was also vanilla. Whether it is trying to select a certain timetable, train, etc.
Just to confirm, "RTX 580" is a typo for an AMD RX 580, not an Nvidia RTX something else, correct? And the GPU isn't overclocked? My thought is that a buildup of hiccups like that is a problem with the driver or settings. Are you using the newest driver version from AMD? My suggestion offhand would be to first try uninstalling the driver (thru AMD's software if possible rather than Windows) and reinstalling (again, downloaded from AMD rather than Windows Update). If you feel like it, you can have it reset your settings to defaults also. Second, if that doesn't work, try an older driver with cleared settings.
Try running lower settings and see if the problem persists. I'd imagine your cpu would be struggling. 1080 res is more taxing on the cpu than 1440 or 4k.
This is worrying. There are too many crash reports from people with capable PC rigs and gen9 consoles. There's nothing about TSW3 that should require more computing power than TSW2 as far as I can see. In fact, on the stream, it was clearly stated that ( and I paraphrase here ) if your setup runs TSW2 OK it will run TSW3. I haven't had any in-game crashes and just one " exit " crash. I-7-1700 RTX 3080 10 GB 32 GB RAM 4k. 60 fps ( capped )
Are you using any engine.ini tweaks? What I've found is that the visual presets in TSW3 are quite a bit more aggressive than TSW2 in some ways, and that means that using a tweak like r.ViewDistanceScale is WAY heavier on system resources than it was in TSW2. I have a 9900k, 32gb of RAM, and a 3080 Ti and I do use that tweak, but only at 1.5 or 1.25, along with r.StaticMeshLODDistanceScale=0.25 and foliage.LODDistanceScale=3. Obviously though it's best to just delete engine.ini and let the game recreate it and test for crashes before you add anything to it or you can never be certain what's causing the crashes. That being said, even with said tweaks to my engine.ini (plus a few other ones pertaining to shadows and ambient occlusion) I have not had a single crash in ~16 hours of gameplay so far (other than the exit crash that I get nearly every time I close the game.)
Exactly. And I'm calling them out on it, because it's not true. The exact same computer that ran TSW2 just fine (with lots of mods and .ini tweaks) can't handle TSW3.
I have also been experiencing crashes with the new TSW3 routes. Upon trying to load a scenario, either the game will crash to the desktop with a fatal error message or upon exiting the game, a fatal error or UE4 crash message appears. TSW2 runs flawlessly but there are many performance issues with running TSW3 routes. Something in the way these new TSW3 routes are developed has to taxing or bogging down the system. It will be great if the devs can elaborate more on why all these crashes occur and if there is a fix on the way. Was this tested before being released I wonder?
Ooo, don't count on that. If that's from MS or your card manufacturer, neither seems to care much in my experience. Anyway, the latest drivers from AMD directly are dated 8/22. Maybe give those a shot. https://www.amd.com/en/support/graphics/radeon-500-series/radeon-rx-500-series/radeon-rx-580
Screen Settings Screen Resolution:1920x 1080 Windows Mode: Fullscreen Graphics Preset: High Foilage: High Shadow Quality: Medium Effects Quality: High Sky Quality: High Post Process Quality: High View Distance Quality: High Texture Quality: High Max FPS: 62 Antialiasing: TAA Vsync: Off Screen Precentage: 100%
That is odd, I've got an I5 (something old) and a RX480 but 46GB (yes I know sound quirky) RAM and the only crashes I have encountered so far with TSW3 is after closing the programm. I have some high settings but play on 1080.
Performance across all systems is poor at the moment. I hope there is some updates soon to start making this enjoyable to play im very disappointed and again I keep giving cash to these people
Same problems here. Unplayable as well, I don't want to upgrade to a new GPU just yet, but I guess I'll have to. No matter if I use the medium or high preset, still crashes aplenty. Intel i7-11700K Nvidia 1660 Ti 6GB 16GB RAM 1920x1080 resolution, capped at 62 FPS and G-Sync enabled
I think performance in TSW3 is definitely a step down from TSW2. Been playing it on both my 3070 laptop and PS5, both have noticeable stuttering whereas TSW2 ran a lot smoother in general. I used to run TSW2 at 4k Ultra on my laptop, generally ran somewhere between 45-60fps in most areas, not too much stuttering depending on route. Move to TSW3, the same settings on there and my laptop runs it at 25-30fps with a lot of stutter too, nowhere near as smooth. Knock it down to 4K High preset and it’s more akin to how TSW2 ran in Ultra at 45-60fps but the regular stuttering is still there and it’s getting difficult to tolerate it. On PS5, I get roughly the same performance in fps as my laptop. Stutters are still easy to spot. They need to work heavily on smoothing out the driving experience. I can only see it getting worse as more add-on packs come out. The stutters aren’t even minor anymore, it throws your focus out of the experience after a while.
Weirdly, AMD's own software's driver-update check reports that my current version is the latest- but you're right, an update was released in August.
I think the RAM is the key: TSW uses a LOT of it, and unless you have a boatload of physical RAM that means constant pagefiling, with the associated read/write delays. Unfortunately my MB can't address more than 16GB
Delete ..saved\config folder, do not touch settings after that, then try I play with 8 GB on default with no problem other than low fps
Wow, am I a dummy! The Radeon card was a modest upgrade which coincided with the arrival of TSW3. Only now, as I pored over the performance stats, did I notice I was only showing 8 GB of memory! It seems that when swapping cards, I slightly dislodged one of the SIMMMs and took half my RAM down- and, of course, it's barely possible to run TSW on 8GB. With 16 restored, it now runs pretty much like TSW2.
Glad it turned out to be an easy fix after all. Regarding drivers, you mentioned May, and that's when the last WHQL driver was released. Everything since has been "optional" (which isn't to say "beta", which is its own thing). Anyway, is AMD's software set to only look for WHQL and ignore optional? Not necessarily a problem; just wanted to point it out in case you do want the drivers updated more often.
