Jump to content

OBD talk:TRBS: Difference between revisions

OBD talk:TRBS (view source)

Revision as of 11:53, 22 October 2012

2,824 bytes removed ,  22 October 2012
m
no edit summary
m (lol that was wrong)
mNo edit summary
Line 43: Line 43:
When extracting a TRBS with onisplit v0.9.41.0 the TRIA instance gets exposed. Then it can be modified by hand to change the hierarchy of body parts.
When extracting a TRBS with onisplit v0.9.41.0 the TRIA instance gets exposed. Then it can be modified by hand to change the hierarchy of body parts.


In the table are two hexhound hierarchies. One modified and one original onisplit-generated.
In the table below you can see examples of TRIA instances: one from Konoko and one from a more or less hypothetical hex-hound.


The extracted xml code of those two is a bit different. They have same hierarchy but the order of body parts is different. As result the head animation was applied to different parts.
: Onisplit v0.9.58.0 and lower needs a dae file where the body part names are strictly correct but the order doesn't matter. The result will be always a standard TRIA.
: Onisplit v0.9.68.0 and higher(?) tolerates unusual body part names but it takes the order ''serious'' to build the hierarchy.
: In other words, when building a custom hierarchy with new onisplit versions you don't need any longer to edit the TRIA instance in xml.
 
Note that the head could be at a different location in the order. As result the head animation would be applied to a different body part.


Normally such overlay animation have "Head" as "<UsedBones>", if your new model's head isn't the 11th part you need to change it.
Normally such overlay animation have "Head" as "<UsedBones>", if your new model's head isn't the 11th part you need to change it.
Line 51: Line 55:
A character with non-standard TRIA needs a complete set of new animations, those animations must be created based on that new TRIA.
A character with non-standard TRIA needs a complete set of new animations, those animations must be created based on that new TRIA.


The order how the body parts get incorporated into the TRBS depends on their position in the dae file.
 
'''Changing the body part order'''


Inside Mod Tool, the objects have an order which can be seen in the Schematics. The user can influence that order by using the Reorder Nodes Tool [I].
Inside Mod Tool, the objects have an order which can be seen in the Schematics. The user can influence that order by using the Reorder Nodes Tool [I].
Line 69: Line 74:
|}
|}


objs = 0
  if selection.count > 0 then
  if selection.count > 0 then
  ' any part could be seleced, let's find the root body part
  ' any part could be selected, let's find the root body part
  SelectNeighborObj selection(0), 4
  SelectNeighborObj selection(0), 4
  ' get children
  ' get all members including the pelvis
  set bodyparts = '''selection(0).FindChildren( , , siMeshFamily)'''
  set bodyparts = '''selection(0).FindChildren( , , siMeshFamily)'''
  for each member in bodyparts
  for each member in bodyparts
Line 84: Line 88:
  logmessage "Y: " & member.Material.CurrentImageClip.source.Parameters("YRes").Value
  logmessage "Y: " & member.Material.CurrentImageClip.source.Parameters("YRes").Value
  end if
  end if
objs = objs + 1
  logmessage "----------------------------------------------------------"
  logmessage "----------------------------------------------------------"
  next
  next
  logmessage "counted body parts: " & objs
  logmessage "counted body parts: " & bodyparts.count
  end if
  end if
   
   
Line 191: Line 194:
| '''standard TRIA'''
| '''standard TRIA'''
| '''hexhound TRIA'''
| '''hexhound TRIA'''
| '''hexhound TRIA'''
|-
| original
| modified
| original (made v0.9.68.0)
|-
|-
|
|
Line 287: Line 285:
             <TRIAElement>
             <TRIAElement>
                 <Parent>16</Parent>
                 <Parent>16</Parent>
                <Child>18</Child>
                <Sibling>0</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>17</Parent>
                <Child>0</Child>
                <Sibling>0</Sibling>
            </TRIAElement>
        </Elements>
    </Instance>
|
    <Instance id="4" type="TRIA">
        <Elements>
            <TRIAElement>
                <Parent>0</Parent>
                <Child>1</Child>
                <Sibling>0</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>0</Parent>
                <Child>2</Child>
                <Sibling>3</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>1</Parent>
                <Child>0</Child>
                <Sibling>0</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>0</Parent>
                <Child>4</Child>
                <Sibling>5</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>3</Parent>
                <Child>0</Child>
                <Sibling>0</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>0</Parent>
                <Child>6</Child>
                <Sibling>7</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>5</Parent>
                <Child>0</Child>
                <Sibling>0</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>0</Parent>
                <Child>8</Child>
                <Sibling>9</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>7</Parent>
                <Child>0</Child>
                <Sibling>0</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>0</Parent>
                <Child>10</Child>
                <Sibling>0</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>9</Parent>
                <Child>11</Child>
                <Sibling>0</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>10</Parent>
                <Child>12</Child>
                <Sibling>14</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>11</Parent>
                <Child>13</Child>
                <Sibling>0</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>12</Parent>
                <Child>0</Child>
                <Sibling>0</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>10</Parent>
                <Child>15</Child>
                <Sibling>17</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>14</Parent>
                <Child>16</Child>
                <Sibling>0</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>15</Parent>
                <Child>0</Child>
                <Sibling>0</Sibling>
            </TRIAElement>
            <TRIAElement>
                <Parent>10</Parent>
                 <Child>18</Child>
                 <Child>18</Child>
                 <Sibling>0</Sibling>
                 <Sibling>0</Sibling>
Paradox-01
8,047

edits

Retrieved from "https://wiki.oni2.net/Special:MobileDiff/20555"