Thu May 15, 2003 8:13 pm by dutch63
giskard,
Well, looking at the starfury model, it looks like another problem rises it's head.
The tga textures used in it, aren't a size that are to the power of 2.
i.e 128x128 or 512x1024.
I'll try to resize them, and see if it might help.
As long as one uses nodes named MIP0 and tga files in the .mat files for textures, there appearently aren't a problem (except the textures still need to be a size that is ^2. Thats why the viper and the cylon doesn't have any problems.
if one uses nodes named MIPS for the textures, then it need to be dds files, with mip maps generated, otherwise there will be untextured ships on lower end PC's or when one has set the detail level in the game to low.
At least thats what the current investigation seem to indicate.
I'll experiment a bit further, and see what I find..
As for the size of the .mat file, I generated a dds file with mipmaps for two of the three textures used on the X-wing (the third texture already had mipmaps...), and imported them in the fcxwing.mat file. The original size was 141 Kb, and the new size was 368 kb.
When zipping up the original X-wing files the resulting zip was 165 kb, when zipping up the X-wing files with the new fcxwing.mat file instead, the resulting zip file was 201 kb. So the filesize increase is a minor thing IMHO.. but ofcourse YMMV depending on the number of textures used.
B. Regards
Dutch63(on the Boomtown #1 server)