Better support when importing FBX

Hi
I imported this FBX and i looked for capture region attributes.

1.I found out that touchdesigner can import up to only 10 ?
while houdini was able to import all of the attributes.
(78).
Houdini also keep the names attributes from the FBX.

  1. Maybe it will be better to attach the capture region attributes to the points and not the vertices ( also like in Houdini ).

  2. somehow Houdini was able to import the whole mesh with groups,
    but touchdesigner brake the mesh by materials.
    I find Houdini method more easy to edit the sop…

Attached FBX file
Attached BHclassic of the geometry that was extracted from same fbx file which imported to Houdini.

generally speaking -FBX import process could have more polish

Thank you
and keep up the great work

Barak.
from_houdini.rar (642 KB)


crossfit.fbx (17.3 MB)

Regarding your first point: in CC_Base_Body/splitGeoMat0/bonegroup there are 78 pCaptPath detail attributes that define the capture regions (along with pCaptData). Is this what you’re looking for?

Hi Eric !

Capture region define the intensity level the bone affect the point.
(as far as i understand)
There are 78 capture regions in that case.

Each point can contain 78 float attributes
or
contain two correlated arrays
one with values
the other the index of the capture region name ( look on the image attached )

that represent the weights values (0-1) of each capture region on the point.
(all sum to the value one)

From the data in the detail attributes i can only understand
that there are 78 capture regions and its names and maybe indexes .
the rest i`m not able to relate to anything .

viewtopic.php?f=27&t=12153

pCapt will contain the weight values for each point. pCapt is formatted so that it alternates between the bone index, and its weight on the point. For instance: (0, 0.25, 1, 0.5, 2, 0.25). Houdini has this information split up into two columns in the attached image: boneCapture_index and boneCapture_data.

Not every point will have all 10 values in the array filled in, 10 is just the maximum, meaning that at least one point has 5 bones that affect it.

You can map the bone indices given in pCapt to the names given in pCaptPath (pCaptPath names are in index order).

I hope this helps.

Eric

Hi Eric thank you very much
I was able to get good results.

I still not sure about the indexing correlation between the name of capture region
to the index number.

In the detail attribute i can see the correlation that start with the row index 1.
I can relay on that?

The bone indices are from 0-77 and will map directly to the index in the pCaptPath[78] array. The first index of pCaptPath should be 0, however in the SOP To DAT it will appear in row 1 because of the header.