The Creo Reader provides full access to the assembly, B-rep, view, and PMI data stored within a particular Creo file. A file does not need to have a particular extension to be read correctly by HOOPS Exchange however the file extensions of Creo files that you can expect to be loaded by HOOPS Exchange are:
Our readers are updated to the latest released version within 90 days of the release of the authoring software. You can see the exact version supported in the current release here.
Incremental load is supported by our Creo reader. Datum planes and construction geometry are also supported and accessed through the assembly tree.
Family Table Support
The HOOPS Exchange Creo file reader has the following behaviors when loading a model with family tables:
If the source file was saved _with_ the instance accelerator, HOOPS Exchange will be able to load the file and the associated XPR/XAS files. The resulting model will look exactly the same as in Creo.
When loading a part or assembly, the generic instance is not loaded by default. Instead, only the tessellation is loaded (if found). A warning message is written in the log file mentioning the fact that this file contains a family table and that XPR/XAS files must be created from Creo to be displayed properly in HOOPS Exchange.
File reader options related to family tables are as follows: * FamilyTables = 0 -> Use only XPR/XAS for family tables. Nothing displayed if XPR/XAS is missing. No family table data is loaded and a warning is written to the log file. * FamilyTables = 1 -> Use tessellation if XPR/XAS is missing (this is the default behavior). The tessellation of the family table is loaded if found. Generics are not loaded by default anymore. * FamilyTables = 2 -> Use wire representation and generic if no tessellation and no XPR/XAS. This representation is the generic representation of the family table. It can be an incorrect representation compared to Creo.
Because HOOPS Exchange can represent the model more accurately with XPR/XAS files, we recommend you generate them every time you handle family tables.
Boolean Operation Support
BooleanOpUseGenericIfNoTess = A3D_FASE -> Tessellation is loaded if available, otherwise nothing is loaded.
BooleanOpUseGenericIfNoTess = A3D_TRUE -> Tessellation is loaded if available, otherwise the generic is loaded.
Flexible Component Support
The generic representation of the flexible component is not loaded anymore by default. * FlexibleCompUseGenericIfNoTess = A3D_FALSE -> Tessellation is loaded if available, otherwise nothing is loaded. * FlexibleCompUseGenericIfNoTess = A3D_TRUE -> Tessellation is loaded if available, otherwise the generic is loaded.
HOOPS Exchange extracts the exact B-rep definition from the model. The list of surface types provided is:
Cylindrical spline surface
The list of available curve types is: * B-spline * Circle * Ellipse * Line * Spline * UV curve
The visualization data for this format is generated by the HOOPS Exchange tessellation engine.
There are two types of views supported in Creo:
Views: A view plane in addition to visibilities that are applied to the PMI entities. Home views are also supported - this is a setting that allows you to create a view that is equivalent to the state in which the file has been saved.
Combined states: A full camera definition, visibilities applied to PMI, visibilities and transformations that can be applied to components in the assembly and the optional definition of section planes. Basic support is provided for simplified representations - this includes master representations, exclusions, and user-defined representations.
All view types are fully supported by HOOPS Exchange.
HOOPS Exchange provides access to all PMI data available in Creo file. This list includes:
Dimension (ordinate baseline)
Dimension (ordinate driven)
Dimension (ordinate reference)
Set datum tag
HOOPS Exchange also supports: * Persistent IDs * User-defined coordinate systems * Cosmetic geometry * User attributes attached to geometrical elements or part / assembly nodes * Entity names attached at all levels of the model (assemblies, parts, instances, faces, coordinate axes, etc.) * Cables at assembly level
A density value of -1 means that no density was set in the CAD file.
HOOPS Exchange cannot use family tables to modify the shape of a model.
Creo does not account for the “Hidden” attribute in an .ASM file, so parts marked as “Hidden” will not actually be hidden when imported into Exchange. In order to set a part as hidden, mark the representation of the instance as “exclude” in Creo.