Game freezes, sound is still on

This isn't related. I see these all the time and I think it's due to how TRS19 and up parse a route and session. In the olden days, a whole route and whole session were loaded into memory. This caused really bad performance due to everything being loaded at once as the program ran out of resources. Starting with a late service pack in T: ANE, routes and sessions are now carved up into smaller chunks so that they load up quicker and run better. Since the asset isn't in the scene, then this message appears. If it was an error, there would be a red X.

The freeze is something else. This usually occurs if the graphics are too heavy for the CPU and the rest of the system to handle. You may want to lower your settings and try again. If you are using regular hard drives and not an SSD, defragment your hard drives. This helps a lot.
 
This isn't related. I see these all the time and I think it's due to how TRS19 and up parse a route and session. In the olden days, a whole route and whole session were loaded into memory. This caused really bad performance due to everything being loaded at once as the program ran out of resources. Starting with a late service pack in T: ANE, routes and sessions are now carved up into smaller chunks so that they load up quicker and run better. Since the asset isn't in the scene, then this message appears. If it was an error, there would be a red X.

The freeze is something else. This usually occurs if the graphics are too heavy for the CPU and the rest of the system to handle. You may want to lower your settings and try again. If you are using regular hard drives and not an SSD, defragment your hard drives. This helps a lot.
Thank you for your answer! What I found weird is that the draw distance is now useless, like all terrain loads up at once, and yet again that causes a lot of resource consumption without it being very needed. I will try to defragment, and I know I have lots of building with high poly, but everything was perfectly fine before the TLR update.
 
Thank you for your answer! What I found weird is that the draw distance is now useless, like all terrain loads up at once, and yet again that causes a lot of resource consumption without it being very needed. I will try to defragment, and I know I have lots of building with high poly, but everything was perfectly fine before the TLR update.
There's a lot more going on with TLR, I wonder if that's adding insult to injury as well. The defrag really does help a lot though.
 
There's a lot more going on with TLR, I wonder if that's adding insult to injury as well. The defrag really does help a lot though.
I will do the defragmentation as you recommended me. May you be kind to also tell me, when I am in driver, bottom left there is the log, which constantly says "deleted". Do you have any idea what it refers to?
 
What you are seeing is the message history. Drivers doing things, the current driver passing signals, other things such as consists derailing, etc. What scripts are you running? Some will post information in the message window.
 
What you are seeing is the message history. Drivers doing things, the current driver passing signals, other things such as consists derailing, etc. What scripts are you running? Some will post information in the message window.
What I was finding weird is that every 20 seconds it was saying deleted, and i thought it could be related to a script (similar to a portal, as portals are known for freezes) that was causing my problem. I found out it was an old atls slave that was actually spawning a train. I will check tomorrow to see if this could have been the cause of the freeze.

I was roaming around the mal for a while, and there was not freeze. It seems they happen only when i drive a train, and don't seem to have anything to do with the bug of speed reaching 57mph.

I will keep you posted.
 
Keep me up-to-date on this.

Uncheck PhysX on the Launcher Trainz Setting performance panel. You'll have to restart.

In-game, located under the 3-bar menu located in the upper right is your graphics settings.

Try lowering your tree and other graphics details including your draw distance. You won't notice much of a difference here and it'll help a lot. The only time you may want to increase them is when you are in Surveyor.

There's a lot of data being pushed at you while you are driving and high-poly assets can eat up resources quickly. By lowering your draw-distance and other graphics settings this gives the GPU a chance to breath so-to-speak.
 
Back
Top