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:
Table of Contents
|
Family tables (m_eFamilyTables):
A family table represents a component with a variable representation
...
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.
...
Creo import options used | Result |
|---|---|
  | |
A3DProEFamTabOrUseTessellationA3DProEFamTabAccelesratorFileOnly |    |
A3DProEFamTabOrUseWireAndGenericA3DProEFamTabAccelesratorFileOnly |  |
Flexible components (m_bFlexCompUseGenericIfNoTess):
...
If the tessellation of the flexible component is stored, it will be loaded by default
The tessellation is the representation of the flexible component in the state it was saved in Creo.
If no tessellation is available the setting m_bFlexCompUseGenericIfNoTess adapts HOOPS Exchange behavior:
If the value is set to
truea generic representation is loaded.If the value is set to
false, no representation is loaded. The component won’t be displayed.
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 |  |
Boolean operations (m_bBoolOpUseGenericIfNoTess):
...
For older versions, only the tessellation generated by Creo will be loaded if available
If no tessellation is available, the setting m_bBoolOpUseGenericIfNoTess adapts HOOPS Exchange behavior:
If the value is set to
truea generic representation is loaded.If the value is set to
false, no representation is loaded. The component won’t be displayed.
Note: if the Creo version used is too recent, or if the tessellation is stored in the file then m_bBoolOpUseGenericIfNoTess won’t have any effect.
Example
Situation | Result |
|---|---|
Model saved in Creo | %20-%20Creo%20Parametric.png?version=1&modificationDate=1665581338564&cacheVersion=1&api=v2) |
The tessellation is stored in the Creo file | %20-%20Creo%20Parametric.png?version=1&modificationDate=1665581364072&cacheVersion=1&api=v2) |
The tessellation is NOT stored in the Creo file m_bBoolOpUseGenericIfNoTess is |  |
The tessellation is NOT stored in the Creo file m_bBoolOpUseGenericIfNoTess is | |
Recommendations
When a model has a defect in HOOPS Exchange, we recommend to resave the file in Creo, and if possible in a more recent version of Creo.
We recommend trying to work as much as possible with models more recent than Creo 4 for the best results in HOOPS Exchange. If possible, resave the file in a recent version of Creo to upgrade the model.
...