07-16-2016, 10:40 PM
I cannot believe I'm saying LIVE DISASSEMBLY might be easier to understand these damn formats
I decided to just give another fresh attempt at the .nut files
*indicates extra notes
I may have found out a few things, at least...nothing super useful
offset 0x00:
6 bytes string fileID 'NUTC€\0x02'
2 bytes short(i think) archived file count *
8 bytes null
offset 0x10 16 bytes null
offset 0x20: 4 bytes int filesize #1*
INDECIPHERABLE BINARY GIBBERISH APPARENTLY*
and then the actual texture data:
[32 byte header]
4 bytes string ID 1 'eXt\0x00'
4 bytes int size offset? 00 00 00 20*
4 bytes int IDK 00 00 00 10
4 bytes null
4 byes string ID 2 'GIDX'
4 bytes int IDK2 00 00 00 10
4 bytes int IDK3 ...varies
*
1. There seems to be more occurrences of 'eXt' than the value of the archive count, perhaps they were removed from record, but not data???
2. This value consistently represents the first file ONLY, and is always at offset 0x20
3. I cannot make heads or tails of anything else in the main header, because any attempt to analyze it has thus far, FAILED
4. if it's a pointer, it's to offset 0x20, ALWAYS. but only the first archived file seems at all able to use it
but i'm also likely just totally lost and have just about everything wrong
I hate these files...HATE THEM
Not like I understand binary data, anyways
In short, I still got basically, nothing
I decided to just give another fresh attempt at the .nut files
*indicates extra notes
I may have found out a few things, at least...nothing super useful
offset 0x00:
6 bytes string fileID 'NUTC€\0x02'
2 bytes short(i think) archived file count *
8 bytes null
offset 0x10 16 bytes null
offset 0x20: 4 bytes int filesize #1*
INDECIPHERABLE BINARY GIBBERISH APPARENTLY*
and then the actual texture data:
[32 byte header]
4 bytes string ID 1 'eXt\0x00'
4 bytes int size offset? 00 00 00 20*
4 bytes int IDK 00 00 00 10
4 bytes null
4 byes string ID 2 'GIDX'
4 bytes int IDK2 00 00 00 10
4 bytes int IDK3 ...varies
*
1. There seems to be more occurrences of 'eXt' than the value of the archive count, perhaps they were removed from record, but not data???
2. This value consistently represents the first file ONLY, and is always at offset 0x20
3. I cannot make heads or tails of anything else in the main header, because any attempt to analyze it has thus far, FAILED
4. if it's a pointer, it's to offset 0x20, ALWAYS. but only the first archived file seems at all able to use it
but i'm also likely just totally lost and have just about everything wrong
I hate these files...HATE THEM
Not like I understand binary data, anyways
In short, I still got basically, nothing