This may help those with resource issues, and RAM optimisation. Requires a little grubbing around in the registry editor and advanced system settings, seems to have helped me. Mods it may be helpful to pin this thread.
Someone with DDR 3 RAM and an AI voiceover, seems sus! This comes with far too much risk for the average user, and no qualitative data about the supposed benefits.
I watched this vid and actually there is not much wrong with it. Windows isn't the most efficient OS, actually it's eating resources for nothing. Also default Windows settings are applying to a wide range of computers, but it's not always the best setting. Lot of settings are fine for lower end hardware, but is holding back high end hardware. The actual benefits of tweaking the named settings is depending on the configuration, so for one system it could really help, for others less. The first chapter about RAM configuration (single or dual channel), actually is very important. Lot of pre-build PCs are delivered with only 1 memory module, so running in single channel. Dual channel memory configuration increase performance a lot. Even with AI voice and DDR3 ram, this vid is still useful. But be careful, before start tweaking, always make a good back-up, so you can easily revert back.
Yes good advice something I should have qualified beforehand! nevertheless it has helped my system to be better optimised and hitching ingame has been reduced significantly, and for clarity my system is running windows 10 64bit home with an RTX 3080 and 32GB 0f DDR4 RAM i9 9900k cpu Prime Z390-P mobo And several M2 SSD drives. Before those "tweaks" I'd get some real long pauses on some routes and loading times were long for the game and the routes, not now, so judge for yourselves I am only trying to help.
I'd prefer not to put players at risk, as modifying system files and behaviors comes with a big risk of screwing up your Windows installation, if you don't know what you are doing. It's also possible any improvements you are seeing are being attributed to the wrong thing. This would be the difference between a fresh and warm shader cache. If you are not starting with a fresh shader cache (i.e. reinstalling the graphics driver) for your before and after, then it won't be a fair test. If you've run the game more than once, you will have a warm shader cache, as the game is caching shaders while you play. As a result, subsequent runs will be smoother, as the game is mostly loading from cached shaders instead of compiling them on the fly. Whatever you do in between could just be a placebo, as the game will be smoother next time you play, if you don't reset the shader cache.
The whole problem with these kinds of videos is that they make a lot of claims, but in reality they make almost no difference. They make it seem like, with just a few clicks, you can turn your average PC into a super‑fast high‑end machine. I actually recommend not tinkering too much and just sticking to the basics. You can break a lot and gain very little. It’s the same with undervolting or overclocking a graphics card. There are countless videos about it, but it delivers very little improvement. In fact, TSW becomes unstable very quickly because of it.
A "warm" shader cache does indeed make the game run smoother. Additionally, there is a second well-known "Unreal Engine issue", repeated stuttering when shifting (?) the game world origin. For the sake of the argument, let's assume both issue are "non-fixable". However, a third and a fourth performance issue is increasingly visible: with more detailed routes (e. g. Frankfurt-Fulda, Pfälzische Ludwigsbahn, Frankfurt S-Bahn) performance is horrible around larger train stations, and FPS is unstable. As Kornwestheim is lacking traffic, and is reported to still suffer from performance issues, one has to assume you, i. e. DTG, know this issue, and this is your band-aid fix. However, this is not sustainable for future releases, and I like to know what will be done in the future to improve these routes, and future routes. Thank you in advance. Best, Underbird II
Low fps on routes like Stuttgart Heilbronn, Frankfurt S-Bahn and Mannheim Kaiserslautern is related to the amount of layers and not the route detail or the length of it. The amount of layers is extremely high on this routes and it will use a lot of CPU. The most people have a weaker CPU and a better GPU so thats why many people experience on pc on some areas a worse fps dropp
This makes sense. However, with most people having a weaker CPU and a better GPU, where does that leave "most people"? Limiting layers to have empty yards cannot be the solution!
Underbird II Good question… Let me give an example from my own experience, which might explain things a bit better. For about 2.5 years my older PC had the following specs: AMD Ryzen 5800X3D and an NVIDIA GeForce 4070TI Super. That’s a system with solid specs, but what I experienced in areas like Frankfurt was that my FPS went completely crazy. I would get around 60 FPS outside Hanau, but when taking the curve toward Frankfurt Main Station, my FPS dropped to around 10–15 FPS on the Kinzigtalbahn DLC. That was not fun. You could clearly see that my GPU wasn’t receiving enough data anymore because the CPU couldn’t keep up. The CPU simply wasn’t able to handle the huge amount of AI trains around Frankfurt Main Station, so the GPU ended up waiting. Recently I made a massive upgrade to an AMD Ryzen 7800X3D and an AMD Radeon 7900 XTX, and the difference is incredible. What do I see in Frankfurt now? 45 FPS instead of 15. Why? Because my system is much more balanced and stable. The GPU now receives enough information from the CPU even in heavy AI situations. The CPU no longer stalls when many AI trains are present. Most users experience exactly this issue. Often it’s because they try to save money, but in the end they end up with an unbalanced system that causes these kinds of problems. So if you want to avoid this, in my experience it’s essential to match your CPU and GPU properly. For example, pairing a 4090 with a 5800X3D makes no sense if you want to keep things balanced.
We appear to suffer, or have suffered, from the same issue then. And in some way you pointed me towards a personal solution - thank you. Once again I have a question to ask, though: What makes TSW so incredibly taxing for a CPU? Many open world games are populated by vast amount of moving objects, e. g. people. In TSW, some - static - trains make the game boarderline unplayable on common hardware. I feel there has to be some room of improvement!
The amount of different AI trains. Not the total amount but how many different AI is loading by the game. So routes with many layers are more affected.
I think that unoptimised routes like Semmering are a problem too, that route is the worst performing one in my whole collection, with those tweaks it is at least playable..... just.
