Size of CDP Files to transfer from TRS19 to TRS 22

davoss

Member
It would be nice to know the size of a CDP file BEFORE it is created. My computer can handle up to a 2GB CDP file when transferring. However, when I select the number of files to include in a CDP file, there is no way for me to determine the size of the file before it is created.
It would be nice if the total size of the files selected for a CDP file be displayed at the bottom edge of the Content Manager list along with the number of files selected. I could then adjust the number of files selected to make sure I stayed below the 2GB limit.
OR - maybe there is a different way for me to determine this number without creating the CDP file first.

Didrik
 
Easier method, in TRS19 open for edit everything apart from packaged, builtin, payware and base you want to transfer.
Then go to TRS22 File > Import Content Folder and select your TRS19 Editing Folder. If and there probably will be anything now showing in open for edit that will be because the items are now builtins in TRS22, just select them all and revert to original.

Alternatively if you are just importing your TR19 user data just copy the TRS19 userdata folder and point TRS22 at that.

You could of course get the file sizes from Manage Content, you have got file size selected on the header? or open them all for edit and get the total unarchived value from the editing folder open for edit however a cdp is an archive of those files so won't have a value until they have been archived, should be less than the open for edit size though, not by much though from observation!
 
Thank you. Good information.

Another question. If I have a Session, in which I added one locomotive, I assume there will only be two dependencies for the Session - the Route and the locomotive. This appears to not be true. The Session dependencies are the same as the Route except for the one locomotive I added; therefore no reason to duplicate this information. This seems to be a rather inefficient and wasteful method of handling data. I realized this when I was working on transferring a Session from TRS19 to TRS22. I am also sharing my files with others that are helping me create the Route and Session, so creating CDPs is the approach I am taking.

Didrik
 
That doesn't sound right a session should only list items used specifically in the session, that includes Rules, Drivers, Driver Commands, Locos, Consists, commodities and the Route asset. If it's listing stuff that is already in the Route it sounds like at some point the Route was merged with the Session easily done since the Unified Driver Surveyor appeared, I avoid editing the session from driver, avoids things ending up on the wrong layers. Simple Example is say adding a Tree in editing the session from driver will put the Tree on the session layer unless you look at it's properties and change to the route layer before saving. It would help if there was an indication as to what layer you are editing rather than having to have to check in the layers tab.

If all the assets used are on the DLS? from the sound of it they might not be all you need to transfer is the Session cdp and the Route cdp, the rest can be downloaded from the DLS, effectively that is everything that has an upload date in Manage Content that isn't builtin Packaged Payware or Base, Package and payware must be downloaded again from the Content Store to ensure it's compatible with the version of Trainz being used.
Stuff not on the DLS but from third party sites will normally show as locally modified and not have an upload date. In which case if transferring to another user all you need is the Route and session cdps and a cdp just containing the non DLS items.

Third party is another option that can be stuff that hasn't fully gone through the DLS process or assets that have failed the DLS validations and is on the Faulty asset list and require repairing by the Content Repair Group, often they still work perfectly well and ended up on the list because of out of date config, config typos or the dependencies hadn't been uploaded first, thus fails the validation due to missing assets, Routes seem to be exempt from this problem though at the moment. I'm the Content Repair Group Co-ordinator by the way. Unknown assets are also often on the repair list and right click download this version will often but not always find them and download as third party.
 
I agree but for a different reason. I found put thw hard way that CM will make useless corrupt CDPs when doing a mass export. As in I *thought* I had all my stuff backed up before doing a reinstall long ago, only to discover the CDP was no good.

Since then I have a process where I highlight what I want to export, hit ctrl C, paste into a spreadsheet and then copy another column which is filled with commands and paste that into a text file.

I save that file as a .bat and run it.

It uses trainzutil commands to make individual CDPs for each item.

Why this isn't available as a right click option in Content Manager (Export as individual CDPs) I'll never know....

https://docs.google.com/spreadsheets/d/1Ur8jjwi8uZClIoD-9vgzp-w-2lQ-McwzV2yM4dvU0bI/edit?usp=sharing
 
Last edited:
Yep. The tool is broken in that regard. It has been that way for so long that I occasionally forget and rediscover the problem months or years later when I try to migrated a big route between machines without a full re-download.

N3V don't appear too worried about fixing this since they'd as soon keep selling first class tickets and subscriptions :confused:
 
Frogpipe, I am wondering if you could have used CDPExplorer to break down the CDP files that CM did not like? I am curious because I have some fairly large, exported CDP files, but CDPExplorer at least seems to handle them OK.
 
No, they crash CDPExporer. You get a partial listing of the contents and can't export any of it.

They are (or were) gigabytes in size.
 
CDP explorer is now incompatible with TRS22 upwards presumably due to the change in the file formats / sizes.
 
Back
Top