Well, iwi's now have a different structure. Mostly interested thing for me is data block, cause may be highly compressed DDS or something different image type or something else.
I hoped guys with coding experience can help us to decompress them.
In my opinion:
[00] - always 0x1D. It's not a part of iwi header. It's reming me data base, where all filenames stored somewhere and all files into archive just have something like defined value, like "the iwi is starting now"
[01-03] - the "Iwi" header
[x04] - iwi version. Now it's always 0x1B
[x05] - saved image type. Like 0x0C is DXT3 image type, 0x0D is DXT5 etc.
[x06] - unknown flag
[x07-x08] - image width
[x09-x0A] - image height
[x0B] - unknown flag
[x0C-x0F] - those bytes are common for mostly iwi's. Not sure what is that.
[x10-0x3F] - 48 bytes totally. Theoretically it's a replacement for MipMaps (4 for all Cod's, except CoD:BO (it's 8). 4 bytes for each mipmap).
[0x40 - n] - Data block
Hopes someone have ideas what is unknown bytes mean.
Thx and GL.
I hoped guys with coding experience can help us to decompress them.
In my opinion:
[00] - always 0x1D. It's not a part of iwi header. It's reming me data base, where all filenames stored somewhere and all files into archive just have something like defined value, like "the iwi is starting now"
[01-03] - the "Iwi" header
[x04] - iwi version. Now it's always 0x1B
[x05] - saved image type. Like 0x0C is DXT3 image type, 0x0D is DXT5 etc.
[x06] - unknown flag
[x07-x08] - image width
[x09-x0A] - image height
[x0B] - unknown flag
[x0C-x0F] - those bytes are common for mostly iwi's. Not sure what is that.
[x10-0x3F] - 48 bytes totally. Theoretically it's a replacement for MipMaps (4 for all Cod's, except CoD:BO (it's 8). 4 bytes for each mipmap).
[0x40 - n] - Data block
Hopes someone have ideas what is unknown bytes mean.
Thx and GL.