SUBSIM Radio Room Forums - View Single Post

09-19-13, 03:35 PM

When I exported the rawchunks I named them as below.
BodyParts
Body
BodyEnd
I'll be useing those names so re-name or remember how you named them.
It's easier to work with those chunks rather then the whole Secondary.dat by the way.

I'll be useing 010 with scripts to do alot of the 'heavy lifting' but I'll do my best to answer questions if you use a 'lesser' Hex Editor.

BodyParts contain the names, in order, of the biped I'm after. (Who would of thunk that!

)

Body contains the positional elements to build the biped.
The X Y Z RX RY RZ W data that SH4 uses as the base position/stance of the biped.

BodyEnd I suspect is how the parts are connected as to Parent-Child?

(Corrections welcome)

We have the basic structure of SH files as to it's 'Node' ID, info size etc in each.
What We do have is a different Parent-Child ID structure. It's no longer 8 bytes but 4 bytes.
Look at the BodyParts in Secondary.dat and you'll see the ID listed but no Parent ID. That's right and wrong for this reason.
BodyParts has no Parent but it's ID is NOT 8 bytes long. It also has no place for a Parent ID as it IS the Top most Parent.
S3D will not show those Parent-Child ID's in the Unknowns so lets look at them in Hex.

BodyParts
02 D1 66 5A 00 00 00 00 = Node type 1516687618/0
C3 01 00 00 = 451 (how much data we need to read AFTER this float)
41 FF 53 59 = ID of this whole chunk.
1F 00 00 00 = 31. Number of parts! NOT the Parent as there is no Parent!
All data after that is just the names of the 31 parts to a standard Biped.
(I posted those earlier so you might want to copy and paste from that post)

Body
72 15 7B 30 00 00 00 00 = Node type 813372786/0
6C 03 00 00 = 876 (how much data we need to read AFTER this float)
D5 F4 B6 D0 = ID of this whole chunk.
41 FF 53 59 = Parent Chunk! See the change here? Check the ID above!!
(SH Games have used an 8 byte ID structure since SH3 at lest to my knowledge. Now it's different which may have contributed to earlier fails at breaking the animations. Not the only one though!)

BodyEnd
You should be able to see the info with a clear understanding at this point.

09-19-13, 03:35 PM	#20
Madox58 Stowaway Posts: n/a Downloads: Uploads:	When I exported the rawchunks I named them as below. BodyParts Body BodyEnd I'll be useing those names so re-name or remember how you named them. It's easier to work with those chunks rather then the whole Secondary.dat by the way. I'll be useing 010 with scripts to do alot of the 'heavy lifting' but I'll do my best to answer questions if you use a 'lesser' Hex Editor. BodyParts contain the names, in order, of the biped I'm after. (Who would of thunk that! ) Body contains the positional elements to build the biped. The X Y Z RX RY RZ W data that SH4 uses as the base position/stance of the biped. BodyEnd I suspect is how the parts are connected as to Parent-Child? (Corrections welcome) We have the basic structure of SH files as to it's 'Node' ID, info size etc in each. What We do have is a different Parent-Child ID structure. It's no longer 8 bytes but 4 bytes. Look at the BodyParts in Secondary.dat and you'll see the ID listed but no Parent ID. That's right and wrong for this reason. BodyParts has no Parent but it's ID is NOT 8 bytes long. It also has no place for a Parent ID as it IS the Top most Parent. S3D will not show those Parent-Child ID's in the Unknowns so lets look at them in Hex. BodyParts 02 D1 66 5A 00 00 00 00 = Node type 1516687618/0 C3 01 00 00 = 451 (how much data we need to read AFTER this float) 41 FF 53 59 = ID of this whole chunk. 1F 00 00 00 = 31. Number of parts! NOT the Parent as there is no Parent! All data after that is just the names of the 31 parts to a standard Biped. (I posted those earlier so you might want to copy and paste from that post) Body 72 15 7B 30 00 00 00 00 = Node type 813372786/0 6C 03 00 00 = 876 (how much data we need to read AFTER this float) D5 F4 B6 D0 = ID of this whole chunk. 41 FF 53 59 = Parent Chunk! See the change here? Check the ID above!! (SH Games have used an 8 byte ID structure since SH3 at lest to my knowledge. Now it's different which may have contributed to earlier fails at breaking the animations. Not the only one though!) BodyEnd You should be able to see the info with a clear understanding at this point. Last edited by Madox58; 09-19-13 at 03:51 PM.