Coding Request For Daxar

First of, thanks a bunch! This is really awesome of you.

However, I haven't really been able to test it yet. First, I got a missing DLL error "libgcc_s_dw2-1.dll", then after I got that there was also one for "libstdc++-6.dll". Once I had both of those, it simply said "The application was unable to start correctly (0xc000007b)."

Any ideas? If it matters at all, my OS is a 64-bit version of Windows 8 Pro.

Ah fantastic; they all work! Of course, I don't have a proper test to use, but compressing and decompressing as with your example works. I also used it on the data I initially wanted to decompress, and checking out the bytes it looks like a valid result.

So should I use #2 or #3 from now on? #1 is a bit of a hassle with the DLLs. Or will you make a sort of "final" version?

OK, so apparently the data I want to decompress is actually compressed in multiple chunks. A set of chunks is preceded by a ZLFW header, and each chunk then has the usual WFLZ header. Here's some code I've been given that should be able to decompress these chunks:

const u32 decompressedSize = wfLZ_GetDecompressedSize( ptrToZFLWHeader );
u8* dst = ( u8* )malloc( decompressedSize );
u32 offset = 0;
while( uint8_t* compressedBlock = wfLZ_ChunkDecompressLoop( info.src, &chunk ) )
{
wfLZ_Decompress( compressedBlock, dst + offset );
const u32 blockSize = wfLZ_GetDecompressedSize( compressedBlock );
offset += blockSize;
}


Where "dst" holds the output data. I assume this is for when you're decompressing from within the actual file, hence the "ptrToZFLWHeader". In your program I think you'd just replace that with "vData.data()".

Sorry, this is getting a bit complex. I really should learn C/++ myself sometime so that I can do these things on my own.

I asked the person who gave me the snippet what "chunk" should be, so I'll say once I get an answer. If you want I could give you the file I'm trying to decompress, but I'm not actually sure what kind of result to expect.

EDIT: So apparently it should be defined as such:

u32* chunk = NULL;

Here's what they said about it, if it helps at all:

You never use it directly, it's basically a state variable that the decompressor uses internally, and you just need to make sure it gets passed to the next call to wfLZ_ChunkDecompressLoop(), so it can iterate through the chunks properly.

Oh my goodness, thanks!!! This is totally awesome! I'll have to find out where the alpha images are stored (I don't own the game myself so I'll have to ask for some ANBs) but this is fantastic! You certainly deserve that sleep : )

There are, however, a couple of things. Firstly, it seems that Scrooge is the only one that comes in one piece; all other characters (that I know of) are made up of weird chunks like this. Did he explain the ANB format? Even if it doesn't contain any info on organising the chunks, I'd be interested in checking it out.

Secondly, what I would prefer is to have the program decompress input into the output, as it did initially. That way I can make a program to take the ANBs, decompress the data with your program and convert it to textures (or have your program produce PNGs to output if you prefer), then merge alpha, organise (if possible), and kind of show in a GUI. That way it'll be simpler for people to use, and they won't have to merge the alpha and organise chunks themselves - this is one of the reasons I looked into the format, since you could already get the textures via RAM dumps but had to arrange everything by hand.

Also yeah, since it's in the Requests forum, new members can't post right away, to prevent people joining purely to request stuff. To be honest someone should actually move that (or make a new thread), since it started out as a request but has now turned into more of a project.

Anyway, once again a huge THANK YOU and hope you sleep well! Looking forward to making more progress : D

You are brilliant, this is really more than I expected. I do kind of wish I could've done more, it looks so interesting. Looking at your source code it looks like you've got most of the ANB format sorted.

What I was actually expecting was something that wrote each image's data to stdout, so that I could pipe it through a wrapper and manage the textures through that. To be honest, I'd still like something like this, just so that I can make it a tad more user-friendly. At this point you've done most of the work though, so just an option to choose the output directory would be enough. Ideally I'd have a full-blown explorer that can add and remove stuff from ANBs, but at this point simply getting the images is what matters. I dunno, I just feel like I haven't done enough work myself.

Anyway, as you said you're busy, and actually I am too. There's no hurry with any further work on this, what you've done is more than enough already. Once we both have more free time though I would really like to make some sort of GUI though, just to help in some way.