Extremely large route problems

Amtrak1561

New member
so first I want to point out this route is 3.4 Gigs….which at that point I understand that it’s not going to run perfect, I’ve found that stream objects makes the route run better but can’t get AI to drive trains farther than 34 baseboards and with the route being so big ai is almost necessary to get trains across the route when I don’t have the time to, you know. Drive a train for 30+ hours lol. If anyone has any recommendations on how I could get the route to function way better it would be a big help, another problem I run into in general is that once there’s about 8+ ai trains running the game start to jitter lag extremely hard

PC specs

RTX 2070
CPU I9900k
RAM 128GB DDR4

Also would like to point out that I’m also running this all on a 2TB hard drive. Would a ssd make a giant performance difference?
 
Just out of curiosity and perhaps unrelated to your question, but you didn't give this info in the post above, which version of Trainz are you using. If it is Trainz Plus are you using HD terrain?
 
PC specs

RTX 2070
CPU I9900k
RAM 128GB DDR4

Also would like to point out that I’m also running this all on a 2TB hard drive. Would a ssd make a giant performance difference?
I found an SSD or NvME drive greatly increased performance. It improves access and draw times, especially where large routes are involved. I am building a large route in TRS22, under half the size of yours 1.2GB and it takes 35 seconds to fully load the route initially. I only run 32GB RAM and have an RTX4060 8GB with an AMD 5700X CPU.
 
Last edited:
By placing track markers for AI to follow in sequence, is ideal for larger routes
Depending if you have a gaming hard drive or just a standard hard drive

I use a 2TB Seagate Barracuda gaming hard drive, it's better than my previous hard drive which fried due to hardcore gaming as I load Trainz up every day and night
 
I see that @Amtrak1561 recently posted about water asset problems in 22. Is this on 22?

I'm not certain what the minimum graphics card is for 22, but using an RTX2070 surprises me. N3V has been transferring more routines from the cpu to the gpu card in these later versions of Trainz.

I don't have any solutions for this or the other problem.
 
Last edited:
I found an SSD or NvME drive greatly increased performance. It improves access and draw times, especially where large routes are involved. I am building a large route in TRS22, under half the size of yours 1.2GB and it takes 35 seconds to fully load the route initially. I only run 32GB RAM and have an RTX4060 8GB with an AMD 5700X CPU.
Ah thanks for the info will definitely invest into a good ssd, my route takes 10-20 minutes to load at times so this would be a great help
 
The route data-size has nothing to do with how AI are driving. Driving only 34 baseboards is indicative of missing track marks and signals more than anything else.

I say this from experience because I have a route that's well close to 190 miles long end-to-end and my AI drivers will travel most of it before they have AI issues unrelated to the route length with some of them being more likely self-inflicted errors such as sending the drivers down the wrong track or to the wrong station platform.

Spacing and the kind of signals you use are critical to the operation. Using Jointed Rail's SL-series signals as an example, I place Type 05 permissive/advance signals within my longer stretches of track to allow more than one driver to share a track block and to warn drivers of upcoming red lights. Type 04s are used when going from double track to single, and Type 06s are used from going from single to double and face towards the double track.

Use track marks to guide the AI. Drive via and Drive to appear to work better than the Navigate series now, before this was the opposite. Set up track marks before mid-way and at the end of yards to guide AI away from the yards, and use them to guide the AI in terminals where they will do the dumb AI driver things.

Set up your schedule using the Schedule Library and use the related Copy Commands from... to place the schedules in your driver command queue. This will allow you to not only assign routes quickly to drivers, but also troubleshoot driver issues. When placing the Copy Command, always use Insert from schedule, and always use a Wait... 20 seconds to allow the commands to load. Using Wait... 20 seconds when starting also allows the simulation to load up prior to the drivers starting their routes. I found from experience that this helped many, many years ago even in the early days, besides, this lets the scenery and track to load up before driving and everything looks better.

I also use spinning rust and use Seagate Iron Wolf 8-TB Enterprise quality drives. With their large cache, they are quite fast for spinning rust and by keeping them defragmented, Trainz and other programs load up quickly. I had looked at some SSDs, but they are well beyond my budget thanks to the tariffs and now the AI greed going on right now scoffing up any silicon they can get their hands on.
 
I had looked at some SSDs, but they are well beyond my budget thanks to the tariffs and now the AI greed going on right now scoffing up any silicon they can get their hands on.
...and that silicon is going to get harder to find as this senseless Middle East war continues. It seems that China, the world's number one producer of Sulfuric Acid (used in the production of silicon chips, mobile phone screens, textiles, EV batteries and 101 other things I never knew about), has "quietly" cut back its exports because its source of Sulfur comes from the Persian Gulf through those now blocked Straits of Hormuz.
 
An ssd is a must for any games anymore. Strangely A standard ssd works better for trainz over an nvme drive. I have no stutters on a standard 2.5 inch ssd. When i use an nvme i get alot of stutters at any settings. I suspect it's because the m.2 nvme just runs warmer than standard ssd drives. My m.2 idles at about 45c, but gets as warm as 70c max under heavy usage. Has anyone else noticed this? I have tried to cool mine m.2 down as much as possible. The motherboard is the only cooling and it's passive cooling. If people could use active cooling maybe the stutters wouldn't happen. I completely understand ssd's and m.2's are sky high right now in price. But even just a standard 1tb dedicated ssd would be ok for trainz. I was kinda lucky and have a 2tb standard ssd, And 3 nvme ssd's 2 2tb nvme's and 1 4tb nvme. I hope the prices go down by the end of the year, Or i don't think people will be upgrading.
 
An ssd is a must for any games anymore. Strangely A standard ssd works better for trainz over an nvme drive. I have no stutters on a standard 2.5 inch ssd. When i use an nvme i get alot of stutters at any settings. I suspect it's because the m.2 nvme just runs warmer than standard ssd drives. My m.2 idles at about 45c, but gets as warm as 70c max under heavy usage. Has anyone else noticed this? I have tried to cool mine m.2 down as much as possible. The motherboard is the only cooling and it's passive cooling. If people could use active cooling maybe the stutters wouldn't happen. I completely understand ssd's and m.2's are sky high right now in price. But even just a standard 1tb dedicated ssd would be ok for trainz. I was kinda lucky and have a 2tb standard ssd, And 3 nvme ssd's 2 2tb nvme's and 1 4tb nvme. I hope the prices go down by the end of the year, Or i don't think people will be upgrading.
I would definitely be concerned with your system being toasty. This can have a detrimental effect on all your components and will eventually cause them to fail. See if you can cool your system somehow by using additional fans or changing the direction that they are facing. Sometimes, well it seems to be a lot of time, case fans face the wrong way or are blocked behind panels, causing hot air to become trapped instead of being sent out of the case.

SSDs run hot, but that's way too warm. SSDs use electricity to alter the internal substrates on the silicon. In the old days, EEROMs and EPROMs worked the same way and used +24 to write and read back at +5. A engineering genius figured out a way to make this faster and now we have flash memory, thumb drives, and SSDs. The voltage change is the same with SSDs due to the changing structure inside and this is what causes the heat on an SSD.

While Trainz is faster loading, due to the very quick read cycle being in the nanoseconds compared to the milliseconds for older technology, it writes constantly to the device. The voltage phase change, used to write the data to the device, wears out the cells where the data is stored. Constant writing will wear down the device faster and require earlier replacement. This is why defragmenting an SSD is so bad and the built-in Windows defragmenter has this operation disabled for SSDs and only TRIMs them.
 
I have Trainz on a platter drive and a GTX 3gb card on the 6 year old computer that Trainz is on. I do have a second computer that's a few years old with an RTX 2070 Super card and an SSD and platter drive with Win 10 for this amusement park sim sequel that requires a beefier computer and Win 10 minimum. Is it possible to minimize slowdown and stuttering on very large DEM routes by upgrading computer components and minimizing the amount of software running at the same time including software running in the background?
 
Last edited by a moderator:
Is it possible to minimize slowdown and stuttering on very large DEM routes
You didn't state which version of Trainz you have. If it is Trainz Plus then was the DEM route created using HD terrain? Very large routes can struggle using HD, particularly with going over the size limit.
 
Update, I spent a pretty penny and upgraded to a RTX 4080, A i71300kf and 32gb of ddr5 ram as well as putting my build folder on a Samsung 990 evo ssd. The game looks way better and runs amazing, however the route still starts to become hazy and lags when a certain amount of consist are active on the route so I’m just going to assume no escaping that problem
 
however the route still starts to become hazy and lags when a certain amount of consist are active on the route
If you’re referring to a session being run, this could be down to poor scripting in driver rules that you’re using (as I found out). Feel free to list them here
 
It could also be one or more bad assets making up the consist, but it would take a lot of testing to find one or more assts that may cause it.
 
Back
Top