Trainz 2022 performance is still so bad

This was a route that came from 2010 and progressed through to the latest build. It just shows a view out of the window travel past Bristol Temple Meads.

Processor Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz 3.60 GHz
Installed RAM 32.0 GB
System type 64-bit operating system, x64-based processor
 
Finally after months of waiting the update for trainz 2022 (SP4) has been released to fix many of the bugs and other stuff that the previous update brought.
but the thing that has me confused is how there hasn't been a big push to fix the performance of trainz 2022.

in the videos below i will be using trainz 22 and trainz 19 to show the difference in performance using the same map, session and graphic settings. Also each session has around 20 AI trains running around doing simple task that i assigned them too.


Trainz 22 (using high graphic settings) can barely pass 60 fps and most of the time the fps is in the mid 40s. the biggest sin of it all is slow rendering of objects such as tracks and trees that require you to pause the game for everything to render in.




Trainz 19 (using high graphic settings) can achieve over 150 Fps and 200 Fps in certain cases. trainz 19 also renders everything way much faster when your moving around or switching locomotives.


Trainz 22 (44fps)


Trainz 19 (199 Fps)



graphical Settings that i used for both Trainz 22 and trainz 19 and my pc specs are 5600x 32 GB ram paired with a RTX 4070. the optimization for trainz truly suck.
One suggestion, see if you can increase your computer RAM from 34 to 64 Gig, just did mine n it help Trainz
 
@JCitron

It’s the same route, same settings, same assets (good and bad), same computer but different programs. In other words, as fair a test as could be done. How can the performance difference not be attributed to the program? Users should reasonably expect the same or better performance from a newer program, not worse.
But it is a combination of software and content. Each version of the program is optimised differently so it is quite possible the same content on two different versions of the program will perform differently.

Cheerio John
 
One suggestion, see if you can increase your computer RAM from 34 to 64 Gig, just did mine n it help Trainz
Thank you for the suggestion but i really doubt that would help since trainz 22 or 19 doesn't even come close to using 32gb of ram on my system. If this was microsoft flight simulator or dcs sure that 64 gb would do wonders but 32gb of ram is more than enough for trainz. since the beginning of August i have completely removed Trainz 22 from my system because of the performance issues it has been giving me and switched over to train simulator classic instead. It runs in 4k high settings with a smoove 60fps with no issues. The thing that is burning me is the amount of money i dropped in the trainz series but the issues is not worth the headache. I will download TRainz 22 once more and give it one more chance but deep down i already know what kind of performance i will get. In my personal opinion i feel like if the Performance Statistics actually did its job properly and showed what's really impacting performance it would make it way much easier to find the worst offender. Who knows, it could be bad script or asset with a high poly count or something else.
 
Thank you for the suggestion but i really doubt that would help since trainz 22 or 19 doesn't even come close to using 32gb of ram on my system. If this was microsoft flight simulator or dcs sure that 64 gb would do wonders but 32gb of ram is more than enough for trainz. since the beginning of August i have completely removed Trainz 22 from my system because of the performance issues it has been giving me and switched over to train simulator classic instead. It runs in 4k high settings with a smoove 60fps with no issues. The thing that is burning me is the amount of money i dropped in the trainz series but the issues is not worth the headache. I will download TRainz 22 once more and give it one more chance but deep down i already know what kind of performance i will get. In my personal opinion i feel like if the Performance Statistics actually did its job properly and showed what's really impacting performance it would make it way much easier to find the worst offender. Who knows, it could be bad script or asset with a high poly count or something else.

Understood, I have had many issues with Software in general, if this TRS22 doesn't perform to your expectations, then you do what is needed to resolve the situation.

Thank you for the additional information, this one reason I still keeping my TRS19 PE version loaded.

For my purposes I have Routes that work better in one over the other Trainz version.
 
But it is a combination of software and content. Each version of the program is optimised differently so it is quite possible the same content on two different versions of the program will perform differently.

Cheerio John
So it would seem that it’s best to stick with 19 in that case, it’s cheaper and performs better.
 
But it is a combination of software and content. Each version of the program is optimised differently so it is quite possible the same content on two different versions of the program will perform differently.

Cheerio John

I don't disagree with any of that, but when two different programs using the same content perform differently, it means the performance or "optimisation" of one is better, one is worse.

In this case, TRS 2022 is the one performing significantly worse than the previous version, TRS 2019. The opening poster, kadanstcyr, is saying this should not be happening. I agree. It is quite reasonable for us to expect improvement, certainly not reversals in performance, as new versions are developed. It's not like the relative performance was measured on just a few assets which might well respond variably depending on the program, it sampled the same large group of assets on the same route. Sometimes complaints are justified and can be instrumental in driving improvements.
 
Last edited:
One of the differences between TRS19 and TRS22 is the performance settings. In TRS19, the shader settings are the same as they were in T:ANE. In TRS22 and its relations including PLUS, they are different with Basic, for example being what Standard is in TRS19. This alone can cause the program to perform poorly for some people because now the settings are higher.

Another difference is scripting. While things worked okay in TRS19, TRS22 has stricter controls on scripting causing some, or as I should say many, to fail outright or to kind a sort a maybe work. Poorly written scripts can cause awful performance issues. This is caused by scripts hogging resources and not allowing other parts of the program to operate, causing performance issues as these blocked scripts keep retrying and trying, and trying until they timeout. This is the reason why the timeout was put in place in T:ANE and up, but the timeouts still occur.

This is something I discovered back in the early days of T:ANE with the Consist Handler Rule we used to use in TS12 for Quick Drive and for placing consists while in Driver. While that loaded in T:ANE, it would cause T:ANE to run worse than it normally did. Once that was removed from circulation as one of the base-loading rules, the performance improved. Today, that rule is considered obsolete and will be marked with a red X next to it if it's referenced in an older route imported into TRS19 or TRS22 and relations.

We also have lots of heavier content than we used before. Heck, we love those high-resolution graphics and all the extra bits but when it comes to pushing pixels around, we need a super computer to do so. Even with my RTX3080, I still limit V-Sync to 30 fps. With Trainz, due to all the content constantly loading, I found that I've never seen anything higher than that and it isn't worth the strain on my expensive video card while trying to squeeze the pixels through at a faster rate and still end up with a headache due to stutters. Speaking of graphics, turn off G-Sync, and whatever it's called for AMD cards. It was mentioned a while ago that Trainz doesn't like it and will perform poorly. Overall, many programs don't like it. Besides, this technology will cause micro-stutters. I mentioned this in another thread. Micro-stuttering will cause awful headaches, at least it does for me.
 
Regardless of how the bad performance occurs, a user should not need to know all the inner workings or the history. It’s on the Company to factor in everything, learning from past faults, cater for the changes they have insisted on and make their program perform better with each edition. Simple fact here is that the older program works better than the new one.
 
I have outdated hardware (i5 6600, GTX 1060 6GB) and I'm probably just lucky. I use V-Sync to 30 FPS, compared dozens of routes, TS19 and TS22 performance is about the same, in some routes TS22 is even better.
On TS19, a couple of routes did not work at all due to signaling errors - NSW Donnybrook Branch and Mojave Sub Division TS12. On TS22, these two routes work without errors and problems.

I became seriously interested in playing Trainz at the beginning of this year, but I tried to play every new version of Trainz about 15 years ago,
and each new Trainz version for 60FPS and max. graphic settings required hardware that would be released 5 years after the release of this game.
 
Last edited:
Regardless of how the bad performance occurs, a user should not need to know all the inner workings or the history. It’s on the Company to factor in everything, learning from past faults, cater for the changes they have insisted on and make their program perform better with each edition. Simple fact here is that the older program works better than the new one.
They do if you are using them on newer hardware. TRS19 performs the same or a bit worse on same hardware today. TS12 was always a crap performer but it performs a bit better, TS10 and TRS2009 are better performers than TS12, but are very limited.
 
Back
Top