Importing Assets.tdx
- Thread starter mkerd261
- Start date
Assets.tdx needs to be a genuine database of all the assets you have installed in TRS or TC. If you simply copy across the Assets file from TRS into TC, it won't include all the new assets in the TC installation and so won't be a complete database.
Once you've moved across the Local folder from TRS, there's no alternative, I think, to rebuilding Assets.tdx in the new installation.
Paul
Once you've moved across the Local folder from TRS, there's no alternative, I think, to rebuilding Assets.tdx in the new installation.
Paul
Unfortunately, rebuilding assets.tdx loses any renaming you've done in CMP. I've been thinking of putting together a program to go through the \local folder and change the actual asset names within the config.txt file for each asset (after saving a copy of the entire \local folder, of course!), so that if assets.tdx rebuilds it'll do so with the proper names. Some of the potential downsides:
1) It'll probably take forever to run with a large collection of assets;
2) Any new renamed assets will need to be manually corrected in order to keep names up to date.
Can anyone think of any other potential problems with this? Has anyone already done anything like this?
--Lamont
1) It'll probably take forever to run with a large collection of assets;
2) Any new renamed assets will need to be manually corrected in order to keep names up to date.
Can anyone think of any other potential problems with this? Has anyone already done anything like this?
--Lamont
Are we talking about the same config files (config.txt)? I've gone in and edited these many times to fix problems or just find information. They're plain text as far as I can tell.
--Lamont
Yes we are. If you open them with CMP or CCP they are decoded and encoded again when you commit the assets. If you look directly in the local folder you'll see config.chump files, not config.txt files.
Paul
Hmmm... That definitely adds a layer of complexity. Fortunately the .chump files look relatively easy to decode, as does the assets.tdx file. Will make for an interesting project when time permits.
It's too bad that Auran didn't build the simple functionality into CMP to actually rename the asset internally when renaming. With thousands of assets carefully re-named in order to make them findable (and I know I'm not alone on this), trying to re-import them into a later version of Trainz and then rename them all over again is a major disincentive to upgrading.
--Lamont
I too have fallen into this trap in the past. An alternative approach is to use keywords and sort assets accordingly. SP1 in TRS06 usefully introduced a function to back-up and reintroduce keywords. However, these functions appear to be disabled in TC3 - we don't know why! 