MMO ARGO

Post by **chrrox** » Sun Apr 10, 2011 7:40 pm

here is a file extractor script

#quickbms script
#ARGO
#from chrrox

open FDDE tbl2 1
set arcnum 0


goto 0x10001C 1

for i = 0
    get offset long 1
    get zsize long 1
    get null3 long 1
    get size long 1
    get arcnum long 1
    print "%arcnum%"
        set NAME1 string "file0"
    set MYEXT string arcnum
    strlen MYEXTSZ MYEXT
    if MYEXTSZ == 1
        string NAME1 += "00"
    endif
    if MYEXTSZ == 2
        string name1 - 1
        string NAME1 += "0"
    endif
    if MYEXTSZ == 3
        string name1 - 1
        string NAME1 += ""
    endif
    string NAME1 += MYEXT
    string NAME1 += .data2
    open FDSE NAME1 0


    get null1 long 1
    get null2 long 1

    get name string 1
    Padding 4 1

    get null long 1
if zsize == size
        log name offset zsize
else
clog name offset zsize size
endif
next i

bmobius · Post by **bmobius** » Sat Apr 16, 2011 11:55 pm

Running the risk of sounding.. well.. retarded... I have the game, but I'm not sure how to use QuickBMS with this game. What files are you unpacking with it and where are the character archives located?

Post by **chrrox** » Sun Apr 17, 2011 1:33 am

Argo\Resources\file.tbl

its the huge set of archives in the game.

Sniperello · Post by **Sniperello** » Sun Apr 17, 2011 4:17 pm

thnx man!

bmobius · Post by **bmobius** » Mon Apr 18, 2011 5:54 am

chrrox wrote:Argo\Resources\file.tbl

its the huge set of archives in the game.

Ah! So that's what I was missing!

Once I pointed QuickBMS to the correct file, everything else fell right into place. It generated a proper folder and unpacked to that location. Then on top, the 3DS Max import script worked like a charm as well as the QuickBMS texture script.

Thanks for the work!

Szkaradek123 · Post by **Szkaradek123** » Tue Apr 26, 2011 6:31 pm

The contents of this post was deleted because of possible forum rules violation.

CriticalError · Post by **CriticalError** » Thu Jun 23, 2011 10:27 pm

thanks a lot guys, all work fine, but 1 question, about bms script when convert xtex to dds don't work, take a look

and about mesh of weapons? is not xac format is xmesh so who import it in MAX? the importer is for xac? anyway thanks a lot for all support and pattience for ppl begin in it.

finale00 · Post by **finale00** » Thu Jun 30, 2011 4:15 am

^I have tried the bms script on some item textures but I converted it to tga afterwards.

If anyone is interested in figuring out the xgeom files (items), here's a couple small ones I picked out.
There are a couple 1 KB ones

My guess is that it uses shorts for stuff like number of characters in a string (based on the last line), but it doesn't seem obvious what some of the other numbers mean before the big section of floats.

The xmesh files tell which xgeom and which xmtl files to load. Some of them are in binary some are them are in XML format, so maybe that makes it easier to tell what the xmesh file is.
one type of xgeom is like

dword xbin
10 bytes [seems always 0D 0A 00 0B 00 00 00 00 00 01]
short charCount
charCount meshName
10 bytes ???
short charCount
charCount unique ID (just some name. Some xgeom have, some don't)
2 bytes ???
short vertType

===== Following applies to vertType 1 only =====
5 bytes ???
short numVerts
short numVerts * 3 (so numFaces = this / 3)

struct vertex {
float_3 x,y,z
float_3 (normals probably)
float_2 u,v
}
struct face {
short_3 v1, v2, v3
}
short ???
short charCount
charCount material library name (.xMtl files)

Seems to be working for the items. There are larger xgeom files that are more complicated.

If someone can help me with the notation to make it clearer that would be great.

finale00 · Post by **finale00** » Thu Jun 30, 2011 4:16 am

Valiant online uses the same format, and it works as well.

The smaller items seems to work using the format up there, but it won't work for a lot of the larger files.

In particular, some differences are

dword xbin
10 bytes [seems always 0D 0A 00 0B 00 00 00 00 00 01]
short charCount
charCount meshName
10 bytes ???
short charCount
charCount unique ID (just some name. Some xgeom have, some don't)
9 bytes [00 12 03 00 00 04 00 00 00]

Instead of 12 01 it is now 12 03. So maybe can conclude there are two different types of xgeom files.
There is also 12 04. Maybe it represents the vertex type since any xgeom file with type 12 01 follows the previous post's structure.

Maybe something special about that second byte.

xmtl files seem pretty straightforward, but I don't understand materials that much so I don't know what the values could be.
Some groups of 4 floats and 3 floats here and there, maybe for RGBA, ambient, and emissive?

Here's some bigger files in case small ones lack detail.
And some bigger files definitely have different format than the small ones.

finale00 · Post by **finale00** » Thu Jun 30, 2011 4:57 pm

Type 1 vertex has vertsize 32
Type 3 vertex has vertsize 48
Type 4 vertex has vertsize 56

Code: Select all

dword xbin
10 bytes [seems always 0D 0A 00 0B 00 00 00 00 00 01]
short charCount
charCount meshName
10 bytes ???
short charCount
charCount unique ID (just some name. Some xgeom have, some don't)
2 bytes ???
short vertType 
5 bytes ???
short numVerts
short numVerts * 3 (so numFaces = this / 3)

struct vertex type 1 {
   float_3 x,y,z 
   float_3 (normals probably)
   float_2 u,v
}

struct vertex type 3 {
  float_3 x,y,z
  float_3 maybe
  float_2 maybe
  16 bytes ???
}
struct vertex type 4 {
   float_3 x,y,z
   float_3 maybe
   float_2 maybe
   24 bytes ???
}
struct face {
   short_3 v1, v2, v3
}
short ???
short charCount
charCount material library name (.xMtl files)

Since coords, uv, and normals have been dealt with in type 1, I'm guessing the rest are bones and stuff? Haven't actually looked into bones yet so I don't know how they are usually stored, or what kind of information they might need.

Any references that I can look at for this info? Most of the tutorials I've read are very practical and just talk about how to make stuff...

finale00 · Post by **finale00** » Fri Jul 01, 2011 3:13 am

Some results:

Works for all non-XML xgeom files.

Also...here are XML versions of the xgeom, xlocus, xmesh, and xmtl files.
I was wondering what was causing certain files to crash my script and noticed this

Those should be straightforward to parse.

Rimbros · Post by **Rimbros** » Sun Nov 06, 2011 3:43 am

xgeom files, but where its the script or the converter, somebody can release this from the code Finale wrhote?

Rimbros · Post by **Rimbros** » Tue Nov 22, 2011 6:20 pm

The contents of this post was deleted because of possible forum rules violation.

Rimbros · Post by **Rimbros** » Sat Dec 10, 2011 6:41 pm

Any idea or news with .xgeom files?

finale00 · Post by **finale00** » Sun Feb 19, 2012 8:00 am

xgeom noesis plugin added.

May not work for all models yet (I think there were some issues with a couple of them when I looked at it, but not sure which)

Test different types of xgeom and see which ones fail. I'm sure it was related to characters though.

XeNTaX

XeNTaX

MMO ARGO

MMO ARGO

Re: MMO ARGO

Re: MMO ARGO

Re: MMO ARGO

Re: MMO ARGO

Re: MMO ARGO

Re: MMO ARGO

Re: MMO ARGO

Re: MMO ARGO

Re: MMO ARGO

Re: MMO ARGO

Re: MMO ARGO

Re: MMO ARGO

Re: MMO ARGO

Re: MMO ARGO