Page Comparison

...

In HOOPS Exchange, flexible components are not fully supported. A flexible component can be loaded only in the state it was saved in Creo, and it depends on the data stored in the native file.

• 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 true a generic representation is loaded.

  • If the value is set to false , no representation is loaded. The component won’t be displayed.

...

• 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 true a 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.

...

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

...