Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
AMD Ryzen 5 5500 Six Core 4.2GHz (Socket AM4) Processor
Kingston HyperX Fury Beast RGB 32GB (2x16GB) DDR4 PC4-28800C18 3600MHz Dual Channel Kit
Asrock Radeon RX 6600 Dual 8GB GDDR6 PCI-Express Graphics Card
WD Blue SN570 1TB SSD NVME M.2 2280 PCIe Gen3 Solid State Drive (WDS100T3B0C)
Like I said, complete newbie haha
Cheers
TSW 3 ran great though, that's why I'm a bit stumped.
Possibly down to the game?
Maybe play around with the settings u should be able to get high settings running at a decent fps .
What resolution are u playing at
I have never had any stuttering in TSW4 when another train is passing from the opposite direction. Also as stated above the first time you run a route from start to finish you will get stutters as the game is building the shaders for that route. Subsequent runs on that route should be minimal.
This is a POST from DTG about the Stuttering:
Unreal Engine 4 Shader Compilation Stutter
Unfortunately, many games built on the Unreal Engine 4 suffer from shader compilation stutter including Train Sim World 4. This is most noticeable as pauses between frames, whenever something new is being rendered for the first time. This kind of stutter will occur on any PC hardware, so it cannot be eliminated with a hardware upgrade.
However, you will find that a second run of the same route will be dramatically smoother. This is because the shader is cached when it first appears. This allows the game to reuse that data, which is much faster than compiling shaders on the fly. The cache size is limited, so eventually it will be overwritten by new data. Furthermore, shaders will need to be recompiled if you update the graphics card driver or change your graphics card.
This doesn't happen on consoles because the hardware inside a console is a known quantity and the shaders can be precompiled and shipped with the game. The different combinations of hardware inside a PC is impossible to predict, so shaders have to be compiled on demand.
Thanks, I'll have to play around. Max FPS is at 62 - I think playing around with the settings, trial and error and I'll sort it.
Like others said, will have to try a few runs
Thanks, that's really insightful
But as many people have said the game is not optimized very well.
start the Game in DX12 its better.
Is there any way to increase the cache size?