Not sure how it would handle the opposite though, where your file is too small because you didn't export with mipmaps for instance.ĮDIT: Even when I set nVidia's PS plugin to use existing mipmaps, it still goes and generates extras and ruins the filesize, what a pain. Maybe it just takes the original filesize and cuts your file to fit into that size if it's too big (which would cut out the 2*2 and 1*1 mipmaps and make everything hackily ok). I don't know how Suzumiya's tool handles that though, if your filesize differs from the original. You must be able to define the number of mipmaps to generate in nVidia's tool somewhere, or hopefully what resolution to go down to. I was told by a friend of mine who was helping me a bit last night with this, who himself is a game programmer, that driver support for DXT textures below 4*4 was really buggy in the past, so it was common to stop at 4*4. Since DXT textures are compressed as blocks of 4*4 pixels by design, it makes sense not to go below a 4*4 dimension.

That would be the extra mipmaps that it generated, the 2*2 and 1*1 mipmaps, which shouldn't be there. So you have the main image at 1024*1024, mipmap1 512*512, mipmap2 256*256, mipmap3 128*128, mipmap4 64*64, mipmap5 32*32, mipmap6 16*16, mipmap7 8*8, mipmap8 4*4.Įxporting with nVidia's plugin will generate a file which is 0x20 bytes bigger than the original. Not all images have mipmaps too of course, so you need to test that first field either way.Ĭharacter textures for instance all have 8 mipmaps. Most mipmaps only go down to a dimension of 4, but they do vary so that *may* not be a perfect test. Well I guess it could do, since nVidia's PS plugin generates mipmaps all the way down to 1x1, but the game doesn't do that.

Dynasty warriors 8 pc textures