Creo Reader
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.
Assembly
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
Family tables are supported, subject to the following conditions:
- 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.
- If the source file has a family table but was saved without the instance accelerator, the behavior of HOOPS Exchange depends on the A3DRWParamsProEData::bUseAcceleratorFilesOnly parameter. If this option is set to true, the entity will be marked as 'missing', will not be displayed, and a warning message will be written to the log file. If this option is false, the generic entity will be displayed.
Because HOOPS Exchange can represent the model more accurately with XPR/XAS files, we recommend you generate them every time you handle family tables. HOOPS Exchange cannot use family tables to modify the shape of a model.
The HOOPS Exchange Creo file reader has the following behaviors when loading a model with family tables:
- When loading a part or assembly: the generic instance is loaded and 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 Exchange.
- When loading an assembly containing subassemblies or parts with family tables, The accelerator files are loaded when they are available, regardless of the value of A3DRWParamsProEData::bUseAcceleratorFilesOnly.
- If the value of A3DRWParamsProEData::bUseAcceleratorFilesOnly is true, but the accelerator files are missing, no data is loaded and a warning is written to the log file.
- If the value of A3DRWParamsProEData::bUseAcceleratorFilesOnly is false, the graphic representation of the family table is loaded. If the family table is missing, the generic instance is loaded.
B-rep
HOOPS Exchange extracts the exact B-rep definition from the model. The list of surface types provided is:
- B-spline surface
- Cone
- Cylinder
- Cylindrical spline surface
- Fillet surface
- Plane
- Revolution surface
- Ruled surface
- Sphere
- Spline surface
- Swept surface
- Tabulated surface
- Torus
The list of available curve types is:
- B-spline
- Circle
- Ellipse
- Line
- Spline
- UV curve
Visualization
The visualization data for this format is generated by the HOOPS Exchange tessellation engine.
Views
There are two types of views supported in Creo:
- Views: A view plane in addition to visibilities that are applied to the PMI entities
- 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.
Both view types are fully supported by HOOPS Exchange.
PMI
HOOPS Exchange provides access to all PMI data available in Creo file. This list includes:
- Dimension (driven)
- Dimension (ordinate baseline)
- Dimension (ordinate driven)
- Dimension (ordinate reference)
- Dimension (reference)
- Geometric tolerance
- Note
- Set datum tag
- Surface finish
- Symbol
Miscellaneous
- A density value of -1 means that no density was set in the CAD file.