XeNTaX

bigfiles are archives that don't appear to contain filenames. we're not sure how they're generated from the bigfile so ekey snags the filenames from the EXE by trapping the contents of eax register from the function that generates filenames. it's really only important if you need names (i don't).

shadowmoy wrote:

Ekey wrote:Filelist updated (patch 1.0.722.3) Added 233 names.

may be a dumb question but what is this filelist for and how do i use it ?

Download this. Unpack. Copy updated filelists in bin_tr9\projects\Tomb Raider 9\files\

Found game menus (not all) and converted to SWFs
Any decompilers work fine... Example 1 , Example 2

you're a pretty silly guy c00l. i just went through all 9,985 mesh files and you know, other than the blend weights (uint08/255.0f) and blend indices (uint08), and the fact that there are two different types of UV formats (type 13 = sint16/2048 which you got and type 1 = real32 which you didn't); you were pretty friggin almost done with your noesis plugin lol. do you want to finish it? i can wait for the models lol.

each vertex buffer is prefaced with a vertex information structure (whose offset is specified in the part list).

-- 0x30-byte vertex
45 3F E1 98 E8 C9 CB 30
06 00 30 00 00 00 00 00
14 E4 F5 36 0C 00 05 00
49 61 7F 3E 10 00 03 00
01 6F A8 64 28 00 05 00
2A 90 17 83 20 00 01 00 -- texture coordinates (2A 90 17 83) vertex offset (20 00) format (01 00 = real32)
23 D8 F7 D2 00 00 02 00
C3 11 ED F1 2C 00 05 00

-- 0x34-byte vertex
AB 18 5F 71 BB 5E E1 31
08 00 34 00 00 00 00 00 - 8 entries - 34 bytes per vertex
14 E4 F5 36 14 00 05 00 - 4-byte vector
49 61 7F 3E 18 00 03 00
C0 91 E6 48 0C 00 06 00 - blend weights
D3 D8 56 51 10 00 07 00 - blend indices
01 6F A8 64 2C 00 05 00 - 4-byte vector
2A 90 17 83 28 00 13 00 -- texture coordinates (2A 90 17 83) vertex offset (28 00) format (13 00 = sint16/2048.0f)
23 D8 F7 D2 00 00 02 00 - 0x00 position
C3 11 ED F1 30 00 05 00 - 4-byte vector

howfie wrote:you're a pretty silly guy c00l. i just went through all 9,985 mesh files and you know, other than the blend weights (uint08/255.0f) and blend indices (uint08), and the fact that there are two different types of UV formats (type 13 = sint16/2048 which you got and type 1 = real32 which you didn't); you were pretty friggin almost done with your noesis plugin lol. do you want to finish it? i can wait for the models lol.

each vertex buffer is prefaced with a vertex information structure (whose offset is specified in the part list).

-- 0x30-byte vertex
45 3F E1 98 E8 C9 CB 30
06 00 30 00 00 00 00 00
14 E4 F5 36 0C 00 05 00
49 61 7F 3E 10 00 03 00
01 6F A8 64 28 00 05 00
2A 90 17 83 20 00 01 00 -- texture coordinates (2A 90 17 83) vertex offset (20 00) format (01 00 = real32)
23 D8 F7 D2 00 00 02 00
C3 11 ED F1 2C 00 05 00

-- 0x34-byte vertex
AB 18 5F 71 BB 5E E1 31
08 00 34 00 00 00 00 00 - 8 entries - 34 bytes per vertex
14 E4 F5 36 14 00 05 00 - 4-byte vector
49 61 7F 3E 18 00 03 00
C0 91 E6 48 0C 00 06 00 - blend weights
D3 D8 56 51 10 00 07 00 - blend indices
01 6F A8 64 2C 00 05 00 - 4-byte vector
2A 90 17 83 28 00 13 00 -- texture coordinates (2A 90 17 83) vertex offset (28 00) format (13 00 = sint16/2048.0f)
23 D8 F7 D2 00 00 02 00 - 0x00 position
C3 11 ED F1 30 00 05 00 - 4-byte vector

Sorry, I'm just too dumb to do it. I bet you could do even better! I just can't do it unfortunately ;(

Too dumb???!!! I got stuck and HAD TO LOOK AT YOUR CODE LOL!!! I don't know what that make me then . OK, I'll finish it up for ya, if shadowmoy or someone else who knows Rich's Noesis Python API doesn't take your noesis script and add like the 10 lines of code needed to finish it .

ninja edit: codeman! i see you on here... you want to finish this up for c00l?

howfie wrote:Too dumb???!!! I got stuck and HAD TO LOOK AT YOUR CODE LOL!!! I don't know what that make me then . OK, I'll finish it up for ya, if shadowmoy or someone else who knows Rich's Noesis Python API doesn't take your noesis script and add like the 10 lines of code needed to finish it .

Main issue is the struct.pack line or the code before it. Not sure why it seems to be erroring for some models. So yeah, I gave up on that one unfortunately if the problem is fixed I will continue it but i just can't seem to figure that one out so I gave up. If Codeman wants to help it'd be cool but I'm sure he has a lot of other stuff to do which is way more interesting

When Ekey finish updating file list, can i extract language files of Tomb Raider 9?

turkgamer wrote:When Ekey finish updating file list, can i extract language files of Tomb Raider 9?

Well in progress. 20579/22828 (90%) . But you can found localization files in next files:

bigfile.000.tiger - Subtitles for movies (Folder default\local\localization\movies\)
bigfile_XXXXXX.000.tiger - Subtitles for movies and Main Text (XXXXXX language name - ENGLISH, RUSSIAN and ect.) (Folders default\local\localization\movies\ , pc-w\local\locals.bin - Main Texts)

Ekey wrote:

turkgamer wrote:When Ekey finish updating file list, can i extract language files of Tomb Raider 9?

Well in progress. 20579/22828 (90%) . But you can found localization files in next files:

bigfile.000.tiger - Subtitles for movies (Folder default\local\localization\movies\)
bigfile_XXXXXX.000.tiger - Subtitles for movies and Main Text (XXXXXX language name - ENGLISH, RUSSIAN and ect.) (Folders default\local\localization\movies\ , pc-w\local\locals.bin - Main Texts)

So, can i extract "bigfile.000.tiger,bigfile_XXXXXX.000.tiger" for now ? How can i extract? We are translation group from Turkey, how can we translate this game? Please help us

C00L12345 wrote:

howfie wrote:Too dumb???!!! I got stuck and HAD TO LOOK AT YOUR CODE LOL!!! I don't know what that make me then . OK, I'll finish it up for ya, if shadowmoy or someone else who knows Rich's Noesis Python API doesn't take your noesis script and add like the 10 lines of code needed to finish it .

Main issue is the struct.pack line or the code before it. Not sure why it seems to be erroring for some models. So yeah, I gave up on that one unfortunately if the problem is fixed I will continue it but i just can't seem to figure that one out so I gave up. If Codeman wants to help it'd be cool but I'm sure he has a lot of other stuff to do which is way more interesting

hum if i got time i will take a look but i didn't promise anything

@C00l: its not a good idea to re-index the faces-numIndex on self-contained models - you will run into negative numbers as soon as the last vertices are building faces with the first vertices.
First of all you have to bind the whole vertices for the mesh and then you can set the triangles-data. Anyway good work to figure out all this stuff.

I updated my plugin-version with your UV-stuff. [Download]

And of course we need a method to auto-detect the correct textures per material.

Edit: Bones added for non-0x06 meshes

Here is the latest TR9 unpacker (With latest file lists)

So how can i edit "locals.bin" ? Is there any editor or converter? ("Locals.bin" in the attachemend)

not bad sammie, not bad
remember, there is an alternative UV type (not all models use scaled signed shorts)
also, don't forget blend weights and blend indices. i described you how to get them in a previous post.