How best to archive

Forester1

Well-known member
Being a pack rat, I tend to pad each version of Trainz until I have a TB or more of content. So with drives filling up I am thinking of putting older versions like T:ANE to rest to save space. However, I don't want to lose assets that may be unique and that I may want in newer versions. I know I need to archive "Modified" assets and probably "Third Party" assets to CDP. Are there others? Particularly are their base and built-in assets in some version that are no longer therein newer versions such that I may need to archive those? I don't know how I would pick them out though. And I am assuming any assets installed from DLS or packaged will always be available, although even that is flawed if someone should have their assets pulled from DLS....
EDIT: I guess that would be "Base" and "Built-in", changed above.
 
Last edited:
Raises hand as another pack rat!

I save all my third-party downloads to external drives. This includes all the assets found during scrounging for dependencies and payware content from Jointed Rail or others I've purchased from. I arrange my content by country and then by author. At the present time, this hoard is about 2 GBs of content out of the TBs installed.

I do regular full-backups rather than rely on incremental backups. I've said before that this is a quick and easy way to restore content because it's much easier to find what's there instead of looking through multiple backups. As time goes on, I do purge the older backups since I didn't use them and they took up space. Only once did I need to go back and that was due to a hard disk crash - knocks on wood, walls, and frozen windowpanes for good lasting luck, and will leave cookies out for the LGM tonight.

Over the years, I moved content along from version to version. Eventually, this caused a complete stuff up and crash. The old content really wasn't worth keeping any longer, including old built-in content from old versions.

While we can technically export and save some of this built-in content, the textures are not very good and worse when we've run the assets through Images2TGA. The other issue we run into is old DLC, just like older content, suffers from age just like we do. What looked so great before and worked fine in the olden days isn't quite up to the task anymore. I ran into this not long ago with the Treez Pack from N3V. I installed it because it was available and also due to having some missing dependencies in a very old route. The trees, not even old Speed Trees mind you, had lost their tree shape and were tree branches with mesh blobs where the leaves were supposed to be. If the meshes worked, the textures were broken. I reported this to N3V and they've pulled the product, although I can still download it because I did purchase it and it's in my Content Store.

I do understand your concern when it comes to dependencies. When I restored my January 2004 TRS2004 route, I had nothing missing. What's interesting is when I did that with a version saved from TRS2006, there was some weirdness due to faulty track and switch levers causing white tracks and missing levers. I ended up pulling out what I needed anyway and replaced the white track splines with real ones. In the end, I ended up seriously rebuilding it because it really was horrible!
 
Thank you for the tips, I guess it is a bit of a gamble either way. I do try to save everything I download from third-party sites, but often they have mixed KUIDs in zip files, so they are hard to track if I am looking for a missing. And I don't always install everything I download, so taking just the modifieds from a version doesn't mean I can look up any KUID, so it is a bit of a crap shoot no matter what I do I reckon.
 
I use Solway's Plain Backup and back up the local and original folders from the data build folder to a remote folder. It will only copy new files or folders. I can copy from Tane or TRS22 to the same backup folder.
 
Back
Top