Just loaded up TSC following the update and I have to say I'm impressed. I will preface this by saying I've only tried the Portsmouth Direct Line so far, but whereas that was previously plagued my poor framerates and stutters knocking it down into the single digits, I'm now getting a far more consistent framerate. Previously, I was getting low 20's on this route as a baseline, with the stutters down into single digits quite regularly making it virtually unplayable. Now, It's more consistently in the high 20s, with the odd stutter here and there into the teens, but far less frequently. Whilst that doesn't sound great, the fact is it's a much more stable framerate as the dips are so much less frequent, to the point where the route is now actually so much better to drive. I'm looking forward to trying out other routes, but purely based on a route I previously felt was as good as unplayable on my PC, I'm really impressed with the update.
Seems the same for me as well. I've also now had a drive of part of the WCML: Euston to Birmingham which was also one of the problem routes for me in terms of performance, and just like the PDL I'm seeing a much more consistent frame-rate, which makes for a far more pleasing experience. I know reading the dev updates they couldn't do everything to the level they wanted for various reasons, but what they have done is a significant improvement.
The actual gains I'm seeing are small really in percentage terms, but what I am getting is drops which are both a lot less frequent and less severe than before, so all in all it makes for a much more consistent framerate and that is in itself a gain, at least for me.
At least you guys managed to get into the game. The update borked mine, and even after file verification, it still didn't work. oh well, back to the drawing board.......
Just seen your other thread. My suggestion would be to uninstall the game completely and delete the game directory to ensure all files are gone, then restart your PC and reinstall from Steam.
And they have fixed the heating issues for the Ryzen CPU's as well! Patch notes says: "The FPS limit now defaults to 60fps (as opposed to 30fps). This limit is now enforced during menus and pause screens in all cases (no matter what command line option is used) to reduce uncapped frame rates and excessive CPU usage whilst browsing the menus, especially with some Ryzen CPUs." They were literally cooking my 7800x3D .
I think I have noticed a problem. The BallastAudioControls.xml files that control things like rail hum etc do not appear to be working. I have tested a number of routes tonight by turning off all the sounds on a loco ( rename the loco's audio directory) which should mean that as it moves it just does a low level rumble but the loco ( and I have tried a number of locos and routes now) runs completely silently. I am almost 100% sure this was working in the previous build. An independant test would be welcome before I flag it up to DTG
Could this be somehow related to the AP Track EP (which mentions something about default trackbed sounds)? (Not checked your report yet) Let's agree on a route and a specific loco. I can test on a clean unmodded build.
I don't have the AP track stuff installed - basically just tried it on the Corris route, weardale and WLOS. Tried with several calandonia works locos and also my narrow gauge locos ( all of them ). I did wonder at first if it was something I had done - which it still could be of course - so spread the testing as wide as was practical.
Just to be sure tried the default Black 5 on the S&D default at Evercreach. Disabled all the locomotive sounds but left the "scenic environment sounds" to make sure I could hear sounds. No track noise at all even at 60+mph OK so just tried something off the wall. If I press the ESC key and then resume play the sounds load. If I shut down TSC and restart then the problem of no track sounds reappears until after I "pause" using the ESC key. Really very wierd
l have a lot of content and prior to TSC2024 it took just over five minutes to load, after the update it reduced to 4 minutes 47 seconds. The next time l played after verifying my files it took six minutes 25 seconds, the same today. I stopped playing TSC in favour of TSW which loads just within a minute, so it’s a lot quicker to play. I had hoped it would improve.
Yes, kudos where it's due, I've definitely noticed performance improvements with this latest update, so thank you guys, you've done a great job with it.
I've noticed that loading times are much quicker and a nice boost to frame rates - I have pretty much everything maxed out and am getting higher than 60fps on some routes - although how many fps does one really need for TSC? It's not like it's a high intensity game like GTA, COD etc.
I have created a ticket for the sound problem I found. I have also done further testing. It only affects the "Tingle", "Derail", and "Trackbed sounds" referenced in the TrackSoundBlueprints, the"Junction" sound which is also refernced there is not affected which is odd. I have double checked a large number of DTG and third party routes as well as rebuilding some of these files from scratch. I am pretty sure now that this a generic problem and is a result of the last update. The solution of presing the ESC key seems a pretty consistent but irritating fix.
Pretty smooth rollout for this update and I was able to continue playing as normal, no massive verification and reinstalling of mods etc which is nice. I did notice a scenario I was playing was crawling along at 20fps and in my investigations to find out why I discovered a 2GB Logmate file, it was continuously writing information about 'Script Performance' from a couple of locos in the scenario. Once I turned Logmate off the fps went back up to around 70. I always run Logmate in the background just in case and from what I understand the 'Script Performance' entry is new with this update, so I just thought I would mention it in case anyone else comes across a similar issue.
No worries, sorry for taking it off topic (but I've already said forget AP stuff in the previous post). I've deleted the messages to not clutter up this thread.
No worries - I was genuinely trying to understand if this was a pointer to root causes. I have deleted my posts as well. DTG have got back to me asking for more info and a video if possible.
Video submission sent to DTG and a personalised response back that they will be doing further investigation.
