reading/writing a CS .fig file (ASCII)

reading/writing a CS .fig file (ASCII)

Anonymous
Not applicable
294 Views
2 Replies
Message 1 of 3

reading/writing a CS .fig file (ASCII)

Anonymous
Not applicable
Hiya ...

I recently realized that a biped figure file (.fig) is in ASCII format ..
I 'm writing a tool to build a biped from scratch thro maxscript using some values I have in a file.
These values that I have are the world transform matrix values of each joint.

If I could understand the values found in a .fig file, that'd be a great start point ...
Does anyone have the know how of the structure of a .fig file?

This is what I've figured out till now:
# A fig file has integer values like 10,11,12,13, and so on, which I presume are some kind of IDs corresponding to various Biped parts.
for eg, I guess
11 : Spine
12 : Head
13 : Neck
101 : COM
Am still trying to figure out the rest.

The number of links of a biped part, I guess, is stored as a integer value which is (numLinks * 3)
Another important value found in the file is the distance between a joint and the next child, in max units.

11 ##SPINE
3
21.796455

eg: If the number of spine link is 1, then the spine ID 11 is followed by the value 3.
If numSpineLinks == 2 then spine ID 11 would be followed by 6 (2 * 3)
21.796455 could be the distance between the spine joint and its child, the neck joint.
It also seems that the matrix values stored in the .fig file are using Y -UP, maya style, instead of max styled Z-UP.

Any gurus out there who could shed more light on this file format, highly appreciated.

Thanks in advance
regards,
shibu
0 Likes
295 Views
2 Replies
Replies (2)
Message 2 of 3

Anonymous
Not applicable
The indices are listed in the mxs docs...

Search for "biped"

Biped Node Hierarchy is the heading you are after.
0 Likes
Message 3 of 3

Anonymous
Not applicable
no mate, its not the same.
The Ids found in .fig files are completely different than the ones that we normally use in scripts

Try this :
Save a .fig file off any biped and open the fig file in any text editor.
0 Likes