It is possible to specify several ProE/Creo specific options (in A3DRWParamsProEData) while importing such CAD files with the HOOPS Exchange API, including the following ones:
Family tables (m_eFamilyTables):
...
A family table represents a component with a variable representation. For example a Screw can be be part of a family table: that means for the same component, Creo have a variety of representation where the Screw length and/or diameters changes.
A component from a family table always have a generic representation (i.e. the default model), but the designer will usually use an element with specific parameters.
This is what it looks like in Creo:
 |
 |
 |
 |
HOOPS Exchange support of Family Tables depends on what data are available in the native Creo file.
Depending on the model, the representation of the family table component can be:
Stored as a tessellated body.
Stored in a Creo accelerator files (.xpr, .xas), provided with the model files by the model designer. BRep may be available.
Not available (no tessellation, no accelerator file). In this case the generic representation is used by HOOPS Exchange to represent the component.
A family table import option impacts the behavior of HOOPS Exchange.
A3DProEFamTabAcceleratorFileOnly: Only use accelerator files. If none are available then no tessellation nor generic parts will be loaded.
A3DProEFamTabOrUseTessellation: Will try to use the accelerator files first when possible. otherwise will load the tessellation instead.
A3DProEFamTabOrUseWireAndGeneric: If no accelerator files nor tessellation are available, will use generic/wire representation.
| Info |
|---|
Further information regarding accelerator files and their generation from Creo software can be found on the official Creo documentation |
Example
Creo import options used | Result |
|---|---|
  | |
   | |
 |
Flexible components
In Creo, a flexible is a part that can has several states, with a variation of dimension, tolerances or material. For a example, a spring can be represented as a flexible component.
...
Note: if the tessellation is stored in the file, m_bFlexCompUseGenericIfNoTess won’t have any effect.
Example
Situation | Result |
|---|---|
Model saved in Creo |  |
The tessellation is stored in the Creo file |  |
The tessellation is NOT stored in the Creo file m_bFlexCompUseGenericIfNoTess is |  |
The tessellation is NOT stored in the Creo file m_bFlexCompUseGenericIfNoTess is |  |
...