as to that yugix, it can be done with action replay codes...
Not a complaint, but an observation, I think I don't have the pak format quite right as the other pak's seem to have a slightly different structure than the nftr pak. I seem to need to remove five bytes from pretty much every file that gets unpacked by normmatt's pak manager. which not his fault that is actually where the pointers are pointing and also the file size seems to be off too... if you look, the nftr had the same size for both columns. Well all the other pak's for files seem to have different sizes and or meaning for the second column. It makes me wonder if there is compression involved. as I cannot seem to make the nclr, ncgr, nscr come out right. what is also bugging me is the normal flag for compression does not seem to be present either. So I am testing with a nclr as you cannot really screw those up too much. I hoping to figure out the type of comression (or if there actually is) soon. as the only reason I can think of for two different values would be for that...
strangely reminds me of the compression in duel love. sigh....
Oh, that's right. I don't know a thing about AR but I think it can be done.
suaqua said:
so to make things clear will there be a beta release when the digivolution data is finished? or will it be after the quests are done as well?
I don't know yet, as I think that not knowing the quest will be harded. So, I think I will need to do it after quests
Normmatt said:
QUOTE(rastsan @ Jul 2 2011, 07:43 AM)
as to that yugix, it can be done with action replay codes...
Not a complaint, but an observation, I think I don't have the pak format quite right as the other pak's seem to have a slightly different structure than the nftr pak. I seem to need to remove five bytes from pretty much every file that gets unpacked by normmatt's pak manager. which not his fault that is actually where the pointers are pointing and also the file size seems to be off too... if you look, the nftr had the same size for both columns. Well all the other pak's for files seem to have different sizes and or meaning for the second column. It makes me wonder if there is compression involved. as I cannot seem to make the nclr, ncgr, nscr come out right. what is also bugging me is the normal flag for compression does not seem to be present either. So I am testing with a nclr as you cannot really screw those up too much. I hoping to figure out the type of comression (or if there actually is) soon. as the only reason I can think of for two different values would be for that...
strangely reminds me of the compression in duel love. sigh....
Looks like the first size is really some sort of memory allocation size rather than a file size, second is file size and third is a flag to say if it should be loaded directly to the address or loaded to some temporary buffer. That temp buffer looks like its being decompressed by the function at 0208A8E0. I need to spend some time working how exactly what that function is doing and recreate it in C#