Yes you can fix the faults, or as I should say, many of them quite easily. Some of the texture faults are related to missing textures, incorrect format, wrong size, or miss-matched alpha and texture files.
The wrong formats include TGA files that have been compressed. You need to uncompress them using a graphics program and using a save-as and choosing uncompressed RLE. BMP files have the same situation if they are anything but 24-bit. There are cases where the files won't load no matter what, how to handle this situation is something I still need to figure out. The texture maybe corrupt and unable to load no matter what.
Missing textures are rather simple to fix. You can either delete the related texture.txt file, or in other cases, particularly if the content is in a group of like pieces, copy the missing texture to the folder that's missing the same.
Textures sometimes have to resized. They have to be the power of 2 - i.e. 32 x 32, 64 x 64, 128 x 128, 256 x 256, etc. Open up the texture files using your graphics program such as PainShop Pro, PhotoShop, Gimp, etc. Resize the file and save uncompressed. Do the same thing for any alphas that aren't of the same size.
Another problem I have found is that sometimes the textures may be reported missing, but you'll see them in the asset folder. This is a mind trick - trust me... In some assets there are shadow, art, body, and night-mesh folders. You need to make sure that the texture mentioned is not missing from these folders. I found out the hard way after spending quite a long time trying to figure out this one. Doh!
Another situation is the file is a texture_name.texture file. These need to be converted and this is done through a command-line utility by Peter V (PEV). The instructions are in the Extras folder on how to use the program.
In addition to the texture errors, you might find other related to the config files. These are usually easy to fix. The config file may contain errors such as something spelled wrong, or contain an invalid word because the creator added some extra words and the text formatted incorrectly. Open the text file in a text editor such as Notepad, Context, UUEdit, etc. Don't use Word or Works for this because these have to be straight ASCII files. Find the error, save the file, close the folder and commit. The error icon should disappear unless there are more errors than the program could list.
Anyway, this is what I've found when I imported the content into TS2009. The older programs were less sensitive to these kinds of errors and many of them are due to configuration file changes that occurred over the past versions of Trainz. What was valid for an earlier version is no longer valid in the current version.
Through the processes mentioned above, I've been able to clean up quite a bit of content on my system. For those errors that can't be solved, I've either disabled the content or deleted it from my system. I have found that Trainz loads a lot faster and runs a lot more reliably with the repaired content.
John
