XML:TRBS: Difference between revisions

Revision as of 14:25, 30 March 2021

TRBS : Totoro Body Set	XML modding tips See HERE to start learning about XML modding. See HERE if you are searching for information on how to handle object coordinates. See HERE for some typical modding errors and their causes.
XML TRAS << Other file types >> TRGE switch to OBD page

General information

TRBS files describe the overall structure of a character's 3D model. They are linked to from the ONCC character class file.
TRBS files are stored globally in level0_Final.dat.
They contain 5 different models with differing levels of detail (known as LODs). A common game development technique for improving performance is to display a reduced polygon-count version of a character when they're farther from the camera.

File structure

TRBS
  |
  +-- TRCM
  +-- TRCM
  +-- TRCM
  +-- TRCM
  +-- TRCM (same for all TRCM)
        |
        +-- TRGA
        |     |
        |     +-- M3GM
        |           |
        |           +-- PNTA
        |           +-- VCRA
        |           +-- TXCA
        |           +-- IDXA
        |           +-- IDXA
        |           +-- texture link (empty because of TRMA usage)
        +-- TRTA
        +-- TRIA

Extraction (new method)

This is more powerful method because it extracts the full range of models (all 5 LODs).

onisplit -extract:xml output_folder input_folder/TRBSname.oni

Extraction (old method)

This older extraction approach lets you choose between extracting only the TRBS or the ONCC file with TRBS. Note that this only extracts the model with the highest poly count.

onisplit -extract:dae output_folder input_folder/TRBSname.oni
onisplit -extract:dae output_folder input_folder/ONCCname.oni

Creation (new method)

This creates a TRBS file with up to 5 different LODs:

onisplit -create output_folder input_folder/TRBSname.xml

Example from TRBSkonoko_body_high.xml (extracted with OniSplit v0.9.68.0):

<?xml version="1.0" encoding="utf-8"?>
<Oni>
   <TRBS id="0">
       <Elements>
           <Link>TRBSkonoko_body_high_TRCM1.dae</Link> <!-- 300 triangles -->
           <Link>TRBSkonoko_body_high_TRCM2.dae</Link> <!-- 842 triangles -->
           <Link>TRBSkonoko_body_high_TRCM3.dae</Link> <!-- 1250 triangles -->
           <Link>TRBSkonoko_body_high_TRCM4.dae</Link> <!-- 2038 triangles -->
           <Link>TRBSkonoko_body_high_TRCM5.dae</Link> <!-- 3294 triangles -->
       </Elements>
   </TRBS>
</Oni>

Creation (old method)

This creates a TRBS file where all LODs use the same model; that's not good for memory usage or performance, but useful enough for testing a character in-game.

onisplit -create:trbs output_folder [-cel] [-normals] input_folder/TRBSname.dae

(The arguments "cel" and "normals" are optional.)

Standard TRIA hierarchy

File:XSI ModTool TRIA.png

Custom TRIA hierarchy

OniSplit creates the TRIA instance on its own. When extracting a TRBS with OniSplit v0.9.41.0, the TRIA instance is exposed. It can then be modified by hand to change the hierarchy of body parts.

In the table below, you can see two examples of a TRIA: one from Konoko and one from a more or less hypothetical Hex Hound.

OniSplit v0.9.58.0 and below need 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(?) tolerate unusual body part names but take the order seriously when building 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 if the head was in a different location in the hierarchy, animations intended for the head 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. A character with non-standard TRIA needs a completely set of new animations based on that new TRIA.

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].

Taking this into account, it should be possible to let Mod Tool generate a TRMA file fitted to the TRBS.

Example

Standard TRIA

Hex Hound TRIA

   <Instance id="8" type="TRIA">
       <Elements>
           <TRIAElement>
               <Parent>0</Parent>
               <Child>1</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>0</Parent>
               <Child>2</Child>
               <Sibling>4</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>1</Parent>
               <Child>3</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>2</Parent>
               <Child>0</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>0</Parent>
               <Child>5</Child>
               <Sibling>7</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>4</Parent>
               <Child>6</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>5</Parent>
               <Child>0</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>0</Parent>
               <Child>8</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>7</Parent>
               <Child>9</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>8</Parent>
               <Child>10</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>9</Parent>
               <Child>0</Child>
               <Sibling>11</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>9</Parent>
               <Child>12</Child>
               <Sibling>15</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>11</Parent>
               <Child>13</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>12</Parent>
               <Child>14</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>13</Parent>
               <Child>0</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>9</Parent>
               <Child>16</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>15</Parent>
               <Child>17</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <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>13</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>11</Parent>
               <Child>0</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>10</Parent>
               <Child>14</Child>
               <Sibling>16</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>13</Parent>
               <Child>15</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>14</Parent>
               <Child>0</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>10</Parent>
               <Child>17</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>16</Parent>
               <Child>18</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
           <TRIAElement>
               <Parent>17</Parent>
               <Child>0</Child>
               <Sibling>0</Sibling>
           </TRIAElement>
       </Elements>
   </Instance>

@@ Line 1: / Line 1: @@
 {{XML_File_Header | prev=TRAS | type=TRBS | next=TRGE | name=Totoro Body Set}}
-===General information===
+==General information==
-* TRBS files are stored ''globally'' (in AE/AEInstaller/vanilla/level0_Final.dat)
+* TRBS files describe the overall structure of a character's 3D model. They are linked to from the ONCC character class file.
-* these files are used by ONCC
+* TRBS files are stored globally in level0_Final.dat.
-* they contain 5 models differing in ("LOD") level of detail (triangle number)
+* They contain 5 different models with differing levels of detail (known as LODs). A common game development technique for improving performance is to display a reduced polygon-count version of a character when they're farther from the camera.
-===File structure===
+==File structure==
   TRBS
     |
@@ Line 30: / Line 28: @@
           +-- TRIA
+==Extraction (new method)==
-===Extraction (LOD)===
+This is more powerful method because it extracts the full range of models (all 5 LODs).
-This is more powerful method because it extracts the full range of models (LODs).
   onisplit -extract:xml ''output_folder input_folder''/TRBS''name''.oni
+==Extraction (old method)==
-===Extraction (no LOD)===
+This older extraction approach lets you choose between extracting only the TRBS or the ONCC file with TRBS. Note that this only extracts the model with the highest poly count.
-With the old extraction you can chose between a TRBS and an ONCC file. Note that this only extracts the model with the highest poly count.
   onisplit -extract:dae ''output_folder input_folder''/TRBS''name''.oni
   onisplit -extract:dae ''output_folder input_folder''/ONCC''name''.oni
+==Creation (new method)==
-===Creation (new)===
+This creates a TRBS file with up to 5 different LODs:
   onisplit -create ''output_folder input_folder''/TRBS''name''.xml
-* this creates a TRBS file with up to 5 different LOD.
+'''Example from TRBSkonoko_body_high.xml''' (extracted with OniSplit v0.9.68.0):
-'''Example'''
-TRBSkonoko_body_high.xml (extracted with onisplit v0.9.68.0)
   <?xml version="1.0" encoding="utf-8"?>
   <Oni>
@@ Line 64: / Line 55: @@
   </Oni>
+==Creation (old method)==
+This creates a TRBS file where all LODs use the same model; that's not good for memory usage or performance, but useful enough for testing a character in-game.
+ onisplit -create:trbs output_folder [-cel] [-normals] input_folder/TRBSname.dae
-===Creation (old)===
+(The arguments [[Importing_character_models#Cel-shading|"cel"]] and "normals" are optional.)
- onisplit -create:trbs output_folder [-cel] [-normals] input_folder/TRBSname.dae
-* this creates a TRBS file whereby the models have the same LOD; that's not so good for the memory but useful enough for testing a character ingame
-* the arguments [[Importing_character_models#Cel-shading|"cel"]] and "normals" are optional
-===Standard TRIA===
+==Standard TRIA hierarchy==
 [[File:XSI_ModTool_TRIA.png]]
+==Custom TRIA hierarchy==
+OniSplit creates the [[TRIA#Investigation|TRIA]] instance on its own. When extracting a TRBS with OniSplit v0.9.41.0, the TRIA instance is exposed. It can then be modified by hand to change the hierarchy of body parts.
-===Custom TRIA===
+In the table below, you can see two examples of a TRIA: one from Konoko and one from a more or less hypothetical [[Oni2:Hex Hound|Hex Hound]].
-Onisplit creates the [[TRIA#Investigation|TRIA]] instance on its own.
-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 [[#example|table]] you can see examples of TRIA instances: one from Konoko and one from a more or less hypothetical hex-hound.
-: 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.
+: OniSplit v0.9.58.0 and below need 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(?) tolerate unusual body part names but take the order ''seriously'' when building the hierarchy.
-A character with non-standard TRIA needs a complete set of new animations, those animations must be created based on that new TRIA.
+: 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 if the head was in a different location in the hierarchy, animations intended for the head 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. A character with non-standard TRIA needs a completely set of new animations based on that new TRIA.
 '''Changing the body part order'''
@@ Line 96: / Line 79: @@
 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].
-Taking this into account it should be possible to let Mod Tool generate a TRMA file fitting to TRBS.
+Taking this into account, it should be possible to let Mod Tool generate a TRMA file fitted to the TRBS.
 '''Example'''
 {| class="wikitable" width=100%
-| '''standard TRIA'''
+| '''Standard TRIA'''
-| '''hexhound TRIA'''
+| '''Hex Hound TRIA'''
 |-
 |
@@ Line 305: / Line 287: @@
      </Instance>
 |}
 {{XML}}

XML:TRBS: Difference between revisions

Revision as of 14:25, 30 March 2021

Contents

General information

File structure

Extraction (new method)

Extraction (old method)

Creation (new method)

Creation (old method)

Standard TRIA hierarchy

Custom TRIA hierarchy

Navigation menu

XML:TRBS: Difference between revisions

Revision as of 14:25, 30 March 2021

General information

File structure

Extraction (new method)

Extraction (old method)

Creation (new method)

Creation (old method)

Standard TRIA hierarchy

Custom TRIA hierarchy

Navigation menu

Search