I once started with TSW2 and today I enjoy running TSW5 on my nearly 6 years old computer (only graphic cards updated through the years) with fine framerates. But now that I feel that TSW5 runs smoother than previous versions, there are still two immersion killers that finally should be eliminate in this modern version of TSW. I mean the moment when the train comes to a stop and there's a jingle sound from the game itself so that you know you can open the doors. The same happens when you close the doors and it's time to depart. Jingle again. Not the jingle itself is the problem but at these moments the game freezes, people that rush towards your train and incoming trains on the other platform freeze. I look outside and think: What is that ? The Matrix ? Or is the program busy searching for the jingle file on my ultrafast SSD ? Or should someone remove the PAUSE command from that jingle routine ? And another feature kills my immersion totally: Yesterday I ran the Gatwick express and in the middle of the run at 90 mph -"BAAAAMMM"- TSW5 smashed a big sign in the middle of the screen while driving, congratulating me for driving 317 miles or so on this route. While the sign was on the screen for several seconds, I could not see signals or speed limit signs. Wouldn't it be better to be able to either switch off such a feature in the Settings menu ? (Or did I miss something and this option alread exists ?) Or congratulate me at the end of the run ? Or at least place that sign somewhere else on the border of the screen, so that it doesn't obscure the railway path... As I said in the headline: PLEASE ! Remove these immersion killers ! You would make an old man very happy.
First point is down to your hardware verses your settings, hardly anything DTG can do about that. Second point I completely agree with, I missed a PZB because of one the other day.
On my pc, and i also noticed in the stream, most task completions with this sounds let the game freeze for 1-2 seconds which is very annoying. So is the freeze coming from the sound or the dispatcher?
The freeze when coming to a stop is the auto save making a checkpoint I believe. You can turn off the save feature I believe, then it should not be doing that.
I know it's just a minor niggle but I find that irritating too. A bit of subtlety would be welcome with that huge notification banner being like simulating a double duvet flying on to the driver's windscreen of a speeding train. Seems overall performance on TSW5 has improved on PCs but not so much on PlayStation 5. Strangely, I found that the Victoria Gatwick Brighton route does seem improved from the TSW4 version but that improvement is lacking on some other routes.
this has been discussed in another thread. as said above, on a completed task, the game autosaves. this can be turned off with a command line for your engine.ini, posted in said other thread
I found the article where the deactivation of the Autosave is described: https://forums.dovetailgames.com/threads/microstutters.84609/#post-896477 I edited my Engine.ini, and .... no more pause ! Thanks to Myron and Dinosbacsi for pushing me in the right direction. You made an old man very happy, now it's DTG's turn ! You know, throwing duvets on the windscreen...
Well, not really. I have a fairly decent PC setup and I don't have crashes or stuttering, actually no performance issues, and I play at ultra all the way at 4k with fps self- limited to 60. I don't think I'm unique in that respect. My beefs with TSW lie elsewhere, mostly with content/quality.
I think you can turn down or even off the objective prompt sound if it kills your immersion. Disabling save game not really recommended if you need to use it. There is no auto save per se anyway, some scenarios will mark a checkpoint from which you can resume.
TSW runs a a very smooth 48fps on my laptop. I don't like making the laptop too hot, because I don't know how hot is too hot. I haven't encountered the stuttering issue yet.
Probably because you get at some point used to trash. The very fact that it stutters in DTGs own livestreams and trailers says a lot..
It's the sort of thing you'd notice regardless of whether or not you're used to it. Stuttering is hard to miss when the game freezes for a few seconds. I may be used to it, but I don't ignore it. I just don't see the point in saying something about it.
Yes... Of course, I could run Cyberpunk at Ultra on my Rx480 if I capped the FPS at 10 as well... OMSI also stuttered when autosaving, or loading tiles. Both are very immersive, one needs a lot of patience.
I don't. Then I come back from playing beautiful, AAA games at triple FPS digits with a flat framerate graph (without having to tinker settings, start perimeters and .ini files for hours) and remember why I stopped playing this game in the first place, and why I stopped playing on console, for that matter.
I grew up playing at 10 fps, and didn't complain, 60FPS with stutters is unplayable to me, in fact Id rather play at 10 fps without stuttering.
I understand players who want to use the savegame function. For me personally its an immersion braker. I used it 1x in my entire tsw time in tsw2 because there was no freeroam, so i didnt want to loose my consist which took 3-4 hours of ductape to create in scenario planner back then
What annoys me most is that the game emits the audible signal when the doors are closed and not when the player should close the doors. The latter is far more important as with the omission of it, I need to keep looking at the HUD (I'm a no HUD guy) or count the 30 seconds in my head to know when I can close the doors or if I don't want to do either of that and just do a rough guess when it's ready, probably lost some time for my service schedule, which all is annoying. On the other side, we have an audible signal for when the doors are closed, which is just a few seconds after engaging the door closing mechanism and everybody knows that the doors should be closed after pressing said button. I can assume that its probably meant to give a "ready to depart" sign, which is not bad, but I still feel a sound to know when to close the doors would be more helpful, at least for players who like to play without HUD. By the way, it would be nice to give the player an ability to change the sound for it as well. I don't like the tone. To be honest, I have no clue why "Enough is Enough" thread is not pumped up with complaints about that. It's so annoying. I mean the notification is nice, but why it has to appear as a big banner in the middle of the screen, preventing me from observing the situation and handling the loco accordingly?
The "loading circle" should just not be a thing, it makes no sense whatsoever. God forbid you close the doors a second too early and have to open them again, everyone will literally fall out of the train
Particularly if running late, I’ve always maintained if the passenger station duties are complete, you should be able to close the doors and get going, not wait for a predefined time to elapse.
Maybe its there to assure the boarding process and animations of passenger in the train working as expected. A loose boarding mechanism would be far better. Oh yes, I know this well. Far too well.
Glossop does quite well with this, assuming you run to time there is a ~30 second dwell time, but the loading circle is only about 5 seconds or so (maybe a little longer) so you can park up at platform 2, open the doors, and given it takes about 10 seconds to close them anyway, just press the close button immediately
A problem on your end them. I'm getting consistent 50-60fps and the game runs as smooth as water in the ocean.
I disagree. I have every right to comment on a simulator game if performance problems like stuttering and poor frame rates ruin my enjoyment by breaking the immersion factor that is crucial to any simulation. I am doing DTG a favour by pointing out a basic flaw in their product that results in me not wanting to spend my money on it. If DTG don't (or can't) improve performance then I will either not buy it at all or hold out till it is almost given away with massive discounts. Turning a blind eye to something like this is not going to happen especially as I have never had these problems in any other title I own despite many being much more extensive and with higher quality graphics. Only TSW fails this badly with performance issues and it is tragic as I would love to support the franchise by buying stuff at full price but I cannot do that because in the state it is in (and has been for years) it just is not worth the asking price.
Yes, of course, issues that have been acknowledged, mentioned since the game came out and are present in their own streams and even trailers. Engine tweaks and start perimeters wouldn't even be relevant if that was the case. Now, "50-60 FPS" is not something to be proud of, and that's far from consistent if it drops from 60, not to mention the 1% lows. Not very smooth as water, however the graphics remind me of a muddy puddle, and that has yet to be improved on. But yes of course, my SYSTEMS are faulty even though they perform above systems of identical specs in benchmarks, mine and DTGs, apparently.
I don't have many routes post Glossop (beyond the core routes), is it still lengthy on UK stuff after that? Its not something I pay attention to really, I just noticed it in Glossop as I could be 5 minutes late at Hadfield leaving cos I had to go to the bog or something, yet still blaze into Pic on time ha
I see plenty folks at stations with those colours. It's the TSW version of the BR Blue era where everyone has ginger afros that does my head in.
It's interesting how those little delays can still make the time work out! The routes can be a little restricted after Glossop, but as long as you pay attention to the schedules, you should be alright.
