Hi everyone, As many of you know, there are ongoing issues with blurry textures and frequent crashes on certain routes—especially on consoles. I'm affected by this as well. Yesterday, I tried turning off motion blur and then ran the Frankfurt–Fulda route. To my surprise, the game ran noticeably better: almost no crashes and significantly improved performance—only the Fulda area still had some issues. I wanted to share this experience in case it helps others. Does anyone know why disabling motion blur would improve performance like this? DTG Alex[/USER] DTG Matt
Any postprocessing effect is going to have a performance impact of a smaller or greater degree. They all use some amount of additional resources. I just turn it off because it hurts my eyes.
I also turn it off, as well as the lightning effects and the (admittedly cool) spark effects, to keep the workload as low as possible. Also, minimal HUD with no unnecessary stuff in it. Nice & clean.
Read in another thread that turning Volumetric Fog off helps too, though oddly that option is under General not the Advanced Graphics.
Okay, thanks for the answer. Honestly, I can hardly see any difference – except that now I don't have to look at those blurry wheels anymore.
I hadn't even thought about that. Did you notice any changes when you turned it off? I'll give it a try.
I know that I encountered fewer crashes in GTA when I turned motion blur off, but that's just because all the other cars no longer kinda smeared together, and I could properly see them coming.
That is hard to say. Maybe it si a "felt" improvement. But I prefer a minimal aesthetic anyway and it can't hurt.
Can I confirm if you're also running with TAA enabled or not in combination with the motion blur disabling? Matt.
Just asked another xbox player to try this and they noted no difference - would appreciate any more insights from players. Matt.
I just drove the Cologne-Aachen route again, where I also experience crashes quite often. Sometimes in the middle of the route. Motion blur was disabled, and I actually didn't experience any crashes on the route until it crashed in Cologne. Blurry textures were unfortunately also present throughout. I believe that disabling motion blur had a minimal impact. It's worth investigating.
Interesting, have to see if this improves anything regarding motion blur. Regarding other things, I've also noticed that switching the display from 4K to HD also reduces, but doesn't completely eliminate, any video memory errors etc for routes like Frankfurt-Fulda.
I have tried many tricks to improve performance on Series S, but definitely forgot to consider motion blur. I will have to try this too. I have posted this elsewhere, but for anyone interested there are certain things that I have done over years of playing TSW on Series S that seem to help performance. Limit the number of Creators Club liveries you have downloaded. Crashes can occur when you approach an AI train with such a livery. Limit the total number of DLC you have downloaded. Among other things, this will reduce the amount of time it takes to start the game initially. I have found that about 21-24 routes is the highest number that works well on Series S. I try to rotate routes or delete something to stay in that range. Yes, run in HD and not 4K. Turning off volumetric fog also helps. It is also better if you don't use the map too much, and remember to zoom out before you close it (I personally think that the new map is the source of a lot of problems). Don't use any external camera, or photo mode, too much either. But the number one thing is to not drive in the rain. Rain really kills the Series S. The only crash I have had on the new SKA timetable is when I forgot to turn off dynamic weather and it started to rain at Köln. I saved often because I knew it would crash and it did. If you are trying to compete a Journey service then sometimes rain can't be avoided. In this case I recommend staying in the cab view and saving often. Good luck!
Hopefully the map consuming memory should be fixed, we found a memory leak in that. That fix should be with you now so let me know if you are still finding the map causing problems. Rain is a bit of a nightmare tbh, in order to prevent rain coming through roofs and other covered areas it basically needs to set up a new render target (think, putting a big camera in the sky looking down to see where roofs are and then using that to control where rain shows and doesnt). So if you're struggling, definitely does help if you don't use rain. Matt.
Sadly that doesn't work for Journey Mode where the weather is fixed even when the element is just taken from the timetable. Maybe down the road add an option to adjust before starting. On PC we can use God Mode to do that if the mod is installed but would be nice to have as a built in option.
The fact that it rains in Journey mode is unequivocally true, but on the other hand rain has never stopped me from (eventually) completing a Journey service. You just have to remember to save, which perhaps leads to an even better suggestion: auto save for consoles. Although, honestly, right now what I am all about is not new game features. With better optimization, which I think we all understand DTG to be working on, perhaps eventually some of these issues will be moot.
On Series X, turning motion blur off doesn't seem to have any major additional effect. So, in my opinion, I still think just switching the display from 4K to HD seems to be the best option instead of doing both.
Interesting. I'm not entirely sure if it really has an impact. I just noticed that I was experiencing more crashes in the Hanau area. When I turned off motion blur, that wasn't the case.
No worries, seems to differ strangely. Have you yet used just the HD display setting but kept motion blur on? Was wondering if you are getting the same outcome as if having motion blur turned off?
motion blur is the work of the devil anyway, it's the first thing I look for and turn off in any new game lol
Pretty much, I still remember the day of finally finding out why Need For Speed Underground was making me feel real-carsick (and turning it off there and everywhere since) and decades later I still have no idea who would ever want that or why.
it's a postprocessing effect which smears stuff based on its movement onscreen, creating a blurred trail effect. It has a few different implementations, which can vary in the degree of nausea they cause, (though I've personally yet to find a tolerable one), based on what precisely they blur and how, based on which parameters. Everything from a broadly applied filter to everything onscreen, to a per-object implementation They all have an effect I'd describe as akin to the feeling of a certain level of drunkenness, just as alcohol starts to impede your visual processing. In games of the 360/PS3 generation, which could have atrocious framerates, it was used to help hide the poor framerate, however that technique worked a LOT better on CRT displays than it does on LCDs or OLEDs. Nowadays it's sometimes used to hide the artifacting of Temporal Antialiasing (Hello TSW!) however, that's much better minimised/compensated for by playing at a high framerate, which reduces TAA ghosting with no impact on overall image quality..
