Read ASE for XCAF output
Transfer ASE meshes into a XCAF workflow with the ASE reader and XCAF writer. This route carries polygonal geometry in the receiving document; it does not recreate the original CAD surfaces or feature history.
Read the ASE asset with the Assimp integration and inspect the supported mesh, material and scene-structure data. Select the objects intended for the output workflow.
Build and store an XCAF document
The Assimp integration provides mesh geometry, colors, materials and scene structure for its supported inputs. Pass that data to a separate OCCT or commercial writer. For STEP, STEP XML or DXF output, use the mesh-capable representation; this does not reconstruct BRep surfaces from polygons.
Place the imported geometry in an XCAF document and map the supported names, colors and structure to its labels. Use the native OCCT document storage appropriate to the selected XBF or XML delivery. Mesh data can remain mesh in the document; creating labels does not generate analytic CAD surfaces.
Check the XCAF result
Validate object transforms and available material references. Keep the authoring source for scene details not represented by the imported mesh and material mapping.
Reopen the document in the intended OCCT application and verify geometry, occurrence placements and mapped attributes. Keep application-specific additions distinct from source properties. XCAF storage is useful for continuing an OCCT workflow, but the recipient must support the chosen document format.
Discuss this conversion with the producing and receiving applications, representative files and required geometry and attributes. Compare the reader/writer catalog when a different representation is needed.