Trying to read Bone info in 3DC files

[sominus]

I didn't put this in the "SMOD" thread so we don't mix things.

I'm trying to load 3DC models (Mobs actually) into 3dStudio. So far I can read the 3D info (vertices, faces, etc) to form the model:

 Spoiler

But for this to be useful, we also need the bones info. (So we later can save that back to a 3DC file).
And I fail to read that, this is what I get (all messed up bones):

 Spoiler

In 3dstudio, to create a bone, we do
BoneSys.createBone <point3>startPos <point3>endPos <point3>zAxis

Using the info from castor4878 in this post I can read the bone data, into a transform matrix:

tfm = matrix3 [m11,m12,m13] [m21,m22,m23] [m31,m32,m33] [m41,m42,m43]

But this is a 4x3 matrix, while 3DC says 'a 4x4 matrix' (I think so )
Also to build a bone hierarchy we would need each bone ParentID, so all bones form a 'chain'.

So, anyone knows what info is stored in that '4 x 4' matrix or has a dump of the data? Or any more info about the BoneMatrix in 3DC files?

PS: This is the code used to import a 3DC from Data\Monster\3DC (use it on a small mob that has only 1 MODEL!)

 Spoiler

/*
test abrir 3DC
// .3DC

typedef struct _3DC {
long tag; // 0 for format 5, 0x000001BC for format 6
long cntBones;
BoneMatrix* bones;
long cntVertices;
VerticesDC* vertices;
long cntFaces;
Faces* faces;
} File3DC;

typedef struct _BoneMatrix {
float m[4][4];
} BoneMatrix;

typedef struct _Vertex3DC {
float x, y, z;
float w;
byte bone1, bone2;
short unk0; // 0000 (padding?)
float nx, ny, nz;
float u, v;
} VerticesDC;

typedef struct _Faces {
unsigned short i1, i2, i3;
} Faces;
*/
-- ////////////////////////////////////////////////////////////////////////////////////////////////// --
--3dc file to import (change the name and path to the one you need)
fname = "d:\\3dsmax\\3dc\\mob_fox_01.3dc" --file name



--open 3dc file for binary read
f = fopen fname "rb" --open file in read only format
-- ARRAYS --
Vert_array = #() --vertex
Normal_array = #() --normals
UV_array = #() --uv map
Face_array = #() --faces
Weight_array = #() --bone weight
Bone_array = #() --bones

-- BONES ------------------------------------------------------------------------
--start reading from byte 4
fseek f 4 #seek_cur
bray = readlong f --bones count
print bray
for i = 1 to bray do (
b1 = readfloat f
b2 = readfloat f
b3 = readfloat f
b4 = readfloat f
b5 = readfloat f
b6 = readfloat f
b7 = readfloat f
b8 = readfloat f
b9 = readfloat f
b10 = readfloat f
b11 = readfloat f
b12 = readfloat f
b13 = readfloat f
b14 = readfloat f
b15 = readfloat f
b16 = readfloat f
)

-- VERTICES -----------------------------------------------------------------------
vray = readlong f --vertices count

for i = 1 to vray do (
--read XYZ
vx = readfloat f
vy = readfloat f
vz = readfloat f
append Vert_array [vx,vy,vz] --add values to Vert_array

w1 = readfloat f --weight
bo1 = readbyte f --bone1
bo2 = readbyte f --bone2
unk0 = ReadShort f --unk0
--print ("w " + w1 as string)
--print ("Bo1 " + bo1 as string)
--print ("Bo2 " + bo2 as string)
append Weight_array [w1,bo1,bo2] --add to weight_array

--read normals
nx = readlong f
ny = readlong f
nz = readlong f
append Normal_array [nx,ny,nz] --add normals to Normal_array

--read UV map
tu = (readfloat f) * 1
tv = (readfloat f) * -1
append UV_array [tu,tv,0] --add UVs to UV_array
)
-- FACES ----------------------------------------------------------------------------
nray = readlong f --faces count

for i = 1 to nray do (
f1 = (readshort f) + 1 --read face indices, games are start form 0, but Max start from 1
f2 = (readshort f) + 1 --so we add 1 to each index
f3 = (readshort f) + 1
append Face_array [f1,f2,f3] --save faces to Face_array
)

--close 3DC file
fclose f

-- BUILD THE MESH-----------------------------------------------------------------
msh = mesh vertices:Vert_array faces:Face_array --build mesh
msh.numTVerts = UV_array.count
buildTVFaces msh

for j = 1 to UV_array.count do setTVert msh j UV_array[j]
for j = 1 to Face_array.count do setTVFace msh j Face_array[j]
for j = 1 to Normal_array.count do setNormal msh j Normal_array[j]

You just run it and the mob will be created in 3dstudio.

Edit:
I've searched everywere and looks like none faund a way to extract bone info into a 'useable' skeleton. So, no way to make new mobs with new animations.

Now, with the code I posted above, you can also import armors into 3dstudio (withoout bones). Just import them piece by piece, they will take the correct position.
Same with complex mobs or bosses with multiple pieces, import them piece by piece, then group them in 3dstudio. You can apply the game textures to the models, and they will match.
At least is useful if you want to render them and make original pictures, to use in the Loading... screens.

Here's a test:

 Spoiler

If you have any doubt, maxscript its a huge language, and has a online manual with all the commands.

[castor4878]

Originally Posted by sominus

In 3dstudio, to create a bone, we do
BoneSys.createBone <point3>startPos <point3>endPos <point3>zAxis

Using the info from castor4878 in this post I can read the bone data, into a transform matrix:

tfm = matrix3 [m11,m12,m13] [m21,m22,m23] [m31,m32,m33] [m41,m42,m43]

But this is a 4x3 matrix, while 3DC says 'a 4x4 matrix' (I think so )
Also to build a bone hierarchy we would need each bone ParentID, so all bones form a 'chain'.

Since years I've made only few (actually not significant) progress on these matrixes.
At least, since the last column is always a vector (0,0,0,1), I feel that they are quaternions expanded to matrix4x4 (possibly a kind of orientation at rest).
In the referenced post, I used the names "BoneMatrix" and "bone1", "bone2" as indexes in that array, but all these nouns were borrowed from structures that looked like them.

I'm not sure whether you're looking for points that contact each others to define a skeleton but names "startPos, endPos and zAxis" may let think so.

Each vertex does contain a position ("at rest") and at least 2 (perheaps 4) indexes of matrix; what would mean a "starting or ending position" for each vertex ?

At least, when one checks the matrixes of a top, bottom, hand & boots .3DC for a given class/sex; they appear to be all identical(1), and so would define all articulation points of a body (player toon, NPC, mob, ...) and not the "bones" (lines that draw the skeleton) of that part of the body; but there I'm sure I'm not reading "bone" with the right (your) meaning.
(1) usually identical but some can contain additional quaternions at end of the list.

My understanding so far is that each vertex is "attached" to matrix(es) (or quaternions) and when a move occurs (as per .ani settings - still not fully understood) each vertex is moved by "some operations" performed between the matrix(es) listed by the vertex and modifiers (translations, rotations) of the .ani. With that hypothesis, the concept of a chain of nodes (point3D or bones or anything) is not required; there is only facets, defined by vertices, and each move is just a move of each facet - and possibly I'm an idiot to not being able to code the few required matrix operations.

Originally Posted by sominus

So, anyone knows what info is stored in that '4 x 4' matrix or has a dump of the data? Or any more info about the BoneMatrix in 3DC files?

Possibly, Zoltán Kárpáti, the author of .
(I exchanged with him in April 2011 to debug some issues of my first 3D viewer.

Here is how he success to draw the Character/human/3DC/co_humf_upper003.3DC file:

 Spoiler

Regarding "dump of the data", a copy from the .3DC viewer of shStudio copies a bitmap and a text definition, pasting in a text-consumer appl will give some dump (usable as samples).

Edit:
By April 26th 2013, I had an exchange with Zoltán on these quaternions (or bones...)
In spoiler below, my questions are in dark-red, his answers in green (some red & blue from his response)

 Spoiler

I'm reading these "bones" as 4x4 arrays of float4. may be a kind of transformation matrix is actually present but a 3D point is also likely present, can you provide me information regarding actual format / meaning (and optionally how they are used)?

Yes, it is a 4x4 transformation matrix, it contains the Bone position also.


Can you explain me your current way to manage these bones?

The main concept was the following:

I am using the XNALara Binary .mesh export format as a 'gateway' to transfer the fully textured objects (with Bone and Vertex Bone Weight information) to the 3D Studio Max.

You can download the Importer/Exporter script from this web page:



The .3dc format contain bone (4x4 matrix), 3d mesh datas, Vertex Bone Weight datas.
The .mesh and .mesh.ascii format contain bone (x,y,z position; no rotation datas!), 3d mesh datas, Vertex Bone Weight datas.
(I don't know 100% the Bones are referenced from 0 or from 1 in the .3dc file.)


Procedure:
1. First time you must copy the "XnaLara Converter.ms" file into your installed 3D Studio Max Scripts folder.
2. Run your 3D Studio MAX

3. Open your original .3dc file with 3D O.C.
4. Export the loaded object as XNALara Binary .mesh format.

5. Run your "XnaLara Converter.ms" script using the MAXScript/Run Script... menuitem.
6. Press the Import button on the XNALara Converter window.
7. Browse the converted .mesh file.
8. Modify your loaded object in the 3D Studio MAX.
9. Press the Export button on the XNALara Converter window.
10. Rename the exported file to *.mesh.ascii.
11. Open the *.mesh.ascii file with 3D O.C.
12. Export your loaded object as Shaiya .3dc file.
13. Test it with the original game.

Unfortunately this procedure does not work with the .3dc file, because
- the Shaiya character's subobjects have same bones and the XNALara format does not support the full 4x4 matrix for the Bones
- I don't know 100% how uses the Shaiya engine the Weight value and Bone references.
In the .3dc file every vertex have the following datas:
Weight
Bone1 (usually >0)
Bone2 (sometimes >0)
Bone3 (always 0)
Bone4 (always 0)

If the B1>0 and B2=0 the Weight=1 (it is OK, because the Sum of Weight=1)

If the B1>0 and B2>0 the Weight=0.5; 0.57; 0.7; 0.84; (?????)

I calculated the Weight2 for B2 like this (for exporting these values to the XNALara format):
Weight2:=1-Weight , but it did not work. Maybe it will work if I use the original bone matrixes when I will generate the .3dc file.


The new concept:
1. Open your original .3dc file with 3D O.C.
2. Export the loaded object as XNALara Binary .mesh format.
3. Open/Modify your loaded object in the 3D Studio MAX.
( Don't modify the Bone or the Vertex Weight datas!)
4. Export your modofied object from 3D Studio MAX and rename the exported file to *.mesh.ascii.
5. Open the *.mesh.ascii file with 3D O.C.
6. Export your loaded object as Shaiya .3dc file.
- You will get an OpenFileDialogBox to select the original .3d file.
(It will load the Bone and the Vertex Bone/Weight datas from the file and export it to the new .3dc file.)
6. Use it with the original game.

Possibly part of this information will help you to validate your Shayia to 3DStudio conversion.
/Edit

Originally Posted by sominus

I've searched everywere and looks like none faund a way to extract bone info into a 'useable' skeleton. So, no way to make new mobs with new animations.

The .ani file, as far as I understand them, consists in a set of sequences (steps of the animation), each step contains:
- a matrix4x4 (where the last column is also (0, 0, 0, 1))
- a list of Index (possibly index of a quaternion of the item to animate) + Vector4 (vector of 4 floats)
- a list of Index (possibly index of a quaternion of the item to animate) + Vector3 (vector of 3 floats)

Possibly, the Vector4 could define a rotation, the Vector3 could define a translation.

Being able to animate some points using the right math may give the keys to understand the shaiya logic; unfortunately I leak some knowledges to do that and so far I haven't find the time to improve them - all 3D modeling appls draw some so nice rotation nodes and let you select and activate the 3 pretty small arcs of rotation (axis of rotation) of these nodes but of course none gives (to idiots) the algebra logic (a long step-in analysis in an open source project may help).

Originally Posted by sominus

Now, with the code I posted above, you can also import armors into 3dstudio (withoout bones). Just import them piece by piece, they will take the correct position.

That's the easy point indeed.
All shapes that consist in several smaller (sub) shapes always share the same coordinates scale and origin.
(the viewer of .3dx (that draws the top, bottom, hands & boots of a toon) simply draws all pieces w/o caring about coords)

[sominus]

I know the way Zoltán told us to load and save bone info, he posted that time ago. But that involves just editing the current shape of an armor (we can't remove or add vertices so we cant actually create a brand new original armor).

Each vertex does contain a position ("at rest") and at least 2 (perheaps 4) indexes of matrix; what would mean a "starting or ending position" for each vertex ?

Start pos is where a bone start, end pos is where it ends so it define its lenght. So, start pos of bone02 would be = end pos of bone01.
Normally, bones are connected (linked), so when you rotate a shoulder, all next bones (arm, elbow, hand) will follow that rotation correctly.
I asume the so called matrix4 is what actually allows (by doing maths in the code) to achieve that.
Now, may be (in the game) the bone lenght and parenting to each other is not needed, so we only draw the bone dots (like vertices), and not the lenght.


These are bones draw by hand to (barelly) represent a human skeleton.
The parts in red circle are 'joints' and the part in blue circle are the bones.

Normally (but may be not generally), the part in blue circles is what 'attracts'
vertices from the 3d mesh to move them (or deform them), due to the weight info.

 Spoiler

And this is what I get importing Mob_FOx_01.3DC

 Spoiler

As you can see the bone skeleton looks like just a random sequence of bones, no noticeable 'shape' at all.

In other games, the mesh file also contains the bones Indexes, that way you know how bones are 'linked' to each other and how the skeleton is built. But 3DC files doesn't have that info (AFAIK), so here Im reading bones just in the sequence they are written in the 3dc file. (But even so... the should make a correct shape).

AND... of course I might be reading them the wrong way, that's why they don't conform a correct skeleton shape.

In my case Im using the info this way (to make a single bone):

BoneSys.createBone
<p3>startPos
<p3>endPos
<p3>zAxis

column4
column4 * (column1)
column3

I took that from a forum

But then again, it might not be the right way to read shaiya bone info.

PS: You say column4 is a vector, [0,0,0,1], but Im not geting that info. This is a line from my bone reading:

"Row1: [1.37091e-006,0,1] Row2: [0,1,0] Row3: [-1,0,1.37091e-006] Row4: [0.356065,-0.538229,-4.88133e-007]"

All the remaining lines looks like that one.

If you want a open source project, BLender is open source and it supports python (to make scripts). I just don't use it because its learning curve is harder for me and I already know the basis for 3dstudio.

But... for anyone here starting from scratch into this, Blender is a very small free download, and it needs many less resources than 3dstudio.

I found this paper about matrix, but it's a very loooong read:

[JuuF]

Originally Posted by sominus

In my case Im using the info this way (to make a single bone):

BoneSys.createBone
<p3>startPos
<p3>endPos
<p3>zAxis

column4
column4 * (column1)
column3

Not sure if you're still interested but you should follow the steps below.

1. Ignore column 4
2. Create an inverse matrix of 4x3 matrix that you see when you ignore the 4th column
3. Use 4th row as startpos
4. Use startpos+(length*DirectionX) as EndPos (where DirectionX is Row1)
5. Use DirectionZ as "zAxis" (where DirectionZ is Row3)

P.S. length = sqrt((x1-x2)^2+(y1-y2)^2+(z1-z2)^2) works good enough to find out which bones are connected together but if you just want to see the bone points you can use 0.1 or something.

[regvn]

If you want to import bones and animation, the best way I do research is to use Fatimport, a software written by a Chinese friend a long time ago. Unfortunately Shaiya is not included, but he said Shaiya has a structure that is easy to handle and he came up with a script like this that I don't know about the script.

 Spoiler

dword constant00
dword numBones
struct Bone {
float_16 Matrix4X4
}
dword numVerts
struct Vert {
float_3 CoordXYZ
float Weight
byte BoneID01
byte BoneID02
float_3 NormalXYZ
float_2 TexCoordUV
}
dword numFaces
struct Face {
word_3 FaceIndices123
}

Fatimport can be downloaded here

[ZEHLENDORF]

Originally Posted by sominus

In my case Im using the info this way (to make a single bone):

BoneSys.createBone
<p3>startPos
<p3>endPos
<p3>zAxis

column4
column4 * (column1)
column3

I took that from a forum

Hello sominus! you were able to load the armature of the .3dc files? I saw that 3d object converter supports it but sadly you need to pay to be able to export the model.