[PS2] Wild Arms 3 .bin archive

[SmashFan127]

Is there anyone out there?

[SmashFan127]

Update:

Using TextureFinder, I was able to look inside the STGEVTD.BIN file and see what appeared to be every character portrait. Please let me know what you think.

[SmashFan127]

Quick update.

I was browsing STGEVTP.BIN in a hex editor when I came across this at the beginning.



outmap.bin? Well, there's no such file in plain sight when looking at the files on the disc. Could this be maps or...?

On another part of the file, I discover this...



There are also .bin files like these, it seems. There are sorted in order; t01.bin to t13.bin, not to mention there are "d" versions of these files as well. I can certainly come to the conclusion "t" stands for "town" while "d" stands for dungeon. There are also "e" variations, which I assume are "event" maps.

EDIT:

A while back, I found some textures inside BTLODT.BIN. I recently viewed it in a hex editor to reveal some formats as seen in the following image.

As far as I know, the extensions seen in the file are easily recognizable. I assume "vu" refers to the UV coordinates used on the textures I discovered using TextureFinder. Bone files can be seen here, along with the .mdl format and .msh, I can say must be mesh. Aside from the that, texture files are housed here, most notably .tim format.

ANOTHER EDIT:

Again, I found some more stuff inside STGEVTD.BIN. It seems to be made up of dialogue with certain numbers standing for names...

A brief example showing an in-game line of Janus, whose number is 072.



NOTICE: To anyone who would like to help with unpacking archives, let me know you are interested and I will gladly send sample files your way.

EDIT.... again...:

I can definitely say there are a ton of files for use with models of enemies inside BTLODT.BIN. The problem is writing a script to extract the files. Is there anyone who can help if I send the sample file?

[Sharppy]

I used VGM toolbox to extract each model. But I noticed several things. The way they are stored isn't like anything ive ever seen. I been looking into all the .BIN files here is what I found.

[BTL]
BTLANM.BIN - Animations (118)
BTLMED.BIN - Animations (111)
BTMEP.BIN - ?
BTLOD.BIN - Textures (128), Animations (33)
BTMON.BIN - Models (362), Textures (827), Animations (5973)
BTLOVR.BIN - ?
BTLSE.BIN ?

[STG]
BTLKAR.BIN - ?
OUTANM.BIN - Animations (32)
STGANM.VIN - Animations (178)
STGEVTD.BIN - Textures (266)
STGEVTP.BIN - ?
STGMAP.BIN - ?
STGOBJ.BIN - Animations (15)
STGOUT.BIN - Animations (247)
STGSE.BIN - ?

[Strings Used]
53536864FFFFFFFF (.tex)
82BE82DD (.model)
0A414E4D (.amn)

After getting some help from Reh over at Zenhax he showed me my .tex are actually readable.


Offset is usually 2196 and the palette is at 1170-1174. I noticed a few times it was 1172 and 1174 so just have to check. But once you do that save a .bmp. This will make it nice to get the textures from all area's without playing the game.
Or you can do it the old way from PCSX2 and manually saving them.

Either way textures aren't too bad. Its the models that have been a struggle. I looked at the raw information and its hard for me to decrypt. I found that I cant get anything by the raw data. Not yet at least.
As for the save states. That's a different story. shakotay2 helped me with the script a few months ago but we still weren't able to get a proper extractor.

The results of the output were not proper uv channels. I don't know where the error is I've looked at the script for about 2 months now. I cant seem to find it. If I shift the bytes x04 i get the world.

Then I think if I shift -0x04 bytes I get this..

Which appears to be the missing faces from the 1st image. Not sure what's going on there. I noticed that this was the post from some years ago. Which included a .blend file. Which i think is the key to all this.

Because in this tutorial of the extractor all the uv's look correct and he supplied all 4 main characters uv mapped.

Here is the extractor he made for the eememeory
https://drive.google.com/file/d/195iKgJ ... sp=sharing
If anyone could help with this game that would be extremely helpful! Its been quite some time.

[shakotay2]

well, seems I mixed the uv channels.

Here's an updated exe (to be copied into the Make_obj folder from the zip in sharppy's google drive):
.

Make_obj_WA3-uvs.zip

(I could add the 2nd channel after someone confirms it's working correctly now.)

edit: added 3ds.exe (uses # before comments now)
(updated Make_obj.exe to net log superfluous vt 0.0 0.0 at obj files end)

Usually you use a batch file (*.cmd) for 3ds.exe containing such line:
3ds.exe %1 > %1.obj

(to log the output into an obj file)

[shakotay2]

WA3_uvs_channel1.png

[Sharppy]

Here is the updated script. Thanks again!

[shakotay2]

To avoid confusion I'd suggest to comment out this line (adding #) in the bms file:
#Log "fInd.bin" 0 sizefInd MEMORY_FILE3 ;

Because the fInd0000000x.bin files contain face indices that are already in the 1.3ds.obj for example.

.bin format (example, first 16 bytes) is
00 00 01 00 02 00 00 00 00 00 02 00 01 00 00 00
->
f 1 2 3, dummy 0, then f 1 3 2 (maybe for the back faces? because of counter winding), dummy 0
as a result, first face (normals not handled)
f 1/1 2/2 3/3
f 4/4 5/5 6/6
f 7/7 8/8 9/9
f 10/10 11/11 12/12
...
----------------------
The whole process (adding uvs)

Code: Select all

- use the modified WA3-sharppy-bms script on a eeMemory.bin file.

You should get some 3ds files AND uvs.bin files (choose rename on the quickbms request!)
You will get uvs.bin, uvs00000001.bin, uvs00000002.bin,...,uvs00000007.bin

In the tools chain below
be sure to combine 1.3ds with uvs.bin, 2.3ds with uvs00000001.bin and so on.
############################################################################

- On a windows command line type
WA3_verts.cmd 1.3ds
or drag&drop 1.3ds onto the cmd file

- 1.3ds.obj being created
-------------------------------------------

change to Make_obj folder, start Make_obj.exe

File/open uvs.bin
(You may need to switch to the folder where the uvs.bin is contained.)

- Makeobj_log.obj being created, contains vt lines
(Be sure to close the tool before accessing that obj file!)

(2.3ds and uvs00000001.bin are the next "pair".)
-----------------------------------------

- copy/paste the contents of Makeobj_log.obj (vt lines) into 1.3ds.obj
  before the face indices lines

- load obj into your preferred 3D rendering software

(You could change the bms script to have an increasing number starting with 0: uvs0.bin, uvs1.bin,...
without the need of pressing 'r' then.)

[Sharppy]

I found that if you change line 27 in the script from seek 15 to 31 you can extract the stages. There seems to be 1 triangle missing tho in each submesh. Might be the way the script is parsing faces in the new order of bytes perhaps ? Uv's are a tangled mess aswell. I found this by examining the original script to this one.