I just transferred 140GB of Trainz 2010 content to TANE from my portable drive to my SSD. About half of the content showed up as faulty, modified but faulty or missing dependencies. The custom buildings, NYCTA elevated structures, NYCTA and Metro North rolling stock is faulty and does not show up in TANE. What would be the process to fix content in the TANE CMP. I remember back in Trainz 2010, there was the Content Creator Plus and config file. Do these options exist in the TANE CMP? I am really debating if I should build the Major Tri State Area Project in TANE or Trainz 2010. TANE is great but from what I have tried out so far, it is not as user friendly as Trainz 2010 and alot of the content is Metro North and NYCTA content is faulty, missing dependencies, or obsolete. Hopefully soon, I can get all the content to work. The Major Tri State Area project will resume once I can more of the content to work.
There is no CCP or equivalent yet in T:ANE. That utility proved to be extremely unstable and would crash terribly so it was left behind. That's not to say that something like that won't be available in the future.
Now regarding the errors. There are three basic types which are repairable very quickly.
1) Texture errors... The content creator referred to a .tga instead of a .texture file. You'll find this with those old art-files.
2) Missing preview meshes.
3) Wrong/missing/incorrect attachment points.
All of these errors can be fixed using a Notepad or other text editor and adding the appropriate preview.im file reference in mesh-table in the config.txt. For some texture errors, you can use PEV's Images2TGA which can create .tga files if they are missing from the assets you imported if all they have is .texture files.
There are, however, some errors which cannot be repaired due to LOD references in some assets. These will require the content-creators to update them if they ever do.
I will say that I imported nearly 170,000 assets, or 540GB) of data from my TS12 installation into T:ANE. Out of this ungodly number of assets, I had 7500 faulty ones. I was able to repair 5400 of these and I deleted the remaining ones until they are updated. These were all assets with LOD errors, and some have been updated recently and up on the DLS so I have downloaded them again.
Repairing is pretty simple. Open the assets for edit, either just the config.txt file or the whole folder. You can right mouse-button click to bring up these options on the assets. You can then use AssetX to fix a lot of the config.txt errors you'll encounter. Yes, these will show up again and again, however, I found it faster to do a manual edit.
For texture.txt errors where there is no corresponding .tga files, you use PEV's Images2TGA as I mentioned above. You can create a batch used in his help file to do this much quicker than manually opening each and every image file when there's lots of them.
You can use a standard image editor such as GIMP, Paint.net and others to repair or create texture files for those assets that have incorrectly sized images, and are missing simple ones like black.tga for example.
And finally use something like Search and Replace Master when you have multiple assets with the same error. Using this program, you can repair 100s of assets at a time that have the same text error in their config.txt files.
Once all the assets are repaired, that you opened, highlight them, and choose submit to submit them again. This is the same as commit in the previous Trainz versions. Why the terminology was changed is beyond me on this one!
I would recommend getting your assets in first and repairing those before bringing your routes. Once these are in and repaired, you can import your routes. This is actually the process I used and I am happy I did it that way because when I got my own routes in, I only had to bring over a few assets I had missed in my transfer previously.
If and when that time comes to bring in your routes, you will need to replace the Speed Trees you have in your routes with non-Speed Tree equivalents. The reason is due to a file version change on the Speed Tree engine, all older trees will not work. By replacing the trees first, you will have no errors with this, making the transfer over simple.
One more thing...
There are TS2010 assets now up on the DLS. You should be able to download these as they have been fixed to work in TS12. Instead of importing these from TS2010, where you'll have to run PEV's Images2TGA on them, try downloading them from the DLS. This will save you a lot of time on that.
If you have any problems fixing assets, let us know. We can surely help you and very quickly too.
John
