I don't understand your format. Is this a symlink-structure?Ekey wrote:
Where : 0xAAAAAAAA - It's original hash, 0xBBBBBBBB - Section number
When you scan the tiger files you loop through 5492 "link-directorys".
Every link-directory contains a number of sections (howdies symlinks) - or in other words, data-offsets to the original files (the CDRM-Sections).
The CDRM-Sections are sometimes splitted in zlib-compressed data-sections, but that is irrelevant.
While looping through the link-directorys and there sections, the first appearance of the target file (mesh,dds,fsb...) is saved (filename=CDRM-Offset) in the "bigfile.00x"-folder. All other sections linked to the same offset will be skipped. So you have only one Offset-Filename per file.
So what is your 0xAAAAAAAA and 0xBBBBBBBB in this scenario and where should be the unique files stored?
Yes, there are meshes starting with different bytes (c00l's plugin support only 0x06), but there are others starting with 0x04,0x03 and a few others with no specific header (bigfile.001/0x29f99800.mesh)Ekey wrote:So the model in other format, plugin for Noesis that does not support it.
0x06 = 9555 files
0x04 =233 files
0x03 = 417 files
0x?? = 170 files
Total 10375 meshes
You think its Lara, cuz its the biggest cdrm? I don't believe Lara is a 70 MB mesh. Maybe around ~1 MB.Axsis wrote:CDRM at offset 0x6BD91800 in bigfile.002.tiger
size: 784580 bytes, uncompressed: 1154664 bytes, i'm sure there is lara model (at least one of them ) it's biggest cdrm
70 MB sounds like a complete scene-file or something else really big. The biggest meshes have a 0x03 starting-byte.
It makes no sense to guess where lara could be. We have to analyze the other mesh-formats, then we will found Lara.