route size

[martinvk]

I know there is an issue with saving to a CDP file but what about just opening a huge route? I'm currently watching the little twirly as Trainz22PE 128487 attempts to open a file that is 2477 MB according to Content Manager. I've been able to open much bigger routes, like 3574 Mb in the past, 2024 specifically so I know it can be done. Is there something in a route that could hinder the opening? Did something change since the the last update? It came from a DEM file so I might have to go back to generate two smaller files if I can't open it.
Well patience is the big word here. I'm past the first hurdle and the route is open but not to he point where I can actually do anything.

Is it true that the first time it is saved in Trainz22PE, the regular flat file is broken into multiple smaller files so that the next time it should open much faster?

 

[pware]

The file size reported by Content Manager is the raw uncompressed size.

Is it true that the first time it is saved in Trainz22PE, the regular flat file is broken into multiple smaller files so that the next time it should open much faster?

I have not heard that one nor have I seen any evidence for it.

 

[JCitron]

The routes and sessions are still their usual files. The small files or slices you see are used within Surveyor and Driver to help load routes and sessions faster and not anything that we can do anything with. This change arrived with T:ANE SP2 or SP3 and broke the ability to change the height of routes in TransDEM.

 

[martinvk]

So this one time conversion process would that be why the first time loading a route made for an older version of Trainz as for example one made by TransDEM, it takes so much longer than subsequent loading?

 

[oldman777]

Is it true that the first time it is saved in Trainz22PE, the regular flat file is broken into multiple smaller files so that the next time it should open much faster?

It's true. The route version is 3.3 on the left (8 files), converted to 5.0 on the right (2194 files):

 

[JCitron]

So this one time conversion process would that be why the first time loading a route made for an older version of Trainz as for example one made by TransDEM, it takes so much longer than subsequent loading?

Yes, this process will make loading older routes slow the first time around.
The route is sliced and diced so that we can jump between sections quickly and load up all the details faster. It puts less of a load on the system overall and helps the AI run smoother. That's what we were told.